Firmware update for 20x series
RFC3261:
Quote from: SteveInWA on May 12, 2018, 04:07:14 pm
There may still be some stragglers into next week.
There will be stragglers for weeks, months, and perhaps even years, as people have managed to put their OBi in a knot, and then when they try to add a GV connection down the line they will wonder what is going on. It is the nature of such roll outs.
Oh, and never forget, there will be a few firmware updates that fail due to hardware issues (there always are a few), and the new firmware will be blamed for turning a perfectly fine OBi2xx into a brick (just like what happened to their OBi1xx all those years ago, and it will just feed into the great conspiracy theory that has been built up).
chilirock:
Quote from: bucksitter on May 12, 2018, 11:38:36 am
After not seeing my Obi 200's firmware update into today, based on a tip from someone over at Howard Forums I accessed my Obi's embedded web page and after verifying still having v3.2.1, I clicked on the Reboot button at the top right of the page. Watched the Obi's lights do a dance for a very short period of time, then checked firmware version. Might have needed to refresh the page again, but within a minute I was able to verify it'd changed to v3.2.2. GV Legacy Settings is showing the ObiTalk device now instead of Chat. This may or may not be the key for some users.
This also worked for a family member of mine whose whose device was still on v5794EX as of this morning. All provisioning settings were enabled, yet it still hadn't received the update. A simple reboot initiated from the local web page UI triggered the upgrade. It's now on v5859EX.
chilirock:
Quote from: SteveInWA on May 11, 2018, 10:25:22 pm
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.
Steve, Well my device finally did upgrade on it's own after all on Friday morning. So factory resetting and re-adding it to the ObiTalk portal didn't trigger the update, at least not for me. It took somewhere between 24-36 hours after that process for the upgrade to get pushed. It just must not have been ready yet. It's working fine for me now. I'll have to keep the change in mind that you mentioned above to FirmwareURL in case things get stuck in the future.
Another device I manage for a family member has one small issue. The family member's Obi200 device is setup to use CallCentric for all inbound and outbound calls. He is now having issues picking up voicemail left on CallCentric. Normally dialing *123 would go into the CC voicemail system to retrieve messages. After the upgrade to v5859EX , dialing *123 results in 5-6 seconds of dead air before a fast busy sound. I checked the CC call records and there is no record of the call, as though it is never sent from the Obi to CC.
Do you think I accidentally changed something in the settings? Any ideas of why it won't go into voicemail or what settings to check?
ma678:
Hi Steve,
I followed your instruction and received 3.2.2 Build 5859EX successfully. Thank you!
Quote from: SteveInWA on May 11, 2018, 10:30:21 pm
Quote from: ma678 on May 11, 2018, 08:56:31 pm
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.
All OBi 200/202 ATAs, and all OBi IP phones, are being pushed the new firmware, regardless of warranty or extended support status. As long as the OBiTALK provisioning system can reach the device, it'll be upgraded. This particular update has supposedly now gone out to all those devices, so if yours has/have not yet been upgraded, then you will need to delete the device off of the OBiTALK web portal, restore it to factory defaults, add it back to the portal, and finally, set up Google Voice again.
SteveInWA:
Quote from: chilirock on May 12, 2018, 06:19:03 pm
Quote from: SteveInWA on May 11, 2018, 10:25:22 pm
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.
Steve, Well my device finally did upgrade on it's own after all on Friday morning. So factory resetting and re-adding it to the ObiTalk portal didn't trigger the update, at least not for me. It took somewhere between 24-36 hours after that process for the upgrade to get pushed. It just must not have been ready yet. It's working fine for me now. I'll have to keep the change in mind that you mentioned above to FirmwareURL in case things get stuck in the future.
Another device I manage for a family member has one small issue. The family member's Obi200 device is setup to use CallCentric for all inbound and outbound calls. He is now having issues picking up voicemail left on CallCentric. Normally dialing *123 would go into the CC voicemail system to retrieve messages. After the upgrade to v5859EX , dialing *123 results in 5-6 seconds of dead air before a fast busy sound. I checked the CC call records and there is no record of the call, as though it is never sent from the Obi to CC.
Do you think I accidentally changed something in the settings? Any ideas of why it won't go into voicemail or what settings to check?
Pulling the power plug and power-cycling it would have done the same thing as rebooting it from the local web server page.
Regarding Callcentric, check the DTMF method setting. It should be set to "Auto", which is the default setting when using the OBiTALK portal with its Callcentric configuration template.
But, that setting usually comes into play AFTER you connect to the called party, and you are saying that the friend can't even key in *123 to reach CC VM? That's sounds like a digit map problem. Can it call ANY number?
Navigation
[0] Message Index
[#] Next page
[*] Previous page