Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager 5.1 (SCCP), Cisco Unified IP Phones 7961G/7961G-GE and 7941G/7941G-GE
Preparing to Install the Cisco Unified IP Phone on Your Network
Downloads: This chapterpdf (PDF - 263.0KB) The complete bookPDF (PDF - 3.32MB) | 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 CallManager

Understanding How the Cisco Unified IP Phone Interacts with the VLAN

Providing Power to the Cisco Unified IP Phone

Power Guidelines

Power Outage

Obtaining Additional Information about Power

Understanding Phone Configuration Files

Understanding the Phone Startup Process

Adding Phones to the Cisco Unified CallManager Database

Adding Phones with Auto-Registration

Adding Phones with Auto-Registration and TAPS

Adding Phones with Cisco Unified CallManager Administration

Adding Phones with BAT

Using Cisco Unified IP Phones with Different Protocols

Converting a New Phone from SCCP to SIP

Converting an In-Use Phone from SCCP to SIP

Converting an In-Use Phone from SIP to SCCP

Deploying a Phone in an SCCP and SIP Environment

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 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 CallManager.

This chapter focuses on the interactions between the Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE and Cisco Unified CallManager, DNS and DHCP servers, TFTP servers, and switches. It also describes options for powering phones.

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

http://www.cisco.com/en/US/partner/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 CallManager Database

Using Cisco Unified IP Phones with Different Protocols

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 CallManager system before sending and receiving calls.

This section includes the following topics:

Understanding How the Cisco Unified IP Phone Interacts with Cisco Unified CallManager

Understanding How the Cisco Unified IP Phone Interacts with the VLAN

Understanding How the Cisco Unified IP Phone Interacts with Cisco Unified CallManager

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

Firmware for phones

Authentication and encryption (if configured for the telephony system)

Configuration file and CTL file, via TFTP service

Phone registration

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

For information about configuring Cisco Unified CallManager to work with the IP devices described in this chapter, refer to Cisco Unified CallManager Administration Guide, Cisco Unified CallManager System Guide, and to Cisco Unified CallManager Security Guide.

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


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 CallManager Administration, go to the following URL and install the latest support patch for your version of Cisco Unified CallManager: http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml


Related Topic

Telephony Features Available for the Cisco Unified IP Phone, page 5-2

Understanding How the Cisco Unified IP Phone Interacts with the VLAN

The Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE have an internal Ethernet switch, enabling forwarding of packets to the phone, and to the access port and the network port on the back of the phone.

If a computer is connected to the 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 to have 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 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, refer to the documentation included with a Cisco switch. You can also access related documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/lan/index.htm

Related Topics

Understanding the Phone Startup Process

Network Configuration Menu, page 4-7

Providing Power to the Cisco Unified IP Phone

The Cisco Unified IP Phone 7961G, 7961G-GE and 7941G, 7941G-GE 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 powering a phone:

Power Guidelines

Power Outage

Obtaining Additional Information about Power

Power Guidelines

Table 2-1 provides guidelines for powering the Cisco Unified IP Phone 7961G and 7941G.

Table 2-2 provides guidelines for powering the Cisco Unified IP Phone 7961G-GE and 7941G-GE.

Table 2-1 Guidelines for Powering the Cisco Unified IP Phone 7961G and 7941G 

Power Type
Guidelines

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

The Cisco Unified IP Phone 7961G and 7941G use the CP-PWR-CUBE-3 power supply.

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.

The Cisco Unified IP Phone 7961G and 7941G support Cisco inline PoE.

The Cisco Unified IP Phone 7961G and 7941G support IEEE 802.3af power on signal pairs and spare pairs.

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. Refer to the documentation for your switch for operating system version information.

External power—
Provided through inline power patch panel WS-PWR-PANEL

The inline power patch panel WS-PWR-PANEL is compatible with the Cisco Unified IP Phones 7961G and 7941G.


Table 2-2 Guidelines for Powering the Cisco Unified IP Phone 7961G-GE and 7941G-GE

Power Type
Guidelines

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

