Google Voice Sporadic Call Failures, e.g. "503 Issue"
pqsteve:
I'm having a similar issue with GV - Current call drops, then when I try to reconnect, I get the "there is no service available" message. GV works from my laptop. My obi100 is ring no answer on incoming calls.
LeoKing:
Redialing the 2nd time, 3rd time, 4th time never worked for me if I used the memory dialing. After reading Joseph's post and doing what he said, I could dial out every time. Now the problem seemed to disappear so it's back to normal again.
Lavarock7:
Could GV be using Callcentric behind the scenes ::)
MikeHObi:
google voice is the cause of the 503 almost positively. If you get disconnected calls and stuff like that, go to your obi Status Page and check out the Uptime. I bet it's pretty low. That indicates the Obi has rebooted for no apparent reason. Normally it will have a code like (3) next to the time if it is a planned reboot.
Reboots are Obi problems, sometimes caused by services it connects to but still it should handle such issues better than spontaneously rebooting.
QBZappy:
Quote from: MikeHObi on October 25, 2012, 04:20:31 pm
Reboots are Obi problems, sometimes caused by services it connects to but still it should handle such issues better than spontaneously rebooting.
This may be the Achilles heel of the OBI. Whether it is still true, the PAP2 ata has a reputation for having echo issues. I hope that this problem doesn't get out from this forum. Sometimes these things are hard to shake off once people start talking about it. Until they fix the spontaneous reboots, mum's the word on this. OK folks!
Navigation
[0] Message Index
[#] Next page
[*] Previous page