token error
GoogleObiONe:
ping: cannot resolve obihai.sip.google.com: Unknown host
GeeObi:
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
jccpa:
For the curious:
If you go to your voice.google.com account, under Legacy Google Voice, Phones, select your OBi device or phone.
Under 'Number' you will see a long code of letters and numbers, followed by '===@obihai.sip.google.com'
This means GV MUST connect to obihai.sip.google.com
That name does not resolve under DNS and cannot be contacted, at least not by name.
Although a few systems may still have had that name's IP address cached, those will be expiring as time goes on.
**If someone whose system still is cached and can give the IP address by pinging it, we might be able to add the domain to a hosts file or RIP table until the DNS is fixed. At this point I cannot yet confirm the server is still operational until someone provides the IP address.
These are troubleshooting techniques and temporary tests/workarounds. Nothing for a typical user to configure or do. Our collective hope is by providing info about the failure and the precise problem, that the right folks will get the info and perhaps speed up their corrective actions.
jccpa:
Quote from: GeeObi on June 13, 2021, 09:10:29 am
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
Can you ping that URL and give us the IP Address, it doesn't resolve via DNS, either
gsu13:
I've used GV and Obihai for 10 years (bought an early Obi100) and it has been very reliable up until this outage. In the first couple years, it had more issues, but that could have been due to slower internet speeds when 5 or 10 or 15 MBPS up/down were considered fast. I'm still hopeful this will all get resolved soon and let your family and friends know it has been great overall. Right now, I just make calls through my PC and browser or iPad and GV app.
FYI - my fathers Obi200 in CA is showing connected, but my mother-in-laws Obi200 in MD is showing "Connecting to 216.239.36.145;Token Error" even though configurations are very similar (dns 1.1.1.1. and 8.8.8.8.). My two Obi202s are also having the same token error
Quote from: DoctorWizard on June 13, 2021, 08:46:32 am
Just chiming in that as of 11:00 AM EDT in Florida, I still cannot get mine, my sisters, or either of my two friends OBi202's to connect. Many other people have said they got it working by manually setting DNS but that has not worked for me, nor has many hours of tinkering including resetting everything and starting over from scratch. I have a spare OBi202 and can't get it working either.
My DNS entries were already set to 1.1.1.1 (CloudFlare) and 8.8.8.8 (Google) but I went ahead and reversed the order and put the Google DNS first. Static IP, Gateway, Mask are all correctly set as well.
I did notice a couple of things no-one else has mentioned though. First, when you try to reconnect the OBi to Google, the Terms-of-Service you are supposed to agree to comes up blank. The 'Accept' button is there though, and apparently works for you to accept the invisible terms.
Second, I tried deleting/resetting everything as mentioned, including deleting the OBi device from my list of GV devices. After going thru the whole setup process over again from scratch, it has NOT re-added my OBi device to my GV device list, and I see no way to add it from the GV settings page.
And for what its worth, my ISP is AT&T fiber (but not using their DNS). I guess none of this is relevant though if the obihai.sip.google.com address won't resolve. Mostly I think I just wanted to vent 🤬 that it still is not working here. The other people I mentioned bought OBi devices upon my recommendation so this is making me look bad!
Navigation
[0] Message Index
[#] Next page
[*] Previous page