Cisco Unified IP Phone 8961, 9951, and 9971 Administration Guide for Cisco Unified Communications Manager 8.6 (SIP)
Preparing to Install the Cisco Unified IP Phone on Your Network
Downloads: This chapterpdf (PDF - 275.0KB) The complete bookPDF (PDF - 15.26MB) | Feedback

Preparing to Install the Cisco Unified IP Phone on Your Network

Table Of Contents

Preparing to Install the Cisco Unified IP Phone on Your Network

Understanding Interactions with Other Cisco Unified IP Telephony Products

Understanding How the Cisco Unified IP Phone Interacts with Cisco Unified Communications Manager

Understanding How the Cisco Unified IP Phone Interacts with the VLAN

Providing Power to the Cisco Unified IP Phone

Power Guidelines

Power Outage

Reducing Power Consumption on the Phone

Power Save Mode

EnergyWise Mode

Power Negotiation over LLDP

Obtaining Additional Information About Power

Understanding Phone Configuration Files

Understanding the Phone Startup Process

Adding Phones to the Cisco Unified Communications Manager Database

Adding Phones with AutoRegistration

Adding Phones with AutoRegistration and TAPS

Adding Phones with Cisco Unified Communications Manager Administration

Adding Phones Using BAT Phone Template

Determining the MAC Address for a Cisco Unified IP Phone


Preparing to Install the Cisco Unified IP Phone on Your Network


Cisco Unified IP Phones enable you to communicate by using voice over a data network. To provide this capability, the IP Phones depend upon and interact with several other key Cisco Unified IP Telephony components, including Cisco Unified Communications Manager.

This chapter focuses on the interactions between the Cisco Unified IP Phone 8961, 9951, and 9971 and Cisco Unified Communications Manager, DNS and DHCP servers, TFTP servers, and switches. It also describes phone power options.

For related information about voice and IP communications, see this URL:

http://www.cisco.com/en/US/products/sw/voicesw/index.html

This chapter provides an overview of the interaction between the Cisco Unified IP Phone and other key components of the Voice over IP (VoIP) network. It includes the following topics:

Understanding Interactions with Other Cisco Unified IP Telephony Products

Providing Power to the Cisco Unified IP Phone

Understanding Phone Configuration Files

Understanding the Phone Startup Process

Adding Phones to the Cisco Unified Communications Manager Database

Determining the MAC Address for a Cisco Unified IP Phone

Understanding Interactions with Other Cisco Unified IP Telephony Products

To function in the IP telephony network, the Cisco Unified IP Phone must be connected to a networking device, such as a Cisco Catalyst switch. You must also register the Cisco Unified IP Phone with a Cisco Unified Communications Manager system before sending and receiving calls.

This section includes the following topics:

Understanding How the Cisco Unified IP Phone Interacts with Cisco Unified Communications Manager

Understanding How the Cisco Unified IP Phone Interacts with the VLAN

Understanding How the Cisco Unified IP Phone Interacts with Cisco Unified Communications Manager

Cisco Unified Communications Manager is an open and industry-standard call processing system. Cisco Unified Communications Manager software sets up and tears down calls between phones, integrating traditional PBX functionality with the corporate IP network. Cisco Unified Communications Manager manages the components of the IP telephony system, such as the phones, the access gateways, and the resources necessary for features such as call conferencing and route planning. Cisco Unified Communications Manager also provides:

Firmware for phones

Configuration file, CTL, and Identity Trust List (ITL) files via the TFTP service

Phone registration

Call preservation, so that a media session continues if signaling is lost between the primary Communications Manager and a phone

For information about configuring Cisco Unified Communications Manager to work with the IP devices described in this chapter, go to the Cisco Unified IP Phone Configuration chapter in the Cisco Communications Manager Administration Guide.

For an overview of security functionality for the Cisco Unified IP Phone, see the "Understanding Security Features for Cisco Unified IP Phones" section.


Note If the Cisco Unified IP Phone model that you want to configure does not appear in the Phone Type drop-down list in Cisco Unified Communications Manager Administration, go to the following URL and install the latest support patch for your version of Cisco Unified Communications Manager: http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml


Related Topic

Telephony Features Available for the Cisco Unified IP Phone

