Filter
Top Products
Deployment Guide for the Polycom VVX 1500 D Phone
2 - 2
4. If you choose to manage a group of phones through a provisioning
server, you need to:
a Set up a provisioning server and download the appropriate files. Refer
to Setting Up the Provisioning Server on page 2-11.
b Create configuration files to support the required features on the
phones. Refer to Deploying Phones From the Provisioning Server on
page 2-13.
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.
c (Optional.) Upgrade the phone software after changing the
configuration files and deploying the phones.
Out of the box, the Polycom VVX 1500 D phone is running BootROM
4.2.1 and SIP 3.2.2. To determine the BootROM version running on the
phone, press the Menu key, select Settings > Status > Platform >
Phone, and then scroll down to BootROM. To determine the Polycom
UC Software version running on the phone, press the Menu key, and
then select Settings > Status > Platform > Application > Main.
Refer to Upgrading the Phone’s Software on page 2-16.
5. If you choose to manage a group of phones through a Polycom®
Converged Management Application™ (CMA™) system, you need to:
a Ensure that the phone is running the correct version to allow
provisioning by a Polycom CMA system.
The VVX 1500 D phone must be running UC software 3.3.0 or later. If
the phone is not running this software version, refer to Upgrading the
Phone’s Software on page 2-16.
b Ensure that the Polycom CMA system is running version 5.0 .
For more information on upgrading the Polycom CMA system, refer
to the Polycom CMA v5.0 Upgrade Guide, which is available at
http://www.polycom.com/support/network/management_schedu
ling/cma_4000_5000.html .
For installation and maintenance of the Polycom VVX 1500 D phone, the use of a
provisioning server is strongly recommended. This allows for flexibility in installing,
upgrading, maintaining, and configuring the phone. Configuration, log, language,
and directory files are normally located on this server. Allowing the phone write
access to the server is encouraged.
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 for
occasions when the provisioning server is not available, but is not intended to be
used for long-term operation of the phones.