Supporting SoundPoint IP 300 and 500 Phones

Administrator’s Guide SoundPoint IP / SoundStation IP

2.Customize new configuration files or apply new or changed parameters to the old configuration files.

Differences between old and new versions of configuration files are explained in the Release Notes that accompany the software. Both mandatory and optional changes may present. Changes to site-wide configuration files such as sip.cfg can be done manually, but a scripting tool is useful to change per-phone configuration files.

Warning The configuration files listed in CONFIG_FILES attribute of the master configuration file must be updated when the software is updated. Any new configuration files must be added to the CONFIG_FILES attribute in the appropriate order.

Mandatory changes must be made or the software may not behave as expected.

For more information, refer to the “Configuration File Management on SoundPoint IP Phones” whitepaper at www.polycom.com/support/voice/ .

3.Save the new configuration files and images (such as sip.ld) on the boot server.

4.Reboot the phones by pressing the reboot multiple key combination. For more information, refer to Multiple Key Combinations on page C-9.

Since the APPLICATION APP_FILE_PATH attribute of the <Ethernet address>.cfg files references the individual sip.ld files, it is possible to verify that an update is applied to phones of a particular model.

For example, the reference to sip.ld is changed to 2345-11605-001.sip.ldto boot the SoundPoint IP 601 image.

The phones can be rebooted remotely through the SIP signaling protocol. Refer to Special Events <specialEvent/> on page A-15.

The phones can be configured to periodically poll the boot server to check for changed configuration files or application executable. If a change is detected, the phone will reboot to download the change. Refer to Provisioning <prov/> on page A-75.