Cisco Unified IP Phone 7906G and 7911G Administration Guide for Cisco Unified Communications Manager 7.0 (SCCP and SIP)
Preparing to Install the Cisco Unified IP Phone on Your Network
Downloads: This chapterpdf (PDF - 447.0KB) The complete bookPDF (PDF - 6.01MB) | 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 Communications 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 Phones 7906G and 7911G

Power Guidelines

Power Outage

Obtaining Additional Information about Power

Understanding Phone Configuration Files

SIP Dial Rules

Understanding the Phone Startup Process

Adding Phones to the Cisco Unified Communications Manager Database

Adding Phones with Auto-Registration

Adding Phones with Auto-Registration and TAPS

Adding Phones with Cisco Unified Communications Manager 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 of 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 Communications and network components, including Cisco Unified Communications Manager, DNS and DHCP servers, TFTP servers, and media resources.

This chapter provides an overview of the interaction between the Cisco Unified IP Phones 7906G and 7911G and other key components of the Voice-over-IP (VoIP) network, and focuses on the interactions between the Cisco Unified IP Phones 7906G and 7911G and Cisco Unified Communications Manager, TFTP server, and switches. It includes these topics:

Understanding Interactions with Other Cisco Unified Communications Products

Understanding the Phone Startup Process

Providing Power to the Cisco Unified IP Phones 7906G and 7911G

Understanding Phone Configuration Files

Adding Phones to the Cisco Unified Communications Manager Database

Using Cisco Unified IP Phones with Different Protocols

Determining the MAC Address of a Cisco Unified IP Phone

Understanding Interactions with Other Cisco Unified Communications Products

To function in the Unified Communications 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 these 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 Cisco Unified Communications system—the phones, the access gateways, and the resources necessary for features such as call conferencing and route planning. Cisco Unified Communications Manager also provides authentication and encryption if configured for the communications system.

For information about configuring Cisco Unified Communications Manager to work with the IP devices described in this chapter, refer to Cisco Unified Communications Manager Administration Guide, Cisco Unified Communications Manager System Guide, and Cisco Unified Communications Manager 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-8.


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, page 5-1

Understanding How the Cisco Unified IP Phone Interacts with the VLAN

The Cisco Unified IP Phone 7911G has an internal Ethernet switch, which enables forwarding of packets to the phone and to the network port and access port on the back of the phone. The Cisco Unified IP Phone 7906G has an Ethernet port, which enables forwarding of packets to the phone and to the network port.

If a computer is connected to the access port (Cisco Unified IP Phone 7911G), the computer and the phone share the same physical link to the switch and the same port on the switch. This shared physical link affects the VLAN configuration on the network in the following ways:

Although current VLANs might be configured on an IP subnet basis, additional IP addresses may not be available to assign the phone to the same subnet as other devices that connect to the same port.

Data traffic present on the data/native VLAN may reduce the quality of Voice-over-IP traffic.

Network security may necessitate the isolation of the VLAN voice traffic from the VLAN data traffic.

You can resolve these issues by isolating the voice traffic onto a separate VLAN, so that the switch port to which the phone is connected uses separate VLANs for the following types of traffic:

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, 7911G only)

Isolating the phones on a separate, auxiliary VLAN improves the quality of the voice traffic and allows a large number of phones to be added to an existing network in which 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/en/US/products/hw/switches/tsd_products_support_category_home.html

Related Topics

Understanding the Phone Startup Process

Network Configuration Menu, page 4-5

Providing Power to the Cisco Unified IP Phones 7906G and 7911G

The Cisco Unified IP Phones 7906G and 7911G 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.

These sections provide more information about powering a phone:

Power Guidelines

Power Outage

Obtaining Additional Information about Power

Power Guidelines

Table 2-1 provides guidelines that apply to external power and to PoE power for the Cisco Unified IP Phones 7906G and 7911G.

Table 2-1 Guidelines for Powering the Cisco Unified IP Phones 7906G and 7911G 

Power Type
Guidelines

External power— Provided through a Cisco external power supply.

The Cisco Unified IP Phone Series 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 phone.

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

The Cisco Unified IP Phones 7906G and 7911G support both Cisco inline power and IEEE 802.3af Power over Ethernet.

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.


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-2. These documents provide information about these topics:

Cisco switches that work with the Cisco Unified IP Phones 7906G and 7911G

The 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 phone's configuration file.

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 Communications Manager, the phone establishes a TLS connection to Cisco Unified Communications Manager Administration. 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 it can register securely.


If you configure security-related settings in Cisco Unified Communications Manager 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 Communications Manager Security Guide.

A phone requests a configuration file whenever it resets and registers with Cisco Unified Communications Manager.

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

You have enabled auto-registration in Cisco Unified Communications Manager

The phone has not been added to the Cisco Unified Communications Manager 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 Communications Manager 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. For more information about how the phone interacts with the TFTP server, refer to Cisco Unified Communications Manager System Guide, "Cisco TFTP" chapter.

If you configure security-related settings in Cisco Unified Communications Manager Administration, the phone configuration file will contain sensitive information. To ensure the privacy of a configuration file, you must configure it for encryption. For more information, refer to the "Configuring Encrypted Phone Configuration Files" chapter in Cisco Unified Communications Manager Security Guide.

SIP Dial Rules

