Connect Failed: No Response on multiple Google Voice / Obi 508 Devices
wseltzer:
I changed the DNS setting on my router.
But, I suppose you can change the DNS settings on the OBi device instead.
fastoy:
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.
Thanks. I am using 8.8.8.8 as my DNS server in my router.
It fixed itself with time. Odd that Google's DNS didn't get updated when Google's Goovle Voice server was changed.
UPDATE: I got an e-mail from OBiTALK that SAID it was working but when I tested it I still can't make calls.
UPDATE 2: I changed the DNS on the OBi200 to 1.1.1.1 and 1.0.0.1 and rebooted. Working now. Fingers crossed.
BenE:
Quote from: wseltzer on December 08, 2018, 01:07:42 pm
I changed the DNS setting on my router.
But, I suppose you can change the DNS settings on the OBi device instead.
I have an ATT Gateway, which doesn't allow me to change the DNS. If anyone knows how to make the change on the OBI200, I'd appreciate it.
Chronoblast:
Changing the DNS server to 1.1.1.1 doesn't help in Dallas, Tx with Spectrum.
ping obihai.telephony.goog yields 64.9.241.172 no matter which DNS provider I go with
(Google - 8.8.8.8, Cloudflare - 1.1.1.1, Cisco/OpenDNS - 208.67.222.222).
curtisghall:
i changed dns setting on my router, didn't work
Navigation
[0] Message Index
[#] Next page
[*] Previous page