Set Up the Provisioning Server

This section provides instructions for setting up your Polycom phones with a provisioning server. If you are new to this process, it is important to read every section in this section.

Because of the large number of optional installations and configurations that are available, this section focuses on one particular way that the Polycom® UC Software and the required external systems might initially be installed and configured in your network.

Set Up the Provisioning Server consists of the following sections:

Why Use a Provisioning Server?

Read this section if you have never set up a provisioning server before.

Polycom strongly recommends that you use a provisioning server to install and maintain your Polycom phones. You can set up a provisioning server on the local LAN or anywhere on the Internet. A provisioning server maximizes the flexibility you have when installing, configuring, upgrading, and maintaining the phones, and enables you to store configuration, log, directory, and override files on the server. If you allow the phone write access to your provisioning server, the phone can use the server to upload all of the file types and store administrator and user settings. The phone is designed such that if it cannot locate a provisioning server when it boots up, it will operate with internally saved parameters. This is useful when the provisioning server is not available.

 

Web Info: Registering Standalone Polycom Phones

If you want to register a single Polycom phone, see the Polycom Web Configuration Utility User Guide.

You can configure multiple (redundant) provisioning servers—one logical server with multiple addresses—by mapping the provisioning server DNS name to multiple IP addresses. The default number of provisioning servers is one and the maximum number is eight. For more information on the protocol used, see Supported Provisioning Protocols.

If you set up multiple provisioning servers, you must be able to reach all of the provisioning servers with the same protocol and the contents on each provisioning server must be identical. The parameters described in Provisioning Server Menu can be used to configure the number of times each server will be tried for a file transfer and also how long to wait between each attempt. You can configure the maximum number of servers to be tried. For more information, contact your Certified Polycom Reseller.

Provisioning Server Security Notes

Read this section if you have never set up a provisioning server before.

For organizational purposes, Polycom recommends configuring a separate log file directory, an override directory, a contact directory, and a license directory, though this is not required. Each directory can have different access permissions. For example, you can allow LOG, CONTACTS, and OVERRIDES to have full read and write access, and LICENSE to have read-only access.

You should ensure that the file permissions you create provide the minimum required access and that the account has no other rights on the server.

 

Tip: Allowing File Uploads to Your Provisioning Server

Polycom recommends that you allow file uploads to the provisioning server where the security environment permits. File uploads allow event log files to be uploaded. Log files provide backup copies of changes users make to the directory, and to the phone’s configuration through the Web server and/or local user interface. These log files help Polycom provide customer support when diagnosing issues that may occur with the phone operation.

The phone’s server account needs to be able to add files that it can write to in the log file directory and the provisioning directory. It must also be able to list files in all directories mentioned in the <MACaddress>. cfg file. All other files that the phone needs to read, such as the application executable and the standard configuration files, should be made read-only using file server file permissions.

 

Tip: Use RFC-Compliant Servers

Polycom recommends that you use RFC-compliant servers.

Each phone may open multiple connections to the server.

The phone will attempt to upload log files, a configuration override file, and a directory file to the server if changed. This requires that the phone’s account has delete, write, and read permissions. The phone will still function without these permissions, but will not be able to upload files.

If you know the phone is going to download a file from the server, you should mark the file as read-only.

Set up an FTP Server as Your Provisioning Server

Read this section if you have never set up a provisioning server before.

A simple provisioning configuration uses File Transfer Protocol or FTP. FTP servers are free, require installation, and use logins and passwords. A free and popular server, FileZilla Server, is available for Windows. FileZilla Server (version 0.9.xx) has been tested with the UC Software.

 

Tip: Choosing a Provisioning Protocol

By default, Polycom sets FTP as the provisioning protocol on all Polycom phones. This guide focuses on the FTP provisioning protocol. Other supported protocols include TFTP, HTTP, and HTTPS.

To set up an FTP server using FileZilla Server:

  1. Download and install the latest version of FileZilla Server.

  2. After installation, a Connect to Server pop-up displays on your computer. Click OK to open the administrative user interface.

  3. To configure a user, select Edit > Users in the status bar.

  4. Click Add.

  5. Enter the user name for the phone and select OK .

    For example, bill123.

  6. Select the Password checkbox and enter a password.

    For example, 1234. The phone will use this password to log in.

  7. Select Page > Shared folders to specify the server-side directory where the provisioning files will be located (and the log files uploaded).

  8. Select Add and pick the directory.

  9. To allow the phone to upload logs onto the provisioning server, select Shared Folders > Files , then select Write and Delete checkboxes, and then click OK .

  10. Determine the IP address of the FTP server by entering cmd in the Run dialog on your Start menu, and enter ipconfig in the command prompt.

    The IP Address of the FTP server is shown.

