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.

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.

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.

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

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.

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.