Google Voice Sporadic Call Failures, e.g. "503 Issue"
Alto2:
My experience is just like analogmonster's. Got my 110 last week, hooked it up, and never had a problem until Tuesday night. Then I started getting some outgoing calls that would ring once and then I'd get a fast busy, but the call went through via the website. I figured I should update my firmware after looking at the posts here, so I did that. Now I get the 503 error, but the call goes through just fine when dialed via the Web. Whatever was done to fix the problem doesn't seem to have been enough!
sm69th:
Add me to the the list...since last night my incoming calls are no longer reaching my Obi. I also just tried placing a call and got the 503 error.
Hope they get this fixed SOON or I will have to find another provider instead of GV...
a140:
I think I found one of the reasons for this error.
Today when I tried to dial into my conference call - I got 503 error. I tried from OBIon on my iPhone and then with handset connected directly to OBI appliance.
Suspecting it was OBI issue, I tried calling from Talkatone app (also configured with google voice) and finally directly from google voice app.
The call failed every time with google voice saying - "This is not a valid number".
Finally, I called the number from my cell and was able to get through.
Final Take - THIS IS GOOGLE VOICE issue (at least for this case).
The real problem is that services like freeconferencecall use high connection fee numbers to make money and GV, being free doesn't want that surcharge. It could also be that these numbers are virtual, unregistered, voip numbers not recognizable by GV.
Read more about it here - http://groups.google.com/a/googleproductforums.com/forum/#!topic/voice/glPvnNQnpB8
userobi110:
Here is the GV log from inside gmail.com. obi110 was powered off. (408) xxx-xxxx is the same number. When called from cell phone to this number - it always work.
Sorry! The phone call with (408) xxx-xxxx failed because of a problem
with our servers at 6:01 PM. Please wait a bit and try again.
Thank you!
(Error ID: f243822d993cf3af)
At 6:01 PM (408) xxx-xxxx was not available for a phone call.
Sorry! The phone call with (408) xxx-xxxx failed because of a problem
with our servers at 6:02 PM. Please wait a bit and try again.
Thank you!
(Error ID: cf5437d0298c5bef)
Sorry! The phone call with (408) xxx-xxxx failed because of a problem
with our servers at 6:02 PM. Please wait a bit and try again.
Thank you!
(Error ID: d9d3104b58a5ca68)
Sorry! The phone call with (408) xxx-xxxx failed because of a problem
with our servers at 6:02 PM. Please wait a bit and try again.
Thank you!
(Error ID: 872111814d33d386)
Is it time to forget about GV and move to other provider?
z15f:
Ya, I have noticed this issue since the last 2 or 3 days too. It seems that rebooting the OBI110 device fixes this for a few hours, but then the problem returns.
Navigation
[0] Message Index
[#] Next page
[*] Previous page