Firmware update for 20x series
chilirock:
Quote from: SteveInWA on May 08, 2018, 09:54:30 am
In any case, your device should receive the new Google Voice firmware soon -- there isn't any way to trigger it manually. I'd suggest setting OBiTALK provisioning and auto firmware update to "periodically".
The first time a device with the new firmware connects to Google's network, it will automatically upgrade the service on the Google Voice side.
Steve, thanks for the reply. Based on your response, it sounds like the Obi firmware comes first, then the Google Voice>Settings change follow after the Obi connects to GV with the new firmware. While I'm waiting for the update to be pushed, I think I'll try removing the device from the ObiTalk portal, factory resetting, then re-adding the device to the portal to see if that jump starts things. I know in the past this process has triggered the latest firmware to be downloaded.
SteveInWA:
Quote from: chilirock on May 08, 2018, 03:04:15 pm
Quote from: SteveInWA on May 08, 2018, 09:54:30 am
In any case, your device should receive the new Google Voice firmware soon -- there isn't any way to trigger it manually. I'd suggest setting OBiTALK provisioning and auto firmware update to "periodically".
The first time a device with the new firmware connects to Google's network, it will automatically upgrade the service on the Google Voice side.
Steve, thanks for the reply. Based on your response, it sounds like the Obi firmware comes first, then the Google Voice>Settings change follow after the Obi connects to GV with the new firmware. While I'm waiting for the update to be pushed, I think I'll try removing the device from the ObiTalk portal, factory resetting, then re-adding the device to the portal to see if that jump starts things. I know in the past this process has triggered the latest firmware to be downloaded.
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.
I understand you are eager to try it out, but it would be best to wait. There are a couple of bugs being worked on now, and there is nothing to be gained by rushing it. I'm told that the deployment is expected be completed by Friday EOD, but as always, subject to change.
YaddaYaddaObi:
Received the new firmware this week. Now, when I receive a call, it rings once and sends the caller to voice mail. Second issue is that when I call people now it shows me as an unknown caller.
Update: Okay, so I removed the google voice account, factory reset my ObiHai 202 and setup the unit fresh and now everything is working correctly again.
chilirock:
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.
Webslinger:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page