Firmware update for 20x series
LTN1:
My OBi202, though out of warranty, is set to automatically update. I've been rebooting it every day to see if 5898 would be updated but nothing yet. It's not a big deal...everything works even with 5897.
SteveInWA:
Quote from: LTN1 on July 11, 2018, 04:38:10 pm
My OBi202, though out of warranty, is set to automatically update. I've been rebooting it every day to see if 5898 would be updated but nothing yet. It's not a big deal...everything works even with 5897.
"set to automatically update"....
There was a widely-held belief, myself included, that making various settings changes to the values on the "System management-->Auto provisioning" tab would either disable or allow firmware updates. In particular, at one time, the portal inserted a Boolean string that tested to see if the existing firmware build was older than some given build, and would then, in theory, upgrade it. OBiTALK is no longer inserting that string,and, in fact, it can actually cause the device to downgrade its firmware, if it is set to a lower value than one that you manually install.
The current behavior, as far as I can tell, is that, as long as you have your device(s) attached to the OBiTALK portal, they'll receive firmware updates, if you have that page set to the current defaults. If you have a value in the "Firmware URL" field, delete it, and set the entire page to "OBiTALK defaults". (I'd post a screenshot, but the forum software isn't allowing it).
AFAIK, this configuration page is only intended for managed service provider use. In theory, one could use it to remotely upgrade a unit to a specific, known firmware stored at a specific location, but that's not what it's used for by default.
LTN1:
Thanks, Steve. I'm going through the portal and everything is set to the OBiTALK Settings. Everything is working as it should. Was at 5859 until a week ago and since then, have not gone above 5897. Unfortunately, I can't attach screenshots at this time either.
LTN1:
Just received the update to 5898 a few minutes ago. I happened to be right in front of the OBi device when it was updating--so was able to confirm it after the automatic reboot. Tested with a call and everything continues to function properly.
madhatter:
SoftwareVersion 3.2.2 (Build: 5898EX) has fixed several problems on my end. Obi not ringing being the main problem. I noticed that the GMAIL account in my OBITALK portal had been changed. I have a gmail account for email and a separate one for GV. The GV account got CHANGED to the email account. How strange is that? I didn't make that change.
I deleted the GV SP1 record and recreated it. After doing this, the 200 would not reconfigure GV. The CONFIGURING message just went into an endless loop. I unplugged the 200 waited 15 seconds and plugged it back in. The OBI200 then went through a series of reboots (red power light, etc.) and when it finally settled down after about 3-5 minutes everything was working fine.
HTH
Navigation
[0] Message Index
[#] Next page
[*] Previous page