white paper configuration file manageme
White Paper
Configuration File Management on Polycom® SoundPoint® IP,
SoundStation® IP, and VVX® Phones
This white paper provides a simple and effective way to manage configuration files and keep desired settings when configuration files are upgraded to new revisions. This information applies to SoundPoint IP phones running BootROM version
3.1.0 or later and SIP software version 1.6 or later.
This information applies to SoundStation IP phones running BootROM version 4.1.3 or later and SIP software version 2.0 or later.
This information applies to VVX 1500 phones running BootROM version 4.1.4 or later and SIP software 3.2.2 or later.
Updates due to changes in BootROM 4.0 or later and SIP 2.2 or later are noted. in August 2007.
This white paper applies to SoundPoint IP, SoundStation IP, and VVX 1500 phones running BootROM version 4.1.4 or earlier and SIP software 3.2.5 or earlier. For later software versions (those starting at BootROM 4.3.0 and
Polycom® UC Software 3.3.0), see the Polycom UC Software Provisioning Best
Practices available on the Polycom Support Web site at http://www.polycom.com/global/forms/verify.html?retURL=http://ww w.polycom.com/global/documents/whitepapers/uc-software-provisioningbest-practices-whitepaper.pdf .
Introduction
If customers modify the configuration files delivered with the SIP firmware for their organization’s needs, those changes are lost or are difficult to recreate when it comes time to update the SIP firmware. The configuration files, supplied with each SIP release, must be used with that release or the software will behave unpredictably.
Distributed Configuration Files
The phone uses configuration files listed in the CONFIG_FILES field of the master configuration file, for example 000000000000.cfg or <Ethernet address>.cfg. Note
August 2011
3725-17461-001/D
As of BootROM 4.0 and SIP 2.2, the use of <Ethernet address>.cfg files is not recommended. The use of substitutions in 000000000000.cfg has been introduced.
Refer to
Configuration File Management on Polycom® SoundPoint® IP,
SoundStation® IP, and VVX® Phones
This white paper provides a simple and effective way to manage configuration files and keep desired settings when configuration files are upgraded to new revisions. This information applies to SoundPoint IP phones running BootROM version
3.1.0 or later and SIP software version 1.6 or later.
This information applies to SoundStation IP phones running BootROM version 4.1.3 or later and SIP software version 2.0 or later.
This information applies to VVX 1500 phones running BootROM version 4.1.4 or later and SIP software 3.2.2 or later.
Updates due to changes in BootROM 4.0 or later and SIP 2.2 or later are noted. in August 2007.
This white paper applies to SoundPoint IP, SoundStation IP, and VVX 1500 phones running BootROM version 4.1.4 or earlier and SIP software 3.2.5 or earlier. For later software versions (those starting at BootROM 4.3.0 and
Polycom® UC Software 3.3.0), see the Polycom UC Software Provisioning Best
Practices available on the Polycom Support Web site at http://www.polycom.com/global/forms/verify.html?retURL=http://ww w.polycom.com/global/documents/whitepapers/uc-software-provisioningbest-practices-whitepaper.pdf .
Introduction
If customers modify the configuration files delivered with the SIP firmware for their organization’s needs, those changes are lost or are difficult to recreate when it comes time to update the SIP firmware. The configuration files, supplied with each SIP release, must be used with that release or the software will behave unpredictably.
Distributed Configuration Files
The phone uses configuration files listed in the CONFIG_FILES field of the master configuration file, for example 000000000000.cfg or <Ethernet address>.cfg. Note
August 2011
3725-17461-001/D
As of BootROM 4.0 and SIP 2.2, the use of <Ethernet address>.cfg files is not recommended. The use of substitutions in 000000000000.cfg has been introduced.
Refer to