1 centralized configuration, 1 ftp vs. tftp, 2 configuration files – Polycom Version 1.4.x 17 User Manual
Page 18
Administrator Guide - SoundPoint
®
IP / SoundStation
®
IP
Installation and Operation
10
Copyright © 2004 Polycom, Inc.
2.2.2.1 Centralized Configuration
The phone application consists of an executable image file (sip.ld) and one or more
XML-format configuration files. In the centrally provisioned model, these files are
stored on a boot server and cached in the phone. If the boot server is available at boot
time, the phone will automatically synchronize its configuration cache with the boot
server: bootROM image, application executable, and configuration files are all
upgraded this way. The phone requires that a SNTP server be properly configured for
this feature to work optimally.
2.2.2.1.1 FTP vs. TFTP
If using a trivial FTP (TFTP) protocol boot server, synchronization with the boot
server will be based on file names, not file timestamps, as is the case with FTP. Exe-
cutable upgrades and changes made to configuration files will not be recognized by
the phone unless their names are changed.
Example:
file.ld file01.ld (an upgrade to SIP 1.0.1)
ipmid.cfg ipmid01.cfg
The master configuration file, which references the other files and is always down-
loaded and parsed by the phone, will need to change to reflect these name changes.
Polycom does not recommend TFTP boot servers for actively managed systems.
File name management is the responsibility of the System Administrator.
2.2.2.1.2 Configuration Files
The phone configuration files consist of master configuration files and application
configuration files.
2.2.2.1.2.1 Master Configuration Files
Central provisioning requires that an XML-format master configuration file be located
in the home directory on the boot server.
Per-phone Master Configuration File
If per-phone customization is required (for all applications that require per-phone cus-
tomization), the file should be named <Ethernet address>.cfg, where Ethernet address
Note
If the phone has bootROM version 2.6.0 or greater, the following restrictions do not apply.