Cisco Unified IP Phone 7906G and 7911G Administration Guide for Cisco Unified Communications Manager 9.0 (SCCP and SIP)
Cisco Unified IP Phones and Telephony Networks
Downloads: This chapterpdf (PDF - 1.32MB) The complete bookPDF (PDF - 5.15MB) | The complete bookePub (ePub - 725.0KB) | The complete bookMobi (Mobi - 1.35MB) | Feedback

Cisco Unified IP Phones and Telephony Networks

Contents

Cisco Unified IP Phones and Telephony Networks

Phone and Telephony Network Overview

Cisco Unified IP Phones enable you to communicate by using voice over a data network. Cisco Unified IP Phones depend on several key Cisco Unified Communications and network components. These include Cisco Unified Communications Manager, DNS servers, 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.

Cisco Unified Communications Product Interactions

Cisco Unified IP Phones must be connected to a networking device (such as a Catalyst switch) to function in the Unified Communications network. 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 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, see 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 Phones, see Supported Security Features.


Note


If the Cisco Unified IP Phones 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


Cisco Unified IP Phones and VLAN Interaction

The Cisco Unified IP Phones 7911G has an internal Ethernet switch. The switch 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 Phones 7906G has an Ethernet port. This port enables forwarding of packets to the phone and to the network port.

If a computer is connected to the access port on a Cisco Unified IP Phones 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 VoIP 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, Cisco Unified IP Phone 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.


Note


Do not configure the switch port for VLAN 1 due to a limitation with the Cisco Unified IP Phone 7911. When the switch port is configured to VLAN 1, the phone forwards tagged packets in VLAN 1 to the switch.


For more information, see the documentation included with the 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 Tasks
Related References

Cisco Unified IP Phone Power

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.

Power Guidelines

The following table provides guidelines that apply to external power and to PoE power for the Cisco Unified IP Phone 7906G and 7911G.

Table 1 Guidelines for Cisco Unified IP Phone 7906G and 7911G Power

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 Phones Power Injector may be used with any Cisco Unified IP Phones. Functioning as a midspan device, the injector delivers inline power to the attached phone. The Cisco Unified IP Phones Power Injector is connected between a switch port and the Cisco Unified IP Phones, and supports a maximum cable length of 100 m 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 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.

Additional Information About Power

For related information about power, refer to the documents shown in the following table. These documents provide information about these topics:

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

Phone Configuration Files

Phone configuration files 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. These load files are digitally signed to ensure the authenticity of the file 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


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


If you configure security-related settings in Cisco Unified Communications Manager Administration, the phone configuration file contains sensitive information. To ensure the privacy of a configuration file, you must configure it for encryption. For detailed information, see "Configuring Encrypted Phone Configuration Files" 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 autoregistration or add the phone to the Cisco Unified Communications Manager database.

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. For more information about how the phone interacts with the TFTP server, see the Cisco Unified Communications Manager System Guide, "Cisco TFTP" section.

If you configure security-related settings in Cisco Unified Communications Manager Administration, the phone configuration file contains 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" 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, see the Cisco Unified Communications Manager Administration Guide.

Phone Startup Process

Cisco Unified IP Phones go through a standard startup process when connecting to the VoIP network. The following steps describe this process. Depending on your specific network configuration, not all steps may occur on your Cisco Unified IP Phone.

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

    For more information, see Cisco Unified IP Phone Power and Startup Problems.

    Step 2   The Cisco 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   Configuring VLAN.

    If the Cisco IP Phone is connected to a Cisco switch, the switch 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.

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

    Step 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 your network does not use DHCP, 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.

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

    Step 5   Accessing a TFTP Server.

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

    Step 6   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 Communications Manager.

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

    Step 7   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 to authenticating a digital signature signed by the servers.

    See the Cisco Unified Communications Manager Security Guide, "Security by Default" chapter.


    Cisco Unified Communications Manager Phone Addition Methods

    Before installing the Cisco Unified IP Phones, you must choose a method for adding phones to the Cisco Unified Communications Manager database.

    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.

    Autoregistration with TAPS

    No

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

    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 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 Administration Guide and to Cisco Unified Communications Manager System Guide.

    Add Phones with BAT

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

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

    To add a phone to the Cisco Unified Communications Manager, perform 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 already created BAT phone template.

      For detailed instructions about using BAT, refer to the Cisco Unified Communications Manager Bulk Administration Guide. For more information on creating BAT Phone Templates, see the Cisco Unified Communications Manager Bulk Administration Guide, "Phone Template" chapter.


      Cisco Unified IP Phones and Different Protocols

      The Cisco Unified IP Phones can operate with Skinny Client Control Protocol (SCCP) or Session Initiation Protocol (SIP). You can convert a phone from using one protocol to using 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 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.

        See the Cisco Unified Communications Manager Administration Guide for more information about Cisco Unified Communications Manager configuration. See 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.
        Step 3   Save the configuration updates, click Apply Config, click OK in the Apply Configuration Information window, and have the user power cycle the phone.

        Related Information

        In-Use Phone Protocol to Protocol Conversion

        For information on how to convert an in-use phone from one protocol to the other, see the Cisco Unified Communications Manager Administration Guide, "Cisco Unified IP Phone Configuration" chapter, "Migrate existing phone settings to another phone" section.

        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 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 more information, see Access Web Page for Phone.