Download Polycom UC Software Files to the Provisioning Server

This section explains how to download the Polycom Unified Communications (UC) Software to the provisioning server.

Go to the Polycom UC Software Support Center to download current and past releases, access supporting documentation; or, you navigate to the downloads and documents available for a specific product. Polycom provides the UC Software download in ZIP file format.

If you need to determine which Polycom UC Software release you need for your phones, refer to the Polycom UC Software/Polycom SIP Software Release Matrix to match your phone model to all UC Software releases and software components. You can download all UC Software from this Release Matrix.

To download the Polycom UC Software:

  1. Access Polycom UC Software from the Polycom UC Software Support Center or the Polycom UC Software/Polycom SIP Software Release Matrix.

    Choose the combined UC Software package or the split UC Software package. Both packages are provided in ZIP file format. The split software package is smaller and simplifies the provisioning process. Whereas the combined version contains all files for all phone models, the split version contains sip.ld files for each phone model, enabling you to choose files for your phone model and store software versions for different phone models in the same directory.

  2. Acknowledge that you read the notices, accept the agreement, and choose Submit .

  3. Save the UC Software ZIP file download.

  4. Extract (uncompress) the ZIP file.

    Copy all files from the distribution ZIP file to the home directory on the provisioning server, maintaining the same folder hierarchy. To simplify provisioning, Polycom recommends editing copies of each file as a best practice to ensure that you have unedited template files containing the default values.

  5. The split image file contains individual sip.ld files for each phone model as well as all of the template configuration files included in the combined image file. To find the sip.ld file for your phones, see Product, Model, and Part Number Mapping.

    For a list and brief description of all available template files included with Polycom UC Software 5.0, see Use the Template Configuration Files.

     

    Note: See the Release Notes for a Description of all Parameters for a UC Software Release

    For a description of each file in a UC Software distribution, see the UC Software Release Notes for a particular UC Software release on the Polycom UC Software Support Center or from the Polycom UC Software/Polycom SIP Software Release Matrix.

Deploy and Update Polycom Phones with a Provisioning Server

This section explains how to deploy and update Polycom phones from a provisioning server. If you are provisioning the phones using a provisioning server for the first time, follow the provisioning process shown in Deploy Polycom Phones with a Provisioning Server. If you are using a phone in one of the following special scenarios, refer to the relevant section:

As of Polycom UC Software 4.0.1, and UC software 5.0, the Updater and UC Software are packaged together for all phones except the SoundStation IP 6000.

As of Polycom UC Software 3.3.0, Polycom phones can boot up without any configuration files; however, you will need to configure certain parameters in the configuration files - for example, a registration address, label, and SIP server address - to make the phones usable.

You can create as many configuration files as you want and your configuration files can contain any combination of parameters you put in them. You can put all parameters into one file or, for example, you can put SIP server parameters in one file and phone features parameters in another file. For detailed information on how to use the configuration files, see the section Use the Template Configuration Files.

For large-scale deployments, the centralized provisioning method using configuration files is strongly recommended. For smaller scale deployments, the Web Configuration Utility or local interface may be used, but administrators need to be aware that settings made using these methods will override settings made using configuration files.

For instructions on how to encrypt your configuration files, see Encrypt Configuration Files.

Deploy Polycom Phones with a Provisioning Server

