December 10, 2018, 12:03:14 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: 1 2 [3]
  Print  
Author Topic: Connect Failed: No Response on multiple Google Voice / Obi 508 Devices  (Read 2566 times)
MARIN
Newbie
*
Posts: 1


« Reply #40 on: December 08, 2018, 05:06:04 pm »

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
Logged
DonaldD
Newbie
*
Posts: 2


« Reply #41 on: December 08, 2018, 05:17:41 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! 
Logged
keithobri
Newbie
*
Posts: 7


« Reply #42 on: December 08, 2018, 05:44:59 pm »

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
Logged
chriszing
Newbie
*
Posts: 1


« Reply #43 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
Logged
BenE
Newbie
*
Posts: 6


« Reply #44 on: December 08, 2018, 06:21: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.
Logged
KMac
Newbie
*
Posts: 1


« Reply #45 on: December 08, 2018, 08:40:15 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
 

Thanks Chronoblast, this fixed my Obi202 that wouldn't work using 1.1.1.1 or others.  I logged into the webpage for the Obi and set the local DNS entry there, rebooted and all was fixed.  I'll just have to remove the entry when the issue is resolved.
Logged
Chronoblast
Newbie
*
Posts: 6


« Reply #46 on: December 08, 2018, 08:45:00 pm »

SteveInWA said: "Do not follow this advice.  Never hard-code server IP addresses;"

@SteveInWA - I totally agree. It is foolish and reckless. Only do it if you want your phone to work.
Then set a reminder to erase this entry after a few days.
« Last Edit: Today at 06:26:15 am by Chronoblast » Logged
dcortez
Newbie
*
Posts: 3


« Reply #47 on: December 08, 2018, 09:03:28 pm »

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

thanks for the tip; unfortunately for me, i cannot make any changes to the DNS settings.
Logged
Psen
Newbie
*
Posts: 2


« Reply #48 on: December 08, 2018, 09:33:34 pm »

Thanks to whoever posted itís a DNS issue. Iíve google mesh router and itís default DNS is 8.8.8.8 and I was getting the connect failed error.
But the moment I switched the router to use Spectrumís DNS, both my google voice accounts connected immediately.
Logged
DG3CA
Newbie
*
Posts: 5


« Reply #49 on: December 09, 2018, 03:42:00 am »

thanks for the tip; unfortunately for me, i cannot make any changes to the DNS settings.
[/quote]

Same here. My AT&T U-Verse/Pace unit doesn't allow manual DNS settings.
Logged
MiKo
Newbie
*
Posts: 3


« Reply #50 on: December 09, 2018, 06:35:49 am »

thanks for the tip; unfortunately for me, i cannot make any changes to the DNS settings.
Same here. My AT&T U-Verse/Pace unit doesn't allow manual DNS settings.
The settings are being changed on the obihai not the router.  I also have AT&T , the changes are to the obihai by logging in to the obihai's IP using admin/admin as the user and password then follow chromblast steps here: http://www.obitalk.com/forum/index.php?topic=15391.msg96475#msg96475
« Last Edit: December 09, 2018, 06:39:53 am by MiKo » Logged
MargaretI
Newbie
*
Posts: 2


« Reply #51 on: December 09, 2018, 08:30:41 am »

Same thing has happened to me. I seem to have the same issue since yesterday. I am using the 202 device. Please let us know what the fix is. I an using OpenDNS and I an still getting this message. I will try Cloudflare to see if this fixes the issue.
Logged
dcortez
Newbie
*
Posts: 3


« Reply #52 on: December 09, 2018, 08:52:40 am »

Quote
The settings are being changed on the obihai not the router.  I also have AT&T , the changes are to the obihai by logging in to the obihai's IP using admin/admin as the user and password then follow chromblast steps here: http://www.obitalk.com/forum/index.php?topic=15391.msg96475#msg96475
i re-read the post (from the link above), made the change and GV is working for me now.  my miss was not logging "directly onto the obitalk device" using the IP address assigned by my router.  Smiley
Logged
torchredraider
Newbie
*
Posts: 3


« Reply #53 on: December 09, 2018, 08:53:28 am »

UPDATE: Device Offline Again
OBI202 device is offline again due to the DNS record changed at 9:00am CT 12/9/2018
for
  • obihai.telephony.goog
changed back to
  • 64.9.241.172
Note: this is the configuration that is now *not working* for an unknown reason as of 12/7/2018.

1. Using Expert Configuration https://www.obitalk.com/obinet/pg/obhdev
Select Service Providers > ITSP Profile A SIP > Outbound Proxy
Uncheck both OBITalk Settings and Device Default

2. Replace
  • obihai.telephony.goog
with
  • c.telephony.goog

3. Click the Submit button

Repeat for ITSP Profile B SIP, ITSP Profile C SIP, ITSP Profile D SIP as needed for your environment.
To revert, swap c.telephony.goog with obihai.telephony.goog in step 2 and recheck both OBITalk Settings and Device Default
Logged
MargaretI
Newbie
*
Posts: 2


« Reply #54 on: December 09, 2018, 10:41:14 am »

This is what worked for me. I switched to Cloud Flare and after doing the fix below, I rebooted the phone by using the phone menu (*** option 9).

Finally!!! Thanks to all who worked on this. I have been down for three days!!!

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

Logged
NotThat_JHud
Newbie
*
Posts: 2


« Reply #55 on: December 09, 2018, 10:55:52 am »

Same problem here. I deleted the obi device out of my google voice, and now it won't reconnect. Have gone through the reset and re-add steps numerous times. What do I do?
Logged
JimM313
Newbie
*
Posts: 1


« Reply #56 on: December 09, 2018, 03:39:47 pm »

UPDATE: Device Offline Again
OBI202 device is offline again due to the DNS record changed at 9:00am CT 12/9/2018
for
  • obihai.telephony.goog
changed back to
  • 64.9.241.172
Note: this is the configuration that is now *not working* for an unknown reason as of 12/7/2018.

1. Using Expert Configuration https://www.obitalk.com/obinet/pg/obhdev
Select Service Providers > ITSP Profile A SIP > Outbound Proxy
Uncheck both OBITalk Settings and Device Default

2. Replace
  • obihai.telephony.goog
with
  • c.telephony.goog

3. Click the Submit button

Repeat for ITSP Profile B SIP, ITSP Profile C SIP, ITSP Profile D SIP as needed for your environment.
To revert, swap c.telephony.goog with obihai.telephony.goog in step 2 and recheck both OBITalk Settings and Device Default

I had same issue in Houston area. Thanks to Torchredraider! Your recommended configuration changes worked perfectly. I now have incoming and outgoing calls working perfectly. Appreciate you posting the solution.
« Last Edit: December 09, 2018, 03:42:38 pm by JimM313 » Logged
differential
Newbie
*
Posts: 2


« Reply #57 on: December 09, 2018, 04:05:06 pm »

Folks, Torchredraider's solution is the correct one. You can view all of Torchredraider's posts about this evolving issue here:
http://www.obitalk.com/forum/index.php?action=profile;u=29101;sa=showPosts

Torchredraider's latest post at 8:53:28am today (12/9/18) is the best way to get your phones working while we are waiting for Google and Obihai to resolve this issue.
« Last Edit: December 09, 2018, 04:07:58 pm by differential » Logged
Pages: 1 2 [3]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC