Codebase version not updating cab
The phones will look for specific firmware files to perform an upgrade/downgrade and will download and upload configuration data in XML files.
Polycom UCS devices can utilize a variety of different file server platforms to store and manage both firmware packages and configuration files, no additional third-party software is required.
The important files are highlighted in the table below.
An additional recommendation is to create dedicated directories to store call and diagnostic logs for each phone.
When receiving a dynamic IP address on the network the phone will by default look for the location of a provisioning server by first checking for the existence of DHCP Option 160.
In the event that option 160 is not configured then it will fall back to looking for Option 66.
Simply double-click the downloaded file to install it.
These options can be defined at either the server or scope level.
The default credentials use the same string for both the username and password and are stored in as case-sensitive so if the FTP server uses case-sensitive username and/or password make sure the uppercase and lowercase characters are used correctly.
(Traditionally username are not case-sensitive while passwords are, but this may depend on the actual file server product used.) It can be difficult to discern if some of these characters are an i, L, or a 1.
In this article a basic FTP server will be used but the phones also support the TFTP, HTTP, and HTTPS protocols.
When a factory-reset device is first powered on it will check for specific DHCP Options that may be defined on the network which would provide a path to the provisioning server.
Instead this process alone can be used to deploy a basic provisioning server in a lab or testing environment when evaluating Polycom SIP phones, and much of the guidance contained reflects a non-production scenario.