Google Voice Sporadic Call Failures, e.g. "503 Issue"
RFord:
I think what OBiSupport is saying is that if there are problems with Google Voice itself or from the GV end, you will experience the issue you are having. If you check the GV Help Forum you will see that a number of GV users who are NOT using the OBi ATA is experiencing just the problem you are having. This is outside the control of OBi and nothing they can do to correct the issue. In other words, the issue is unrelated to the Firmware upgrade and just happen to coincide with it!
Quote from: S--F on February 08, 2012, 03:02:10 am
Quote from: OBiSupport on February 07, 2012, 11:56:38 pm
When the OBi announcement makes the "Service Unavailable" 503 message is is is not an issue with your OBi device's operation. The OBi is simply providing some additional context as to why the particular call cannot be completed by the service provider (we feel this is a bit better than returning a generic busy signal or other special information tone).
That said, we are studying this particular issue. As well, please look to the GV Help Forum for more information.
The 503 error may indicate service being unavailable temporarily on the Google Voice connection. And yes, a redial of the same number might make the call go through.
Well I'm not getting a 503 error. The phone isn't ringing. Any input on that?
S--F:
Well then this is a pretty big coincidence, and I'm not sure I believe it.
BillS:
I have the OBI110 up and running fine with GV. I am getting ready to port my Landline (with AT&T) to a AT&T Go Phone and then port to GV. I have read that many have done this. I chatted with AT&T to confirm it could be done and they said yes.
Just checking to see if anyone has had any issues doing this lately.
Thanks much
Dale:
Setup: GV configured on Obi box and generally working fine.
We have seen a few instances of the following:
Nobody using the phone.
No known internet connectivity issues.
Obi box online
Google Voice (on my machine where I am logged into my Google account) goes 'ping' and indicates that an inbound call has just been missed.
No inbound call is shown on the Obibox log.
If I call the same GV number from another phone (Eg Bobsled) the phone rings as usual for the inbound test call. If we call out to the number that just called us (the so-called missed call) it connects perfectly.
Last night this happened twice (from the same caller), a cell phone from area code 614.
Since there is nothing in the Obi log I suspect the problem is external to our home network - either in Google or in the ObiHai network.
Has anyone else seen this?
jimates:
This just happened to me twice. Once about 30 min ago and once while I was typing this. Both times when my wife called from her cell. Another call came in about 10 min ago that rang all the phones as normal.
this has happened before but very very rare, I think perhaps less than 5 times in many months.
I am sure it is a google problem. I called my cell phone from my GV page using the google talk phone and my Obi rings fine.
Remember also, you can't have your gmail open in a browser or have Groove IP or Talkatone active on a cell phone. If you do the Obi will not be logged into the corresponding Google Voice account.
Navigation
[0] Message Index
[#] Next page
[*] Previous page