Understanding How the Cisco Unified IP Phone Interacts with the VLAN

The Cisco Unified IP Phone 8961, 9951, and 9971 contain an internal Ethernet switch, enabling forwarding of packets to the phone, and to the Computer (access) port and the Network port on the back of the phone.

If a computer is connected to the Computer (access) port, the computer and the phone share the same physical link to the switch and share the same port on the switch. This shared physical link has the following implications for the VLAN configuration on the network:

The current VLANs might be configured on an IP subnet basis. However, additional IP addresses might not be available to assign the phone to the same subnet as other devices connected to the same port.

Data traffic present on the VLAN supporting phones might reduce the quality of Voice-over-IP traffic.

Network security may indicate a need to isolate the VLAN voice traffic from the VLAN data traffic.

You can resolve these issues by isolating the voice traffic onto a separate VLAN. The switch port that the phone is connected to would be configured for separate VLANs for carrying:

Voice traffic to and from the IP Phone (auxiliary VLAN on the Cisco Catalyst 6000 series, for example)

Data traffic to and from the PC connected to the switch through the Computer (access) Port of the IP Phone (native VLAN)

Isolating the phones on a separate, auxiliary VLAN increases the quality of the voice traffic and allows a large number of phones to be added to an existing network where there are not enough IP addresses for each phone.

For more information, see the documentation included with a Cisco switch. You can also access switch information at this URL:

http://cisco.com/en/US/products/hw/switches/index.html

Related Topics

Understanding the Phone Startup Process

Ethernet Setup Menu

Providing Power to the Cisco Unified IP Phone

The Cisco Unified IP Phone 8961, 9951, and 9971 can be powered with external power or with Power over Ethernet (PoE). External power is provided through a separate power supply. PoE is provided by a switch through the Ethernet cable attached to a phone.


Note When you install a phone that is powered with external power, connect the power supply to the phone and to a power outlet before you connect the Ethernet cable to the phone. When you remove a phone that is powered with external power, disconnect the Ethernet cable from the phone before you disconnect the power supply.


The following sections provide more information about phone power:

Power Guidelines

Power Outage

Reducing Power Consumption on the Phone

Power Negotiation over LLDP

Obtaining Additional Information About Power

Power Guidelines

Table 2-1 provides guidelines for Cisco Unified IP Phone 8961, 9951, and 9971 power.

Table 2-1 Guidelines for Cisco Unified IP Phone 8961, 9951, and 9971 Power 

Power Type
Guidelines

External power—Provided through the CP-PWR-CUBE-4= external power supply.

The Cisco Unified IP Phone 8961, 9951, and 9971 use the CP-PWR-CUBE-4 power supply.

Note You must use the CP-PWR-CUBE-4 when you deploy the Cisco Unified IP Phone 9971 on a wireless network.

External power—Provided through the Cisco Unified IP Phone Power Injector.

The Cisco Unified IP Phone Power Injector may be used with any Cisco Unified IP Phone. Functioning as a midspan device, the injector delivers inline power to the attached phone. The Cisco Unified IP Phone Power Injector is connected between a switch port and the IP Phone, and supports a maximum cable length of 100m between the unpowered switch and the IP Phone.

PoE power—Provided by a switch through the Ethernet cable attached to the phone.

Cisco Unified IP Phone 8961, 9951, and 9971 support IEEE 802.3af Class 3 power on signal pairs and spare pairs.

Cisco Unified IP Phone 8961, 9951, and 9971 support IEEE 802.3at for external add-on devices.

To ensure uninterruptible operation of the phone, make sure that the switch has a backup power supply.

Make sure that the CatOS or IOS version running on your switch supports your intended phone deployment. See the documentation for your switch for operating system version information.

Support for NG-PoE+—The Cisco Unified IP Phone 8961, 9951, and 9971 can draw more power than IEEE 802.3at, as long as there is NG-PoE+ switch support.


Power Outage

Your accessibility to emergency service through the phone is dependent on the phone being powered. If there is an interruption in the power supply, Service and Emergency Calling Service dialing do not function until power is restored. In the case of a power failure or disruption, you may need to reset or reconfigure equipment before using the Service or Emergency Calling Service dialing.

