Filter
Top Products
91-30
Cisco Unified Communications Manager Administration Guide
OL-18611-01
Chapter 91 Cisco Unified IP Phone Configuration
Migrating Existing Phone Configuration to a Different Phone
Additional Information
For more information on phone configuration, as well as H.323 clients, CTI ports, and other devices from
Cisco Unified Communications Manager Administration, see the
“Related Topics” section on
page 91-42.
Migrating Existing Phone Configuration to a Different Phone
The Phone Migration window in Cisco Unified Communications Manager Administration allows you to
migrate feature, user, and line configuration for a phone to a different phone. You can migrate data to a
different phone model or to the same phone model that runs a different protocol. For example, you can
migrate data from a Cisco Unified IP Phone 7965 to a Cisco Unified IP Phone 7975, or you can migrate
data from a phone model that runs SCCP, for example, the Cisco Unified IP Phone 7965 (SCCP) and
move it to the same phone model that runs SIP, for example, the Cisco Unified IP Phone 7965 (SIP).
Tip Phone migration allows you to port existing phone configuration to a new phone without the need to add
a phone, lines, speed dials, and so on.
Before you migrate existing phone configuration to a different phone, see the following topics:
• Before You Begin, page 91-30—information to review before you migrate the settings.
• Procedure, page 91-31—procedure to perform for migrating the settings.
• Table 91-3—configuration settings that display in the Phone Migration Configuration window
Before You Begin
Before you can migrate phone configuration to a new phone, consider the following information:
• If the phone models do not support the same functionality, be aware that you may lose functionality
on the new phone after the migration occurs. Before you save the migration configuration in the
Phone Migration window, Cisco Unified Communications Manager Administration displays a
warning that you may lose feature functionality.
• Some phone models do not support phone migration; for example, CTI port, H.323 client,
Cisco
Unified Mobile Communicator, Cisco IP Softphone, and so on.
• Before you can migrate the phone configuration, you must create a phone template in BAT for the
phone model and protocol to which you want to migrate. For example, if you want to migrate the
configuration for a Cisco Unified IP Phone 7965 to a Cisco Unified IP Phone 7975, you create the
phone template for the Cisco Unified IP Phone 7975.
If the Phone Configuration window does not display a field for the original phone, but the field is
required for the new phone, the new phone uses the value from the phone template for the required
field.
• The new phone uses the same existing database record as the original phone, so migrating the phone
configuration to the new phone removes the configuration for the original phone from Cisco Unified
Communications Manager Administration/the Cisco Unified Communications Manager database;
that is, you cannot view or access the configuration for the original phone after the migration.
Migrating to a phone that uses fewer speed dials or lines does not remove the speed dials or lines
for the original phone from Cisco Unified Communications Manager Administration/the Cisco
Unified Communications Manager database, although some speed dials/lines do not display on the
new phone. After you migrate the configuration, you can see all speed dials and lines for the original
phone in the Phone Configuration window for the new phone.