OBiTALK Community

General Support => On-Topic: Obihai and OBi Products => Topic started by: martinsmithson on November 03, 2017, 08:47:28 am



Title: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: martinsmithson 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


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Taoman 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 (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 (http://www.obitalk.com/forum/index.php?topic=13111.msg84117#msg84117)


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: GPz1100 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. 


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: martinsmithson 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 (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 (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



Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: martinsmithson 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


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: drgeoff 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.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Taoman 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 (http://www.obitalk.com/forum/index.php?topic=13113.msg84151#msg84151)


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA 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 (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.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: martinsmithson 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


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA 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.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Taoman 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.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA on November 03, 2017, 09:59:24 pm
Or, in this user's case, simply not reading.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: martinsmithson 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


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Taoman 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.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: brianfmorris 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........


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: arobbert 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


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Jackson 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?


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: drgeoff 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.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: arobbert 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.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Jackson 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.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on November 07, 2017, 11:16:51 pm
Why is the OBI100/110 picture showing on the banner of the homepage and says "Works with Google Voice" and "Officially supported" still there?

Obi100 still being sold on amazon, first bullet point says "Works with google voice"

I was told that it was End of Life?

I'd like a firmware update please as it was noted this was only a google certificate update.  I'm getting the "Backing off" msg as of yesterday.

Please don't delete my posts this time.  A forum is normally a place where users go to share information. If the useful info is deleted then what is the point?

Thanks


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Jackson on November 08, 2017, 05:06:12 am
Why is the OBI100/110 picture showing on the banner of the homepage and says "Works with Google Voice" and "Officially supported" still there?

Obi100 still being sold on amazon, first bullet point says "Works with google voice"


(https://s26.postimg.org/5u36qex21/Obi_sip.jpg)


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: WelshPaul on November 08, 2017, 05:37:45 am
They forgot to update Amazon.co.uk:

(https://image.prntscr.com/image/QGhsRzzeSYKYd1f51RiQjg.png)

So there you have it! There will be no firmware update for the OBi1xx series for sure.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on November 08, 2017, 06:03:26 am
Nice, after posting yesterday and having my post removed, it seems someone updated the amazon bullet point that it works with google voice.

Its still on the homepage banner though.

(http://ObiBanner.PNG)


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on November 08, 2017, 06:08:31 am
From Google Cache as of Nov 5th(was the same yesterday)
First Bullet Point...

Good luck to all the people that purchased the obi100 from amazon recently

(http://GoogleCachedAmazonWorksWithGoogleVoice.PNG)


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: WelshPaul on November 08, 2017, 06:57:51 am
From Google Cache as of Nov 5th(was the same yesterday)
First Bullet Point...

Good luck to all the people that purchased the obi100 from amazon recently

(http://GoogleCachedAmazonWorksWithGoogleVoice.PNG)

They can be returned for a refund if purchased recently.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA on November 08, 2017, 03:33:19 pm
From Google Cache as of Nov 5th(was the same yesterday)
First Bullet Point...

Good luck to all the people that purchased the obi100 from amazon recently

(http://GoogleCachedAmazonWorksWithGoogleVoice.PNG)

Obihai can't control whether or not third-parties sell their products on Amazon.  The listing you are describing is an unauthorized private party selling old-stock products.  It has no bearing whatsoever on anything to do with this issue.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on November 08, 2017, 03:46:43 pm
Obihai sure got them to change it quickly.  Funny when I looked at Amazon yesterday it said that I purchased that item, with that description.

Even if it somehow is not authorized Obihai as a brand owner can get it done to make the description accurate.

The banner on their own website still isn't accurate to me atleast


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA on November 08, 2017, 03:58:35 pm
Obihai sure got them to change it quickly.  Funny when I looked at Amazon yesterday it said that I purchased that item, with that description.

Even if it somehow is not authorized Obihai as a brand owner can get it done to make the description accurate.

The banner on their own website still isn't accurate to me atleast

You are misunderstanding how products are sold on Amazon, regardless of whether the product is from Obihai, or from any other manufacturer.  Amazon unfortunately lumps third party sellers into the same listing as the manufacturer's own.  The manufacturer has no control over this.  As long as the third party isn't selling counterfeit merchandise (think fake designer handbags), the manufacturer can't kick off the third party listings.

None of this has any relevance to the availability of firmware.

If you don't want to buy a new OBi, you can re-purpose it as a SIP ATA, and use it with the Simonics Google Voice Gateway, or with any SIP service provider.

See:  http://www.obitalk.com/forum/index.php?topic=13147.0 (http://www.obitalk.com/forum/index.php?topic=13147.0)


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on November 08, 2017, 08:08:53 pm
I thought there was usually 1 listing per product, at least that is what I see for the obi100. There are multiple sellers but one description.

Anyway, you're right... nothing to do with this topic.

Are there any free alternatives that will work with gv with the obi100 if we have no options of getting the firmware updated?  Is it possible for someone to modify the latest obi110 firmware so that it will contain the same updates that obi2xx users received? 

Does anyone have the skills to compare the .fw files of the last obi2xx and the new obi2xx firmware that resolves this issue and somehow incorporate those changes into the latest obi110 firmware?


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: LTN1 on November 08, 2017, 08:23:24 pm
Does anyone have the skills to compare the .fw files of the last obi2xx and the new obi2xx firmware that resolves this issue and somehow incorporate those changes into the latest obi110 firmware?

I have a friend, a software engineer. He moonlights doing these things. He charges about $200 per hour and says he can probably incorporate the codes from the 2XX into the 1XX--and will probably only take about 7.5 hours to do. I can put you in touch with him...or you can buy the OBi212 for $80. Hard to decide isn't it?


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA on November 08, 2017, 08:25:20 pm
I thought there was usually 1 listing per product, at least that is what I see for the obi100. There are multiple sellers but one description.

Anyway, you're right... nothing to do with this topic.

Are there any free alternatives that will work with gv with the obi100 if we have no options of getting the firmware updated?  Is it possible for someone to modify the latest obi110 firmware so that it will contain the same updates that obi2xx users received? 

Does anyone have the skills to compare the .fw files of the last obi2xx and the new obi2xx firmware that resolves this issue and somehow incorporate those changes into the latest obi110 firmware?

Give it a rest.  If you keep posting about firmware hacking, you're likely to get banned from this company-sponsored forum.  Are you really sooooo cheap that you refuse to spend a few bucks to use the Simonics GVGW?


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on November 08, 2017, 09:27:24 pm
Does anyone have the skills to compare the .fw files of the last obi2xx and the new obi2xx firmware that resolves this issue and somehow incorporate those changes into the latest obi110 firmware?

I have a friend, a software engineer. He moonlights doing these things. He charges about $200 per hour and says he can probably incorporate the codes from the 2XX into the 1XX--and will probably only take about 7.5 hours to do. I can put you in touch with him...or you can buy the OBi212 for $80. Hard to decide isn't it?

Ahh, he must be the one selling the old devices on amazon with his updated firmware. I'm totally kidding don't ban me!


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on November 08, 2017, 09:33:51 pm
I thought there was usually 1 listing per product, at least that is what I see for the obi100. There are multiple sellers but one description.

Anyway, you're right... nothing to do with this topic.

Are there any free alternatives that will work with gv with the obi100 if we have no options of getting the firmware updated?  Is it possible for someone to modify the latest obi110 firmware so that it will contain the same updates that obi2xx users received? 

Does anyone have the skills to compare the .fw files of the last obi2xx and the new obi2xx firmware that resolves this issue and somehow incorporate those changes into the latest obi110 firmware?

Give it a rest.  If you keep posting about firmware hacking, you're likely to get banned from this company-sponsored forum.  Are you really sooooo cheap that you refuse to spend a few bucks to use the Simonics GVGW?

I just asked if it was possible, and If so can anyone do it. I wasn't aware that this was "hacking" and against some rule. SORRY Sir

Is there an End of Life listing for all of their products?  I was thinking about buying a new one, but I'm afraid they will announce EOL suddenly for my newly purchased device.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: WelshPaul on November 09, 2017, 03:18:13 am
I thought there was usually 1 listing per product, at least that is what I see for the obi100. There are multiple sellers but one description.

Anyway, you're right... nothing to do with this topic.

Are there any free alternatives that will work with gv with the obi100 if we have no options of getting the firmware updated?  Is it possible for someone to modify the latest obi110 firmware so that it will contain the same updates that obi2xx users received?  

Does anyone have the skills to compare the .fw files of the last obi2xx and the new obi2xx firmware that resolves this issue and somehow incorporate those changes into the latest obi110 firmware?

Give it a rest.  If you keep posting about firmware hacking, you're likely to get banned from this company-sponsored forum.  Are you really sooooo cheap that you refuse to spend a few bucks to use the Simonics GVGW?

I just asked if it was possible, and If so can anyone do it. I wasn't aware that this was "hacking" and against some rule. SORRY Sir

Is there an End of Life listing for all of their products?  I was thinking about buying a new one, but I'm afraid they will announce EOL suddenly for my newly purchased device.

Is there something wrong with you? I can't work out if you're stupid, trolling or plain old tight. The OBi1xx series has been EOL for over a year now and as explained many times now, they will not receive any firmware updates. So either pay the $6 and use the Simonics GVGW or purchase an OBi200, OBi202 or OBi212.

FYI, nobody here knows when the OBi2xx series will reach EOL status. Given that the OBi212 has only recently been released, it's likely going to be around for a few years to come for sure.

On a final note, maybe you should look at using a SIP based VoIP provider rather than Google Voice because if you think that you're going to purchase a VoIP ATA and use it along side a free VoIP service such as Google Voice to obtain a free phone line until your passing then you're in for more bad news i'm afraid.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: drgeoff on November 09, 2017, 04:28:39 am
The SIP standards are reasonably stable so there is a good chance that a SIP based hardware product will keep working until the hardware conks out.

Google's past is littered with things it has changed or abandoned.  I don't expect the future to be different. 


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on November 09, 2017, 09:42:33 am
Dude its only a one time $6 fee @ Simonics.  Signed up, set up and obi100 is working again.  Just like the title, I'm "backing off" 

Thanks to everyone that provided useful info and sorry for being a d**k!


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: jmsnyc on December 04, 2017, 11:11:17 pm
Hey quick question, is it $6 per GV account or $6 per Obi device ?  Guessing if I am currently using two GV numbers with my Obi10 so guessing its $12.  either way it is still cheap, just curious.   I will probably do this tomorrow as I wasted some time trying to resolve the backing off error and its 2am


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA on December 04, 2017, 11:16:08 pm
It is six dollars per Google account.

Why not just buy a new OBi 200 and be happy?


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on December 04, 2017, 11:20:20 pm
I'm guessing it's per google voice number, but not sure. I ended up just buying an obi202 with 2 lines for around $50 after I paid the $6. I'm sure this simon guy is cool and all but I just didn't feel right after a couple of days giving him access to my google voice account/text/audio etc. I revoked access and gave obi access again.  Lets hope this 202 lasts 6-7 yrs like my obi100.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: billsimon on December 05, 2017, 09:19:06 am
I'm guessing it's per google voice number, but not sure. I ended up just buying an obi202 with 2 lines for around $50 after I paid the $6. I'm sure this simon guy is cool and all but I just didn't feel right after a couple of days giving him access to my google voice account/text/audio etc. I revoked access and gave obi access again.  Lets hope this 202 lasts 6-7 yrs like my obi100.

Thanks for assuming I'm cool  ;)

To be very clear about the access Google Voice Gateway (and its proprietor) have:

You authorize systems that have our app credentials (specifically, any of the current 7 GVGW VoIP servers) to log in to your Google Chat account ONLY. There is no other access to your Google account, including the Google Voice page, SMSes, or anything else. Audio does pass through our servers, obviously, but it is not monitored (Who has time for that?) nor is it tracked in any way that would make it convenient or easy to do so. Use TLS to hide your signaling for good measure.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: truelies on December 05, 2017, 11:31:09 am
My obi100 doesn't work today, it shows

Backing Off :
TCP connection to 173.194.200.125 failed

, Not at Nov 3 like others. So the OBI100 won't be able to work with google voice anymore?


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Jackson on December 05, 2017, 11:45:59 am
My obi100 doesn't work today, it shows

..... So the OBI100 won't be able to work with google voice anymore?

Pony up $6 and get/do this.

http://www.obitalk.com/forum/index.php?topic=13147.0


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: atom on December 05, 2017, 12:54:26 pm

Thanks for assuming I'm cool  ;)

To be very clear about the access Google Voice Gateway (and its proprietor) have:

You authorize systems that have our app credentials (specifically, any of the current 7 GVGW VoIP servers) to log in to your Google Chat account ONLY. There is no other access to your Google account, including the Google Voice page, SMSes, or anything else. Audio does pass through our servers, obviously, but it is not monitored (Who has time for that?) nor is it tracked in any way that would make it convenient or easy to do so. Use TLS to hide your signaling for good measure.

Hi Mr. Simon! Thanks for your response and for clearing some things up. To be clear on my end, I really do think you're cool and not the creepy guy listening to our conversations on the weekends :-) After I signed up I was checking out the third party app access in my google account and saw the attached Image below.

It just made me think, who is this guy and what have I done. It says it has access to google hangouts, view and send chat messages. If one has the option turned on to receive google voice texts and voicemail via hangouts I was unsure. I thought I may have just given access to my SMS and voicemail which I really didn't want to give a guy that I don't know. I don't know why, but I feel more comfortable giving a company that sells their products at Bestbuy/Walmart/Newegg etc the same access instead.  But seeing your reply here makes me want to trust you more.

I couldn't stop thinking about it, I'm weird like that... Around the same time I get a promo for the obi202 from newegg so I just picked one of those up. Now obi has access to view and send chat messages. :-)

You have made the Google Voice Gateway service very easy to set up/use and a great option for older obi100 devices that now receive the "Backing off" error. I also enjoyed seeing caller ID as well. From the few days that I used it, it worked very well.  Thank you for giving us the option for the ridiculously low one time $6 setup fee.



Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: vtsnaab on December 05, 2017, 02:12:26 pm
We have Simonics set up on a Panasonic cordless SIP phone & after the initial setup it has been 100% flawless.

As of this morning BOTH our Obi boxes ceased to function;

No big shock with the Obi110 - but the Obi2xx also quit at the very same time.

None of this is endearing me towards Obi anymore except to use the boxes as ATAs going forward; absolutely NOT planning to buy anymore stuff from Obi when there are other alternatives that can work with GV and need not cost as much as Obi products tend to, even during their 'sales'.

So - currently seeking other good ideas for connecting before pulling the trigger to move our lines over to the GVGW.
Any further helpful info will be greatly appreciated.

Thanks.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA on December 05, 2017, 02:19:25 pm

Thanks for assuming I'm cool  ;)

To be very clear about the access Google Voice Gateway (and its proprietor) have:

You authorize systems that have our app credentials (specifically, any of the current 7 GVGW VoIP servers) to log in to your Google Chat account ONLY. There is no other access to your Google account, including the Google Voice page, SMSes, or anything else. Audio does pass through our servers, obviously, but it is not monitored (Who has time for that?) nor is it tracked in any way that would make it convenient or easy to do so. Use TLS to hide your signaling for good measure.

Hi Mr. Simon! Thanks for your response and for clearing some things up. To be clear on my end, I really do think you're cool and not the creepy guy listening to our conversations on the weekends :-) After I signed up I was checking out the third party app access in my google account and saw the attached Image below.

It just made me think, who is this guy and what have I done. It says it has access to google hangouts, view and send chat messages. If one has the option turned on to receive google voice texts and voicemail via hangouts I was unsure. I thought I may have just given access to my SMS and voicemail which I really didn't want to give a guy that I don't know. I don't know why, but I feel more comfortable giving a company that sells their products at Bestbuy/Walmart/Newegg etc the same access instead.  But seeing your reply here makes me want to trust you more.

I couldn't stop thinking about it, I'm weird like that... Around the same time I get a promo for the obi202 from newegg so I just picked one of those up. Now obi has access to view and send chat messages. :-)

You have made the Google Voice Gateway service very easy to set up/use and a great option for older obi100 devices that now receive the "Backing off" error. I also enjoyed seeing caller ID as well. From the few days that I used it, it worked very well.  Thank you for giving us the option for the ridiculously low one time $6 setup fee.



What Bill is discussing is this:

In ye olden days, users would authenticate to their Google accounts by supplying an email address and a password.  That gave whoever had those two things complete access to that Google account; a very bad idea.  Google implemented a safer alternative, using a secure (digitally signed) token exchange, known as OAUTH 2.0.  By using OAUTH, Google can limit access to specific services on your Google account.  The party desiring access (Obihai or Simonics) sends a request to Google, which then pops a dialog box or page, asking that Google user if it's ok to allow that third party access to the specific service you want to use with them, and you approve.  At no point does the third party ever have your Google password.

So, specific to Google Voice, GVGW is just being granted access, by you, to the telephony stuff, and nothing else.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: jmsnyc on December 05, 2017, 05:21:00 pm
It is six dollars per Google account.

Why not just buy a new OBi 200 and be happy?

I'd rather spend $6 than $60.

Something must have been wrong last night.  Now it is working.  I am guessing you do not thinking "working " on 110 will be consistent


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA on December 05, 2017, 05:30:20 pm
It is six dollars per Google account.

Why not just buy a new OBi 200 and be happy?

I'd rather spend $6 than $60.

Something must have been wrong last night.  Now it is working.  I am guessing you do not thinking "working " on 110 will be consistent

Right -- you cannot assume that a OBi 110 or 100 will keep working with Google Voice.  Eventually, you will need to either upgrade to an OBi 200 series, or use the Simonics GVGW, or not use Google Voice.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: JLDP on December 06, 2017, 03:41:17 pm
We were hit by the same problem yesterday. Googled a lot, fixed it by adding a DNS server.
Came home from work to the same problem, again. No DNS server setting in our box either.
How often do we need to set the DNS server? Is GV erasing it remotely?
Why even the need for DNS entries? If configured properly, the service should work flawlessly, without IT-level intervention in Expert Mode etc. It worked for years. Who broke it?
</rant>

I'll see if I can fix it. Again.
We need our phone line ... you know ... for making phone calls. Daring, right? It's not here only for decoration.
Hoping that there is a more permanent fix than temporary DNS settings.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: drgeoff on December 06, 2017, 03:52:13 pm
We were hit by the same problem yesterday. Googled a lot, fixed it by adding a DNS server.
Came home from work to the same problem, again. No DNS server setting in our box either.
How often do we need to set the DNS server? Is GV erasing it remotely?
Why even the need for DNS entries? If configured properly, the service should work flawlessly, without IT-level intervention in Expert Mode etc. It worked for years. Who broke it?
</rant>

I'll see if I can fix it. Again.
We need our phone line ... you know ... for making phone calls. Daring, right? It's not here only for decoration.
Hoping that there is a more permanent fix than temporary DNS settings.
There are three permanent fixes.  All have been discussed many, many times in these forums.

1.  If you have an Obi2xx device or an OBi IP phone it needs a firmware update.

2.  If you have an OBi1x0 device then either replace it with an OBi2xx

or

3.  Pay the one-time $6 to use the Simonics GV gateway.

Changing DNS is just playing whack-a-mole except that sooner or later your mallet will break - game over.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: JLDP on December 06, 2017, 04:31:44 pm
Thank you for the explanation.
I do not normally go and read these forums, I only came by from a Google link while searching for a fix to my problem.
Truth is I got spoiled by nice companies that at least try to notify their customers before they discontinue their service. I completely forgot that we're dealing with Google instead.

The second DNS fix didn't take so it is time to either pay Mr. Simon or buy an expensive new box to replace one that isn't broken. Thanks, Google! </sarcasm>
And thanks, Geoff, appreciate the input.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: utsc on December 07, 2017, 06:01:00 pm
It is six dollars per Google account.

Why not just buy a new OBi 200 and be happy?

Hi Steve,

Brand New OBi 100 & 110 was SOLD online in major online retailers without EOL warning recently. I did see it with my own eyes about 6 months ago as I was comparing prices and purchased Obi 200 as it was on "sale" for my relative.

I have been using  my OBi 110 for about 5 years or even more and I have purchased about 4 devices for my extended family and recommended OBi for a lot of friends and also in many forum posts as I strongly believed that OBi was the best device for GV.

Therefore IF OBi thinks that customer good will and word of mouth marketing is  worth nothing for OBi then go ahead with EOL non support.  EOL non support is a pure money grabbing strategy to sell new devices as the OBi 100/110 hardware is fully capable of handling Google Voice. Importantly there is very minimal improvement (IF ANY) in the OBi 200 series devices. Hence it's not like throwing away your iPhone 5 to buy an iPhone 8 


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: SteveInWA on December 07, 2017, 06:30:56 pm
It is six dollars per Google account.

Why not just buy a new OBi 200 and be happy?

Hi Steve,

Brand New OBi 100 & 110 was SOLD online in major online retailers without EOL warning recently. I did see it with my own eyes about 6 months ago as I was comparing prices and purchased Obi 200 as it was on "sale" for my relative.

I have been using  my OBi 110 for about 5 years or even more and I have purchased about 4 devices for my extended family and recommended OBi for a lot of friends and also in many forum posts as I strongly believed that OBi was the best device for GV.

Therefore IF OBi thinks that customer good will and word of mouth marketing is  worth nothing for OBi then go ahead with EOL non support.  EOL non support is a pure money grabbing strategy to sell new devices as the OBi 100/110 hardware is fully capable of handling Google Voice. Importantly there is very minimal improvement (IF ANY) in the OBi 200 series devices. Hence it's not like throwing away your iPhone 5 to buy an iPhone 8 


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Nightowl on December 07, 2017, 08:46:24 pm


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.
[/quote]

Steve thanks for the Simonics gateway idea.  My old Obi110 worked fine up till December 7, 2017.  I already bought the Obi 200 a couple days ago so it has replaced the 110.  I could give the 110 to my daughter.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: azrobert on December 07, 2017, 10:10:57 pm
I already bought the Obi 200 a couple days ago so it has replaced the 110.  I could give the 110 to my daughter.

When you get your OBi200, you can define 2 GV trunks on it, one for you and one for your daughter. She can then access the OBi200 from the OBi110 and make and receive calls, both of you could be on simultaneous calls. No need for the Simonics GVGW.

Here is the setup:
http://www.obitalk.com/forum/index.php?topic=13136.0


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Svakars on December 08, 2017, 06:58:52 pm
There is another way to keep Google Voice.
1. Create a Callcentric SIP account on second OBI 100/110 profile.
2. Assign the incoming Free New York number to your Callcentric account.
3. In Google Voice settings forward ALL calls to the Free New York number.

At least you can receive all incoming calls to your Google account for Free!
As a temporarily solution.
I am hoping that one day Google service will be back to OBI 100/110.
If you need to make calls from a Google number:

For outgoing calls you need to delete Google Voice profile and create an account with Localphone .
I think you have to put $10 credit to be able to make outgoing calls. $0.005c per minute in US. $0.01 for UK calls .etc.
You can assign outcoming calls with your Google number. In this way your recipients will see that you are calling from the Google number. 


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: jmsnyc on December 09, 2017, 09:24:55 am
My obi100 doesn't work today, it shows

..... So the OBI100 won't be able to work with google voice anymore?

Pony up $6 and get/do this.

http://www.obitalk.com/forum/index.php?topic=13147.0


Quick question on this.  Once you sign up and get SIP credentials , you can use your GV on any generic sip app on Android ?  Any app that will support GV text messages with this as I hate the GV app?


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: billsimon on December 09, 2017, 09:40:05 am
Quick question on this.  Once you sign up and get SIP credentials , you can use your GV on any generic sip app on Android ?  Any app that will support GV text messages with this as I hate the GV app?

You can use Android SIP apps. I use and recommend Grandstream Wave. The native Android SIP dialer doesn't work.

SMS is not supported.


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: jmsnyc on December 09, 2017, 08:30:54 pm
Quick question on this.  Once you sign up and get SIP credentials , you can use your GV on any generic sip app on Android ?  Any app that will support GV text messages with this as I hate the GV app?

You can use Android SIP apps. I use and recommend Grandstream Wave. The native Android SIP dialer doesn't work.

SMS is not supported.

Thank you .


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: heny on December 09, 2017, 09:57:32 pm
paid $6 and setup GVGW, now it is working. thanks!

I have my settings in obitalk, I am thinking to move all the settings back to my obi100 device so won't have to rely on obitalk.com at all.

here is my current setting:
sp1 connects to GVGW.
SP2 connects to callcentric (GV also forward calls to that callcentric number)
voice gateway 3: set to voip provider for international calling. (using digitalmap to router calls).

are those all possible to setup locally in the obi100 interface? any guide?

Thanks!


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: azrobert on December 09, 2017, 10:24:51 pm
are those all possible to setup locally in the obi100 interface? any guide?

When you use OBiTalk to provision your OBi, the configuration is downloaded to your device. You just have to login locally and disable OBiTalk Provisioning and you're done.

System Management -> Auto Provisioning
Under OBiTalk Provisioning
Method: Disabled


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Mr_C on December 11, 2017, 03:07:46 am

Thanks for assuming I'm cool  ;)

To be very clear about the access Google Voice Gateway (and its proprietor) have:

You authorize systems that have our app credentials (specifically, any of the current 7 GVGW VoIP servers) to log in to your Google Chat account ONLY. There is no other access to your Google account, including the Google Voice page, SMSes, or anything else. Audio does pass through our servers, obviously, but it is not monitored (Who has time for that?) nor is it tracked in any way that would make it convenient or easy to do so. Use TLS to hide your signaling for good measure.

I have signed up simonics (paid $6) and updated the obitalk portal following the directions.  However, something is not working.  I am still getting Backing Off :TCP connection to 173.194.204.125 failed.

Any suggestions?

Thanks - Eric


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: bitstopjoe on December 11, 2017, 03:33:36 am

Thanks for assuming I'm cool  ;)

To be very clear about the access Google Voice Gateway (and its proprietor) have:

You authorize systems that have our app credentials (specifically, any of the current 7 GVGW VoIP servers) to log in to your Google Chat account ONLY. There is no other access to your Google account, including the Google Voice page, SMSes, or anything else. Audio does pass through our servers, obviously, but it is not monitored (Who has time for that?) nor is it tracked in any way that would make it convenient or easy to do so. Use TLS to hide your signaling for good measure.

I have signed up simonics (paid $6) and updated the obitalk portal following the directions.  However, something is not working.  I am still getting Backing Off :TCP connection to 173.194.204.125 failed.

Any suggestions?

Thanks - Eric

 I had the same problem. I had to go into the OBiTalk dashboard and DELETE my OBi 110 and then go through the OBi install procedure ( ***5, etc). Then I re-did the Simonics install and after a few reboots, all worked. Give that a try and see.

Merry Christmas

Joe Sica


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: Mr_C on December 11, 2017, 03:49:50 am
I had the same problem. I had to go into the OBiTalk dashboard and DELETE my OBi 110 and then go through the OBi install procedure ( ***5, etc). Then I re-did the Simonics install and after a few reboots, all worked. Give that a try and see.

Merry Christmas

Joe Sica

Ha!  I was just getting ready to reply that I got it working by physically rebooting the Obi 110.  Thanks for the note

Eric


Title: Re: Backing Off : TCP connection to 173.194.193.125 failed . . . is BACK AGAIN
Post by: tower110 on December 11, 2017, 09:28:13 pm
it seems simonics GVGW not allowing new signup now. I get this message -

<Sorry, we are temporarily not taking new users for Google Voice Gateway.>

Did anyone else got this message? Any other workaround?