Reducing Power Consumption on the Phone

You can reduce the amount of energy that the Cisco Unified IP Phone consumes using the following methods:

by scheduling when the phone goes into power save mode.

by scheduling when the phone goes into EnergyWise (Power Save Plus) mode.

Power Save Mode

In Power Save mode, the backlight on the screen is not lit when the phone is not in use. The phone remains in Power Save mode for the scheduled duration or until the user lifts the handset or presses any button. In the Phone Configuration window on Cisco Unified Communications Administration, configure the following parameters.

Days Display Not Active—Specify the days that the backlight remains inactive.

Display on Time—Schedule the time of day that the backlight automatically activates. on the days listed in the off schedule.

Display on Duration—Indicates the length of time that the backlight is active after the backlight is enabled by the programmed schedule

Display Idle Timeout—Defines the period of user inactivity on the phone before the backlight is turned off.

EnergyWise Mode

In addition to Power Save mode, the Cisco Unified IP Phone 8961, 9951, and 9971 support Cisco EnergyWise (Power Save Plus). When your network contains an EnergyWise (EW) controller (for example, a Cisco switch with the EnergyWise feature enabled), you can configure these phones to sleep (power down) and wake (power up) on a schedule to further reduce your power consumption.

You set up each phone to enable or disable the EnergyWise settings. If EnergyWise is enabled, you configure a sleep and wake time, as well as other parameters. These parameters are sent to the phone as part of the phone configuration XML file. In the Phone Configuration window on Cisco Unified Communications Administration, configure the following parameters

Enable Power Save Plus—Selects the schedule of days for which the phone powers off.

Phone On Time—Determines when the phone automatically turns on for the days selected in the Enable Power Save Plus field.

Phone Off Time—The time of day that the phone powers down for the days selected in the Enable Power Save Plus field.

Phone Off Idle Timeout—The length of time that the phone must be idle before the phone powers down.

Enable Audio Alert—When enabled, instructs the phone to play an audible alert starting at 10 minutes before to the time specified in the Phone Off Time field.

EnergyWise Domain—The EnergyWise domain that the phone is in.

EnergyWise Secret—The security secret password that is used to communicate within the EnergyWise domain.

Allow EnergyWise Overrides—Determines whether you allow the EnergyWise domain controller policy to send power level updates to the phones.

When a phone is sleeping, the power sourcing equipment (PSE) provides minimal power to the phone to illuminate the Select key, and the Select key can be used to wake up the phone when it is sleeping.

Power Negotiation over LLDP

The phone and the switch negotiate the power that the phone can consume. Cisco Unified IP Phone 8961, 9951, and 9971 operate at multiple power settings, which lowers their consumption when less power is available.

After a phone reboots, the switch locks to one protocol (CDP or LLDP) for power negotiation. It locks to the first protocol (containing a power Threshold Limit Value (TLV)) that the phone transmits. If the system administrator disables that protocol on the phone, it cannot power up any accessories because the switch does not respond to power requests in the other protocol.

Cisco recommends that Power Negotiation always be enabled (default) when connecting to a switch that supports power negotiation.

If disabled, the switch may disconnect power to the phone. If the switch does not support power negotiation, then disable the Power Negotiation feature before you power up accessories over PoE. When the Power Negotiation feature is disabled, the phone can power the accessories up to the maximum allowed by the IEEE 802.3af-2003 standard.


Note When CDP and Power Negotiation are disabled, the phone can power the accessories up to 15.4W.


To enable or disable power negotiation, see Table 8-1, "Telephony Features for the Cisco Unified IP Phone".

Obtaining Additional Information About Power

For related information about power, see the documents shown in Table 2-2. These documents provide information about the following topics:

Cisco switches that work with Cisco Unified IP Phones

Cisco IOS releases that support bidirectional power negotiation

Other requirements and restrictions regarding power


Understanding Phone Configuration Files

Configuration files for a phone are stored on the TFTP server and define parameters for connecting to Cisco Unified Communications Manager. In general, any time you make a change in Cisco Unified Communications Manager that requires the phone to be reset, a change is automatically made to the configuration file for the phone.

