December 13, 2017, 02:36:55 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: 1 [2] 3
  Print  
Author Topic: Outgoing Google Voice calls give Rejected notification 503  (Read 16446 times)
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3953



« Reply #20 on: March 27, 2017, 07:11:49 pm »

The fact that your OBi displays a status of "Connected" for the SPx in question means, that the OBi has successfully accessed, and is now accessing, the Google Chat/XMPP service on the Google account that you previously authorized it to use.

The error code indicates a problem further along in the call process, such that the server isn't responding.  It's a Google issue.  We've reported it to Google, but we have no further information at this time.  Typically, their automated system monitoring will detect this and alert their support personnel, who will investigate and fix the problem.

Bottom line, "Do not adjust your set".  Just wait.
Seems strange since both GV#'s are in the same exchange just different slots on the obi.
The affected # still forks incoming calls to a cell & rings the GV dinger on computer account too, just our obi doesn't ring the pots phone on that #.

Incoming and outgoing calls use a different path.  The outbound calling failure is somewhere on the Google side, that acts as the XMPP server.  It's either not responding (hung or dead), or sending back something invalid.  This is different than the inbound call path, whereby Google's carrier partner and/or Google directly receive an inbound telephone call, and then Google Voice forwards that call over the phone network to your forwarding number(s), and to Chat/OBi.
Logged

zoom38
Newbie
*
Posts: 7


« Reply #21 on: March 27, 2017, 07:37:49 pm »

I get the same "The number you dialed, xxx-xxx-xxxx, was rejected by the service provider.  Reason is 503." message when making calls thru my OBI100.  Just started today.  Hope someone comes up with a fix soon.
Logged
TAZVIKING
Newbie
*
Posts: 5


« Reply #22 on: March 27, 2017, 08:10:38 pm »

I'm getting the same 503 code, are there any reasons why yet?
Logged
Almighty1
Jr. Member
**
Posts: 28


« Reply #23 on: March 27, 2017, 08:28:04 pm »

Works again for me.
« Last Edit: March 27, 2017, 08:31:37 pm by Almighty1 » Logged
Almighty1
Jr. Member
**
Posts: 28


« Reply #24 on: March 27, 2017, 08:34:33 pm »

Spoke too soon, problem is back!
Logged
restamp
Full Member
***
Posts: 193


« Reply #25 on: March 27, 2017, 08:34:50 pm »

FWIW, this is probably not the best resource, but I've used it more than once for decoding errors that go along with those undesirable SIT tones:

http://blog.onvoy.com/connections/21-common-voip-error-codes
Logged
Almighty1
Jr. Member
**
Posts: 28


« Reply #26 on: March 27, 2017, 08:46:02 pm »

FWIW, this is probably not the best resource, but I've used it more than once for decoding errors that go along with those undesirable SIT tones:

http://blog.onvoy.com/connections/21-common-voip-error-codes

This is a more complete list, sounds like HTTP error codes...

https://en.wikipedia.org/wiki/List_of_SIP_response_codes
Logged
dwhitejazz
Jr. Member
**
Posts: 31


« Reply #27 on: March 27, 2017, 08:52:07 pm »

For what's it worth my Obi202 stopped working yesterday as well.  Status is "Connected" but outgoing calls have the "503 error" and incoming calls do not ring.

Dave White
Logged
restamp
Full Member
***
Posts: 193


« Reply #28 on: March 27, 2017, 10:31:00 pm »

@Almighty1:  Thanks for the Wikipedia cite.

Most of my GV numbers seem to be working fine tonight.  Interestingly, the one exception is a number that I access through the Simonics Google Voice Gateway.  It shows as registered, but I get a busy signal or 503 error whenever I try to call out, and it rings to GV voicemail when I try to dial in.

Guess I'll check it tomorrow and see if anything has changed.
Logged
zorlac
Full Member
***
Posts: 203



« Reply #29 on: March 28, 2017, 04:16:13 am »

Same thing this morning,  Cry
Logged
Inet
Newbie
*
Posts: 3


« Reply #30 on: March 28, 2017, 05:05:22 am »

Should have read the forum before trying everything else I could think of...  Smiley

Who is the problem with, OBI or GV?
Logged
Almighty1
Jr. Member
**
Posts: 28


« Reply #31 on: March 28, 2017, 07:00:21 am »

Should have read the forum before trying everything else I could think of...  Smiley

Who is the problem with, OBI or GV?

It could be one or a combination of both.  I wanted to ask, is the female voice with the error message actually provided by Obi or is it GV?
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 2713


« Reply #32 on: March 28, 2017, 07:07:15 am »

GV calls from your Obi don't use any Obihai server or Obihai run facilities. Unless:

1. Obihai has forced an update to your device in the last day or so

or

2.  There is some bug in Obihai's firmware which has been exposed by the time/date

this one would appear to be down to GV.
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 2713


« Reply #33 on: March 28, 2017, 07:13:11 am »

Should have read the forum before trying everything else I could think of...  Smiley

Who is the problem with, OBI or GV?

It could be one or a combination of both.  I wanted to ask, is the female voice with the error message actually provided by Obi or is it GV?
The verbal message is generated by your OBi as a result of it receiving the 503 from somewhere. GV does not use SIP so don't interpret the 503 as being a SIP error code or it being initiated by GV.
Logged
moby
Newbie
*
Posts: 1


« Reply #34 on: March 28, 2017, 07:58:15 am »

I have an Obi100 and an Obi202 on the same network. The 100 is giving me the "call rejected by the service provider" error but the 202 works fine.

Maybe I should upgraded a while back Huh
Logged
mikepanic
Newbie
*
Posts: 6


« Reply #35 on: March 28, 2017, 08:13:50 am »

I have an Obi100 and an Obi202 on the same network. The 100 is giving me the "call rejected by the service provider" error but the 202 works fine.

Maybe I should upgraded a while back Huh

I had been using an OBi100 and it was great, a few weeks ago there was a promo on the OBi200 and I bought one since the 100 was end of life.  Last night the error started, I figured it was time to swap them out.  Both boxes give the same error. It's not a hardware issue I'm afraid.
Logged
mikepanic
Newbie
*
Posts: 6


« Reply #36 on: March 28, 2017, 08:16:30 am »

11:15AM EST, my OBi200 box is working again. 
Logged
Almighty1
Jr. Member
**
Posts: 28


« Reply #37 on: March 28, 2017, 08:25:46 am »

As of 8:23AM PDT/11:23AM EDT - it is working again! 
Logged
hapollo
Jr. Member
**
Posts: 51


« Reply #38 on: March 28, 2017, 09:22:11 am »

Incoming forked calls still not ringing. Since my incoming is forked to Callcentric for CNAM, I simply went to GV Dashboard and checkboxed Google Talk and phone rings but still no ring of forked calls to other carriers. At least something rings now.
« Last Edit: March 28, 2017, 09:42:06 am by hapollo » Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3953



« Reply #39 on: March 28, 2017, 12:15:58 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.
Logged

Pages: 1 [2] 3
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC