Cisco Unified IP Phone 6921, 6941, 6945, and 6961 Administration Guide for Cisco Unified Communications Manager 9.0 (SCCP and SIP)
Cisco Unified IP Phones and telephony networks
Downloads: This chapterpdf (PDF - 1.29MB) The complete bookPDF (PDF - 5.04MB) | The complete bookePub (ePub - 1.09MB) | Feedback

Cisco Unified IP Phones and Telephony Networks

Contents

Cisco Unified IP Phones and Telephony Networks

Phone and Telephony Networks Overview

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 6921, 6941, 6945, and 6961 and Cisco Unified Communications Manager, DNS and DHCP servers, TFTP servers, and switches. It also describes options for powering phones.

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

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

This chapter provides an overview of the interaction between Cisco Unified IP Phones and other key components of the Voice over IP (VoIP) network.

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.

Cisco Unified IP Phone and Cisco Unified Communications Manager Interaction

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: 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 using the TFTP service
  • Authentication and encryption (if configured for the telephony system)
  • 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 phones described in this chapter, see "Cisco Unified IP Phone Configuration" chapter in the Cisco Communications Manager Administration Guide.


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

For more information, see "Software Upgrades" chapter in the Cisco Unified Communications Operating System Administration Guide.


Cisco Unified IP Phone and VLAN Interaction

The Cisco Unified IP Phone 6921, 6941, 6945, and 6961 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 (for example, auxiliary VLAN on the Cisco Catalyst 6000 series)
  • 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 when 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 Tasks
Related References

Cisco Unified IP Phone and Cisco Unified Communications Manager Express Interaction

When the Cisco Unified IP Phone works with the Cisco Unified Communications Manager Express (Unified CME), the phones must go into Unified CME mode.

When a user invokes the conference feature, the tag allows the phone to use either a local or network hardware conference bridge.

The Cisco Unified IP Phones do not support the following actions:

Transfer

Only supported in the connected call transfer scenario.

Conference

Only supported in the connected call conference scenario.

Join

Supported using the Conference button.

Hold

Supported using the Hold button.

Barge

Not supported.

Direct Transfer

Not supported.

Select

Not supported.

The users cannot create conference and transfer calls across different lines.

Cisco Unified IP Phone Power

The Cisco Unified IP Phone 6921, 6941, 6945, and 6961 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.


Power Guidelines

The following table provides guidelines for powering the Cisco Unified IP Phone 6921, 6941, 6945, and 6961.

Table 1 Guidelines for Powering the Cisco Unified IP Phone 6921, 6941, 6945, and 6961

Power Type

Guidelines

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

The Cisco Unified IP Phone 6921, 6941, 6945, and 6961 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 6921, 6941, 6945, and 6961 support IEEE 802.3af Class 2 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 Phone 6921, 6941, 6945, and 6961.

Power Outage

Your access to emergency service through the phone requires the phone to receive power. If an interruption in the power supply occurs, 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 you can use the Service or Emergency Calling Service dialing.

Phone Power Reduction

You can reduce the amount of energy that the Cisco Unified IP Phone consumes by using Power Save or 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 Manager Administration, configure the following parameters:

Days Display Not Active

Specifies the days that the backlight remains inactive.

Display on Time

Schedules 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 supports Cisco EnergyWise (Power Save Plus) mode. 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 power consumption.

Set up each phone to enable or disable the EnergyWise settings. If EnergyWise is enabled, 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 in Cisco Unified Communications Manager 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 that are selected in the Enable Power Save Plus field.

Phone Off Time

Determines the time of day that the phone powers down for the days that are selected in the Enable Power Save Plus field.

Phone Off Idle Timeout

Determines 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 10 minutes before the time that the Phone Off Time field specifies.

EnergyWise Domain

Specifies the EnergyWise domain that the phone is in.

EnergyWise Secret

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

Additional Information About Power

The documents in the following table provide more information on the following topics:

  • Cisco switches that work with Cisco Unified IP Phones
  • Cisco IOS releases that support bidirectional power negotiation
  • Other requirements and restrictions about power

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

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

  • You have enabled autoregistration 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

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. Otherwise, the phone establishes a TCP connection.


Note


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



Note


Cisco Extension Mobility Cross Cluster is an exception, in that the phone permits a TLS connection to Cisco Unified Communications Manager for secure signaling even without the CTL file.


If you configure security 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, see "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 only when the phone has not received a valid Trust List file containing a certificate assigned to the Cisco Unified Communications Manager and TFTP.

If auto registration is not enabled and you did not add the phone to the Cisco Unified Communications Manager database, the phone does not attempt to register with Cisco Unified Communications Manager. The phone continually displays the "Configuring IP" message until you either enable auto-registration or add the phone to the Cisco Unified Communications Manager database.

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 SIP phones, the TFTP server generates these SIP configuration files:

  • SIP IP Phone:
    • For unsigned and unencrypted files—SEP<mac>.cnf.xml
    • For signed files—SEP<mac>.cnf.xml.sgn
    • For signed and encrypted files—SEP<mac>.cnf.xml.enc.sgn
      • Dial Plan—<dialplan>.xml
      • Softkey Template—<softkey_template>.xml

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.

For more information about phone configuration settings, see "Cisco Unified IP Phone Configuration" chapter in the Cisco Communications Manager Administration Guide.

For more information, also see Cisco Unified Communications Manager Security Guide.

Phone Startup Process

When connecting to the VoIP network, the Cisco Unified IP Phone 6921, 6941, 6945, and 6961 goes through a standard startup process that is described in the following procedure. Depending on your specific network setup, not all of these steps may occur on your Cisco Unified IP Phone.

