Updated firmware OBi 200/202/212 devices?

[SteveInWA]

The non-trivial part would be distributing the update(s) via a combination of pushing to devices that are enabled for remote updates, posting links for manual downloads of the firmware, and dealing with the thousands of people who have disabled updates without understanding what they've done, and then ranting and raging.  It's going to be a shit-storm.

Don't forget the non-zero number of customers whose OBi's will fail the firmware update and/or the reboot (the flash programming fails, the power supply is right at the edge such that a reboot pushes it over, etc.).

"The firmware bricked my OBi!" will be the new rant of the day.

I wonder if Poly has a canary deployment process as part of their firmware pushes so that the thundering herd issue can at least be mitigated.

Best case:  since only the certificate needs to be replaced in the firmware, it should simply work.  Of course, as you point out too, there will be a lot of failures to update for one reason or another.

Unfortunately, there is no way to "beta test" the fix.  The only way to test it would be to update the firmware on a device, which would then make it unable to authenticate with Google's servers until after Google also updates the servers with the new certificate.  Conversely, if Google replaced the certificate on their servers now, all of the currently-working devices would fail to authenticate until they are updated.  There are additional details that preclude testing in advance, but this summarizes it.

As soon as I have any new information to share, I'll post it here:

https://support.google.com/voice/thread/114914789

[MSRobi]

I've seen that post when you first announced it.  It shows at the top of the post "6/26/21".  I now see at the bottom of it "last edited 6 days ago".  I also see the changed wording there that "Poly is working on a new firmware release.", which is a big deal that you have confirmation that they are working on the update.

[RFC3261]

Unfortunately, there is no way to "beta test" the fix.

Are you sure about that?

Proper x509 certification validation supports multiple root certificates and chains, all of which can be in various stages of being valid, becoming valid, and becoming expired.  That is the entire point of the entire x509 ecosystem.

To not support multiple x509 certificates and chains would mean Poly engineers are brain dead (which, I suppose, is possible).

[lrosenman]

Based on the banner on obitalk.com, the new Firmware is out and will be auto-updated 8/5/2021 at 17:00 PDT.  You can also do the update NOW by following the instructions in the link in the banner.

[Andy_Shiekh]

Much appreciated

https://www.poly.com/us/en/support/knowledge-base/kb-article-page?lang=en_US&urlName=OBi1K-Phones-OBi2K-Phones-and-OBi2xx-Series-ATA-Device-Manual-Update-Instructions-For-Latest-Firmware-Version

I am delighted that I can keep on using Google Voice

[Taoman]

Just wondering if anyone can get a Trunk Group to work as a PrimaryLine with the 8680EX firmware? For me this still doesn't work. I had downgraded to 5859EX to get Trunk Groups working. But now, because of the Google root certificate issue, I'm forced to upgrade.

@azrobert
Don't you use Trunk Groups? Do they work for you as a PrimaryLine?

[azrobert]

TGs never worked for me. Maybe not never, but a very long time. The circumvention is not to use {(Mpli):pli). I use {(Mtg1):tg1}. I'm not sure if you need to change the Phone DigitMap.

This is working for me on 8680EX.

The symptom when using the Primary Line was no dial tone.

[MSRobi]

I have an Obi202 device.  I downloaded the firmware OBi2xx-3-2-2-8680EX.fw from obitalk.com.

