Connect Failed: No Response on multiple Google Voice / Obi 508 Devices
cwmm:
I have 7 devices spread across 4 locations connected variously to 4 GV numbers. 3 Obi1022 devices lost their connections yesterday, same as others reporting, the others remain connected and working fine - to the same numbers. Other devices are an Obi1062 and 3 Obi200 devices remain connected to the numbers. The 3 1022 units with problems are connected to numbers that both the Obi1062 & 2 of the Obi200 units are connected to.
Obi1022 & Obi1062 units all on firmware 5.1.11
I'd speculate there is some regional problem with Obi or GV. Of course lots of possible causes for that. The units having problems are in Houston & connected to internet via AT&T. The others are in Michigan (Spectrum), Oklahoma (Suddenlink) & California (Comcast/Xfinity).
wuench:
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.
wseltzer:
SP1 Service Status
Status Connect Failed: No Response (server=64.9.241.172; retry in 139s)
drgeoff:
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?
That is not easy to answer as it just shows "Connected" with no mention of the IP address.
However, during a call it shows the peer RTP address as 74.125.39.42
cwmm:
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.
Great sleuthing to figure that out, thank you!
Navigation
[0] Message Index
[#] Next page
[*] Previous page