Connect Failed: No Response on multiple Google Voice / Obi 508 Devices
MARIN:
Quote from: wuench on December 08, 2018, 11:00:06 am
For those of you that are working, what IP address is it connected to?
My failed IP was also the 64.9.241.172, which is what googles 8.8.8.8 and 8.8.4.4 DNS are resolving to. Doing a dig via the internet a new IP comes up 216.239.36.144. It looks like this outage is the result of some DNS changes on the obihai.telephone.goog DNS name.
For those of you that are still having issues switching your DNS away from google's DNS may fix it. I switched my DNS server to cloudfare's 1.1.1.1 and it is now connected. Or you can wait for DNS to converge and it should correct on it's own....eventually.
Just tried this switch and its working fine now
DonaldD:
Quote from: Chronoblast on December 08, 2018, 04:00:52 pm
For me setting the DNS to 1.1.1.1 and flushing the DNS cache worked only intermittently - the proxy IP address kept going bad.
I fixed it on my 1022 phone by going to the local (built in to the phone) web interface (in my case typing 192.168.1.16 into my browser address field), then:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
6. Select Reboot at the top of the page
Thank you Chronoblast! What a great workaround. I use OpenDNS on my network so it is resolving wrong IP too. My Google Voice service came right up with the local DNS entry!
keithobri:
This worked for me as well on my Obi200. Just went to expert settings and followed the directions below:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
chriszing:
I am not expert user. Are you guys saying that the problem is with Google Voice DNS server? It has been fixed, however, the corrected address has not been propagated to all the home devices yet. That means, if I wait for another day or so, my Obi200 will work again. Do I understand correctly?
Chris
BenE:
Quote from: chriszing on December 08, 2018, 06:08:35 pm
I am not expert user. Are you guys saying that the problem is with Google Voice DNS server? It has been fixed, however, the corrected address has not been propagated to all the home devices yet. That means, if I wait for another day or so, my Obi200 will work again. Do I understand correctly?
Chris
What happened was the IP address assigned to the GV server url was changed, but that had not yet propagated to the various DNS servers, but eventually should. But yes, you should see the OBI200 working soon. Use the workaround only if you need it today.
Navigation
[0] Message Index
[#] Next page
[*] Previous page