Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN

(1/14) > >>

martinsmithson:
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

Taoman:
Quote from: martinsmithson on November 03, 2017, 08:47:28 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

GPz1100:
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. 

martinsmithson:
Quote from: Taoman on November 03, 2017, 09:15:13 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!   ;D

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

martinsmithson:
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

Navigation

[0] Message Index

[#] Next page