Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  1. Download the downgrader from Polycom site. You can find it here: http://support.polycom.com/PolycomService/support/us/support/voice/polycom_uc/polycom_uc_software_support_center.html
  2. Deactivate all Polycom device files.
  3. Create a new Polycom "Device files" and upload the Upgrader on the SIP Application (zip) field and under 4.0.X firmware (we assume all phones needed to be downgraded are at 4.0.X firmware revision). (Leave the Bootrom field blank.) (Use common sense, if phone is actually 3.2.X in sipXconfig database, upload it under 3.2.X firmware.)
  4. Reboot phones. NOTE: if you have phones with 4.0 firmware which you do not want to downgrade, make sure you do not reboot them.
  5. Phones will pickup the new bootrom and firmare (3.3.5).
  6. Create another Device files (or activate it if you already have one) with 3.2 firmware. I used 4.3.1 bootrom, and 3.2.6 firmware. Make sure you set the correct firmware version (3.2.X).
  7. Change the phone(s) firmware version (either from phone or from group).
  8. Send profiles to the phone(s).
  9. Phone(s) will reboot and pickup the bootrom and firmware.

NOTE: phones might reboot a couple of times after it gets new bootrom / SIP app / configuration. I don't know exactly if there is a pattern, but just keep this in mind.

Important

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.

...