December 10, 2017, 04:17:15 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1] 2 3 4
  Print  
Author Topic: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN  (Read 10270 times)
martinsmithson
Newbie
*
Posts: 12


« on: November 03, 2017, 08:47:28 am »

As of 10:30 AM EDT . . .

Backing Off :
TCP connection to
173.194.193.125 failed

. . . has returned to both SP's on my OBi100.  At this time, said with fingers crossed, the SP's on my OBi202 are working.

Yesterday I changed DNSServer1 and DNSServer2 to 8.8.8.8 and 8.8.4.4 respectively for both OBi units and all worked perfectly.

While all SP's on OBi202 remains working, OBi100's SP's are currently useless.  In an attempt to resolve the problem, I reset both DNSServers to OBiTALK - no joy, and then DEFAULT - no joy, and back to 8.8.8.8. and 8.8.4.4 - again, no joy.

I can only wonder how many minutes or short-hours it's gonna take before all SP's "Back Off" on my OBi202.  UGH!!!

So . . . on behalf of our engineering firm, I have to ask the OBihai Support Team . . . how long will it take to resolve this TCP connection to 173.194.193.125 failed PROBLEM?  

I ask because our company president wants to remove (we call it "redline") OBi products from our master specification's pre-approved manufacturers and pre-approved bidders lists for all future projects.  Why?  Well, three years ago, based on my recommendation, our firm purchased thirty-five OBi202 and in the last 5 days they've not worked twice.  Yesterday, the company spent $800 USD to have Comcast re-activate the old phone system due to the multiple OBi system failures in the last 5 days.  But I digress.

MS


* OBi100 - Dashboard.jpg (75.65 KB, 800x293 - viewed 358 times.)

* OBi100 - OBi Expert 1.jpg (127.48 KB, 800x500 - viewed 361 times.)

* OBi100 - OBi Expert 2.jpg (198.39 KB, 800x628 - viewed 407 times.)

* OBi100 - OBi Expert 2A.jpg (206.84 KB, 800x546 - viewed 308 times.)
« Last Edit: November 03, 2017, 08:53:34 am by martinsmithson » Logged
Taoman
Hero Member
*****
Posts: 924


« Reply #1 on: November 03, 2017, 09:15:13 am »


So . . . on behalf of our engineering firm, I have to ask the OBihai Support Team . . . how long will it take to resolve this TCP connection to 173.194.193.125 failed PROBLEM?  


If you haven't done so already, update the firmware on all 20X series devices via the OBitalk web portal and the yellow triangle.

http://www.obitalk.com/forum/index.php?topic=13113.msg84139#msg84139

As far as 100/100 devices your choices are limited. Read the entire thread listed above.
You can also try changing DNSServer1 to 209.244.0.3 to see if that helps.

http://www.obitalk.com/forum/index.php?topic=13111.msg84117#msg84117
Logged
GPz1100
Full Member
***
Posts: 109


« Reply #2 on: November 03, 2017, 09:30:10 am »

Steve, your company is using obi/google voice for their phone service?

If that's the case, they're getting what they pay for.  This whole arrangement is nice when/while it works, but i'd never consider it a business solution.  Sure it saves money but what happens when there's a problem.  You can't reach a live person at google, and obi ticket support is poor (or at least their front line ticket support, my ticket never got to level 2 or 3 - if there is such a thing).

Based on other posts the 100 series models are end of life with no more software updates. Your choices to make them work with google voice is either to use the simonics gateway or setup a pbx.  Pbx choice isn't very viable if the boxes are on different networks or locations. 
Logged
martinsmithson
Newbie
*
Posts: 12


« Reply #3 on: November 03, 2017, 10:19:10 am »


If you haven't done so already, update the firmware on all 20X series devices via the OBitalk web portal and the yellow triangle.

http://www.obitalk.com/forum/index.php?topic=13113.msg84139#msg84139

As far as 100/100 devices your choices are limited. Read the entire thread listed above.
You can also try changing DNSServer1 to 209.244.0.3 to see if that helps.