Configuration files also contain information about which image load the phone should be running. If this image load differs from the one currently loaded on a phone, the phone contacts the TFTP server to request the required load files.

A phone accesses a default configuration file named XmlDefault.cnf.xml from the TFTP server when the following conditions exist:

You enable autoregistration in Cisco Unified Communications Manager

You have not added the phone to the Cisco Unified Communications Manager database

The phone is registering for the first time


Note If the device security mode in the configuration file is set to Authenticated or Encrypted, but the phone has not received a CTL or ITL file, the phone tries four times to obtain the file so it can register securely.


If auto registration is not enabled and the phone does not exist in the Cisco Unified Communications Manager database, the system rejects the phone registration request and a blank screen displays.

If the phone has registered before, the phone accesses the configuration file named SEPmac_address.cnf.xml, where mac_address is the MAC address of the phone.

The filenames are derived from the MAC address and description fields in the Phone Configuration window of Cisco Unified Communications Manager Administration. The MAC address uniquely identifies the phone.

Understanding the Phone Startup Process

When connecting to the VoIP network, the Cisco Unified IP Phone 8961, 9951, and 9971 go through a standard startup process that is described in Table 2-3. Depending on your specific network configuration, not all of these steps may occur on your Cisco Unified IP Phone.

Table 2-3 Cisco Unified IP Phone Startup Process 

Task
Purpose
Related Topics

1.

Obtain power from the switch.

If a phone is not using external power, the switch provides in-line power through the Ethernet cable attached to the phone.

Adding Phones to the Cisco Unified Communications Manager Database.

Resolving Startup Problems.

2.

(For a Cisco Unified IP Phone 9971 in a wireless LAN only) Scanning for an access point.

The Cisco Unified IP Phone scans the RF coverage area with the radio. The phone searches the network profiles and scans for access points that contain a matching SSID and authentication type. The phone associates with the access point with the highest RSSI that matches with the network profile.

Interacting with Cisco Unified Wireless APs.

3.

(For a Cisco Unified IP Phone 9971 in a wireless LAN only) Authenticating with the access point.

The Cisco Unified IP Phone begins the authentication process:

If set for Open, then any device can authenticate to the access point. For added security, static WEP encryption might optionally be used.

If set to Shared Key, the phone encrypts the challenge text using the WEP key and the access point must verify the WEP key used to encrypt the challenge text before network access is available.

If set for LEAP or EAP-FAST, then the user name and password are authenticated by the RADIUS server before network access is available. For more information about the name and password authentication, see "WLAN Setup Menu" section.

If set for Auto (AKM), the phone looks for an access point with one of the following key management options enabled:

WPA, WPA2, or CCKM—The username and password are authenticated by the RADIUS server before network access is available.

WPA-Pre-shared key, WPA2-Pre-shared key—The phone authenticates with the access point using the pre-shared key.

Authentication Methods.

4.

Load the stored phone image.

The Cisco Unified IP Phone has non-volatile Flash memory in which it stores firmware images and user-defined preferences. At startup, the phone runs a bootstrap loader that loads a phone firmware image stored in Flash memory. Using this image, the phone initializes the software and hardware.

Resolving Startup Problems.

5.

Configure the VLAN.

If the Cisco Unified IP Phone is connected to a Cisco Catalyst switch, the switch next informs the phone of the voice VLAN defined on the switch. The phone needs to know the VLAN membership before it can proceed with the Dynamic Host Configuration Protocol (DHCP) request for an IP address.

Ethernet Setup Menu.

Resolving Startup Problems.

6.

Obtain an IP address.

If the Cisco Unified IP Phone is using DHCP to obtain an IP address, the phone queries the DHCP server to obtain one. If you are not using DHCP in your network, you must assign static IP addresses to each phone locally.

Ethernet Setup Menu.

Resolving Startup Problems.

7.

Requesting the CTL file.

The TFTP server stores the CTL file. This file contains the certificates necessary for establishing a secure connection between the phone and Cisco Unified CM.

See Cisco Unified Communications Manager Security Guide, Configuring the Cisco CTL Client.

8.

Requesting the ITL file.

