You must change the legacy phone parameters to match the file names of the latest sip_xyz.ld, phone1_xyz.cfg, and sip_files on your provisioning server.
In the example shown next, the legacy software xyz versions are 213, 316, and 323 respectively: Legacy Phone Parameters If the approach described above is not used, then the file associated with each legacy phone will need to be modified.
If you are unsure of the ethernet addresses, you will need to add the legacy phone parameters (shown in the previous graphic) to every Since legacy phones are not compatible with Boot ROM versions after their last supported release, Polycom recommends that split images be used for maintenance and upgrade of Boot ROM releases.
Since you cannot rename the Boot ROM release files like the SIP release files, as discussed in the previous section, the relevant files will need to be placed on the provisioning server for each phone model.
By using a special adapter cable, I can answer the phone from the wireless headset without the need for a mechanical handset lifter.
If all you want to do is configure one phone, you might just want to use the phone’s web interface. However, if you have a lot of phones to configure, or even if you just want to have the configurations stored on your server, you’ll need to set up a boot server (we’ll use tftp) and create configuration files. This creates the /tftpboot directory and starts the tftp service.
This technical bulletin describes how to maintain older phones in deployments running software versions past their respective last supported releases.
As of UC Software 3.3.0, the unsupported models include the Sound Point IP 300, 301, 430, 500, 501, 600, 601 and Sound Station IP These models, known as legacy phones, have been discontinued and are only supported with critical patch releases.
Legacy phones are configured from the cfg master configuration file.
All files that match the ethernet addresses of your legacy phones must be deleted from the provisioning server.
Polycom maintains support for legacy phones with critical patch releases that end in.x, where x is the patch version.
For example, a phone running will be supported by release 3.1.x (such as release 3.1.6) but not release or later.
(This post explains how to do that.) To allow writing and enhance logging, I made the following changes.