New firmware for Obi 200/202
GPz1100:
Quote from: WelshPaul on January 22, 2018, 03:01:57 am
Nope, can't find any release notes on the server for these builds. Not sure if it's because Polycom are taking over and things are no longer a priority, or if it's due to the OBi100 series firmware patch and that OBIHAI don't want to announce that they have fixed that issue in these releases.
It could also be that OBIHAI changed their file name structure and I just haven't found it.
Thanks for your comments. My preference is to always keep any automated firmware updates disabled. If it's not broke don't fix it. For now everything is working fine with the 5757ex build on our 200/202 units.
I suppose if obi wasn't so stingy with the updates hacking the 1xx firmware would not be necessary.
RFC3261:
Quote from: IterationIsFailure on January 21, 2018, 05:38:23 pm
such as the Google Voice configuration, which I recall having to do via the OBI website.
As I recall, because of the way that OBi obtains auth tokens to pass to the OBixxx device (one does not store Google passwords on the device, but authentication tokens) one has to use the OBi site to set things up. But after setup, if you do not reset the device, you should not need to access the portal again. The same setup via the portal requirement is (was?) true for some of the VoIP providers, which do not provide you with the actual passwords so you could manually enter them (I am thinking the cheap Anveo e911 service password was opaque to people; AFAIK that is still true, but it may have changed). So, at some point, either due to a factory reset, or some significant requirements change, may need to re-add the device to the portal.
My guess is that the portal (and all it implies) is used by many. Those, such as yourself, which are doing things a bit differently are likely going to have to remember that some future gyrations may be needed if you need to change things or accomplish more complex tasks (? add to portal, make changes, remove from portal, update something different, force specific firmware, ?) I suspect keeping regular XML backups of the configuration may be desirable.
IterationIsFailure:
Quote from: RFC3261 on January 22, 2018, 10:28:55 am
Quote from: IterationIsFailure on January 21, 2018, 05:38:23 pm
such as the Google Voice configuration, which I recall having to do via the OBI website.
As I recall, because of the way that OBi obtains auth tokens to pass to the OBixxx device (one does not store Google passwords on the device, but authentication tokens) one has to use the OBi site to set things up. But after setup, if you do not reset the device, you should not need to access the portal again. The same setup via the portal requirement is (was?) true for some of the VoIP providers, which do not provide you with the actual passwords so you could manually enter them (I am thinking the cheap Anveo e911 service password was opaque to people; AFAIK that is still true, but it may have changed). So, at some point, either due to a factory reset, or some significant requirements change, may need to re-add the device to the portal.
My guess is that the portal (and all it implies) is used by many. Those, such as yourself, which are doing things a bit differently are likely going to have to remember that some future gyrations may be needed if you need to change things or accomplish more complex tasks (? add to portal, make changes, remove from portal, update something different, force specific firmware, ?) I suspect keeping regular XML backups of the configuration may be desirable.
Great information. Thank you!
jentzd:
Yup! Good tip on setting up google via portal then going dark.
Just for reference the one thing that the new firmware broke for me was the SIP proxy ability on a 202. Using this feature extensively to supply a whole office.
Other than this saturdays firmware induced outage, has been working nicely.
Kage:
No forced update with my OBi200, I've got Auto Firmware Update and OBiTalk Provisioning disabled so maybe you need both. For now 5757ex is working good so until they post what changes have been made with their latest firmware updates I'm going to leave it as is.
Navigation
[0] Message Index
[#] Next page
[*] Previous page