The phone requests the ITL file after it requests the CTL file. The ITL file contains the certificates of the entities that the phone can trust. The certificates are used for authenticating a secure connection with the servers or authenticating a digital signature signed by the servers. The ITL file is supported on the Cisco Unified CM 8.5 and later.

See the "Preparing to Install the Cisco Unified IP Phone on Your Network" chapter.

See the "Troubleshooting and Maintenance" chapter.

9.

Access a TFTP server.

In addition to assigning an IP address, the DHCP server directs the Cisco Unified IP Phone to a TFTP Server. If the phone has a statically defined IP address, you must configure the TFTP server locally on the phone; the phone then contacts the TFTP server directly.

Note You can also assign an alternative TFTP server to use instead of the one assigned by DHCP.

Ethernet Setup Menu.

Resolving Startup Problems.

10.

Request the configuration file.

The TFTP server has configuration files, which define parameters for connecting to Cisco Unified Communications Manager and other information for the phone.

Adding Phones to the Cisco Unified Communications Manager Database.

Resolving Startup Problems.

11.

Contact Cisco Unified CM

The configuration file defines how the Cisco Unified IP Phone communicates with Cisco Unified CM and provides a phone with the load ID. After obtaining the file from the TFTP server, the phone attempts to make a connection to the highest priority Cisco Unified CM on the list.

If the security profile of the phone is configured for secure signaling (encrypted or authenticated), and the Cisco Unified CM is set to secure mode, the phone makes a TLS connection. Otherwise, it makes a nonsecure TCP connection.

If the phone was manually added to the database, Cisco Unified Communications Manager identifies the phone. If the phone was not manually added to the database and autoregistration is enabled in Cisco Unified Communications Manager, the phone attempts to autoregister itself in the Cisco Unified Communications Manager database.

Note Autoregistration is disabled when you configure the CTL client. In this case, the phone must be manually added to the Cisco Unified CM database.

See the "Preparing to Install the Cisco Unified IP Phone on Your Network" chapter.

See the "Troubleshooting and Maintenance" chapter.


Adding Phones to the Cisco Unified Communications Manager Database

Before installing the Cisco Unified IP phone, you must choose a method for adding phones to the Cisco Unified Communications Manager database. These sections describe the methods:

Adding Phones with AutoRegistration

Adding Phones with AutoRegistration and TAPS

Adding Phones with Cisco Unified Communications Manager Administration

Adding Phones Using BAT Phone Template

Table 2-4 provides an overview of these methods for adding phones to the Cisco Unified Communications Manager database.

Table 2-4 Methods for Adding Phones to the Cisco Unified Communications Manager Database 

Method
Requires MAC Address?
Notes

Autoregistration

No

Results in automatic assignment of directory numbers

Autoregistration with TAPS

No

Requires autoregistration and the Bulk Administration Tool (BAT); updates information in the Cisco Unified IP Phone and in Cisco Unified Communications Manager Administration

Using the Cisco Unified Communications Manager Administration

Yes

Requires phones to be added individually

Using BAT

Yes

Allows for simultaneous registration of multiple phones


Adding Phones with AutoRegistration

By enabling autoregistration before you begin installing phones, you can:

Add phones without first gathering MAC addresses from the phones.

Automatically add a Cisco Unified IP Phone to the Cisco Unified Communications Manager database when you physically connect the phone to your IP telephony network. During autoregistration, Cisco Unified Communications Manager assigns the next available sequential directory number to the phone.

Quickly enter phones into the Cisco Unified Communications Manager database and modify any settings, such as the directory numbers, from Cisco Unified Communications Manager.

Move autoregistered phones to new locations and assign them to different device pools without affecting their directory numbers.


Note Cisco recommends you use autoregistration to add less than 100 phones to your network. To add more than 100 phones to your network, use the Bulk Administration Tool (BAT). See the "Adding Phones Using BAT Phone Template" section.


Autoregistration is disabled by default. In some cases, you might not want to use autoregistration; for example, if you want to assign a specific directory number to the phone, or use a secure connection with Cisco Unified CM as described in Cisco Unified CM Security Guide. For information about enabling autoregistration, go to the "Enabling Auto-Registration" section in the Cisco Unified Communications Manager Administration Guide.

Related Topics

Adding Phones with AutoRegistration and TAPS

