Outgoing Google Voice calls give Rejected notification 503
Almighty1:
Quote from: zorlac on March 27, 2017, 06:43:37 pm
Quote from: Almighty1 on March 27, 2017, 06:42:09 pm
@zorlac - still broken here with the same error message. Did you do anything like rebooting?
Nope, it's just a computerized miracle. ;D
Lucky you, I rebooted and still the same error message from the handset.
zorlac:
Broke again. :P
SteveInWA:
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.
zorlac:
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 #.
Almighty1:
Quote from: zorlac on March 27, 2017, 07:03:54 pm
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 #.
In my case, SP1 which is a AT&T landline ported to Google Project Fi (March 2016) and then GV from Project Fi did not have the problem.
SP2 which is a GV native number from 2009 or earlier that GV got from Level 3 number which is the one with problems.
You can check who owns the number by putting the Area code plus the first 3 digits and look at the carrier section at the bottom using this URL:
http://www.npanxxsource.com/npa-nxx-databases.htm
Navigation
[0] Message Index
[#] Next page
[*] Previous page