Master Configuration File

The master configuration file provides flexibility in large deployments to customize features and settings for your phones.

You can use the master configuration file to configure features and apply settings for all the phones in your deployment, including groups of phones, specific phone models, or a single phone.

The default name for the master configuration file is 00000000000.cfg. You can use the default name or rename the master configuration file. The file name must contain at least five characters and end with .cfg.

You can also specify the location of the master configuration file you want the phones to use, for example, http://usr:pwd@server/dir/example1.cfg.

The master configuration file applies settings from the component configuration files listed in the CONFIG_FILES XML attribute in the following ways:
  • Phones read the files you enter from left to right.
  • Duplicate settings are applied from the configuration file in the order you list them.

The following table describes the XML field attributes in the master configuration file and the APPLICATION directories.

Table 1. Master Configuration File XML Field Attributes

Attribute

Description

APP_FILE_PATH

The path name of the UC software application executable. The default value is sip.ld. Note that the phone automatically searches for the sip.ld and <part number>.sip.ld files. This field can have a maximum length of 255 characters.

If you want the phone to search for a sip.ld file in a location other than the default or use a different file name, or both, modify the default. For example, you can specify a URL with its own protocol, user name, and password: http://usr:pwd@server/dir/sip.ld .

CONFIG_FILES

Enter the names of your configuration files in this attribute as a comma-separated list. Each file name has a maximum length of 255 characters and the entire list of file names has a maximum length of 2047 characters, including commas and white space. If you want to use a configuration file in a different location or use a different file name, or both, you can specify a URL with its own protocol, user name, and password, for example ftp://usr:pwd@server/dir/phone2034.cfg. The files names you enter to the CONFIG_FILES field write are read from left to right. Duplicate settings are applied from the configuration file in the order you list them.

MISC_FILES

A comma-separated list of files. Use this to list volatile files that you want phones to download, for example, background images and ringtone.wav files. The phone downloads files you list here when booted, which can decrease access time.

LOG_FILE_DIRECTORY

An alternative directory for log files. You can also specify a URL. This field is blank by default.

CONTACTS_DIRECTORY

An alternative directory for user directory files. You can also specify a URL. This field is blank by default.

OVERRIDES_DIRECTORY

An alternative directory for configuration overrides files. You can also specify a URL. This field is blank by default.

LICENSE_DIRECTORY

An alternative directory for license files. You can also specify a URL. This field is blank by default

USER_PROFILES_DIRECTORY

An alternative directory for the <user>.cfg files.

CALL_LISTS_DIRECTORY

An alternative directory for user call lists. You can also specify a URL. This field is blank by default.

COREFILE_DIRECTORY

An alternative directory for Polycom device core files to use to debug problems. This field is blank by default.

CAMERA_PRESETS_DIRECTORY Specify a sub-directory to store the camera preset thumbnail images on the provisioning server. By default, this field is blank and thumbnail images are stored in the root directory of the provisioning server. However, if you set the attribute CAMERA_PRESETS_DIRECTORY="presets", the images are stored to an existing sub-directory called Presets.
Note: The directories labeled APPLICATION_SPIPXXX indicate phone models that are not compatible with the latest UC software version. If you are using any of the phone models listed in these directories, open the directory for the phone model you are deploying, and use the available fields to provision and configure your phones.