Adding Phones with Cisco Unified Communications Manager Administration

Adding Phones Using BAT Phone Template

Adding Phones with AutoRegistration and TAPS

You can add phones with autoregistration and TAPS, the Tool for AutoRegistered Phones Support, without first gathering MAC addresses from phones.

TAPS works with the Bulk Administration Tool (BAT) to update a batch of phones that were already added to the Cisco Unified Communications Manager database with dummy MAC addresses. Use TAPS to update MAC addresses and download pre-defined configurations for phones.


Note Cisco recommends you use autoregistration and TAPS to add less than 100 phones to your network. To add more than 100 phones to your network, use the Bulk Administration Tool (BAT). See the "Adding Phones Using BAT Phone Template" section.


To implement TAPS, you or the end-user dial a TAPS directory number and follow voice prompts. After the process is complete, the phone contains the directory number and other settings, and the phone is updated in Cisco Unified Communications Manager Administration with the correct MAC address.

Autoregistration must be enabled in Cisco Unified Communications Manager Administration (System > Cisco Unified CM) for TAPS to function.


Note When you configure the cluster for mixed mode through the Cisco CTL client, autoregistration is automatically disabled. When you configure the cluster for non-secure mode through the Cisco CTL client, autoregistration is not enabled automatically.


For more information, see the Cisco Unified Communications Manager Bulk Administration Guide.

Related Topics

Adding Phones with AutoRegistration

Adding Phones with Cisco Unified Communications Manager Administration

Adding Phones Using BAT Phone Template

Adding Phones with Cisco Unified Communications Manager Administration

You can add phones individually to the Cisco Unified Communications Manager database by using Cisco Unified Communications Manager Administration. To do so, you first need to obtain the MAC address for each phone.

For information about determining a MAC address, see the "Determining the MAC Address for a Cisco Unified IP Phone" section.

After you collect MAC addresses, in Cisco Unified Communications Manager Administration, choose Device > Phone and click Add New to begin.

For complete instructions and conceptual information about Cisco Unified Communications Manager, go to the "Cisco Unified Communications Manager Overview" chapter in the Cisco Unified Communications Manager System Guide.

Related Topics

Adding Phones with AutoRegistration

Adding Phones with AutoRegistration and TAPS

Adding Phones Using BAT Phone Template

Adding Phones Using BAT Phone Template

The Cisco Unified Communications Bulk Administration Tool (BAT) enables you to perform batch operations including registration on multiple phones.

To add phones using BAT only (not in conjunction with TAPS), you must obtain the appropriate MAC address for each phone.

For information about determining a MAC address, see the "Determining the MAC Address for a Cisco Unified IP Phone" section.

For detailed instructions about adding phones using Bulk Administration menu, see the Cisco Unified Communications Manager Bulk Administration Guide, chapter Inserting Phones.

To add a phone to the Cisco Unified Communications Manager, follow these steps:

Procedure


Step 1 From Cisco Unified Communications Manager, choose Bulk Administration > Phones > Phone Template.

Step 2 Click Add New.

Step 3 Choose a Phone Type and click Next.

Step 4 Enter the details of phone specific parameters like Device Pool, Phone Button Template, Device Security Profile and so on.

Step 5 Click Save.

Step 6 From Cisco Unified Communications Manager, choose Device > Phone > Add New to add a phone using an existing BAT phone template.


For more information about using BAT, see the Cisco Unified Communications Manager Bulk Administration Guide. For more information about creating of BAT Phone Templates, see the Cisco Unified Communications Manager Bulk Administration Guide, Phone Template.

Related Topics

Adding Phones with AutoRegistration

Adding Phones with AutoRegistration and TAPS

Adding Phones with Cisco Unified Communications Manager Administration

Determining the MAC Address for a Cisco Unified IP Phone

Several procedures described in this manual require you to determine the MAC address of a Cisco Unified IP Phone. You can determine the MAC address of a phone in these ways:

From the phone, press the Applications button, choose Phone Information, and look at the MAC Address field.

Look at the MAC label on the back of the phone.

Display the web page for the phone and click the Device Information hyperlink.

For information about accessing the web page, see the "Accessing the Web Page for a Phone" section.