Overview
4.6.17 introduces support for Polycom 3.3 and above firmware. It also removes support for firmwares below 3.1, as well as for phones SPIP 300 and 500. Instead it introduces support for VVX 500 model.
Admins will have to specify the phone version when adding/configuring a new or existing Polycom model. Firmwares 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. A manual upgrade migrating procedure is described below, since sipXecs has no way of automatically knowing what specific firmware version a phone has.
...
| Note |
|---|
| 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, since they would both go to tftproot/polycom/3.2.X folder. |
Installing firmwares
The Device files interface for Polycom firmwares has not changed visually, except for adding a new Version field - a combo with "3.1.X", "3.2.X" and "4.0.X" values. An admin should choose the correct version of the firmware installed. By doing that the admin will ensure the firmware will be unpacked in the correct folder.
...
Admins can deploy multiple (major) firmware versions. You can have a 3.1.X, a 3.2.X and a 4.0.X firmware deployed for the situation in which there are multiple phones with different firmware versions.
Installing bootrom
| Note | ||
|---|---|---|
| ||
| While not forbiddendisallowed by sipXecs, it is strongly discouraged to have multiple bootroms deployed. |
To install a bootrom you need to upload and activate the bootrom in any of your Polycom device files or create a separate device file for it. Bootrom files will be unpacked in tftproot folder, and not in a firmware folder (like polycom/3.2.X). The reason for that is that a phone will look only in the root folder for the bootrom.
Migrating from 4.6
When upgrading from 4.6 admins can leave the device files in place just fine and the system and its defined phones will continue to function just like before. Even when profiles are sent to a phone, although [MAC].cfg will be configured with the new path to the sip.ld file, if the phone will not find it it will just use the existing SIP application.
...
| Note |
|---|
| It is important to note that you need to change "Firmware version update" and not the field "Firmware version" since the latter is not saved in the group settings and it is used to present correct settings based on the selected phone model. (For instance different models might have different set of codecs.) |
In the scenario where you already have a group with phones that have different firmwares, create different groups for all the versions and then use the above procedure to update the phones firmware versions. You may delete the groups after doing that.
...