GV on Obi 1062 unreliable
SteveInWA:
Just as a point of comparison, I've got 2 OBi 1022s, an OBi 1032, an OBi 2182, and each is connected to three different Google accounts, and none of them have dropped the connection in a long time (not this year, anyhow). All three accounts are enrolled in the VoIP beta.
billsimon:
Any idea on the significance of the 404 response? What would "not found" mean with respect to a SIP registration -- especially one that just worked within the last hour? It's funny that both accounts on the phone would get the same response from Google. I also have a SIP account with another provider on this phone, and it stays active when the GV accounts go away. So this is not a general network disruption.
SteveInWA:
Beats me, since 404 is about as ambiguous as error 500. As you know, it's just saying "I tried to connect to this address, and it didn't respond back". I think that is a symptom/byproduct of whatever your OBi is trying to reach at that point being the wrong destination.
I'm still wondering why it reports that particular (wrong) IP address in the failure. I wonder if it's a DNS issue? You said that your non-GV SIP Service Provider still works. Does the OBiTALK dashboard show the device as "Offline", or does it just show the two GV SPs as not connected? You could try going into expert mode and setting the DNS servers to Google's DNS, at 8.8.8.8 / 8.8.4.4, or the Quad9 DNS at 9.9.9.9 (https://www.quad9.net/). Note that there are two different places to set DNS in OBi Expert, depending on whether you are using Ethernet or WiFi.
I know you're an expert, but assuming nothing, did you try power-cycling your router to clear out its cache?
What makes troubleshooting problems with Google Voice unique, is that, since there are so many users, if something is actually failing on Google's side, we quickly see many, many reports of the same error on the GV forum. Nobody is reporting the error you're getting.
I have a couple of test GV accounts that I know work, since they're currently active on my OBi phones. If you'd like to rule out an account-related issue, PM me and I'd be happy to let you borrow one of the accounts.
A_Friend:
Quote from: billsimon on August 18, 2018, 04:09:40 pm
My Obi 1062 with two Google Voice accounts has recently become unreliable. Firmware is 5.1.11, 4858EX.1311. Every day for the past four days, at some point in the day, the line keys turn orange and the service is unavailable. Status shows "Connect Failed: 404 Not Found (server=64.9.243.108". The only solution is a reboot of the phone.
My hunch is that this is a problem with Google Voice and not the phone itself, but I don't know.
It might not be a primary problem with GV itself. When this happens, see if you can see any signs on your cable modem indicating how long it's been up. Your cable provider might be doing work on the system during what are normally slack times for most of their users. Maybe an interruption is bouncing GV offline.
I've seen this in the past, where GV drops and others stay up on the same device (in other words, survive a brief interruption of internet), but that was back when GV was on XMPP. It might be possible that GV registration connections, even on SIP, are more fragile than those of say, a Callcentric or Voip.ms. As for what's going on with it when the cable modem came back online, you'd probably need a sniffer to figure that one out. I can't imagine why it wouldn't simply reregister to the right server.
Another approach is call your cable company and ask them if they're doing work that would briefly interrupt your connection, and when they'll be done. If that's the cause, you won't need to do anything except wait and see if the problem goes away.
By the way, if this is what's happening, the long term solution is a firmware mod by Obihai to better deal with loss of GV registration.
billsimon:
I'm using Cisco OpenDNS for my network. The IP address is what I get when I look up obihai.telephony.goog proxy:
Name: obihai.telephony.goog
Address: 64.9.243.108
If this keeps up I might try switching at least the phone over to the 8.8.8.8 resolver as you've suggested.
404 seems to be, to the phone, a fatal error, where it doesn't retry. I have let it sit in the failed state for a few hours thinking that it might re-register eventually, but it doesn't seem to try again. Yet when I reboot it comes up right away. If that's so, then I agree with A_Friend that the firmware should handle this error better. Still, I'd like to know why I'm getting it, and others apparently are not.
Navigation
[0] Message Index
[#] Next page
[*] Previous page