Firmware update for 20x series
JohnRadu:
After spending hours trying to fix a seemingly defective automatic firmware update (power light flashed green, then after unplugging/replugging flashed red/green), I finally found a solution that worked for me. It does not seem like the flashing process is the problem. The problem seems to be when the device reboots and tries to reinitialize. That's when it gets hung up.
The solution: Factory-Reset. (***Note: it may take several factory resets to actually get solid green power light***)
Instructions: https://www.obitalk.com/info/faq/Troubleshooting-sec/How-to-Factory-Reset
I really had to factory reset several times for it to finally boot up correctly and have a solid power light, but then I was able to re-register the device on obitalk.com and been working like a charm. Hope this helps.
zorlac:
Quote from: RFC3261 on May 15, 2018, 10:59:31 am
Quote from: zorlac on May 14, 2018, 07:02:25 pm
But I'd still be able to flash the obi fw if I could just get the stupid file!
Perhaps I am reading too much into the words, but it seems to me that those that are paid by the companies involved (either directly, or indirectly) have made it pretty clear that if you want to use an OBi (especially with GV), you are going to have to learn to live within their ecosystem and the way they have chosen to move forward and deliver service. If you do not like what Obihai and Google are doing (and some will not), you should probably start the planning of your move to one of the alternatives available to you. A number of vendors (some actively participating on this board) have offered to help you move to their service(s). The OBi devices (and/or the GV service) were never for everyone.
Then why not just take away the ability to upload a fw file directly to the device (the fw update ability is still available with the current fw)? If the manufacturer doesn't want provide access to the fw files having a user flash routine is rather pointless isn't it? Also, the device's fw is something that can affect normal sip services not just GV.
If you go back to the beginning of this topic you'll see that the fw was pretty readily available years ago not to mention quite a few active links to outdated fw.
If they provided a normal ftp site at least the fw revisions would be in some type of logical hierarchy.
On a more positive note, I was on the phone today for over two hours with two different people and the annoying delay that makes GV pretty frustrating at times has been GREATLY reduced, less than probably 1/2 what it used to be. So this update was certainly a BIG improvement for GV IMO!!
FWIW, these stats used to be a lot worse with this amount of data.
RFC3261:
Quote from: zorlac on May 15, 2018, 08:24:12 pm
Then why not ...
As you state, Obihai decided to end formal firmware distribution to customers not using their automated upgrades (or via partners who have a different contractual arrangement) quite a long time ago. That some people that participate here have managed to "guess" the new firmware locations, and then share how to access them, is not a fully supported solution. It just happened to work. Times may change. It is impossible to accurately predict the future. Polycom (last I knew) offers free downloads of firmware, but charges substantially more upfront (which presumably helps pays for the future software development). That is certainly one way to move forward. Another is to keep the lower upfront cost and move to a more formal licensing model for future software updates. The fact that Obihai decided in this case to release the firmware for the new (and improved?) GV integration for free via their automated processes is a really nice gift. I would have fully expected to have to pay for that upgrade (I had been using the device for many years without paying a dime for that software development work). In any case, their business, their choices, so all we can do is wait and see what happens. If the current situation, or any changes, are not to ones liking, it will be time to move on to another solution that meets ones expectations.
ma678:
It seems GV took sometime to settle up. Now all accounts connect without any drops.
Quote from: SteveInWA on May 13, 2018, 12:06:26 am
Quote from: ma678 on May 12, 2018, 10:43:53 pm
My three GV accounts show "Connecting to 64.9.240.172" every few minutes. May I change setting anywhere to keep alive interval longer?
Thanks.
NO. Do NOT change the keep-alive interval. Google Voice will specifically block connections if the endpoint is sending rapid keep-alives. Leave it at the default. In fact, the error you describe can be caused by changing the keep-alive settings.
If you can't get your device to connect and stay connected, then delete it off of the OBiTALK portal, restore it to factory defaults, re-add it to the portal, and re-configure Google Voice. Do not make any "expert mode" changes to the Google Voice SPx settings.
NomadTech:
Quote from: zorlac on May 14, 2018, 11:42:04 am
Is there a working url for their ftp sever to download the latest revision of fw?
I wish they had a normal ftp site that I could peruse. :-[
This works: http://fw.obihai.com/OBi202-3-2-1-5794EX.fw
But this doesn't: http://fw.obihai.com/OBi202-3-2-2-5859EX.fw
Thanks
Try this https://www.obitalk.com/images/OBi202-3-2-2-5857EX-19283837473.fw and don't worry abou it saying 5857 as it is 5859. I am using it on my second OBI202 that didn't update no matter what I did, while the first one did.
Navigation
[0] Message Index
[#] Next page
[*] Previous page