Overview
4.6.0 Update 1 introduces introduces support for Polycom 4.0 firmware. It also discontinues support for firmwares firmware revisions below 3.1, as well as for phones SPIP 300 and 500. Instead it introduces Update 1 also introduces the ability to configure multiple versions of Polycom firmware. Configuration support for VVX 500 modeland 600 models is also introduces as part of this update.
| Note | ||
|---|---|---|
| ||
4.6.1 discontinues support for firmware older than 3.1. However models SPIP 300 and SPIP 500 will continue to work with sipXecs. Most probably in a future release, support for those phones will be removed. Models SPIP 301 and 501 are able to work with firmware up to 3.1.8, thus they are still supported. |
Admins Administrators will have to specify the phone version when adding/configuring a new or existing Polycom model. Firmwares Firmware versions currently defined are 3.1.X , 3.2.X and 4.0.X. In the future maybe finer grained versioning will be defined if necessary. Since in In earlier sipXecs versions all Polycom phones are defined as having firmware version 2.0 version, there is . There are both an automatic and a manual procedures procedure to migrate the phones to the new system and to the correct firmware version. Both are described below.
Another major difference is that multiple Multiple Polycom firmware versions can be activated simultaneously. This way, an admin An administrator can define multiple phones or groups of phones with different versions. Firmware applications together with whatever files packed in the zip archive downloaded from Polycom site will be unpacked in specific folders in tftproot. In previous releases of sipXecs only a single version of Polycom firmware could be active at one time.
| Info | ||
|---|---|---|
| ||
Note that by multiple versions we understand at most one firmware per major version defined. For instance we will not be able to have 3.2.6 and 3.2.7 versions deployed at the same time, since they would both go to tftproot/polycom/3.2.X folder. |
| Note | ||
|---|---|---|
| ||
In 4.6.0 and earlier releases of sipXecs some phones were defined as paired models, since they had the same configuration. In 4.6.1 the models have been split. On migration to 4.6.0 Update 1, phones will be able to automatically pick up the correct model. Also a combo box was added in the phone's page for the specific models, in order for an admin to be able to manually choose the correct phone model. The models are (all phones are SPIP):
|
Installing
...
firmware
| Warning | ||
|---|---|---|
| ||
Please note that Polycom device files installed in 4.6.0 (be it active or inactive) will be deleted on upgrade. Admins are advised to re-add the device files for the wanted firmware. |
...
Downgrading
Downgrading is currently not a supported procedure on sipXecs 4.6.0. It can be done and the procedure is documented on Polycom site. Basically, in order to downgrade a phone from 4.0 to 3.2 one must deploy another special bootrom called Downgrader and a 3.3 firmware, and only after that deploy a 3.2 firmware.
...
If you have a phone compatible with 4.0 but you DO NOT WANT TO UPGRADE it to 4.0 and keep it to 3.2 (or 3.1) version, you must make sure you do not keep the Upgrader deployed. If you do so, on reboot the phone will pickup the new bootrom and try to find a compatible image in the 3.2.X or 3.1.X folder. Those images are not compatible with the upgrader, and you will get a "Image is incompatible with the phone" error.
...