FUENTES DE LAS OPORTUNIDADES EMPRESARIALES

The master configuration files can be one of:

• Specified master configuration file—The master configuration file can be explicitly specified in the boot server address, for example,

http://usr:pwd@server/dir/example1.cfg. The filename must end with .cfg and be at least five characters long. If this file cannot be downloaded, the phone will search for the per-phone master configuration file

(described next).

• Per-phone master configuration file—If per-phone customization is required, the file should be named <Ethernet address>.cfg, where Ethernet address is the MAC address of the phone in question. For A-F hexadecimal digits, use upper or lower case, for example,

0004f200106c.cfg. The Ethernet address can be viewed using the About soft key during the auto-restart countdown of the bootROM or through the Menu > Status > Platform > Phone menu in the application. It is also printed on a label on the back of the phone. If this file cannot be

downloaded, the phone will search for the default master configuration file (described next).

• Default master configuration file—For systems in which the configuration is identical for all phones (no per-phone <Ethernet address>.cfg files), the default master configuration file may be used to set the configuration for all phones. The file named 000000000000.cfg (<12 zeros>.cfg) is the default master configuration file and it is recommended that one be present on the boot server. If a phone does not find its own <Ethernet address>.cfg file, it will use this one, and establish a baseline configuration. This file is part of the standard Polycom distribution of configuration files. It should be used as the template for the <Ethernet address>.cfg files.

The default master configuration file, 000000000000.cfg, 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. -->

<!-- $Revision: 1.14 $ $Date 2005/07/27 18:43:30 $ --> < APPLICATION APP_FILE_PATH=”sip.ld”

CONFIG_FILES=”phone1.cfg, sip.cfg” MISC_FILES=”” LOG FILE DIRECTORY=”” OVERRIDES_DIRECTORY=”” CONTACTS_DIRECTORY=”” LICENSE_DIRECTORY=””/> Master configuration files contain six XML attributes:

• APP_FILE_PATH—The path name of the application executable. It can have a maximum length of 255 characters. This can be a URL with its own protocol, user name and password, for example

• 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/

CONFIG_FILES=”phone1[MACADDRESS].cfg, sip.cfg” MISC_FILES=”” LOG FILE DIRECTORY=”” OVERRIDES_DIRECTORY=””

CONTACTS_DIRECTORY=”” LICENSE_DIRECTORY=””/>

If you have a requirement for separate application loads on different phones on the same boot server, you can modify the application that is loaded when each phone reboots. An example is 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[PHONE_PART_NUMBER].ld” CONFIG_FILES=”phone1.cfg, sip.cfg” MISC_FILES=””

LOG FILE DIRECTORY=”” OVERRIDES_DIRECTORY=”” CONTACTS_DIRECTORY=”” LICENSE_DIRECTORY=””/> You can also use the substitution strings PHONE_MODEL,

PHONE_PART_NUMBER, and PHONE_MAC_ADDRESS in the master configuration file.

You can also direct phone upgrades to a software image and configuration files based on the phone model number and part number. All XML attributes can be modified in this manner. An example is 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.ld” CONFIG_FILES=”phone1.cfg, sip.cfg” MISC_FILES=”” LOG_FILE_DIRECTORY=””

OVERRIDES_DIRECTORY=”” CONTACTS_DIRECTORY=”” LICENSE_DIRECTORY=”” APP_FILE_PATH_SPIP330=”SPIP330.sip.ld” CONFIG_FILES_SPIP330=”phone1_SPIP330.cfg, sip_SPIP330.cfg” APP_FILE_PATH_SPIP501=”SPIP501.sip.ld” CONFIG_FILES_SPIP501=”phone1_SPIP501.cfg, sip_SPIP501.cfg” /> For more information, refer to “Technical Bulletin 35361: Overriding Parameters in Master Configuration File on SoundPoint IP Phones“ at

http://www.polycom.com/support/voice/.