I logged into my local web config (http://192.168.249.5), followed the instructions and applied the new firmware.

After it successfully applied itself and rebooted, everything is working properly except now when I try to access the local web page, it comes back with "The requested URL was not found!".  I know that the device is still on 192.168.249.5 since I have the obi202 assigned as a static IP.  I also double-checked by  ***1 on my phone and heard it say the IP address is 192.168.249.5.

Another interesting tidbit...the title of the page (on the browser tab) shows "Obi1000".  My  OBi dashboard looks good, everything shows up as "Connected".  My settings look fine and were untouched by the firmware update.

Anybody else have this happen to them?  Any suggestions on workarounds or fixes to get local access to obi config?

UPDATE: I figured it out, see my next post.

[MSRobi]

I misunderstood the instructions on updating the firmware.  This is very important (but admittedly confusing):

"NOTE:  For the OBi202 ATA Device model, to access the integral local web-page via the WAN port (if prompted), at phone plugged-in, dial:  ***0, 30#, 1, 1# and 1."

Basically what it is doing is enabling local web config, which is disabled after the firmware update.  I had to pause after entering "***" and listen for obi to respond "Device configuration menu" before I entered "0" (you can enter "0" as soon as you hear the response).  When you enter "30#", it should respond with "option 30 current value is disabled...", then you press 1 to enter the new value, then "1#" to enable option 30, then "1" to save the new value.

The "(if prompted)" is what threw me off initially.  Nothing prompted me after the firmware successfully updated.

[Taoman]

Anybody else have this happen to them?  Any suggestions on workarounds or fixes to get local access to obi config?

Happens to everyone with an OBi202. In addition to enabling web gui access from the LAN port I would suggest switching your OBi202 to bridge mode. Otherwise you will have a Double NAT going on which is to be avoided if it isn't necessary.

From the local web gui:
Router Configuration-->LAN settings-->OperationMode

[drgeoff]

I also got the "The requested URL was not found!" response from my browser even though I had obviously used it just a few minutes previously to initiate the firmware upgrade.  That setting to enable WAN access is also available via Expert Mode on the portal (if Obitalk Provisioning has not been disabled) so I used that.

Not clear why the upgrade changes that setting.  I haven't done an exhaustive check but I didn't notice any other config changes.

[drgeoff]

Anybody else have this happen to them?  Any suggestions on workarounds or fixes to get local access to obi config?

Happens to everyone with an OBi202. In addition to enabling web gui access from the LAN port I would suggest switching your OBi202 to bridge mode. Otherwise you will have a Double NAT going on which is to be avoided if it isn't necessary.

From the local web gui:
Router Configuration-->LAN settings-->OperationMode

I'm not convinced that the "SIP stuff" would be double NATted.  No doubt though about anything fed from the 202's LAN jack.

[Taoman]

I'm not convinced that the "SIP stuff" would be double NATted.

Had not really thought about it but you could be right.

If you have an OBi202 and it was in "bridge" mode then the firmware update would have also switched it back to router mode.

[MSRobi]

I also got the "The requested URL was not found!" response from my browser even though I had obviously used it just a few minutes previously to initiate the firmware upgrade.  That setting to enable WAN access is also available via Expert Mode on the portal (if Obitalk Provisioning has not been disabled) so I used that.

Not clear why the upgrade changes that setting.  I haven't done an exhaustive check but I didn't notice any other config changes.

I just went into OBI Expert -> System Management -> Device Admin.  I saw that "AccessFromWAN" was unchecked.  Since I have Obitalk provisioning enabled, I made the change to have AccessFromWAN checked.  This is better than the recommended enabling by phone (***0, 30#), because when I make future changes in OBi Expert, I don't have to worry about provisioning resetting my local web access to disabled.

[MSRobi]

I'm not convinced that the "SIP stuff" would be double NATted.  No doubt though about anything fed from the 202's LAN jack.

Since I have nothing plugged into my 202's LAN jack, the LAN settings are probably irrelevant in my case.

[DocHudson]

Since I didn't want to do manual updates (for the fear of messing something up), I let auto-update and for the last 2 days, I am getting flashing red/green lights. Obitalk portal shows Obi 200 offline so does the router admin page.

I tried resetting by power cycling and using the reset button but didn't work.

Do I have any option to upgrade the firmware (using a USB port may be) and make this Obi 200 usable again?

Thanks in advance.

(If this question is already discussed, pls direct me. I tried searching but found nothing.)

[drgeoff]

Since I didn't want to do manual updates (for the fear of messing something up), I let auto-update and for the last 2 days, I am getting flashing red/green lights. Obitalk portal shows Obi 200 offline so does the router admin page.

I tried resetting by power cycling and using the reset button but didn't work.

Do I have any option to upgrade the firmware (using a USB port may be) and make this Obi 200 usable again?

Thanks in advance.

(If this question is already discussed, pls direct me. I tried searching but found nothing.)

Perhaps the discussion you started last year is relevant. http://www.obitalk.com/forum/index.php?topic=17609.msg105715#msg105715

Your search also failed to find https://www.obitalk.com/info/support/troubleshooting

[DocHudson]

Perhaps the discussion you started last year is relevant. http://www.obitalk.com/forum/index.php?topic=17609.msg105715#msg105715

Your search also failed to find https://www.obitalk.com/info/support/troubleshooting

Thank you very much for highlighting the posts.

Here, my previous post is irrelevant, because at that time I used to power cycle. I have stopped it since then.
For the second link (which I had already checked), if you reread my post, I have stated that Obi200 is offline in router admin as well i.e. I can't figure out the IP address to perform a manual update.

I tried hard reset a couple of times, but it has been unsuccessful. It fails at stage 3 of step 2. After 10 seconds of holding the reset pin down and powering up, the Power LED should start flashing green (slowly) but instead, it goes blank. If I release the reset pin then, it cycles back to flashing red and green. If I understand correctly, it fails to perform reset.

Not too sure if there is anything else that can be done.

[drgeoff]

The relevance of the previous thread is the power LED alternating between red and green.  At boot time a checksum is calculated over the contents of the firmware and compared with what it should be.  The expected value is also stored in the firmware.  A mismatch means the firmware is corrupt and is reported to the user by the red-green power LED.

The only published method for an end-user to attempt .rectification is the one reached by following the troubleshooting link.

If you actually mean that now the power LED is alternating between red and off while one or both of the other LEDs is/are blinking/flashing, that is a different situation

[SoNic67]

I misunderstood the instructions on updating the firmware.  This is very important (but admittedly confusing):

"NOTE:  For the OBi202 ATA Device model, to access the integral local web-page via the WAN port (if prompted), at phone plugged-in, dial:  ***0, 30#, 1, 1# and 1."

Basically what it is doing is enabling local web config, which is disabled after the firmware update.  I had to pause after entering "***" and listen for obi to respond "Device configuration menu" before I entered "0" (you can enter "0" as soon as you hear the response).  When you enter "30#", it should respond with "option 30 current value is disabled...", then you press 1 to enter the new value, then "1#" to enable option 30, then "1" to save the new value.

The "(if prompted)" is what threw me off initially.  Nothing prompted me after the firmware successfully updated.

Thank you! That was throwing me off too!