Outgoing Google Voice calls give Rejected notification 503
SteveInWA:
Quote from: zorlac on March 27, 2017, 07:03:54 pm
Quote from: SteveInWA on March 27, 2017, 06:55:08 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.
zoom38:
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.
TAZVIKING:
I'm getting the same 503 code, are there any reasons why yet?
Almighty1:
Works again for me.
Almighty1:
Spoke too soon, problem is back!
Navigation
[0] Message Index
[#] Next page
[*] Previous page