December 11, 2017, 05:07:52 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1] 2
  Print  
Author Topic: All devices backing off  (Read 2548 times)
ACE1970
Newbie
*
Posts: 1


« on: October 31, 2017, 01:48:11 pm »

In the middle of a phone call today i was cut off. Here is the exact message i received.

Backing Off :
TCP connection to 125.141.125.74 failed
SP2Google Voice AaronBacking Off :
TCP connection to 125.141.125.74 failed

All devices had the 2016 update
Any suggestions? Thank you
Logged
Webslinger
Full Member
***
Posts: 103


« Reply #1 on: October 31, 2017, 02:03:14 pm »

In the middle of a phone call today i was cut off. Here is the exact message i received.

Backing Off :
TCP connection to 125.141.125.74 failed

TCP connection to 125.141.125.74 failed

Yeah, I saw the same issue today with someone else (tcp connection was 125.202.125.74, in Japan), but I didn't have time to troubleshoot the issue fully.

125.141.125.74 is in Korea.

Temporary fix is to reboot your router. Wait for SSiDs to populate or for it to start passing data fully. Then reboot the ATA. But I'm not sure if the issue is more random than this.

I have no clue where these crazy East Asian IP addresses are coming from. At first I thought it was a DNS issue, but specifying Google DNS and Opendns in the ATA's Internet Settings section with a Static setup didn't help.

I was also briefly considering checking TCP timeouts, NAT corruption, etc.
« Last Edit: October 31, 2017, 04:46:13 pm by Webslinger » Logged
Webslinger
Full Member
***
Posts: 103


« Reply #2 on: October 31, 2017, 04:29:28 pm »


 (tcp connection was 125.202.125.74, in Japan), but I didn't have time to troubleshoot the issue fully.

125.141.125.74 is in Korea.


Wth? Aren't these IP addresses backwards?


https://searchcode.com/file/126978396/tests/conftest.py


name 74.125.130.125 GTalk01 description Google talk server
name 74.125.134.125 GTalk02 description Google talk server
name 74.125.139.125 GTalk03 description Google Talk server
name 74.125.142.125 GTalk04 description Google Talk server
name 74.125.192.125 GTalk05 description Google Talk server
name 74.125.140.125 GTalk06 description Google Talk server
name 74.125.137.125 GTalk07
name 74.125.138.125 GTalk08
name 74.125.141.125 GTalk09
name 74.125.136.125 GTalk10
name 74.125.135.125 GTalk11


 Huh Huh Huh Huh Huh Huh
« Last Edit: October 31, 2017, 04:37:53 pm by Webslinger » Logged
GPz1100
Full Member
***
Posts: 109


« Reply #3 on: October 31, 2017, 04:34:05 pm »

^^Came to the same conclusion in the other thread after looking at the firewall logs.  https://www.obitalk.com/forum/index.php?topic=13022.0 .

I'm not sure if it's a google issue or obi, or a combination.  Likely the latter 2 as my pbx has no issue connecting and maintaining connectivity.  Occasionally the obi box will create a successful connection too.  Not sure how wide spread this is either. 
Logged
Webslinger
Full Member
***
Posts: 103


« Reply #4 on: October 31, 2017, 04:41:43 pm »

Came to the same conclusion in the other thread after looking at the firewall logs.

lol yay, I'm not insane.

Quote
Occasionally the obi box will create a successful connection too.

Yeah. I can't reproduce this issue, but someone else I know can; and it was driving her nuts today.
« Last Edit: October 31, 2017, 05:04:11 pm by Webslinger » Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3934



« Reply #5 on: October 31, 2017, 04:43:33 pm »

Obihai is investigating this now. 
Logged

sorin
Newbie
*
Posts: 4


« Reply #6 on: October 31, 2017, 05:36:33 pm »

Same here on both my devices, 100 and 200.  I restarted my modem, router, obi gizmo, same results. I noticed similar messages on other forums (dslreports) as well so it appears to be an outage. OBI support, any help? Thanks
Logged
GPz1100
Full Member
***
Posts: 109


« Reply #7 on: October 31, 2017, 05:45:10 pm »

@Webslinger,

I think you changed one of your comments after posting, but this gave me an idea.

Quote

Occasionally the obi box will create a successful connection too.


There's no issue when the router is booted, followed by the ATA.

When the ATA reboots on its own, then this issue can occur.

This suggests that whatever the obi box is trying to access is probably down, but is still part of a dns hunt group.

I think you or someone else posted this earlier.

Code:
name 74.125.130.125 GTalk01 description Google talk server
name 74.125.134.125 GTalk02 description Google talk server
name 74.125.139.125 GTalk03 description Google Talk server
*name 74.125.142.125 GTalk04 description Google Talk server
name 74.125.192.125 GTalk05 description Google Talk server
name 74.125.140.125 GTalk06 description Google Talk server
*name 74.125.137.125 GTalk07
name 74.125.138.125 GTalk08
name 74.125.141.125 GTalk09
name 74.125.136.125 GTalk10
name 74.125.135.125 Gtalk11