The Cisco Unified IP Phone 7961G-GE and 7941G-GE use the CP-PWR-CUBE-3 external power supply only.

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.

The gigabit Ethernet Cisco Unified IP Phone 79161G-GE and 7941G-GE do not support Cisco inline PoE.

The Cisco Unified IP Phone 7961G-GE and 7941G-GE support IEEE 802.3af power on signal pairs and spare pairs. The Cisco Unified IP Phone 79161G-GE and 7941G-GE are not compatible with Cisco switches that are not IEEE-compliant.

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. Refer to the documentation for your switch for operating system version information.

External power—
Provided through inline power patch panel WS-PWR-PANEL

The inline power patch panel WS-PWR-PANEL is compatible with the Cisco Unified IP Phones 7961G-GE and 7941G-GE.


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 will 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.

Obtaining Additional Information about Power

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

Cisco switches that work with the Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE

The Cisco IOS releases that support bidirectional power negotiation

Other requirements and restrictions regarding power

Table 2-3 Related Documentation for Power

Document Topics
URL

Cisco Unified IP Phone Power Injector

http://www.cisco.com/en/US/products/hw/phones/ps379/prod_installation_guides_list.html

PoE Solutions

http://www.cisco.com/en/US/netsol/
ns340/ns394/ns147/ns412/networking_solutions_
package.html

Cisco Catalyst Switches

http://www.cisco.com/univercd/cc/td/
doc/product/lan/index.htm

Integrated Service Routers

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

Cisco IOS Software

http://www.cisco.com/en/US/products/sw/iosswrel/products_ios_cisco_ios_software_category_home.
html


