...
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.4
When upgrading from 4.4 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.
In 4.4 all Polycom models have by default a hardcoded "2.0" version. When upgrading. In 4.6.1, we have kept this version in code however it has no corresponding support in configuration files or firmware. However the configuration files are by default created after 3.2 image as you can see from the following if-else block.
...
It is recommended that admins take some steps to "upgrademigrate" their Polycom phones to 4.6.1 new system. (Note that by this we don't mean updgrade upgrade the phones to a different firmware version/bootrom.)
...
| Note |
|---|
| Applying a version to a group will update all the phones in the group with the specified version. You might not want to do that if you have phones with different versions in the group. If you do not want phones firmware to be updated just leave the Firmware version update field blank (select blank option). |
| Note |
|---|
| If in a group there is a phone that does not support the chosen version, its version will not be changed. |