The two addresses with * next to them don't respond to ping. I wonder if what happens is when rebooting the obi, it tries to connect to one of those two.  Since the router has cached the ip's, it keeps trying until the router is rebooted (or cache cleared).  Randomly, another ip is chosen.  It may be the same one, may be different.

I think that explains why sometimes a connection happens, other times not.
Logged
sorin
Newbie
*
Posts: 4


« Reply #8 on: October 31, 2017, 06:13:43 pm »

Working now - thanks, OBI!
Logged
Webslinger
Full Member
***
Posts: 103


« Reply #9 on: October 31, 2017, 06:16:26 pm »

@Webslinger,

I think you changed one of your comments after posting

Yeah, I deleted that because I wasn't entirely sure how random the issue was, but when
I was testing for a friend, the issue was occurring only when the ATA was being rebooted without
the router also being rebooted.

When the router rebooted as well, before the ATA rebooted, then the issue didn't occur.

But it wasn't as though I was testing that over and over again for hours.



Quote
I think you or someone else posted this earlier.

Yes, that's a very old search result though. I was just randomly looking for Google Talk IPs and stumbled across that link.

Quote
Since the router has cached the ip's, it keeps trying until the router is rebooted (or cache cleared).  Randomly, another ip is chosen.

Sure, but I'm more interested in where these backward server IPs are getting pulled from. I'd have to, remotely, check someone's logs, telnet into her router, etc.
« Last Edit: October 31, 2017, 06:20:19 pm by Webslinger » Logged
GPz1100
Full Member
***
Posts: 109


« Reply #10 on: October 31, 2017, 06:27:47 pm »

@sorin  Like russian roulette? I suspect if you reboot the obi it likely will not reconnect.

@Webslinger, check your private box on dslr.
Logged
Rulo
Newbie
*
Posts: 14


« Reply #11 on: November 01, 2017, 02:57:18 pm »

Having the same problems with my Obi 200, but only with my 3 Google voice accounts, I have a VoIP.ms that works perfectly, the problem persists for me.
Any help from OBI?
Logged
GPz1100
Full Member
***
Posts: 109


« Reply #12 on: November 01, 2017, 03:00:38 pm »

^^Did you try the dns servers provided earlier in the thread or in one of the other threads?

DNSServer1   8.26.56.26   
DNSServer2   8.20.247.20

My units did not gain connectivity immediately after reboot (like in the past), but after a minute or two.
Logged
Rulo
Newbie
*
Posts: 14


« Reply #13 on: November 01, 2017, 03:16:40 pm »

Updated DNS but still not working...
Logged
Rulo
Newbie
*
Posts: 14


« Reply #14 on: November 01, 2017, 03:20:19 pm »

Now it came back with those DNS servers that you suggested. I was using Google's before.
8.8.8.8
8.8.4.4
Weird...
Thanks for your suggestion.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3934



« Reply #15 on: November 01, 2017, 03:43:44 pm »

Now it came back with those DNS servers that you suggested. I was using Google's before.
8.8.8.8
8.8.4.4
Weird...
Thanks for your suggestion.

8.8.8.8 and 8.4.4.4 are the Google DNS.

I have six OBis at two different locations on two different ISPs, successfully connecting to Google Voice (technically, the old Google Chat), and I've been using those two DNS for years, and I have not had the backing-off error. 

What I want to know is if anyone has changed to those servers and is still having problems.
Logged

GPz1100
Full Member
***
Posts: 109


« Reply #16 on: November 01, 2017, 03:52:57 pm »





I think there's more to this issue than just dns.
« Last Edit: November 01, 2017, 03:55:11 pm by GPz1100 » Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3934



« Reply #17 on: November 01, 2017, 04:23:31 pm »

Thanks.  Yes, it is most likely not a DNS issue, but since somebody claimed they fixed it (and then twice posted instructions on how to change the DNS), I wanted to definitively rule it out, which you have done.

My "educated guess" is that the OBi devices (regardless of model or firmware level) are trying to contact a Google server or servers, out of a pool of servers, that are dead and/or have been changed.

If I get any update from Obihai, I'll post it, but for now, this is a "Do not attempt to adjust your set" issue that can't be fixed by the user.
Logged

drgeoff
Hero Member & Beta Tester
*****
Posts: 2697


« Reply #18 on: November 01, 2017, 05:17:51 pm »

For info I'm not seeing any GV issues.

My FreePBX GV trunk continues to work just fine. (OAuth 2)

I powered up my OBi1032 and its GV trunk also works just fine.

Neither have had any changes to their GV settings for at least a year.

Both have DNS set to to my router which has ISP supplied DNS addresses.
Logged
chilirock
Jr. Member
**
Posts: 52


« Reply #19 on: November 02, 2017, 07:14:37 am »

Same issue here with Google Voice. I had the error yesterday morning, but after rebooting the Obi200 a couple times, the device connected. It stayed connected for the entire day. But this morning it shows the "backing off" error again. This time multiple reboots of the Obi200 does not resolve the issue. I had to temporarily switch outbound calls to CallCentric (from GV) until the issue gets resolved. Looking forward to hearing the root cause and resolution.
Logged
Pages: [1] 2
  Print  
 
Jump to:  

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