Polycom 1725-11530-310 Manual Do Utilizador
Setting up Your System
3 - 21
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
These are the relevant files for all phones except the SoundPoint IP 300 and
500 phones.
3.
Rename sip.ld, sip.cfg, and phone1.cfg from the previous distribution to
sip_212.ld, sip_212.cfg, and phone1_212.cfg respectively on the boot
server.
These are the relevant files for supporting the SoundPoint IP 300 and 500
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:
For example:
<APPLICATION
APP_FILE_PATH="sip.ld"
APP_FILE_PATH_SPIP500="sip_212.ld"
APP_FILE_PATH_SPIP300="sip_212.ld"
CONFIG_FILES="[PHONE_MAC_ADDRESS]-user.cfg, phone1.cfg, sip.cfg"
CONFIG_FILES_SPIP500="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_212.cfg, sip_212.cfg"
CONFIG_FILES_SPIP300="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_212.cfg, sip_212.cfg"
MISC_FILES=""
LOG_FILE_DIRECTORY=""
OVERRIDES_DIRECTORY=""
CONTACTS_DIRECTORY=""
/>
5.
Remove any <Ethernet address>.cfg files that may have been used with
earlier releases from the boot server.
Note
This approach takes advantage of an enhancement that was added in
SIP2.0.1/BootROM 3.2.1 that allows for the substitution of the phone specific
[MACADDRESS] inside configuration files. This avoids the need to create unique
<Ethernet address>.cfg files for each phone such that the default
000000000000.cfg file can be used for all phones in a deployment.
SIP2.0.1/BootROM 3.2.1 that allows for the substitution of the phone specific
[MACADDRESS] inside configuration files. This avoids the need to create unique
<Ethernet address>.cfg files for each phone such that the default
000000000000.cfg file can be used for all phones in a deployment.
If this approach is not used, then changes will need to be made to all the <Ethernet
address>.cfg files for SoundPoint IP 300 and 500 phones or all of the <Ethernet
address>.cfg files if it is not explicitly known which phones are SoundPoint IP 300
and 500 phones.
address>.cfg files for SoundPoint IP 300 and 500 phones or all of the <Ethernet
address>.cfg files if it is not explicitly known which phones are SoundPoint IP 300
and 500 phones.