Firmware update for 20x series
SteveInWA:
Quote from: Webslinger on May 11, 2018, 10:23:01 am
Is 3.2.2 (Build: 5859EX) being pushed to all OBi2xx ATA owners who have Obitalk Service, Obitalk Provisioning, and Auto Firmware Update enabled? Or is it only being sent to certain regions at a time?
I'm seeing a couple of instances where it's not being pushed.
It's being pushed to all devices. It's a phased roll-out. I was told it would be completed by today or tomorrow. If yours isn't upgraded by Monday, you may want to consider deleting it off of your OBiTALK dashboard, factory-restoring it to defaults, and then re-adding it.
Webslinger:
Quote from: SteveInWA on May 11, 2018, 02:28:27 pm
It's being pushed to all devices. It's a phased roll-out. I was told it would be completed by today or tomorrow. If yours isn't upgraded by Monday, you may want to consider deleting it off of your OBiTALK dashboard, factory-restoring it to defaults, and then re-adding it.
Thanks
ma678:
Will Obi push out 3.2.2 B5859EX regardless 200/202 is under or out of warranty? Which fw should I stay before receiving OTA? I am currently on 3.2.1 B5757EX.
Thanks.
restamp:
FWIW, my 202 is out of warranty and was running 5757EX. Yesterday, at SteveofWA's urging, I saved and imported my configuration to OBiTalk, set the 202 to update on boot, and booted it. It came up on 5859EX after the boot, and even retained the passwords across the upgrade. The GV line and one SIP service came up immediately. It took a bit of finagling to get the other two services going, one simple, the other atypical setup was more involved. On the whole, I'd say the OBi programmers did a good job of engineering this major upgrade.
SteveInWA:
Quote from: chilirock on May 09, 2018, 07:35:37 am
Quote from: SteveInWA on May 08, 2018, 04:46:11 pm
I'm unclear why you'd do that. The process is automated. Your OBiTALK configuration will get updated and the new firmware will be pushed to your device. Manually removing and re-adding the device, before your device has been converted, is not likely to work.
Hi Steve, I removed the device, factory reset it, and added it back to the dashboard after all. I wanted to make sure that there weren't any lingering changes that I had made on the local UI settings that may prevent the firmware update from being pushed down. After completing the above steps, the firmware remained at v5757EX. I did notice that the FirmwareURL under the Auto Firmware Update section was updated from IF ( $FWV <3.2.1.5757EX...) to IF ( $FWV < 3.2.2.5853...). Perhaps that will trigger an update the next time the Obi checks. For now, I'll hang tight and let the kinks get worked out.
Actually, I re-discovered a self-inflicted bug yesterday, on a friend's 200. We had previously changed that setting, without really understanding how it works. Yesterday, his 200 had the orange triangle on the OBiTALK dashboard. I clicked it, it upgraded, and then presented another orange triangle. I clicked it, it DOWNgraded, and displayed the triangle again. What it was doing was alternately doing "upgrades" based on the incorrect syntax of that setting. Simply blanking out that field and checking the OBiTALK default setting and submitting, fixed it, and it immediately upgraded to the correct build. So, just erase that field and hopefully, you'll be good to go.
Navigation
[0] Message Index
[#] Next page
[*] Previous page