News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Google Voice Status Connect Failed: No Response

Started by DonObi, December 08, 2018, 12:01:25 PM

Previous topic - Next topic

DonObi

After using my OBi200 for a couple of years, it has suddenly stopped making or receiving phone calls.  On the device information page it shows a status of "Connect Failed: No Response".  I have done the following multiple times and it doesn't help.

Delete Device
Factory Reset Device (both with ***8 & with the button on the bottom.
Deleted app permissions from my google account.
Added the device again.
Set up Google voice again.
Added the device IP address to my router's DMZ list.

Every time I try, I get the same error.

What else can I do to get it working again?

differential

Am getting the same "Connect Failed: No Response" error on my OBi200. This particular OBi device is only one year old. Been using OBi devices with Google Voice for years and never had this happen before. Am wondering if the problem is Google.

keithobri

Check this out.  http://www.obitalk.com/forum/index.php?topic=15391.0  Seems like it happened to quite a few devices.  Possibly a DNS workaround. 

DonObi

I tried the 1.1.1.1/1.0.0.1 DNS servers and I get the same error.

DonObi

I waited a while and now it is up again using the cloudfire DNS.

doctor34

Quote from: keithobri on December 08, 2018, 12:37:54 PM
Check this out.  http://www.obitalk.com/forum/index.php?topic=15391.0  Seems like it happened to quite a few devices.  Possibly a DNS workaround. 

Thanks for that link...  Hard to find on a search!  :)

The DNS change to one that updates more often (1.1.1.1) is a fix for me!

Damn AT&T doesn't update their DNS server too often, so it may take 24 hours for the new IP address of the GV server to show on my router otherwise!!!

DonObi

Quote from: keithobri on December 08, 2018, 12:37:54 PM
Check this out.  http://www.obitalk.com/forum/index.php?topic=15391.0  Seems like it happened to quite a few devices.  Possibly a DNS workaround. 

Thank you very much for chiming in.  I was getting nowhere with my searching.