-
Cisco Unified IP Phone Model 7905G and 7912G Administration Guide for Cisco Unified CallManager Release 4.2 and later
-
Index
-
Preface
-
Overview of the Cisco Unified IP Phone
-
Preparing to Install the Cisco Unified IP Phone on Your Network
-
Setting Up the Cisco Unified IP Phone
-
Configuring Network Settings on the Cisco Unified IP Phone
-
Configuring Features, Services, Templates, and Users
-
Viewing Status, Statistics, Model, and Firmware Information on the Cisco Unified IP Phone
-
Troubleshooting the Cisco Unified IP Phone
-
Additional Configuration Methods and Parameters
-
Providing Information to Users Via a Website
-
Supporting International Users
-
Updating Firmware for the Cisco Unified IP Phone
-
Changing the Graphic on the Cisco Unified IP Phone Screen
-
Technical Specifications
-
Feedback
Table Of Contents
Preparing to Install the Cisco Unified IP Phone on Your Network
Understanding Interactions with Other Cisco 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 Cisco Catalyst Family of Switches
Understanding the Phone Startup Process
Understanding Phone Configuration Files and Profile Files
Providing Power to the Cisco Unified IP Phone
Methods for 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
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 using voice over a data network. To provide this capability, the IP Phones depend upon and interact with several other key Cisco IP Telephony components, including Cisco Unified CallManager.
This chapter focuses on the interactions between the Cisco Unified IP Phone 7905G and 7912G and Cisco Unified CallManager, DNS and DHCP servers, TFTP servers, and switches. It also describes options for powering phones. For related information about other major components in a Voice over IP (VoIP) network, refer to Cisco IP Telephony Solution Reference Network Design (SRND) for Cisco Unified CallManager 4.0, which is available at this URL:
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 you with an important overview of the interaction between the Cisco Unified IP Phone 7905G and 7912G and other key components of the Voice over IP (VoIP) network.
This chapter includes the following topics:
•
Understanding Interactions with Other Cisco IP Telephony Products
•
•
•
•
•
Understanding Interactions with Other Cisco 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 covers the following topics:
•
•
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 runs on a Windows 2000 server and 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, access gateways, and the resources necessary for such features as call conferencing and route planning.
For information about configuring Cisco Unified CallManager to work with the IP devices described in this chapter, refer to Cisco Unified CallManager Administration Guide and Cisco Unified CallManager System Guide.
Related Topic
•
Understanding How the Cisco Unified IP Phone Interacts with the Cisco Catalyst Family of Switches
The Cisco Unified IP Phone 7912G has an internal Ethernet switch, enabling it to switch incoming traffic to the phone, to the access port, or to the network port. The Cisco Unified IP Phone 7905G does not include an internal Ethernet switch or an access port.
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:
•
•
You can resolve these issues by isolating the voice traffic onto a separate VLAN on each of the ports connected to a phone. The switch port configured for connecting a phone would have separate VLANs configured for carrying:
•
•
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 more information, refer to the documentation included with the Cisco Catalyst switch.
Related Topics
•
Understanding the Phone Startup Process
When connecting to the VoIP network, the Cisco Unified IP Phone goes through a standard startup process composed of several steps, as described in Table 2-1. Depending on your specific network configuration, not all of these steps may occur on your Cisco Unified IP Phone.
Table 2-1 Cisco Unified IP Phone Startup Process
1. Obtaining Power from the Switch
You can connect the Cisco Unified IP Phone to a Cisco Catalyst switch with one of the modules that provides power to the phone (WS-X6348-RJ45V). See the "Providing Power to the Cisco Unified IP Phone" section for details.
If you use this optional configuration, the phone receives phantom power and powers up when you connect the Cisco Unified IP Phone to the switch. The phone then sends Cisco Discovery Protocol (CDP) notifications to the switch indicating that it is ready to receive CDP packets and indicating the power requirement for the phone. The switch allocates power and sends it over the network cable.
•
•
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.
•
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.
•
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 a static IP address to each phone locally.
•
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.
•
6. Requesting the Configuration File and the Profile File
The TFTP server has configuration files and profile files. A configuration file includes parameters for connecting to Cisco Unified CallManager and information about which image load a phone should be running. A profile file contains various parameters and values for phone and network settings.
•
7. Contacting Cisco Unified CallManager
The configuration file defines how the Cisco Unified IP Phone communicates with Cisco Unified CallManager. After obtaining the file from the TFTP server, the phone attempts to make a TCP connection to the highest priority Cisco Unified CallManager on the list.
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.
Cisco Unified CallManager informs devices using .cnf or .cnf.xml format configuration files of their load ID. Devices using .xml format configuration files receive the load ID in the configuration file.
•
Understanding Phone Configuration Files and Profile 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 new image file.
The phone first requests the configuration file SEPxxxxxxxxxxxx.cnf.xml, where each xx is the two-digit lowercase hexadecimal representation of each integer in the phone's MAC address. If the phone cannot find this file, it requests the configuration files XMLDefault.cnf.xml and SEDDefault.cnf.
After the phone obtains one of the .cnf.xml files or the .cnf file, it requests a phone-specific profile file. If a phone cannot find this profile file, it requests the appropriate common profile file. For more information about profile files, see "Additional Configuration Methods and Parameters."
After the phone finds one of the profile files, or if it cannot find a profile file, it continues with its startup process.
Related Topics
•
•
Providing Power to the Cisco Unified IP Phone
You can power a Cisco Unified IP Phone by the following sources:
•
•
Note
•
This module sends power on pins 1 & 2 and 3 & 6, which are also used to transmit Ethernet signals. Before the switch sends power, it tests for the presence of a Cisco Unified IP Phone, avoiding damage to other Ethernet devices.
Note
•
This module sends power on pins 4, 5, 7, & 8, which are not used for Ethernet signaling. The power patch panel also attempts to verify that the attached device is a Cisco Unified IP Phone before providing power.
Related Topics
•
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.
Related Topics
•
•
Methods for 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. The following sections describe these methods:
•
•
•
Table 2-2 provides an overview of these methods for adding phones to the Cisco Unified CallManager database.
Adding Phones with Auto-Registration
You can add phones with auto-registration without first gathering MAC addresses from the phones.
When auto-registration is enabled, Cisco Unified CallManager begins the automatic startup process to obtain a directory number. During auto-registration, Cisco Unified CallManager automatically assigns the next available sequential directory number to the phone.
When you use this method, Cisco Unified CallManager automatically assigns directory numbers to new phones as they register with Cisco Unified CallManager.
You can use auto-registration to quickly enter phones into the Cisco Unified CallManager database. You can then modify any settings, such as the directory numbers, from Cisco Unified CallManager. Additionally, you can move auto-registered phones to new locations and assign them to different device pools without affecting their directory numbers.
Auto-registration is disabled by default.
For information about enabling and configuring auto-registration, refer to Cisco Unified CallManager Administration Guide.
Related Topics
•
•
Adding Phones with Auto-Registration and TAPS
You can add phones with auto-registration and TAPS without first gathering MAC addresses from phones.
TAPS, the Tool for Auto-Registered Phones Support, works with the Bulk Administration Tool (BAT) to update phones that were already added to the Cisco Unified CallManager database with dummy MAC addresses. Use TAPS to update MAC addresses and download pre-defined configurations for phones.
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.
You must make sure that Auto-registration is enabled in Cisco Unified CallManager Administration (System > Cisco CallManager) for TAPS to function.
Refer to Bulk Administration Tool User Guide for Cisco Unified CallManager for detailed instructions about BAT and about TAPS.
Related Topics
•
•
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. See the "Determining the MAC Address of a Cisco Unified IP Phone" section for instructions.
After you have collected MAC addresses, choose Device > Add a New Device in Cisco Unified CallManager Administration to begin.
For additional 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 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.
To add phones using BAT only (not in conjunction with TAPS), you first need to obtain the appropriate MAC address for each phone. See the "Determining the MAC Address of a Cisco Unified IP Phone" section for instructions.
For detailed instructions about using BAT, refer to Cisco Unified Unified CallManager Administration Guide and to Bulk Administration Tool Guide for Cisco Unified CallManager.
Related Topics
•
•
•
•
Determining the MAC Address of a Cisco Unified IP Phone
There are several procedures that require you to determine and enter the MAC address of a Cisco Unified IP Phone. These procedures include adding phones to the Cisco Unified CallManager database using Cisco Unified CallManager Administration or using BAT.
Table 2-3 describes the methods that you can use to determine the MAC address of a phone.
Table 2-3 Determining the MAC Address of a Phone
7905G and 7912G
Choose Menu > Settings > Network Configuration and look at the MAC Address field
See "Configuring Network Settings on the Cisco Unified IP Phone"
7905G and 7912G
Display the phone web page and click the Device Information hyperlink
