News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

The number you dialed was rejected by the service provider, reason is 503

Started by TAZVIKING, March 27, 2017, 06:51:32 PM

Previous topic - Next topic

TAZVIKING

I get this message when dialing "The number you dialed was rejected by the service provider, reason is 503".

There are no new updates on my dashboard.

I can also dial out using google hangouts on my cell phone and tablet, leading me to believe it's not GV.

I've reset the obi200 box and modem several times.

Has anyone else had this problem and what was the fix?

zoom38

I have a similar issue.  When calling out I get the same message.  Phone does not ring upon incoming calls but the computer rings in GVoice.  No solution yet.

TAZVIKING

Quote from: zoom38 on March 27, 2017, 06:53:53 PM
I have a similar issue.  When calling out I get the same message.  Phone does not ring upon incoming calls but the computer rings in GVoice.  No solution yet.

Let me know if you figure it out.

FormerYooper

Quote from: TAZVIKING on March 27, 2017, 06:51:32 PM
I get this message when dialing "The number you dialed was rejected by the service provider, reason is 503".

There are no new updates on my dashboard.

I can also dial out using google hangouts on my cell phone and tablet, leading me to believe it's not GV.

I've reset the obi200 box and modem several times.

Has anyone else had this problem and what was the fix?
Quote from: zoom38 on March 27, 2017, 06:53:53 PM
I have a similar issue.  When calling out I get the same message.  Phone does not ring upon incoming calls but the computer rings in GVoice.  No solution yet.


See these threads, folks.  This seems to be widespread ...

http://www.obitalk.com/forum/index.php?topic=12554.msg80745#msg80745

http://www.obitalk.com/forum/index.php?topic=12554.20

Moej


classpro

Same issue here.  Can't call out.  Reset several times.  How do we contact Obi?

SteveInWA

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.