Polycom SIP 3.0.2 manual Supporting SoundPoint IP 300 and 500 Phones, APPFILEPATH=sip.ld

Setting up Your System

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

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.

To upgrade your SIP application:

1.Do one of the following steps:

a Place the bootrom.ld file corresponding to BootROM revision 4.0.0 (or later) onto the boot server.

b Ensure that all phones are running BootROM 4.0.0 or later code.

2.Copy sip.ld, sip.cfg and phone1.cfg from the SIP2.2.0 or later release distribution onto the boot server.

These are the relevant files for all phones except the SoundPoint IP 300 and 500 phones.

3.Rename sip.ld, sip.cfg, and sip_212.ld, sip_212.cfg, and server.

phone1.cfg from the previous distribution to phone1_212.cfg respectively on the boot

These are the relevant files for supporting the SoundPoint IP 300 and 500 phones.

4.Modify the 000000000000.cfg file, if required, to match your configuration file structure.

For example:

<APPLICATION

APP_FILE_PATH="sip.ld"

APP_FILE_PATH_SPIP500="sip_212.ld" APP_FILE_PATH_SPIP300="sip_212.ld"

3 - 19