Polycom SIP 3.1 manual Supporting SoundPoint IP 300 and 500 Phones

Models: SIP 3.1

1 347
Download 347 pages 532 b
Page 52
Image 52
Supporting SoundPoint IP 300 and 500 Phones

Administrator’s Guide SoundPoint IP / SoundStation IP

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-10.

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-16.

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-90.

Supporting SoundPoint IP 300 and 500 Phones

With enhancements in BootROM 4.0.0 and SIP 2.1.2, you can modify the 000000000000.cfg or <Ethernet address>.cfg configuration file to direct phones to load the software image and configuration files based on the phone model number. Refer to Master Configuration Files on page A-2.

The SIP 2.2.0 or later software distributions contain only the new distribution files for the new release. You must rename the sip.ld, sip.cfg, and phone1.cfg from a previous 2.1.2 distribution that is compatible with SoundPoint IP 300 and 500 phones.

The following procedure must be used for upgrading to SIP 2.2.0 or later for installations that have SoundPoint IP 300 and 500 phones deployed. It is also recommended that this same approach be followed even if SoundPoint IP 300 and 500 phones are not part of the deployment as it will simplify management of phone systems with future software releases.

3 - 20

Page 52
Image 52
Polycom SIP 3.1 manual Supporting SoundPoint IP 300 and 500 Phones