Supporting Soundpoint Ip 300, 301, 500, 501, 600 And 601 And Soundstation Ip 4000 Phones - Polycom IP 320 Administrator's Manual

Supporting SoundPoint IP 300, 301, 500, 501, 600 and 601 and
SoundStation IP 4000 Phones
4. Reboot the phones using automatic methods such as polling or
check-sync.
Using the reboot multiple key combination should be done as a backup
option only. For more information, refer to
page C-11.
Since the APPLICATION APP_FILE_PATH attribute of the
<MACaddress>.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-11670-001.sip.ld to
boot the SoundPoint IP 670 image.
The phones can be rebooted remotely through the SIP signaling protocol.
Refer to Special Events <specialEvent/>
The phones can be configured to periodically poll the provisioning 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
<prov/> on page A-114.
With enhancements available since BootROM 4.0.0 and SIP 2.1.2, you can
modify the 000000000000.cfg or <MACaddress>.cfg configuration file to
direct phones to load the software image and configuration files based on the
phone model number. Refer to
The SIP 3.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.x distribution that is compatible with SoundPoint IP 300
and 500 phones or a previous 3.1.y distribution that is compatible with
SoundPoint IP 301, 501, 600, and 601 SoundStation IP 4000 phones.
The following procedure must be used for upgrading to SIP 3.2.0 or later for
installations that have SoundPoint IP 300, 301, 500, 501, 600, 601 and
SoundStation IP 4000 phones deployed. It is also recommended that this same
approach be followed even if these 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:
Place all bootrom.ld files corresponding to BootROM release zip file
a
onto the provisioning server.
Ensure that all phones are running BootROM 4.0.0 or later code.
b
Multiple Key Combinations
on page A-20.
Master Configuration Files
Setting up Your System
on
Provisioning
on page A-2.
3 - 23