...
| 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.0 Update 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):
|
Before you update
Here are some things you need to know before upgrading 4.6.0 to 4.6.0 Update 1. All of them will be explained in more detail in this wiki page
- All Polycom device files installed will be deleted. You will need to re-upload them.
- After update all Polycom phones will reboot twice in order for configuration database to be updated with the correct firmware revision installed on them (and model if it's the case), and generate the correct profiles for them.
- Provision role must be enabled and firewall rules must allow phones to contact provision port (8185) for the automatic procedure to take place.
- In case automatic update procedure fails you will be able to manually update phones via phones page, or using groups.
- It is important that you install different firmware revisions in their respective folders.
- While not forbidden, it is not recommended to have multiple bootroms deployed at any one time.
- It is possible to have different phones with different firmware revisions installed, however you must exercise caution since a phone will pickup latest bootrom deployed if it is compatible with the phone, and some SIP images are not compatible with some bootroms (for instance 3.2 image is not compatible with Upgrader). In this scenario we recommend deploying a bootrom only when needed (for instance when a phone is added to the system). On the same note, a phone with 4.0 revision will not downgrade itself to 3.2.
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. |
...
| Warning |
|---|
Please note that Polycom device files installed in 4.6.0 will be deleted after upgrade in 4.6.0 Update 1. This is due to the fact in the new schema device files would go to a version specific folder, and sipXecs would have no way of knowing what version of firmware is deployed. Admins Administrators are advised to reupload the Polycom device files. |
...
- Problem: Phone keeps rebooting and displays "Misc file error"
Solution: On phones page choose correct model, installed firmware, apply changes and send profiles - Problem: Phone keeps rebooting and displays "Image is incompatible with the phone"
Solution: Bootrom and sip.ld are incompatible. Most likely Upgrader is deployed as bootrom, and phone is set to 3.1.X or 3.2.X. On phone's page choose 4.0.X and reboot the phone. Make sure a 4.0 image is deployed (active).
Experimental 4.1 support
We have introduced in 4.6.0 Update 1 support for phones using 4.1 firmware revision. It is possible to upload 4.1 device files in their folders. The configuration profiles are generated based on 4.0 profiles.