Procedure
    Step 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.

    For more information, see Cisco Unified Communications Manager Phone Addition Methods and Startup Problems.

    Step 2   Load the Stored Phone Image. The Cisco Unified IP Phone has nonvolatile 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.

    For more information, see Startup Problems.

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

    For more information, see Network Setup Menu and Startup Problems.

    Step 4   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.
    Step 5   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.

    For more information, see Network Setup Menu and Startup Problems.

    Step 6   Request the CTL file. The TFTP server stores the certificate trust list (CTL) file. The CTL file contains the certificates necessary for establishing a secure connection between the phone and Cisco Unified Communications Manager.

    For more information, see the Cisco Unified Communications Manager Security Guide, "Configuring the Cisco CTL Client" chapter.

    Step 7   Request the ITL file. The TFTP server stores the identity trust list (ITL) file. The ITL file contains the certificates necessary for establishing a secure connection between the phone and Cisco Unified Communications Manager.

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

    Step 8   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.

    For more information, see Cisco Unified Communications Manager Phone Addition Methods and Startup Problems.

    Step 9   Contact Cisco Unified Communications Manager. The configuration file defines how the Cisco Unified IP Phone communicates with Cisco Unified Communications Manager 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 Communications Manager on the list.

    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 auto-registration is enabled in Cisco Unified Communications Manager, the phone attempts to auto-register itself in the Cisco Unified Communications Manager database.

    For more information, see Startup Problems.


    Cisco Unified Communications Manager Phone Addition Methods

    Before installing the Cisco Unified IP Phone, you must choose a method for adding phones to the Cisco Unified Communications Manager database. Be aware that each phone type requires a fixed number of device license units and the number of unit licenses that are available on the server may impact phone registration. For more information about licensing, see "Licenses for Phones" section in the Cisco Unified Communications Manager System Guide.

    The following table provides an overview of these methods for adding phones to the Cisco Unified Communications Manager database.

    Table 2 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

    Not available when security or encryption is enabled

    Note   

    Autoregistration is disabled when security is enabled on Cisco Unified Communications Manager. In this case, the phone must be manually added to the Cisco Unified Communications Manager database.

    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

    Autoregistration Phone Addition

    If you enable 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 CM 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 that you use autoregistration to add fewer than 100 phones to your network. To add more than 100 phones to your network, use the Bulk Administration Tool (BAT).


    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. For information about enabling autoregistration, see "Enable autoregistration" section in the Cisco Unified Communications Manager Administration Guide.


    Note


    When you configure the cluster for mixed mode through the Cisco CTL client, autoregistration is automatically disabled. When you configure the cluster for nonsecure mode through the Cisco CTL client, autoregistration is automatically enabled.


    Autoregistration and TAPS Phone Addition

    You can add phones with autoregistration 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 predefined configurations for phones.


    Note


    Cisco recommends that 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).


    To implement TAPS, dial a TAPS directory number and follow the voice prompts. When the process completes, the phone has downloaded 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 nonsecure mode through the Cisco CTL client, autoregistration is automatically enabled.


    For more information, see "Bulk Administration" chapter in the Cisco Unified Communications Manager Administration Guide and the "Tool for Auto-Registered Phones Support" chapter in the Cisco Unified Communications Manager Bulk Administration Guide.

    Cisco Unified Communications Manager Administration Phone Addition

    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.

    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, see the "Cisco Unified Communications Manager Overview" chapter in the Cisco Unified Communications Manager System Guide.

    BAT Phone Addition

    Cisco Unified Communications Manager Bulk Administration Tool (BAT) enables you to perform batch operations, including registration, on multiple phones. To access BAT, choose the Bulk Administration drop-down menu in Cisco Unified Communications Manager Administration.

    To add phones using BAT only (not in conjunction with TAPS), you can use the MAC address for each phone or dummy MAC addresses if you have a large number of new phones.

    For detailed instructions about using BAT, see the Bulk Administration chapter in the Cisco Unified Communications Manager Administration Guide.

    Cisco Unified IP Phones and 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.

    Convert 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 autoregister the phone, set the Auto Registration Phone Protocol parameter in Cisco Unified Communications Manager 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 window in Cisco Unified Communications Manager Administration. For more information about Cisco Unified Communications Manager configuration, see Cisco Unified Communications Manager Administration Guide. For more information about using BAT, see Cisco Unified Communications Manager Bulk Administration Guide.
      Step 2   If you are not using DHCP in your network, configure the network parameters for the phone.

      See Network Settings.

      Step 3   Save the configuration updates, click Apply Config, click OK when the Apply Configuration Information dialog displays, then have the user power cycle the phone.

      In-Use Phone Protocol to Protocol Conversion

      Phones using SCCP can be upgraded to use SIP. To change from SCCP to SIP, the phone firmware must be updated to the recommended SIP version before the phones can register. New Cisco Unified IP Phones ship from the factory with SCCP phone firmware. These new phones must be upgraded to the recommended SIP version before they can complete registration.

      For information about how to convert an in-use phone from one protocol to the other, see the Cisco Unified Communications Manager Administration Guide, chapter "Cisco Unified IP Phone Configuration", section "Migration Existing Phone Configuration to a Different Phone".

      Deploy Phone in 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 autoregistration parameter specifies SCCP, perform these general steps:

      Procedure
        Step 1   Set the Cisco Unified Communications Manager auto_registration_protocol parameter to SCCP.
        Step 2   From Cisco Unified Communications Manager, choose System > Enterprise Parameters.
        Step 3   Install the phones.
        Step 4   Change the Auto Registration Protocol enterprise parameter to SIP.
        Step 5   Autoregister the SIP phones.

        Cisco Unified IP Phone MAC Address Determination

        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, select 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 select Device Information. For information about accessing the web page, see the "Accessing the Web Page for a Phone" section of this document.