...
After updating to 4.7 phones will reboot twice. The first time the [MAC].cfg will be changed in order to instruct the phone to contact the provisioning servlet. The provisioning servlet will read the correct firmware installed on the phone (using the User Agent header of the phone's request) and then via a sipXconfig REST service will update the phone's firmware version in the database. On second reboot sipXconfig will generate the correct config files which phones will pick up. Both reboots are scheduled after 1 minute to give phones time to register.
| Note |
|---|
| Phone Auto-Provisioning role must be enabled in order for the automatic migration to take place. Also make sure that firewall rules do not prevent phones from contacting provisioning server which by default runs on port 8185. |
Manual migration
If somehow the automatic procedure fails for some of the phones (for some reason the phones could not have been rebooted) admins may try to manually reboot the phones (listed in the failed jobs table). Phones should pick up the correct version and configs.
...
| Note |
|---|
| If in a group there is a phone that does not support the chosen version, its version will not be changed. |
Upgrading to 4.0
In order to upgrade a phone to 4.0.X firmware you must deploy a special bootrom and, of course, the 4.0 firmware. The special bootrom is called Upgrader, and the latest 4.0 firmware is 4.0.3F. You can download them from Polycom site:
After deploying the 2 items, when restarting the phone, the phone will pickup the new bootrom and sip.ld and will upgrade to the new firmware.
| Note |
|---|
| You must change the phone version to 4.0.X in order for a phone to be upgraded. Failing to do so might render the phone unable to start due to the fact it will pickup the new bootrom and try to find a suitable sip.ld in a folder other than 4.0.X, however any other sip.ld is incompatible with the phone new bootrom. you might get "Image is incompatible with the phone" error on the phone. |
Downgrading
Downgrading is currently not a supported procedure on sipXecs 4.6. 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.
Important
If you have a phone compatible with 4.0 but you DO NOT WANT TO UPGRADE it to 40 and keep it to 3.2 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.