December 16, 2017, 06:16:13 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: 1 ... 3 4 [5] 6 7
  Print  
Author Topic: TCP connection to 125.141.125.74 failed  (Read 17443 times)
Stuart_505
Newbie
*
Posts: 3


« Reply #80 on: November 04, 2017, 02:10:36 pm »

This problem started for me sometime last night with my Obi200 (which is connected to Google Voice); I noticed the phone indicator (right hand LED) was off this morning, and started Googling the problem, winding up on this thread.  I've only had my Obi200 since August, and it was working fine up to now.  I had set the device to automatically check for firmware updates by following the directions on this Obitalk webpage:  https://www.obitalk.com/info/faq/Troubleshooting-sec/How-do-I-automate-upgrades   but apparently it had not actually been checking for updates, since my firmware version this morning was 3.1.1.5463.  I tried forcing the update by dialing ***6, but the robot voice told me no updates were available, which I didn't believe based on earlier posts in this thread.  I also looked at some Google results about manually updating the Obi's firmware, but in the Obi Expert configuration settings under System Management, there was no Device Update selection available, so that wouldn't have worked for me.

Anyway, in the Obi Expert menu I inadvertently clicked on the Revert to ObiTALK button, not realizing that it would remove my specific changes in Obi Expert, which were basically the settings for auto updating.  When I realized that, I went back in and reset those selections.  Then I noticed the Obi200 resetting itself a couple of times (the left hand LED going to red), and then it started working again.  When I checked the firmware version (***0, then 1#) I discovered it had updated to 3.2.1.5757.  Outgoing and incoming calls are working again, and the Anveo 911 test says that's all working as well.

Sorry to be so wordy, but I wanted to describe the things which were supposed to be working but weren't.  It appears that a firmware update solved the problem for me.  It's just that I couldn't initiate that update in the way that is supposed to work, and I'm not sure exactly what it was that I did that made it happen.  And without that manual update option, I guess I'm going to have to pay Obihai after next August if I want to keep the Obi200 working.
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 2730


« Reply #81 on: November 04, 2017, 02:30:46 pm »

All you had to do was click the yellow triangle against your OBi200 on your Dashboard.  http://www.obitalk.com/forum/index.php?topic=13113.msg84139#msg84139

The other update methods do normally work but Obihai has by necessity pushed this update out very quickly.
Logged
Stuart_505
Newbie
*
Posts: 3


« Reply #82 on: November 04, 2017, 04:42:03 pm »

Ah ha, I see the yellow triangle mentioned in two of the posts of the four earlier pages of the thread.  I guess I didn't realize the significance because at the time I didn't realize my Obi200 wasn't updating itself.  I don't remember seeing a yellow triangle on the Obitalk dashboard (of course there isn't one now) but I'm guessing it was there, although if the Obi200 didn't think it needed updating when I did the ***6 thing, maybe not.  Next time something like this happens, I'll know what to look for.  Thanks for letting me know.
Logged
JonX
Newbie
*
Posts: 2


« Reply #83 on: November 05, 2017, 08:11:35 am »

http://fw.obihai.com/OBi202-3-2-1-5757EX.fw

I have an OBi200 with firmware 3.0.1 (Build: 4581) and have seen no issue as of yet with my google voice connections. DNSServer 1 and 2 are blank and default checked. At the OBiTALK online dashboard, google voice SPs are shown as connected. I do have a yellow triangle with an exclamation mark indicating "firmware update." Clicking on and selecting cancel I get redirected to a form thread that has a link to the latest (http://fw.obihai.com/OBi2-latest.fw which appears to be the same as http://fw.obihai.com/OBi202-3-1-1-5463EX.fw) which when I download appears to be version  OBi2XX_FW_PACK00
v3.1.1 (Build: 5463EX) (MD5SUM: b7c15c8a7146e27795cbc4a050165f59). From a forum search it appears this was released sometime in Dec 2016 or before. If I had clicked "ok" instead of "cancel" I'm not sure what version would be installed.

I've seen reference to OBi 2xx series: 3.2.1 (Build: 5757EX) (http://www.obitalk.com/forum/index.php?topic=13113.msg84139#msg84139) as a fix which seems to be found at:

   http://fw.obihai.com/OBi202-3-2-1-5757EX.fw

(MD5SUM: f5e249b85b99f29bf9b94c651161d16e).

A thread wiki for this issue would be nice.


Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 2730


« Reply #84 on: November 05, 2017, 08:32:16 am »

http://fw.obihai.com/OBi202-3-2-1-5757EX.fw

I have an OBi200 with firmware 3.0.1 (Build: 4581) and have seen no issue as of yet with my google voice connections. DNSServer 1 and 2 are blank and default checked. At the OBiTALK online dashboard, google voice SPs are shown as connected. I do have a yellow triangle with an exclamation mark indicating "firmware update." Clicking on and selecting cancel I get redirected to a form thread that has a link to the latest (http://fw.obihai.com/OBi2-latest.fw which appears to be the same as http://fw.obihai.com/OBi202-3-1-1-5463EX.fw) which when I download appears to be version  OBi2XX_FW_PACK00
v3.1.1 (Build: 5463EX) (MD5SUM: b7c15c8a7146e27795cbc4a050165f59). From a forum search it appears this was released sometime in Dec 2016 or before. If I had clicked "ok" instead of "cancel" I'm not sure what version would be installed.

I've seen reference to OBi 2xx series: 3.2.1 (Build: 5757EX) (http://www.obitalk.com/forum/index.php?topic=13113.msg84139#msg84139) as a fix which seems to be found at:

   http://fw.obihai.com/OBi202-3-2-1-5757EX.fw

(MD5SUM: f5e249b85b99f29bf9b94c651161d16e).

A thread wiki for this issue would be nice.



Just click the yellow triangle, click OK and get on with the rest of your life.
Logged
Troyer
Newbie
*
Posts: 1


« Reply #85 on: November 05, 2017, 10:01:48 am »

There wasn't a firmware update available for my 200, but changing the DNSServer1 to 4.2.2.2 corrected the problem.
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 2730


« Reply #86 on: November 05, 2017, 10:10:14 am »

There wasn't a firmware update available for my 200, but changing the DNSServer1 to 4.2.2.2 corrected the problem.
How many times does it have to be said!!!???

This is not a DNS problem and changing DNS is not a lasting fix.

For an OBi200 you need firmware 3.2.1 (Build: 5757EX).  Currently the only way to get that is log into your Dashboard at obitalk.com and click the yellow triangle.

http://www.obitalk.com/forum/index.php?topic=13113.msg84139#msg84139
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #87 on: November 05, 2017, 03:43:12 pm »


How many times does it have to be said!!!???


If only people with "write only memory" would stop posting the same nonsense again and again, but I guess that's too much to expect.


* Midvale School.jpg (39.43 KB, 321x266 - viewed 65 times.)
Logged

Brenda72
Newbie
*
Posts: 4


« Reply #88 on: November 06, 2017, 12:08:30 pm »

I am confused by this.  I have an Obi100

What do I need to do to get my service working again?  Everyone is talking about the Obi200 but I have Obi100
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #89 on: November 06, 2017, 12:23:39 pm »

I am confused by this.  I have an Obi100

What do I need to do to get my service working again?  Everyone is talking about the Obi200 but I have Obi100

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

Logged

mstbone67a
Newbie
*
Posts: 1


« Reply #90 on: November 07, 2017, 04:32:19 pm »

 well poop sticks.  interesting read about using a rpi for a fix.
https://narahari.wordpress.com/2017/11/07/obi110-reuse-using-raspbx-how/

Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #91 on: November 07, 2017, 04:53:21 pm »

well poop sticks.  interesting read about using a rpi for a fix.
https://narahari.wordpress.com/2017/11/07/obi110-reuse-using-raspbx-how/



Take note:  that solution uses the outdated and less-secure Google account login method, with a userID and password stored on the Pi.  Doing that gives that box full access to everything on that Google account.  Google strongly discourages it. 

By contrast, OBi devices and the Simonics GVGW use the Google-approved OAUTH 2.0 authentication, which only grants access to the XMPP service on the Google account.  No Google account password is stored on the device.
Logged

omegastar
Newbie
*
Posts: 1


« Reply #92 on: November 07, 2017, 07:03:29 pm »

So I take it ObiTalk is gonna screw all the OBI110 owners now. Cant see how they still sell this device but dont support it.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #93 on: November 07, 2017, 07:04:48 pm »

So I take it ObiTalk is gonna screw all the OBI110 owners now. Cant see how they still sell this device but dont support it.

They don't still sell the device.  Any that you might find for sale are not being sold by authorized retailers.

I predict that a metric ton of used 100s and 110s will appear for sale on Craigslist and eBay soon.
Logged

GPz1100
Full Member
***
Posts: 121


« Reply #94 on: November 07, 2017, 07:33:56 pm »

This solves the issue of Oauth 2 for the Raspberry Pi Zero W.

http://nerdvittles.com/?p=21777

The $6 gateway option will save you days in terms of configuration time.

Asterisk 14.7 and above already has direct support for oauth 2 (for manually edited config files).  Presently it's a matter of the motif module getting updated to support this in freepbx flavors.
Logged
Icall
Newbie
*
Posts: 2


« Reply #95 on: November 08, 2017, 06:44:03 am »

Thanks @GPZ1100. I will be updating my setup to remove app password with the Oauth2. Found some info here. http://www.dslreports.com/forum/r30021383-Upgrade-Asterisk-to-an-OAUTH2-0-connection-with-Google-Voice~start=30
Logged
adymax
Newbie
*
Posts: 3


« Reply #96 on: November 08, 2017, 06:44:47 pm »

Just got this issue today, Changing the DNS IPs on the router to 8.26.56.26 & 8.20.247.20 fixed it for me. Thank you all for your help!
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #97 on: November 08, 2017, 06:46:28 pm »

Just got this issue today, Changing the DNS IPs on the router to 8.26.56.26 & 8.20.247.20 fixed it for me. Thank you all for your help!

This is not a DNS issue.  Eventually, yours will fail.

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

adymax
Newbie
*
Posts: 3


« Reply #98 on: November 08, 2017, 07:13:22 pm »

If that's the case I  have OBI100 so no FW update for us?
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3973



« Reply #99 on: November 08, 2017, 07:18:54 pm »

If that's the case I  have OBI100 so no FW update for us?

I explained it, right in the linked post, along with a workaround.
Logged

Pages: 1 ... 3 4 [5] 6 7
  Print  
 
Jump to:  

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