However, the Polycom phone will, if permitted, upload some log files and create backups of locally-configured settings on the tftp server.
We also would like more detailed tftp logging in /var/log/messages than is provided by default.
At the time of publishing, the versions of the.x patch releases listed in the following table were 2.1.3, 3.1.6, and For the current release versions, see Polycom Support at Polycom recommends that all legacy phones be updated to the most recent patch of their last supported SIP and Boot ROM software versions.
Using these files, even if a phone is completely wiped (including its flash memory), it should be able to reboot to its fully-configured state as long as it can access the boot server.
2 Ensure that all software and configuration files for your non-legacy phones are on the provisioning server.
3 Download the file associated with each legacy phone s most recent supported software patch release to the provisioning server. The phone1and configuration files are not compatible with UC Software release or later, but are required to maintain compatibility with legacy phones.
The best way to do this is to download the most recent patch release for every Boot ROM version (for example, download 4.0.x, 4.1.x, 4.2.x, etc) as follows: 1 Download and unzip the most recent Boot ROM 4.0.x split release.
2 Download and unzip the most recent patch release of every subsequent Boot ROM version (for example, download 4.1.x, then 4.2.x, then 4.3.x, etc).