Configuration Files
A - 3
• CONFIG_FILES—A comma-separated list of configuration files. Each file
name has a maximum length of 255 characters and the list of file names has
a maximum length of 2047 characters, including commas and white space.
Each configuration file can be specified as a URL with its own protocol,
user name and password, for example
ftp://usr:pwd@server/dir/phone2034.cfg.
• MISC_FILES—A comma-separated list of other required files. Dictionary
resource files listed here will be stored in the phone's flash file system. So
if the phone reboots at a time when the boot server is unavailable, it will
still be able to load the preferred language.
• LOG_FILE_DIRECTORY—An alternative directory to use for log files if
required. A URL can also be specified. This is blank by default.
• CONTACTS_DIRECTORY—An alternative directory to use for user
directory files if required. A URL can also be specified. This is blank by
default.
• OVERRIDES_DIRECTORY—An alternative directory to use for
configuration overrides files if required. A URL can also be specified. This
is blank by default.
• LICENSE_DIRECTORY—An alternative directory to use for license files if
required. A URL can also be specified. This is blank by default.
If you have a requirement for different application loads on different phones
on the same boot server, you can create a variable in the master configuration
file that is replaced by the MAC address of each phone when it reboots. An
example is shown below:
<?xml version=”1.0” standalone=”yes”?>
<!-- Default Master SIP Configuration File -->
<!-- edit and rename this file to <Ethernet-address>.cfg for
each phone. -->
<!-- $RCSfile: 000000000000.cfg,v $ $Revision:$ -->
< APPLICATION APP_FILE_PATH=”sip[MACADDRESS].ld”
Note
On the SoundPoint IP 500, there is insufficient room for a language file. Specifying
one will cause a reboot loop
Warning
The order of the configuration files listed in CONFIG_FILES is significant:
• The files are processed in the order listed (left to right).
• The same parameters may be included in more than one file.
• The parameter found first in the list of files will be the one that is effective.
This provides a convenient means of overriding the behavior of one or more phones
without changing the baseline configuration files for an entire system.
For more information, refer to the “Configuration File Management on SoundPoint
IP Phones” whitepaper at www.polycom.com/support/voice/