December 17, 2017, 12:08:33 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: 1 ... 5 6 [7]
  Print  
Author Topic: TCP connection to 125.141.125.74 failed  (Read 17506 times)
samsungs70
Newbie
*
Posts: 2


« Reply #120 on: December 13, 2017, 02:07:20 pm »

How do you change the DNS settings?

There is no point to changing DNS settings.  It will not solve this problem.

Read:

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

and

http://www.obitalk.com/forum/index.php?topic=13147.0
Hello Steve,
I followed the instruction to use Simonics service. I paid $6. It worked for a few days. It's still working but I got non-stop incoming calls from weird numbers shown on my phone display: phone number #1: 8004
phone number #2: 4-131-528-1818
phone number #3: 00390239297988
These are not human made calls because as soon as I power the Obi, I got incoming calls. Pick them up: no one answers from the other end. Then the calls are disconnected by themselves.
Does anyone experience this? Thanks.


Yes, an issue many have experienced -- check out this post to evade the scanners:

https://www.obitalk.com/forum/index.php?topic=13278.msg85407#msg85407

On an unrelated note, per chance have you dialed any Google Voice phone numbers? Several of us are experiencing issues in not being able to call folks from our Obi devices (see here: https://www.obitalk.com/forum/index.php?topic=13310.0)
Thanks, I fixed it and am still monitoring the situation. And no, I'm not aware of the other problem (calling obi devices).
Logged
Goldenmeadow
Jr. Member
**
Posts: 20


« Reply #121 on: December 13, 2017, 04:07:40 pm »

Hi everyone!

Here we go again...
Today my GV in Obi200 says:
TCP connection to 125.166.233.64 failed

after refreshing page:
TCP connection to 125.133.125.74 failed

I guess it's trying several servers...

Changing DNS values didn't help (as Steve was saying last time). Am I the only one?

Thanks


UPDATE: I fixed by flashing latest firmware. So if someone has the same problem - get latest firmware for your Obi Smiley
« Last Edit: December 13, 2017, 04:16:00 pm by Goldenmeadow » Logged
Taoman
Hero Member
*****
Posts: 945


« Reply #122 on: December 13, 2017, 04:13:42 pm »


Changing DNS values didn't help (as Steve was saying last time). Am I the only one?


What firmware version are you on with your OBi200?
Logged
Goldenmeadow
Jr. Member
**
Posts: 20


« Reply #123 on: December 13, 2017, 04:16:53 pm »


Changing DNS values didn't help (as Steve was saying last time). Am I the only one?


What firmware version are you on with your OBi200?

It was older version Smiley I just updated it and everything works Smiley  Thanks for such prompt reply!!!
Logged
miketexas
Newbie
*
Posts: 1


« Reply #124 on: December 15, 2017, 04:09:40 pm »

OBI100 here. DNS did not work for me, as Steve what's-his-name keeps telling everyone. When I  log in for the Simonics service, I get this message:

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

Oh well. I'm not interested in purchasing yet another piece of hardware that will work just fine yet somehow be deemed obsolete and thus unsupported. It's maddening to have to junk a perfectly good device.
Logged
Lavarock7
Sr. Member
****
Posts: 481



« Reply #125 on: December 16, 2017, 06:19:28 am »

MY uneducated guess is that the DNS trick only worked because some DNS servers had not pointed to places with the new certificates. It was a hack someone found and people took it for a cure.

The 110 should still work, just not with GV. You could pay a buck or two a month and use it with a real SIP provider; yes one that you have to pay to use.

The Simonics gateway will be up again fairly soon.

Logged

My websites: Kona Coffee: http://ItsKona.Com and Web Hosting: http://PlanetAloha.Info
A simplified Voip explanation: http://voip.planet-aloha.com
Pages: 1 ... 5 6 [7]
  Print  
 
Jump to:  

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