http://www.obitalk.com/forum/index.php?topic=13111.msg84117#msg84117

Thanks for your support, Taoman!   Grin

I have SUCCESSFULLY upgraded 202XXXXXX's firmware to 3.2.1 (Build 5757EX).

I also read the entire thread as you suggested - didn't much care for the "hijacking" comments associated with GPz1100, but learned to ignore him/her as I will on my post.

I regularly ***6 my OBi202 and prior to reading your post, there was no update available.  While I'm a bit confused why, I trust the 3.2.1 firmware update (noted above) resolves THAT issue (not to be confused with the "Backing Off" issue).

Given your support directing me to SteveInWA's post on November 02, 2017, 06:48:43 pm, I now have a better understanding of WHY this "Backing Off" issue has been happening - and how to remain calm during the process.  I will be informing our company's president of same and trust he will do same.

Thanks again, Taoman!!

MS

2017-11-03 UPDATES regarding OBi100

1:22 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed

« Last Edit: November 03, 2017, 10:24:45 am by martinsmithson » Logged
martinsmithson
Newbie
*
Posts: 12


« Reply #4 on: November 03, 2017, 04:15:54 pm »

2017-11-03 UPDATE regarding OBi100

7:15 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 2695


« Reply #5 on: November 03, 2017, 04:29:29 pm »

2017-11-03 UPDATE regarding OBi100

7:15 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed
You can keep posting your updates until hell freezes over but it is anyone's guess whether that or Obihai releasing a fixed firmware for 1x0 models will happen first.

You can be back up and running in under 30 minutes by giving Bill Simons your custom.
Logged
Taoman
Hero Member
*****
Posts: 924


« Reply #6 on: November 03, 2017, 05:52:00 pm »

2017-11-03 UPDATE regarding OBi100

7:15 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed

Did you read my post below? It's not going to get better for the OBi100/OBi110 series of devices.

http://www.obitalk.com/forum/index.php?topic=13113.msg84151#msg84151
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3931



« Reply #7 on: November 03, 2017, 06:12:06 pm »

2017-11-03 UPDATE regarding OBi100

7:15 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed

Did you read my post below? It's not going to get better for the OBi100/OBi110 series of devices.

http://www.obitalk.com/forum/index.php?topic=13113.msg84151#msg84151

RE: 110/100 devices, if those owners want to continue using an OBi device directly with Google Voice (not via Simonics gateway), it is highly likely that the 200 series will go on sale soon as part of "Black November" or similar holiday sales.
Logged

martinsmithson
Newbie
*
Posts: 12


« Reply #8 on: November 03, 2017, 08:00:39 pm »

It's funny that the OBi100 device suffered "Backing Off" on Sunday, but was back up and running fine on Monday.  Then the same thing happened on Tuesday morning/Tuesday evening.  And now on Friday - nothing.

2017-11-03 UPDATE regarding OBi100

11:00 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3931



« Reply #9 on: November 03, 2017, 08:09:27 pm »

It's funny that the OBi100 device suffered "Backing Off" on Sunday, but was back up and running fine on Monday.  Then the same thing happened on Tuesday morning/Tuesday evening.  And now on Friday - nothing.

2017-11-03 UPDATE regarding OBi100

11:00 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed

For the love of gawd, why won't you just accept the posted answers?  Your OBi 100 will not work any more with Google Voice.  It may work today or tomorrow, but it will soon stop working entirely.  There is no solution, other than to a) use the Simonics Google Voice Gateway via SIP, or to buy a new OBi 200 device.
Logged

Taoman
Hero Member
*****
Posts: 924


« Reply #10 on: November 03, 2017, 09:53:07 pm »


For the love of gawd, why won't you just accept the posted answers?  

I think some people still hold out hope that Obihai can be pressured/persuaded to release new firmware for the OBi100/OBi110 series. In my view Obihai has been quite explicit in stating that ain't gonna happen.

Quote from: Obihai blog