Understanding Phone Configuration Files

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

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. (These files are digitally signed to ensure the authenticity of the files' source.)

In addition, if the device security mode in the configuration file is set to Authenticated and the CTL file on the phone has a valid certificate for Cisco Unified CallManager, the phone establishes a TLS connection to Cisco Unified CallManager. Otherwise, the phone establishes a TCP connection.


Note If the device security mode in the configuration file is set to Authenticated or Encrypted, but the phone has not received a CTL file, the phone will continuously try to obtain a CTL file so that it can register securely.


If you configure security-related settings in Cisco Unified CallManager Administration, the phone configuration file will contain sensitive information. To ensure the privacy of a configuration file, you must configure it for encryption. For detailed information, refer to the "Configuring Encrypted Phone Configuration Files" chapter in Cisco Unified CallManager Security Guide.A phone requests a configuration file whenever it resets and registers with Cisco Unified CallManager.

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

You have enabled auto-registration in Cisco Unified CallManager

The phone has not been added to the Cisco Unified CallManager Database

The phone is registering for the first time

If auto registration is not enabled and the phone has not been added to the Cisco Unified CallManager Database, the phone registration request will be rejected. In this case, the phone will reset and attempt to register repeatedly.

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

Understanding the Phone Startup Process

When connecting to the VoIP network, the Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE go through a standard startup process that is described in Table 2-4. Depending on your specific network configuration, not all of these steps may occur on your Cisco Unified IP Phone.

Table 2-4 Cisco Unified IP Phone 7961G/7961G-GE and 7941G/7941G-GE Startup Process  

Step
Description
Related Topics

1. Obtaining 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 CallManager Database.

Resolving Startup Problems, page 9-2.

2. Loading 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 image stored in Flash memory. Using this image, the phone initializes its software and hardware.

Resolving Startup Problems, page 9-2.

3. Configuring 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 its VLAN membership before it can proceed with the Dynamic Host Configuration Protocol (DHCP) request for an IP address.

Network Configuration Menu, page 4-7.

Resolving Startup Problems, page 9-2.

4. Obtaining 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.

Network Configuration Menu, page 4-7.

Resolving Startup Problems, page 9-2.

5. Accessing 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.

Network Configuration Menu, page 4-7.

Resolving Startup Problems, page 9-2.

6. Requesting the CTL     file

The TFTP server stores the certificate trust list (CTL) file. This file contains a list of Cisco Unified CallManagers and TFTP servers that the phone is authorized to connect to. It also contains the certificates necessary for establishing a secure connection between the phone and Cisco Unified CallManager.

For more information, refer to Cisco Unified CallManager Security Guide

7. Requesting the     Configuration File

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

Adding Phones to the Cisco Unified CallManager Database

Resolving Startup Problems, page 9-2.

1. Contacting Cisco Unified CallManager

The configuration file defines how the Cisco Unified IP Phone communicates with Cisco Unified CallManager and provides a phone with its load ID. After obtaining the file from the TFTP server, the phone attempts to make a connection to the highest priority Cisco Unified CallManager on the list. If security is implemented, the phone makes a TLS connection. Otherwise, it makes a non-secure TCP connection.

If the phone was manually added to the database, Cisco Unified CallManager identifies the phone. If the phone was not manually added to the database and auto-registration is enabled in Cisco Unified CallManager, the phone attempts to auto-register itself in the Cisco Unified CallManager database.

Note Auto-registration is disabled when security is enabled on Cisco Unified CallManager. In this case, the phone must be manually added to the Cisco Unified CallManager database.

Resolving Startup Problems, page 9-2.


Adding Phones to the Cisco Unified CallManager Database

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

Adding Phones with Auto-Registration

Adding Phones with Auto-Registration and TAPS

Adding Phones with Cisco Unified CallManager Administration

Adding Phones with BAT

Table 2-5 provides an overview of these methods for adding phones to the Cisco Unified CallManager database.

Table 2-5 Methods for Adding Phones to the Cisco Unified CallManager Database 

Method
Requires MAC Address?
Notes

Auto-registration

No

Results in automatic assignment of directory numbers

Auto-registration with TAPS

No

Requires auto-registration and the Bulk Administration Tool (BAT); updates information in the Cisco Unified IP Phone and in Cisco Unified CallManager Administration

Using the Cisco Unified CallManager Administration

Yes

Requires phones to be added individually

Using BAT

Yes

Allows for simultaneous registration of multiple phones


Adding Phones with Auto-Registration

By enabling auto-registration before you begin installing phones, you can:

Automatically add a Cisco Unified IP Phone to the Cisco Unified CallManager database when you physically connect the phone to your IP telephony network. During auto-registration, Cisco Unified CallManager assigns the next available sequential directory number to the phone.

Add phones without first gathering MAC addresses from the phones.

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

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


Note You should use auto-registration 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 with BAT" section.


In some cases, you might not want to use auto-registration: for example, if you want to assign a specific directory number to the phone or if you plan to implement authentication or encryption, as described in Cisco Unified CallManager Security Guide. For information about enabling auto-registration, refer to "Enabling Auto-Registration" in the Cisco Unified CallManager Administration Guide.


Note Cisco Unified CallManager automatically disables auto-registration if you configure the cluster-wide security mode for authentication and encryption through the Cisco CTL client.


Related Topics

Adding Phones with Auto-Registration and TAPS

Adding Phones with Cisco Unified CallManager Administration

Adding Phones with BAT

Adding Phones with Auto-Registration and TAPS

TAPS, the Tool for Auto-Registered Phones Support, works with the Bulk Administration Tool (BAT) to update a batch of phones that were already added to the Cisco Unified CallManager database with dummy MAC addresses. You use TAPS to update MAC addresses and download pre-defined configurations for phones.

You can add phones with auto-registration and TAPS without first gathering MAC addresses from phones.


Note You should use auto-registration 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 with BAT" section.


To implement TAPS, you or the end-user dial a TAPS directory number and follow voice prompts. When the process is complete, the phone will have downloaded its directory number and other settings, and the phone will be updated in Cisco Unified CallManager Administration with the correct MAC address.

Auto-registration must be enabled in Cisco Unified CallManager Administration (System > Cisco CallManager) for TAPS to function.


Note Cisco Unified CallManager automatically disables auto-registration if you configure the cluster-wide security mode for authentication and encryption through the Cisco CTL client.


Refer to Cisco Unified CallManager Bulk Administration Guide for detailed instructions about BAT and about TAPS.

Related Topics

Adding Phones with Auto-Registration

Adding Phones with Cisco Unified CallManager Administration

Adding Phones with BAT

Adding Phones with Cisco Unified CallManager Administration

You can add phones individually to the Cisco Unified CallManager database using Cisco Unified CallManager 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 have collected MAC addresses, in Cisco Unified CallManager Administration, choose Device > Phone and click Add New to begin.

For complete instructions and conceptual information about Cisco Unified CallManager, refer to Cisco Unified CallManager Administration Guide and to Cisco Unified CallManager System Guide.

Related Topics

Adding Phones with Auto-Registration

Adding Phones with Auto-Registration and TAPS

Adding Phones with BAT

Adding Phones with BAT

The Cisco Bulk Administration Tool (BAT) is a plug-in application for Cisco Unified CallManager that enables you to perform batch operations, including registration, on multiple phones.

Before you can add phones using BAT only (not in conjunction with TAPS), you must 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.

For detailed instructions about using BAT, refer to Cisco Unified CallManager Administration Guide and to Cisco Unified CallManager Bulk Administration Guide.

Related Topics

Adding Phones with Auto-Registration

Adding Phones with Auto-Registration and TAPS

Adding Phones with Cisco Unified CallManager Administration

Using Cisco Unified IP Phones with Different Protocols

The Cisco Unified IP Phone can operate with SCCP (Skinny Client Control Protocol) or SIP (Session Initiation Protocol). You can convert a phone that is using one protocol for use with the other protocol.

This section includes these topics:

Converting a New Phone from SCCP to SIP

Converting an In-Use Phone from SCCP to SIP

Converting an In-Use Phone from SIP to SCCP

Deploying a Phone in an SCCP and SIP Environment

Converting a New Phone from SCCP to SIP

A new, unused phone is set for SCCP by default. To convert this phone to SIP, perform these steps:

Procedure


Step 1 Take one of these actions:

To auto-register the phone, set the Auto Registration Phone Protocol parameter in Cisco Unified CallManager Administration to SIP.

To provision the phone using the Bulk Administration Tool (BAT), choose the appropriate phone model and choose SIP from the BAT.

To provision the phone manually, make the appropriate changes for SIP on the Phone Configuration page in Cisco Unified CallManager Administration.

Refer to Cisco Unified CallManager Administration Guide for detailed information about Cisco Unified CallManager configuration. Refer to Cisco Unified CallManager Bulk Administration Guide for detailed information about using the BAT.

Step 2 If you are not using DHCP in your network, configure the network parameters for the phone.

See the "Configuring Startup Network Settings" section on page 3-14.

Step 3 Power cycle the phone.


Converting an In-Use Phone from SCCP to SIP

You can use the Bulk Administration Tool (BAT) to convert a phone that is in use in your network from SCCP to SIP. To access BAT from Cisco Unified CallManager Administration, choose Bulk Administration > Phones > Migrate Phones > SCCP to SIP. For detailed information, refer to Cisco Unified CallManager Bulk Administration Guide.

Converting an In-Use Phone from SIP to SCCP

To convert a phone that is in use in your network from SIP to SCCP, perform these steps. For more information, Cisco Unified CallManager Administration Guide.

Procedure


Step 1 In Cisco Unified CallManager Administration, delete the existing SIP phone from the Cisco Unified CallManager database.

Step 2 In Cisco Unified CallManager Administration, create the phone as an SCCP phone.

Step 3 Power cycle the phone.


Deploying a Phone in an SCCP and SIP Environment

To deploy Cisco Unified IP Phones in an environment that includes SCCP and SIP and in which the Cisco Unified CallManager Auto-Registration parameter is SCCP, perform these general steps:

1. Set the Cisco Unified CallManager auto_registration_protocol parameter to SCCP.

To do so, from Cisco Unified CallManager Administration, choose System > Enterprise Parameters.

2. Install the phones.

3. Change the auto_registration_protocol parameter to SIP.

4. Auto-register the SIP phones.

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 a phone's MAC address in these ways:

From the phone, press the Settings button and select Model 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 on page 8-2.