TCP connection to 125.141.125.74 failed

<< < (3/26) > >>

SteveInWA:
Quote from: Ryan_Chicago on October 31, 2017, 07:38:15 pm

Same here with my Obi 110 attempting to reconnect to Google Voice (GV) :(

Backing Off : TCP connection to 209.85.234.125 failed
Backing Off : TCP connection to 74.125.69.125 failed

Is this because Google has permanently shutdown their XMPP API?

https://cloud.google.com/appengine/docs/deprecations/xmpp

I fear all of the Obi GV users may be SOL.


No,  "all of the OBi GV users" are not SOL.  This is not impacting every user.  It's a bug that Obihai is investigating, and will fix.  Google Voice is still available and supported by Obihai.

And, No, the deprecation you referenced does not apply in this situation.

mikeb0:
My OBi 200 worked flawlessly for 1.5 years and today get the same issue here...
Phone LED is off, no inbound calls, and outbound I hear "No service configured error".
Echo test (**9 222 222 222) works perfectly.

SP1 Service Status: Backing Off (2s):TCP connection to 125.132.125.74 failed

Tried updating firmware but no luck.
SoftwareVersion   3.2.1 (Build: 5735EX)

Hope there's a fix soon.

FireSQer:
I followed these directions on two different boxes with great success:
https://www.obitalk.com/info/faq/GV-and-the-OBi/Using-openDNS-GV-Status-BackingOff
Quick summary:
1. Log into obitalk.com
2. Choose Obi Expert Configuration
3. Choose Enter Obi Expert
4. Click on System Management
5. Choose WAN Settings
6. UNcheck ObiTalk Settings by DNSServer1
7. UNcheck Device Default
8. Enter 8.8.4.4 in DNSServer1 field
9. Scroll to bottom and Submit

I also upgraded firmware while I was at it.
10. Back to the Obi Dashboard.
11. Click on the yellow triangle to upgrade firmware.

Now I'm dialing out as well as receiving calls.

HTH.

Mike

phonebob:
Quote from: FireSQer on October 31, 2017, 08:47:37 pm

I followed these directions on two different boxes with great success:
https://www.obitalk.com/info/faq/GV-and-the-OBi/Using-openDNS-GV-Status-BackingOff
Quick summary:
1. Log into obitalk.com
2. Choose Obi Expert Configuration
3. Choose Enter Obi Expert
4. Click on System Management
5. Choose WAN Settings
6. UNcheck ObiTalk Settings by DNSServer1
7. UNcheck Device Default
8. Enter 8.8.4.4 in DNSServer1 field
9. Scroll to bottom and Submit

I also upgraded firmware while I was at it.
10. Back to the Obi Dashboard.
11. Click on the yellow triangle to upgrade firmware.

Now I'm dialing out as well as receiving calls.

HTH.

Mike

I tried this, and it didn't change anything.  Then I followed the link in the quoted post.  I noticed it said to use 4.2.2.2 (not 8.8.4.4).  I tried that, and it works.

Ryan_Chicago:
Yup changing DNS servers seems to have fixed the issue. My Obi110 was previously using the RCN DNS servers:

207.172.3.9
207.172.3.11

I switched to Comodo DNS servers and this resolved the issue for now:

8.26.56.26
8.20.247.20

I would guess that Google recently changed the DNS records for it's XMPP servers and the RCN DNS servers are still serving up the old/stale A records.

Also, FWIW I'm specifically avoiding using the Google DNS servers because strangely, and albeit many years ago, I encountered an issue with the Obi110 whereas the message indicator light on my phone would not function when using Google DNS.

Navigation

[0] Message Index

[#] Next page

[*] Previous page