Started by GreenView, October 05, 2017, 02:07:42 PM
Quote from: kevin-in-sa on October 30, 2017, 08:48:14 AMUPDATE: I just ran across this announcement from OBi - http://blog.obihai.com/2016/08/end-of-life-announcement-obi100-and.html
Quote from: Lensor on October 31, 2017, 05:48:02 PMI used the IP lookup at www.ultratools.com/tools/ipWhoisLookup and found the IP reported in the error that I see is in a block owned by a company called BIGLOBE Inc. in Tokyo. The IP in the title of this one appears to be from KR.
Quote from: Ryan_Chicago on October 31, 2017, 07:38:15 PMSame here with my Obi 110 attempting to reconnect to Google Voice (GV) Backing Off : TCP connection to 22.214.171.124 failedBacking Off : TCP connection to 126.96.36.199 failedIs this because Google has permanently shutdown their XMPP API?https://cloud.google.com/appengine/docs/deprecations/xmppI fear all of the Obi GV users may be SOL.
Quote from: FireSQer on October 31, 2017, 08:47:37 PMI followed these directions on two different boxes with great success:https://www.obitalk.com/info/faq/GV-and-the-OBi/Using-openDNS-GV-Status-BackingOffQuick summary:1. Log into obitalk.com2. Choose Obi Expert Configuration3. Choose Enter Obi Expert4. Click on System Management5. Choose WAN Settings6. UNcheck ObiTalk Settings by DNSServer17. UNcheck Device Default8. Enter 188.8.131.52 in DNSServer1 field9. Scroll to bottom and SubmitI also upgraded firmware while I was at it. 10. Back to the Obi Dashboard. 11. Click on the yellow triangle to upgrade firmware.Now I'm dialing out as well as receiving calls.HTH.Mike