To deploy phones with a provisioning server:

  1. Obtain a list of MAC addresses for the phones you want to deploy.

    The MAC address is a 12-digit hexadecimal number on a label on the back of the phone and on the outside of the shipping box.

  2. Create a per-phone phone<MACaddress>.cfg file.

     

    Tip: Choosing the File Name for a Per-Phone Configuration File

    Do not use the following file names as your per-phone file name: <MACaddress>-phone.cfg, <MACaddress>-web.cfg, <MACaddress>-app.log, <MACaddress>-boot.log, or <MACaddress>-license.cfg. These file names are used by the phone itself to store user preferences (overrides) and logging information.

    Add phone registration parameters to the file, for example reg.1.address, reg.1.label, and reg.1.type.

  3. Create a per-site site<location>.cfg file.

    For example, add the SIP server or feature parameters such as voIpProt.server.1.address and feature.corporateDirectory.enabled.

     

    Settings: Configuring Your Phone for Local Conditions

    Most of the default settings are typically adequate; however, if SNTP settings are not available through DHCP, you will need to edit the SNTP GMT offset, and (possibly) the SNTP server address for the correct local conditions. Changing the default daylight savings parameters will likely be necessary outside of North America. Disable the local Web (HTTP) server or change its signaling port if the local security policy dictates (see <httpd/>). Change the default location settings for user interface language and time and date format (see <lcl/>)

  4. Create a master configuration file by performing the following steps:

    1. Enter the name of each per-phone and per-site configuration files created in steps 2 and 3 in the CONFIG_FILES attribute of the master configuration file (000000000000.cfg ). For help using the master configuration file, see Understand the Master Configuration File.

      For example, add a reference to phone<MACaddress>.cfg and sip650.cfg .

    2. (Optional) Edit the LOG_FILE_DIRECTORY attribute of master configuration file so that it points to the log file directory.

    3. (Optional) Edit the CONTACT_DIRECTORY attribute of master configuration file so that it points to the organization’s contact directory.

    4. (Optional) Edit the USER_PROFILES_DIRECTORY attribute of master configuration file if you intend to enable the User Login feature.

      For more information, see Set User Profiles.

    5. (Optional) Edit the CALL_LISTS_DIRECTORY attribute of master configuration file so that it points to the user call lists.

  5. Perform the following steps to configure the phone to point to the IP address of the provisioning server and set up the user:

    1. On the phone’s Home screen or idle display, select Settings > Advanced > Admin Settings > Network Configuration > Provisioning Server .

      When prompted for the administrative password, enter 456 . The Provisioning Server entry is highlighted.

    2. Press the Select soft key.

    3. Scroll down to Server Type and ensure that it is set to FTP .

    4. Scroll down to Server Address and enter the IP address of your provisioning server.

      Press the Edit soft key to edit the value and the OK soft key to save your changes.

    5. Scroll down to Server User and Server Password and enter the user name and password of the account you created on your provisioning server, for example, bill1234 and 1234, respectively.

    6. Press the Back soft key twice.

    7. Scroll down to Save & Reboot , and then press the Select soft key.

      The phone reboots.

      The UC Software modifies the APPLICATION APP_FILE_PATH attribute of the master configuration file so that it references the appropriate sip.ld files. For example, the reference to sip.ld is changed to 2345-12600-001.sip.ld to boot the SoundPoint IP 650 image.

      After this step, the UC Software will try the unmodified APPLICATION APP_FILE_PATH attribute.

      At this point, the phone sends a DHCP Discover packet to the DHCP server. This is found in the Bootstrap Protocol/option “Vendor Class Identifier” section of the packet and includes the phone’s part number and the BootROM version.

      For example, a SoundPoint IP 650 might send the following information:

      5EL@ DC?5cSc52*46*(9N7*<u6=pPolycomSoundPointIP-SPIP_6502345-12600-001,1BR/4.0.0.0155/23-May-07 13:35BR/4.0.0.0155/23-May-07 13:35

    For more information, see Parse Vendor ID Information.

  6. Ensure that the configuration process completed correctly.

    On the phone, press the Menu key, and then select Status > Platform > Application > Main to see the UC Software version and Status > Platform > Configuration to see the configuration files downloaded to the phone.

    Monitor the provisioning server event log and the uploaded event log files (if permitted). All configuration files used by the provisioning server are logged.

    The phone will upload two logs files to the LOG_DIRECTORY directory:

    <MACaddress>-app.log and <MACaddress>-boot.log .

    You can now instruct your users to start making calls.

Upgrade Polycom UC Software

You can upgrade the software that is running on the Polycom phones in your organization. The upgrade process varies with the version of Polycom UC Software that is currently running on your phones and with the version that you want to upgrade to. The Updater, UC Software executable, and configuration files can all be updated using centralized provisioning.

 

Admin Tip: Updating UC Software on a Single Phone

You can use the Software Upgrade tool in the Web Configuration Utility to update the UC Software version running on a single phone. Note that configuration changes made to individual phones using the Web Configuration Utility will override configuration settings made using central provisioning. For instructions on how to update UC Software, see Use the Software Upgrade Tool in the Web Configuration Utility (Feature Profile 67993).

 

Web Info: Downgrading from UC Software 4.0.0 or later

Once you have deployed the phones using UC Software 4.0.0 or later, you can downgrade to a previous software release by following the instructions in Technical Bulletin 64731: Upgrading Polycom Phones to and Downgrading Phones From Polycom UC Software 4.0.0.

To continue setting up a provisioning server, administrators can use the instructions shown in Upgrade Phones from UC Software 4.0.x. If you provisioned a VVX 1500 phone using CMA, see Upgrade Polycom UC Software Using Polycom CMA.

If you are using legacy phones—including SoundPoint IP 300, 301, 320, 330, 430, 500, 501, 600, 601, and 670, or SoundStation IP 4000, 6000 and 7000 phones—you will need to change the phone configuration files to support these legacy phones. To provision legacy phones, go to Support Legacy Phones.

The following models were discontinued:

  • The SoundPoint IP 300 and 500 phones as of May 2006

  • The SoundPoint IP 301, 600, and 601 phones as March 2008

  • The SoundPoint IP 501 phone as of August 2009

  • The SoundStation IP 4000 phone as of May 2009

  • The SoundPoint IP 430 phone as of April 2010

  • The SoundPoint IP 320 and 330 phones as of December 2009

The following models will not be supported beyond UC Software 4.0.x:

  • The SoundStation IP 6000 phone

  • The SoundStation IP 7000 phone

  • The SoundPoint IP 670 phone

Upgrade Phones from UC Software 4.0.x

If your Polycom phones are running a version of UC Software 4.0.x or later, you can upgrade to a more recent UC Software version using the instructions in this section. If your phones are running a software release earlier than UC Software 4.0.x, you can upgrade to UC Software 4.0.x by following the instructions in Technical Bulletin 64731: Upgrading Polycom Phones to and Downgrading Phones From Polycom UC Software 4.0.0.

To update phones to Polycom UC Software 4.0.1:

  1. Back up your existing application and configuration files.

  2. Create your new configuration using UC Software 4.1.0.

    Configuration file changes and enhancements are explained in the Release Notes that accompany the software.

     

    Caution: Mandatory Changes to Configuration Files

    To ensure predictable phone behavior, the configuration files listed in CONFIG_FILES attribute of the master configuration file must be updated when the software is updated. You will need to add new configuration files to the CONFIG_FILES attribute in the appropriate order.

  3. Save the new configuration files and images (such as sip.ld ) on your provisioning server.

  4. Reboot the phones using an automatic method such as polling or check-sync.

    The phones can be rebooted remotely through the SIP signaling protocol. See <voIP.SIP.specialEvent.*/>.

The phones can be configured to periodically poll the provisioning server for changed configuration files or application executables. If a change is detected, the phone may reboot to download the change.

 

Tip: Rebooting Your Phone

You should only reboot your phone using the multiple-key combination as a backup option if another reboot method fails. For details on using a multiple key combination to reboot your phone, see Multiple Key Combinations.

You can reboot phones remotely through the SIP signaling protocol. See the parameter voIpProt.SIP.specialEvent.checkSync.alwaysReboot in <voIpProt/>.

You can configure the phones 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. See prov.polling.*.

Support Legacy Phones

With enhancements available since BootROM 4.0.0 and SIP 2.1.2, you can specify a different software and configuration files for legacy phones in the same master configuration file you are using for your non-legacy phones.

Polycom UC Software 5.0 or later software distributions contain only the files for that release. To use a software version for a legacy phone in the same master configuration file, you need to specify the phone product name, phone model number, or phone part number, and rename the legacy phone configuration files.

To get the phone product name, phone model number, or phone part number for a phone, see Product, Model, and Part Number Mapping.

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, 601, and SoundStation IP 4000 phones, or a previous 3.2.z distribution that is compatible with SoundPoint IP 430 phones, or a previous 3.3.w distribution that is compatible with SoundPoint IP 320 and 330 phones, or a previous 4.0.v distribution that is compatible with SoundPoint IP 670 and SoundStation IP 6000 and 7000 phones.

The SoundPoint IP 300 and 500 phones will be supported on the latest maintenance patch release of the SIP 2.1 software stream—currently SIP 2.1.4. Any critical issues that affect SoundPoint IP 300 and 500 phones will be addressed by a maintenance patch on this stream until the End of Life date for these products. Phones should be upgraded to BootROM 4.0.0 for these changes to be effective.

The SoundPoint IP 301, 501, 600, and 601, and the SoundStation IP 4000 phones will be supported on the latest maintenance patch release of the SIP 3.1 software stream—currently SIP 3.1.7 . Any critical issues that affect SoundPoint IP 300 and 500 phones will be addressed by a maintenance patch on this stream until the End of Life date for these products. Phones should be upgraded to BootROM 4.0.0 or later for these changes to be effective.

The SoundPoint IP 430 phone will be supported on the latest maintenance patch release of the SIP 3.2 software stream—currently SIP 3.2.4RevB. Any critical issues that affect SoundPoint IP 430 phones will be addressed by a maintenance patch on this stream until the End of Life date for these products. Phones should be upgraded to BootROM 4.2.2 for these changes to be effective.

The SoundPoint IP 320 and 330 phones will be supported on the latest maintenance patch release of the UC Software 3.3.1 software stream—currently UC Software 3.3.1RevF. Any critical issues that affect SoundPoint IP 320 and 330 phones will be addressed by a maintenance patch on this stream until the End of Life date for these products. Phones should be upgraded to BootROM 4.0.0 for these changes to be effective.

The SoundPoint IP 670 and SoundStation IP 6000 and 7000 are supported only by UC Software 4.0.x. Critical issues that affect these phones will be addressed by a maintenance patch on the 4.0.x stream until the End of Life date for these products. Phones should be upgraded to BootROM 4.0.0 for these changes to be effective.

If you are upgrading legacy phones to UC Software 4.0.x, Polycom recommends modifying your configuration files in the following way.

To upgrade legacy phones to UCS 4.1.x:

  1. Complete one of the following steps:

    • Place all bootrom.ld files corresponding to the BootROM release zip file onto the provisioning server.

    • Ensure that all phones are running BootROM 4.x.x or later.

  2. Copy sip.ld (or the appropriate individual sip.ld from the split image file) from the UC Software 4.1.0 or later release distribution onto the provisioning server.

  3. Rename the sip.ld , sip.cfg , and phone1.cfg from the previous distribution to one of the following sets of names, depending on the phone models that you are provisioning:

    • For SoundPoint IP 300 and 500 phones, rename the files to sip_21x.ld , sip_21x.cfg , and phone1_21x.cfg , respectively.

    • For SoundPoint IP 301, 501, 600, 601, and SoundStation IP 4000 phones, rename the files to sip_31y.ld , sip_31y.cfg , and phone1_31y.cfg , respectively.

    • For SoundPoint IP 430 phones, rename the files to sip_323.ld , sip_323.cfg , and phone1_323.cfg , respectively.

    • For SoundPoint IP 320 and 330 phones, rename sip.ld to sip_33x.ld and add *_33x to the end of each .cfg configuration files (for example, rename phone1.cfg to phone1_33x.cfg and rename sip-basic.cfg to sip-basic_33x.cfg ).

  4. Save the renamed configuration files to the provisioning server.

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

    The following illustration shows an example file:

    image

  6. Remove the <MACaddress>.cfg files on your provisioning server if the files correspond to legacy phones.

    You can support legacy phones using an enhancement that was added in BootROM 3.2.1/SIP 2.0.1. This enhancement enables you to use a phone-specific variable substitution [PHONE_MAC_ADDRESS] to name your configuration files and avoid the need to create a unique <MACaddress>.cfg file for each phone.

    If you do not use a variable substitution, you will need to change all of the <MACaddress>.cfg files for SoundPoint IP 300, 301, 320, 330, 430, 500, 501, 600, and 601, and SoundStation IP 4000 phones. You will also need to make changes to all of the <MACaddress>.cfg files if you do not know which phones are SoundPoint IP 300, 301, 320, 330, 430, 500, 501, 600, and 601 or SoundStation IP 4000 models.

    For details on using variable substitution as a configuration method, see Provision with the Master Configuration File (Best Practices 75907) on the Polycom UC Software Support Center.

    For more information, see Technical Bulletin 35311: Maintaining Older Polycom Phones Beyond Their Last Supported Software Release.

Provision VVX 1500 Phones Using a Polycom CMA System

You can provision your organization’s VVX 1500 phones and update the software using a Polycom CMA system. See the latest UC Software Release Notes on the Latest Polycom UC Software Release for Polycom UC Software and Polycom CMA for specific compatibility requirements and recommendations.

You can also provision your organization’s VVX 1500 phones in a hybrid way, using both Polycom CMA and a provisioning server. In hybrid scenarios, settings made using the Polycom CMA have a higher priority than settings made using centralized provisioning. When the phone reboots, it will check the Polycom CMA system first for new software, and then check the provisioning server for configuration files and directories. Note that the phone will not check the provisioning server for software when CMA provisioning is enabled. To disable the CMA system, see Disable the Polycom CMA System.

In dynamic management mode, the Polycom CMA system can do the following:

  • Configure your VVX 1500 phones using an automatic provisioning service

  • Register your VVX 1500 phones with a standard-based presence service, so that presence states are shared with Polycom CMA contacts

  • Provide your VVX 1500 phones with automatic software updates

     

    Web Info: Provisioning VVX 1500 Phones using a Polycom CMA System

    For more information about provisioning by a Polycom CMA system, see the Polycom CMA System Operations Guide.

This section contains information on:

Provision Using Polycom CMA

In order to provision using the Polycom CMA system, the VVX phones must be installed with Polycom UC Software 3.3.1 or later.

Polycom CMA requires that the management application be installed on the same network to which your VVX 1500 phones are connected.

To configure the provisioning service settings on VVX 1500 phones:

  1. Press the Menu key, and then select Settings > Advanced > Administration Settings > Network Configuration > CMA Menu .

    You must enter the administrator password to access the network configuration. The factory default password is 456 .

  2. Enter the following values:

    • CMA Mode : Select Static or Auto . If Auto: CMA picks the DNS name (ignores the Server Address—listed next). If Static, CMA uses the server address, listed next.

    • Server Address : Enter the address of the Polycom CMA system running the provisioning service. The address can be an IP address or a fully qualified domain name. For example, 123.45.67.890.

  3. Scroll to Login Credentials and tap the Select soft key. Enter the following values:

    • Domain : Enter the domain for registering to the provisioning service. For example, NorthAmerica.

       

      Tip: Domain When You Are Not Using Single Sign On

      If you are not using a Single Sign On login with Active Directory on the Polycom CMA system, the phone will use the local accounts created on the Polycom CMA server.

    • User : Enter the user name for registering to the provisioning service. For example, bsmith.

    • Password : Enter the password that registers the VX 1500 phone to the provisioning service (associated with the CMA user account). For example, 123456.

  4. Tap the Back soft key three times.

  5. Select Save Config .

    The VVX 1500 phone reboots.

     

    Tip: Configuring the Line Key with a Polycom CMA System

    Only one phone line associated with a Polycom CMA system can be provisioned on a VVX 1500 phone, but the line key associated with that line is configurable. For more information on configuration file settings, see <prov/>.

     

    Web Info: Searching the CMA Directory

    The user can now search for CMA users and groups in the CMA directory, place calls to those contacts, and view their presence status. For more information, see the User Guide for the Polycom VVX 1500 Phone.

Disable the Polycom CMA System

If you provision phones using the CMA system, and then want to disable that provisioning, use the following procedure.

To disable Polycom CMA provisioning:

  1. Press the Menu key, and then select Settings > Advanced > Administration Settings > Network Configuration > CMA Menu .

    You must enter the administrator password to access the network configuration. The default password is 456.

  2. In CMA Mode: select Disable .

  3. Tap the Back soft key twice.

  4. Select Save Config .

    The VVX 1500 phone reboots.

Upgrade Polycom UC Software Using Polycom CMA

Software upgrades of the VVX 1500 phones are triggered by the Polycom CMA system as either automatic or scheduled updates.

Software update timer changes will not take effect until the next interval—after the current interval expires. For example:

  • The current software update timer is set to 60 minutes.

  • The provisioning by the Polycom CMA system fails.

  • The software update timer is reset to five minutes (default). The five-minute timer is not set off until the last 60 minutes timer expires.

Monitor Using Polycom CMA

The following information is sent by the VVX 1500 phone to the Polycom CMA system:

  • Network adapter probe  This is the first message that the VVX 1500 phone sends to the Polycom CMA system. It provides the phone’s IP address.

  • Software update check  This message provides the phone model, MAC address, and UC Software version currently running on the phone.

  • Software update status  This message provides confirmation of the phone’s software upgrade.

  • Provisioning profile  This message requests configuration data for the phone so that the user can access the CMA directory, add CMA contacts to their Buddy list, and place audio and video calls to those contacts.

  • Provisioning status  This message provides confirmation of the receipt of the configuration data from the Polycom CMA system.

  • Call statistics  These messages are sent for all calls placed or answered by the phone’s user.

  • Call end  This message is sent after all calls have ended.

  • Heartbeat data  This message contains status information about the phone. This message is sent to the Polycom CMA system periodically. How often the message is sent is configured by the administrator of the Polycom CMA system.

  • Events  This message provides information like gatekeeper registration events, presence registration events, and LDAP events to the Polycom CMA system.