Any considerations required when jumping from 3.0.1 4581 to 3.1.0 5135?
restamp:
I am currently running a fairly old firmware load on my OBi202. It is 4581, which is what was installed when I acquired this little box a little under a year ago. I generally don't upgrade firmware that is not causing me problems (and especially firmware that has no published release notes), but since I am coming up on the date that my OBi will fall out of warranty, I am considering upgrading while the warranty is still in effect.
First, are there any known problems with the latest load (which I believe is 5135)? If so, what are they?
From what I have observed here, the base VoIP functionality in these OBis is pretty well wrung out and there are no major fixes in this area. So, what will I be losing and gaining with such a move? Will I simply be giving up the potential to have OBiPlus for the potential to have OBiExtras?
OBiHAI has been known to sometimes put "diodes" in some of their firmware loads that make it impossible to flash back to an earlier load. Can anyone tell me if that is the case here? If I find a problem with the 5135 load, will I be able to back out to 4581?
What (if anything) will I have to do after upgrading the firmware? Will I have to re-specify passwords? Will my auto-provisioning specs change?
Anything else I should be aware of? I think 4581 is just new enough that I can jump directly to 5135 without going though any intervening steps. Correct?
And finally, can anyone tell me what the significance of the 3.0.1 and 3.1.0 designators is?
Thanks in advance.
SteveInWA:
The firmware upgrade on the 200 series is benign and doesn't alter any of the device's settings. I've upgraded five 200 series devices from that level or older, and it didn't cause any issues. There is no reason at all to downgrade at this point; the current firmware is stable, and hasn't introduced any reported new issues.
restamp:
Thanks, Steve. The upgrade, as you suggested, was uneventful. Honestly I've noticed no difference in the way the box handles calls. None at all. The OBiPlus Service Status is still present on the System Status page after the upgrade, and I noticed some additional items that were saved as part of the backup, probably having to do with the OBiExtras offering.
I used the "***6" method of upgrading. It took a few minutes to complete, but after it finally came up, all my original data was intact -- no need to re-enter passwords or any other data.
I did not try to revert back to the earlier load, so I don't know if that would be allowed.
I did note that there is a new section under Auto Provisioning: LUA Script Update. Anyone know what it does? Since I had all the other auto-provisioning commands Disabled, I disabled this one, too.
But chalk this up as another success with a OBiHAI firmware upgrade. Now, if we could just get them to provide us with some release notes.
Brisk:
Quote from: restamp on March 24, 2016, 07:06:39 pm
The OBiPlus Service Status is still present on the System Status page after the upgrade
Meaningless. 5135 killed OBiPLUS.
So, if you had OBiPLUS firmware, its features no longer work.
"OBiPlus is no longer a supported feature on the OBi.
As such, the extra AAs as you describe, are no longer available." -- OBihai Support
Anyone with OBiPLUS firmware may want to think twice before updating to 5135.
RFC3261:
Quote from: Brisk on March 29, 2016, 06:26:33 am
Quote from: restamp on March 24, 2016, 07:06:39 pm
The OBiPlus Service Status is still present on the System Status page after the upgrade
Meaningless. 5135 killed OBiPLUS.
So, if you had OBiPLUS firmware, its features no longer work.
Interesting, since I am using an existing OBiPlus (Basic/Lite/Free) subscription just fine with firmware 5135. It is true that OBiPlus can no longer be added to an account (no longer sold), but the existing features/functions seem to work the same as before (for better or worse)
Now, OBiPlus is likely on life support (I would not be surprised if it will have its plug pulled and no longer be allowed to be renewed at the next cycle), but its not entirely dead yet.
Navigation
[0] Message Index
[#] Next page