However, any services that cannot be supported with the current software (firmware) will not work on the OBi100 and OBi110.

With this EOL announcement, affecting only the OBi100 and OBi110, it is important to understand that Obihai will no longer develop and release software updates.

For example, if Google Voice, Anveo or any other service makes changes in the way they deliver their service where new software is required for the continued use the service with the OBi device, it will not be made available for the OBi100 and OBi110.

August 12, 2016 End Of Life for the OBi100 and OBi110.
No new software/firmware will be developed and released for the OBi100 and OBi110 after this date.

The OBi100 and OBi110 devices have been good soldiers, but have reached the end of their useful life which necessitates the decision to discontinue the product and software development.

As long as Google makes no changes in how the service works with the OBi, your OBi100/OBi110 device will continue to work.

However, with the EOL announcement, there is no further software development for the OBi100 and the OBi110 devices.

However, it is important to note there is no further software development for OBi100 and OBi110.


Seems crystal clear to me there will no new firmware released for OBi100/OBi110. They are End Of Life as far as making a direct connection to Google Voice is concerned. They are now SIP only devices.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3931



« Reply #11 on: November 03, 2017, 09:59:24 pm »

Or, in this user's case, simply not reading.
Logged

martinsmithson
Newbie
*
Posts: 12


« Reply #12 on: November 04, 2017, 09:12:11 am »

2017-11-04 UPDATE regarding OBi100

12:12 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed
Logged
Taoman
Hero Member
*****
Posts: 924


« Reply #13 on: November 04, 2017, 09:16:49 am »

2017-11-04 UPDATE regarding OBi100

12:12 PM EDT, SP1 and SP2 remain unchanged, still . . .

Backing Off :
TCP connection to
173.194.193.125 failed

Cool story. And in other news it's supposed to rain today.
Logged
brianfmorris
Newbie
*
Posts: 1


« Reply #14 on: November 05, 2017, 10:33:11 am »

Updating the firmware fixed my issues

Interestingly enough - my error was:

TCP connection to 125.191.233.64 failed

That IP address is in Korea........
Logged
arobbert
Newbie
*
Posts: 5


« Reply #15 on: November 05, 2017, 11:04:54 am »

Having the same issue today with several OBI100's. Added Simon Telephonics and now it's working with Google Voice. A little tricky to configure. Found good information on this post. $6 insead of $50.

https://www.obitalk.com/forum/index.php?topic=6136.0
Logged
Jackson
Full Member
***
Posts: 141


« Reply #16 on: November 05, 2017, 02:33:47 pm »

Having the same issue today with several OBI100's. Added Simon Telephonics and now it's working with Google Voice. A little tricky to configure. Found good information on this post.

I'm a bit confused.  Do I delete my non functioning (Obi100) SP2 GV completely?
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 2695


« Reply #17 on: November 05, 2017, 03:27:25 pm »

Having the same issue today with several OBI100's. Added Simon Telephonics and now it's working with Google Voice. A little tricky to configure. Found good information on this post.

I'm a bit confused.  Do I delete my non functioning (Obi100) SP2 GV completely?
You reconfigure whatever SP was GV to be SIP and registered to the Simonics gateway.
Logged
arobbert
Newbie
*
Posts: 5


« Reply #18 on: November 05, 2017, 06:08:09 pm »

Having the same issue today with several OBI100's. Added Simon Telephonics and now it's working with Google Voice. A little tricky to configure. Found good information on this post.

I'm a bit confused.  Do I delete my non functioning (Obi100) SP2 GV completely?
I deleted the existing GV config and manually setup a connection using the expert configuration.
Logged
Jackson
Full Member
***
Posts: 141


« Reply #19 on: November 06, 2017, 04:05:06 am »

Thanks for the explanation.  I thought I could simply forward my GV # to my Anveo # on SP1.  I used my cell to call.  My phone rings but answering it does nothing, the cell keeps ringing then goes to GV VM.
Logged
Pages: [1] 2 3 4
  Print  
 
Jump to:  

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