My OBi200 was working just fine all day until a few minutes ago. I cannot receive incoming calls. When I try to dial out I get a message stating "The number you dialed XXXXX was rejected by the provider reason 503. This issue is only occurring on SP1, which is a Google Voice number. I can dial out & receive calls on Sp2, Sp3 and Sp4 (Sp2 & Sp3 are Google Voice numbers & Sp4 is Callcentric). I went into the Obitalk dashboard and deleted my Sp1 and reconfigured it. Still no dice. The Google Voice number associated with Sp1 is working because I can take calls through Hangouts on my tablet. Any ideas as what I might do to remedy this issue? You are all so helpful & knowledgeable on this forum.
I'm also experiencing the same issue with the rejection error 503. Must be some issue with OBi because I can make phone calls via Google Hangout.
Just started getting the same error for GV line
Quote from: Chan168 on March 27, 2017, 04:20:42 PM
I'm also experiencing the same issue with the rejection error 503. Must be some issue with OBi because I can make phone calls via Google Hangout.
I am able to make & receive calls on Sp2, Sp3 & Sp4 though just fine. So, it can't be an OBi problem.
Did you setup the same account you had on sp1? I am having trouble with outgoing calls and it just started couple of hours ago.
Quote from: FormerYooper on March 27, 2017, 04:01:12 PM
My OBi200 was working just fine all day until a few minutes ago. This issue is only occurring on SP1 (http://www.obitalk.com/forum/index.php?topic=12554.msg80745#msg80745), which is a Google Voice number. I can dial out & receive calls on Sp2, Sp3 and Sp4 (Sp2 & Sp3 are Google Voice numbers & Sp4 is Callcentric).
My gut feeling is that this is an obi thing, not GV, since my affected GV# still forks incoming calls to a cell # OK and rings the computer's GV account ok too.
Add me to list with the same issue
I'm having the problem today too. I have an Obi 200 and an Obi 100 on the same LAN segment (different buildings). Neither can call out, "Reason 503". Haven't tried incoming yet...
My Obi dashboard shows everything green and properly connected.
If others are having the same problem I won't start blindly reconfiguring everything under the assumption that my equipment or account has been glitched.
Looking forward to reports back from others if anything is discovered...
Quote from: zorlac on March 27, 2017, 06:00:26 PM
Quote from: FormerYooper on March 27, 2017, 04:01:12 PM
My OBi200 was working just fine all day until a few minutes ago. This issue is only occurring on SP1 (http://www.obitalk.com/forum/index.php?topic=12554.msg80745#msg80745), which is a Google Voice number. I can dial out & receive calls on Sp2, Sp3 and Sp4 (Sp2 & Sp3 are Google Voice numbers & Sp4 is Callcentric).
My gut feeling is that this is an obi thing, not GV, since my affected GV# still forks incoming calls to a cell # OK and rings the computer's GV account ok too.
Thanks much for the link to the other thread. We'll just have to wait & see if OBi fixes this issue.
This problem existed at least 3 hours ago for me, when I tried to place a call.
But just now I just tried an incoming call and it worked. Tried an outgoing call and it worked also.
So at the moment things are back to normal. I'll keep testing periodically to see if it is intermittent or fully fixed.
Good news, anyway...
Quote from: Nrupalp on March 27, 2017, 05:43:34 PM
Did you setup the same account you had on sp1? I am having trouble with outgoing calls and it just started couple of hours ago.
Yes, I set up the same account. There are quite a few others with the same problem. Look at this thread ...
http://www.obitalk.com/forum/index.php?topic=12554.msg80745#msg80745 (http://www.obitalk.com/forum/index.php?topic=12554.msg80745#msg80745)
Quote from: rufusputnam on March 27, 2017, 06:33:31 PM
This problem existed at least 3 hours ago for me, when I tried to place a call.
But just now I just tried an incoming call and it worked. Tried an outgoing call and it worked also.
So at the moment things are back to normal. I'll keep testing periodically to see if it is intermittent or fully fixed.
Good news, anyway...
Still not working for me ... :'(
Seems fixed now.
Broke again. :P
Yup, worked for a bit then broke again. Intermittent at this point.
Same problem here, doesn't work.
Same issue today (i.e. The number you dialed was rejected by the service provider, reason 503).
I visited https://www.obitalk.com/obinet/pg/obhdev, observed that firmware needed to be upgraded, and let it to be upgraded (Successfully upgraded xxxxxx's firmware to 3.1.1 (Build: 5463EX).). After that, OBi resumed normal work. Issue solved for now, I will monitor for re-occurrence.
Issue just like OPs started 4 hrs ago seems resolved on my Obi200. Problem now seems to have migrated to Obi110 at family member's house. agree that it appears more like a an Obi issue than GV issue
Issue resolved briefly, but has returned. Just a wait & see situation & be patient for a fix either from OBi or Google.
Add me to the list, GV on my Obi100 (1.3.0.2886 fw) has been out of service most of the day. I hope this isn't something that requires a fw upgrade and kills the unsupported devices.
I don't have the problem on my Obi200, but do get that "Error 503" on all calls from my Obi110 (and it does not ring on incoming calls).
I have the same exact problem now and I have obi 202.
Same thing this morning, :'(
Mine still isnt working and i have the Obi200. Incoming is ok, outgoing isnt working. I checked for firmware update and none available. I signed up for the service 2 weeks ago, not a good start. Anyone want to chime in what I can try to get this resolved?
Same issue with our Obi200. It started sometime yesterday. I followed the troubleshooting suggestions: reboot, download updated firmware, opened routers DMZ for the Obi, etc. Nothing has helped. I opened a support ticket last night, but so far no response, and it's still not working this morning.
Mine is doing this too. Firmware level is the same as what is available, so that can't be it. Anyone have any clues as to what the heck is causing this? We can't ALL be having user side issues, this would have to be something either GV related or Obi related. So, who's gonna take responsibility and offer some solutions Obi????
I noticed the same this morning. Incoming calls not working at all. Outgoing give 503 error. Updating firmware right now to see if it helps.
It works again somehow.
Google found and fixed the issue. Again, this was not a problem with OBi devices nor with their configuration; it was an issue on the Google end.
Quote from: SteveInWA on March 28, 2017, 12:14:34 PM
Google found and fixed the issue. Again, this was not a problem with OBi devices nor with their configuration; it was an issue on the Google end.
SteveInWA ... appreciate your getting back & posting that the issue was on Google's end. Your follow-up, as always, is superb!
Quote from: FormerYooper on March 28, 2017, 01:32:11 PM
Quote from: SteveInWA on March 28, 2017, 12:14:34 PM
Google found and fixed the issue. Again, this was not a problem with OBi devices nor with their configuration; it was an issue on the Google end.
SteveInWA ... appreciate your getting back & posting that the issue was on Google's end. Your follow-up, as always, is superb!
Thanks for the feedback!
BTW, for years, I thought your username referred to being a former Yahoo employee, until I did a Google search on "Yooper"!
Quote from: FormerYooper on March 28, 2017, 01:32:11 PM
Quote from: SteveInWA on March 28, 2017, 12:14:34 PM
Google found and fixed the issue. Again, this was not a problem with OBi devices nor with their configuration; it was an issue on the Google end.
SteveInWA ... appreciate your getting back & posting that the issue was on Google's end. Your follow-up, as always, is superb!
Yes, thanks much. Gives final resolution to an issue that seemed somewhat intermittent and arbitrary.