TCP connection to 125.141.125.74 failed
maorsela:
I have an Obi110, I paid Simon's Gateway the $6 and now GV works again for me.
C6silver:
Quote from: Jasper on November 03, 2017, 09:26:48 pm
I knew our days with Obi100 were numbered after Obihai's EOL announcement last year.
Was ready to buy the OBI202 when this problem began a few days ago. Wife insisted we explore other options before investing in another box that's destined to become outdated again. Fixed income does that to you. Came across some references on here to gvsip and simonics gateways. Researching both I discovered gvsip is no longer in business. Simonics gateway got lots of hits and good reviews everywhere.
Trying to find actual configuration instructions was more difficult. Howto bits and pieces scattered everywhere. Started by creating my account here https://simonics.com/gw/ . SIP ID and password is on the main gateway page after paying a $5.99 fee.
Sip Login = GV18005551212 (replace 8005551212 with your actual Google Voice number)
Sip Password = 12 character alphanumeric sequence; if you do a copy/paste make sure to remove the trailing space before pasting
Server = gvgw.simonics.com
Armed with this information I logged into obitalk.com dashboard. I didn't see a specific option for Simonics gateway under service providers. Common sense suggested I try the "Generic Service Provider" option. I filled it in like this.
Service Provider Proxy Server = gvgw.simonics.com
Service Provider Proxy Server Port = 5060
Outbound Proxy Server = gvgw.simonics.com
Outbound Proxy Server Port = 5060
Username = GV18005551212
Password = {PASSWORD}
URI = <blank> (nothing)
Don't forget to hit save. This reboots the Obi100. After a few moments try a test call. Mine went through right away. Good luck!
Google chat must be selected as a forwarding option under Phones in the google voice settings for incoming calls to work. Short time later a telemarketing call came in. An unexpected surprise was the name along with the number. Only the number came through before, no names. Nice!
The whole process took about 10 minutes to set up after I got my bearings. Getting to this point took much longer ;)
We'll keep the Obi100 until it stops working or until the gateway goes away. Although we've gotten our money's worth over the years it would be a terrible shame to throw away a perfectly good piece of equipment because the manufacturer finds innovative ways to force an upgrade.
Wanted to thank you for writing this up. Paid the $5.99 and used your guide. Got setup in only a minute or two. Inbound and outbound calls working again. Appreciate it!
kelemvor:
I fixed mine earlier by using the Comodo DNS (or whatever it was). Now today it seems to have broken again.
TCP connection to 64.233.166.125 failed
SteveInWA:
This has been answered over and over. You cannot fix this permanently by changing the DNS. Either buy a new OBi or use the Simonics GVGW, as explained in the two sticky posts in the Google Voice section of this forum.
castaneda247:
Just some final thoughts as I have read through ALL the messages for this post (@SteveInWA ;-).
I switched over to Simonics.com workaround described in a previous post to restore telephone service to 3 locations/OBi100 devices (my own, my parents and my in-laws). For those intimidated by the setup, don't fret, it's simple, so don't go out and buy the latest OBi device if you don't have to. Just follow the instructions laid out in the post and you will be fine.
I'm not convinced, though, of the issue Obihai is reporting with Google making changes, but I also don't want to spent too much time trying to investigate a problem that only takes $6 bucks to fix. The reason I'm skeptical is because Obihai does not seem to have the greatest backdoor communications with Google. Years ago, like 4-5, they said that Google would be discontinuing Google Voice and that we'd all have to move to some other service. Well, that was a major blunder on their part as Google Voice never went offline and still continues to this very day. Wish I still had that message they put out.
My service only recently went offline (like as of 12/3/17 or 12/4/17) when others reported it over a month ago and Obihai posting the cause of the issue on 11/7/17 on their blog. So why did mine still continue to work when Google supposedly change something.
Something just seems fishy.
Navigation
[0] Message Index
[#] Next page
[*] Previous page