For Cisco Unified IP Phones running under SIP, the administrator uses dial rules to configure SIP phone dial plans. These dial plans must be associated with a SIP phone device to enable dial plans to be sent to the configuration file. If the administrator does not configure a SIP phone dial plan, the phone does not display any indication of a dial plan. In this case, you must press the Dial softkey, unless the phone supports key press markup language (KPML).

For more information on configuring SIP dial rules, refer to the Cisco Unified Communications Manager Administration Guide.

Understanding the Phone Startup Process

When connecting to the VoIP network, the Cisco IP Phone goes through a standard startup process, as 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.

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.

See the "Providing Power to the Cisco Unified IP Phones 7906G and 7911G" section.

See the "Resolving Startup Problems" section on page 9-1.

2.

The Cisco 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.

See the "Resolving Startup Problems" section on page 9-1.

3.

Configuring VLAN.

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

If a third-party switch is used and VLANs are configured, the VLAN on the phone must be manually configured.

See the "Network Configuration Menu" section on page 4-5.

See the "Resolving Startup Problems" section on page 9-1.

4.

Obtaining an IP Address.

If the Cisco 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.

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.

See the "Network Configuration Menu" section on page 4-5.

See the "Resolving Startup Problems" section on page 9-1.

5.

Accessing a TFTP Server.

See the "Network Configuration Menu" section on page 4-5.

See the "Resolving Startup Problems" section on page 9-1.

6.

Requesting the CTL file.

The TFTP server stores the certificate trust list (CTL) file. This file contains a list of Cisco Unified Communications Managers 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 Communications Manager.

Refer to the Cisco Unified Communications Manager Security Guide, "Configuring the Cisco CTL Client" 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 Auto-Registration

Adding Phones with Auto-Registration and TAPS

Adding Phones with Cisco Unified Communications Manager Administration

Adding Phones with BAT

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

Auto-registration

No

Results in automatic assignment of directory numbers.

Not available when security or encryption is enabled.

Auto-registration with TAPS

No

Requires auto-registration and the Bulk Administration Tool (BAT); updates the Cisco Unified Communications Manager database with the MAC address and DNs for the device when user calls TAPS from the phone.

Using the Cisco Unified Communications Manager Administration

Yes

Requires phones to be added individually

Using BAT

Yes

Can add groups of same model of phone.

Can schedule when phones are added to the Cisco Unified Communications Manager database.


Adding Phones with Auto-Registration

By enabling auto-registration 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 auto-registration, 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 auto-registered phones to new locations and assign them to different device pools without affecting their directory numbers.


Note Cisco recommends you 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.


Auto-registration is disabled by default. 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 Communications Manager Security Guide. For information about enabling auto-registration, refer to "Enabling Auto-Registration" in the Cisco Unified Communications Manager Administration Guide.


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


Related Topics

Adding Phones with Auto-Registration and TAPS

Adding Phones with Cisco Unified Communications Manager Administration

Adding Phones with BAT

Adding Phones with Auto-Registration and TAPS

You can add phones with auto-registration and TAPS, the Tool for Auto-Registered 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 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 Communications Manager Administration with the correct MAC address.

Auto-registration 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, auto-registration is automatically disabled. When you configure the cluster for non-secure mode through the Cisco CTL client, auto-registration is automatically enabled.


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

Related Topics

Adding Phones with Auto-Registration

Adding Phones with Cisco Unified Communications Manager Administration

Adding Phones with BAT

Adding Phones with Cisco Unified Communications Manager Administration

You can add phones individually to the Cisco Unified Communications Manager database 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 of a Cisco Unified IP Phone" section.

After you have collected 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, refer to Cisco Unified Communications Manager Administration Guide and to Cisco Unified Communications Manager System Guide.

Related Topics

Adding Phones with Auto-Registration

Adding Phones with Auto-Registration and TAPS

Adding Phones with BAT

Adding Phones with BAT

Cisco Unified Communications Manager Bulk Administration Tool (BAT), a standard Cisco Unified Communications Manager application, enables you to perform batch operations, which includes registration, on multiple phones.

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

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

Related Topics

Adding Phones with Auto-Registration

Adding Phones with Auto-Registration and TAPS

Adding Phones with Cisco Unified Communications Manager 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 enterprise parameter in Cisco Unified Communications Manager Administration to SIP.

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

To provision the phone manually, make the appropriate changes for SIP on the Phone Configuration window in Cisco Unified Communications Manager Administration.

Refer to the Cisco Unified Communications Manager Administration Guide for more information about Cisco Unified Communications Manager configuration. Refer to Bulk Administration Tool Administration Guide for more information about using 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 Communications Manager Administration, choose Bulk Administration > Phones > Migrate Phones > SCCP to SIP. For more information, refer to the "Migrating Phones" chapter Bulk Administration Tool 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 Communications Manager Administration Guide.

Procedure


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

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

Step 3 Power cycle the phone.



Tip Before deleting a SIP phone (that you want to convert to a SCCP phone) from the Cisco Unified Communications Manager database, copy all of the phone configuration information, so when you add the phone back to the database, you will have the configuration information readily available.


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 Communications Manager Auto-Registration parameter is SCCP, perform these general steps:

1. Set the Cisco Unified Communications Manager auto_registration_protocol parameter to SCCP.

From Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.

2. Install the phones.

3. Change the Auto Registration Protocol enterprise parameter to SIP.

4. Auto-register the SIP phones.

Determining the MAC Address of a Cisco Unified IP Phone

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

From the phone, press the Applications Menu button, then choose Settings > Network Configuration, 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-1.