Polycom SOUNDPOINT SIP 2.2.0 - Manual (Page 22)

Administrator’s Guide SoundPoint IP / SoundStation IP
2 - 6
Application Configuration Files
Typically, the files are arranged in the following manner although parameters
may be moved around within the files and the filenames themselves can be
changed as needed. These files dictate the behavior of the phone once it is
running the executable specified in the master configuration file.
The application files are:
• Application—It contains parameters that affect the basic operation of the
phone such as voice codecs, gains, and tones and the IP address of an
application server. All phones in an installation usually share this category
of files. Polycom recommends that you create another file with your
organization’s modifications. If you must change any Polycom templates,
back them up first. By default, sip.cfg is included.
• Per-phone—It contains parameters unique to a particular phone user.
Typical parameters include:
— display name
— unique addresses
Each phone in an installation usually has its own customized version of
user files derived from Polycom templates. By default, phone1.cfg is
included.
Central Provisioning
The phones can be centrally provisioned from a boot server through a system
of global and per-phone configuration files. The boot server also facilitates
automated application upgrades, logging, and a measure of fault tolerance.
Multiple redundant boot servers can be configured to improve reliability.
In the central provisioning method, there are two major classifications of
configuration files:
• System configuration files
• Per-phone configuration files
Parameters can be stored in the files in any order and can be placed in any
number of files. The default is to have 2 files, one for per-phone setting and one
for system settings. The per-phone file is typically loaded first, and could
contain system level parameters, letting you override that parameter for a
given user. For example, it might be desirable to set the default CODEC for a
remote user differently than for all the users who reside in the head office. By
adding the CODEC settings to a particular user’s per-phone file, the values in
the system file are ignored.
Note Verify the order of the configuration files. Parameters in the configuration file loaded
first will overwrite those in later configuration files.