TCP connection to 125.141.125.74 failed
Stuart_505:
I discovered about an hour ago that my Obi200, which somehow got firmware update last weekend to 3.2.1.5757 and has worked fine since, was not working. Checking the firmware version, it seems that it had somehow reverted to 3.1.1.5463. Apparently setting the auto update as I described in an earlier post is a bad idea. To get back to the proper update I chose to try the manual method rather than simply clicking the yellow triangle next to the Obi200, since both should give the same result. I went to http://fw.obihai.com/OBi2-latest.fw and downloaded the update, then entered the Obi200's setup via its web portal using its IP address. When I attempted to update the firmware, I got the message that the update I was trying to apply was the same as the current version. So I went to an earlier post in this thread from JonX and followed the link http://fw.obihai.com/OBi202-3-2-1-5757EX.fw and repeated the update process, and this time got the right update. So this leaves me wondering a couple of things, including, why the link http://fw.obihai.com/OBi2-latest.fw doesn't actually give you the latest firmware; and how to find a specific link to a particular update version. I know drgeoff is just going to tell me to click the yellow triangle and get on with my life, but I'm curious why Obihai doesn't put the latest version in the file they call OBi2-latest.fw.
drgeoff:
Quote from: Stuart_505 on November 12, 2017, 01:26:54 pm
... I'm curious why Obihai doesn't put the latest version in the file they call OBi2-latest.fw.
Just one of the many unanswered questions about Obihai. :)
It is easy to think of Obihai as a company with plenty of staff to do this that and the other but I suspect the reality is rather different. Estimate how many ATAs and phones are bought each month. Estimate how much profit they net from each one. Multiply the two together and divide by how much it costs to employ someone for a month (salary and all the overheads). How many people does that give you?
wecen:
Today I found out that my google voice cant dial out. So I check the forum.
Thank you for "rfryar" message. I tried:
DNSServer1: 4.2.2.2
DNSServer2: 8.8.4.4
It works.
Thank you so much.
DaniloC:
Same for me. I had to put both to start working. Thanks a lot guys for the guidance!
Cheers!
helpful55:
This worked for me (4.2.2.2). Thanks
Quote from: OBiSupport on November 02, 2017, 08:02:58 am
Obihai support team is still looking into this issue. In the mean time, please try the following in your OBiTALK account:
Click your OBi number 510xxxxxx (300XXXXXX, 200XXXXXX, 500XXXXXX, 630XXXXXX, 610XXXXXX, 600XXXXXX).
At SP1, delete your Google Voice account.
Click SP1 again, follow steps to re-authenticate back to your Google Voice account.
When “Connected”, please make test calls in/out.
If status "Backing off..." remain, then click the OBi Expert Configuration blue button at bottom / Enter OBi Expert blue button.
Modify the DNSServer1 parameter value: Select System Management / Network Settings / to DNSServer1 / input 4.2.2.2 (or 8.8.8.8 ).
Click Submit to save and your OBi device will reboot automatically.
Allow up to 1 minute to complete, check your Google Voice status for "Connected" then make test calls.
Please stay tuned and we will do a follow-up.
Thank you and best regards,
Obihai Technology, Inc
Navigation
[0] Message Index
[#] Next page
[*] Previous page