-
Cisco IP Phone Model 7960G and 7940G Administration Guide for Cisco CallManager Release 4.1
-
Preface
-
An Overview of the Cisco IP Phone
-
Preparing to Install the Cisco IP Phone on Your Network
-
Setting Up the Cisco IP Phone
-
Configuring Network Settings on the Cisco IP Phone
-
Configuring Features, Templates, Services, and Users
-
Viewing Model Information, Status, Statistics, and Security Information on the Cisco IP Phone
-
Monitoring the Cisco IP Phone Remotely
-
Troubleshooting the Cisco IP Phone
-
Providing Information to Users Via a Website
-
Supporting International Users
-
Technical Specifications
-
Index
-
Table Of Contents
Preparing to Install the Cisco IP Phone on Your Network
Understanding Interactions with Other Cisco IP Telephony Products
Understanding How the Cisco IP Phone Interacts with Cisco CallManager
Understanding How the Cisco IP Phone Interacts with the Cisco Catalyst Family of Switches
Understanding the Phone Startup Process
Understanding Phone Configuration Files
Providing Power to the Cisco IP Phone
Adding Phones to the Cisco CallManager Database
Adding Phones with Auto-Registration
Adding Phones with Auto-Registration and TAPS
Adding Phones with Cisco CallManager Administration
Configuring the Cisco IP Phone 7960G to Support the Cisco IP Phone 7914 Expansion Module
Preparing to Install the Cisco IP Phone on Your Network
Cisco 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 CallManager.
This chapter provides an overview of the interaction between the Cisco IP Phone models 7960G and 7940G 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 IP Phone must be connected to a networking device, such as a Cisco Catalyst switch. You must also register the Cisco IP Phone with a Cisco CallManager system before sending and receiving calls.
This section covers the following topics:
•
•
Understanding How the Cisco IP Phone Interacts with Cisco CallManager
Cisco CallManager is an open and industry-standard call processing system. Cisco 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 CallManager manages the components of the IP telephony system—the phones, the access gateways, and the resources necessary for such features as call conferencing and route planning. Cisco CallManager also provides authentication and encryption if configured for the telephony system.
For information about configuring Cisco CallManager to work with the IP devices described in this chapter, refer to Cisco CallManager Administration Guide, Cisco CallManager System Guide, and to Cisco CallManager Security Guide.
For an overview of security for the Cisco IP Phone, see the "Understanding Security Features for Cisco IP Phones" section.
Note
Related Topic
•
Understanding How the Cisco IP Phone Interacts with the Cisco Catalyst Family of Switches
The Cisco IP Phone models 7960G and 7940G have an internal Ethernet switch, enabling proper forwarding of appropriate packets to the phone, to the access port (labeled 10/100 PC on the phone), and to the network port (labeled 10/100 SW on 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:
•
•
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 IP Phone goes through a standard startup process that is 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 IP Phone.
Table 2-1 Cisco IP Phone Startup Process
1.
You can connect the Cisco IP Phone to a Cisco Catalyst switch with one of the modules that provides power to the phone (WS-X6348-RJ45V).
If you use this optional configuration, the phone receives phantom power and powers up when you connect the Cisco 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.
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.
3.
If the Cisco 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.
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.
•
5.
In addition to assigning an IP address, the DHCP server directs the Cisco 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.
Before requesting a configuration file, a phone accesses a CTL file. If you want a phone to use security features, the CTL file should be available.
For information about creating the CTL file, refer to Cisco CallManager Security Guide.
7.
The TFTP server has configuration files, which define parameters for connecting to Cisco CallManager and other information for the phone.
•
•
8.
The configuration file defines how the Cisco IP Phone communicates with Cisco CallManager. After obtaining the file from the TFTP server, the phone attempts to make a connection to the highest priority Cisco CallManager on the list. If security is implemented, the phone makes a TLS connection. Otherwise, it makes a non-secure TCP connection.
If the phone was manually added to the database, Cisco CallManager identifies the phone. If the phone was not manually added to the database and auto-registration is enabled in Cisco CallManager, the phone attempts to auto-register itself in the Cisco CallManager database.
Note
Cisco CallManager informs devices using .cnf 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
Configuration files for a phone are stored on the TFTP server and define parameters for connecting to Cisco CallManager. In general, any time you make a change in Cisco 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.
In addition, if the device security mode in the configuration file is set to Authenticated, the phone contains a valid LSC, and the CTL file on the phone has a valid certificate for Cisco CallManager, the phone establishes a TLS connection to Cisco CallManager. Otherwise, the phone establishes a TCP connection.
Note
A phone requests a configuration file whenever it resets and registers with Cisco CallManager.
Note
A phone accesses a default configuration file named XmlDefault.cnf.xml from the TFTP server when the following conditions exist:
•
•
•
•
All other times, a phone accesses a .cnf.xml file corresponding to its device name.
Providing Power to the Cisco IP Phone
You can power a Cisco IP Phone from an external power supply, from a switch port, or from a power source between the phone and the switch.
The Cisco IP Phone can be powered by the following sources:
•
•
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 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. Like the inline power, the power patch panel also attempts to verify that the attached device is a Cisco IP Phone before providing power.
Related Topics
•
•
Power Source Design
The phone and upstream switch automatically determine which power source the phone uses. (An upstream switch is any switch that connects to Cisco IP Phones, such as a Cisco Catalyst 4500 switch.) If power has to be provided by a different source, the phone user will experience different results based on which power source is being used by the phone.
Use the following information to choose a power source for the phone:
Case 1: The upstream switch can provide power over Ethernet
•
•
•
•
Case 2: The upstream switch cannot provide power over Ethernet
•
•
Caution
Related Topics
•
•
•
Redundancy Feature
For redundancy, you can use the Cisco AC adapter even if you are using inline power from the Cisco Catalyst switches. The Cisco IP Phone can share the power load being used from the inline power and external power source. If either the inline power or the external power goes down, the phone can switch entirely to the other power source.
To use this redundancy feature:
1.
2.
3.
Related Topics
•
•
•
Adding Phones to the Cisco CallManager Database
Before installing the Cisco IP phone, you must choose a method for adding phones to the Cisco CallManager database. The following sections describe these methods:
•
•
•
Table 2-2 provides an overview of these methods for adding phones to the Cisco 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 CallManager begins the automatic startup process to obtain a directory number. During auto-registration, Cisco CallManager automatically assigns the next available sequential directory number to the phone.
When you use this method, Cisco CallManager automatically assigns directory numbers to new phones as they register with Cisco CallManager.
You can use auto-registration to quickly enter phones into the Cisco CallManager database. You can then modify any settings, such as the directory numbers, from Cisco 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 CallManager Administration Guide.
Note
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 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 CallManager Administration with the correct MAC address.
You must make sure that Auto-registration is enabled in Cisco CallManager Administration (System > Cisco CallManager) for TAPS to function.
Note
Refer to Bulk Administration Tool User Guide for Cisco CallManager for detailed instructions about BAT and about TAPS.
Related Topics
•
•
Adding Phones with Cisco CallManager Administration
You can add phones individually to the Cisco CallManager database using Cisco CallManager Administration. To do so, you first need to obtain the MAC address for each phone.
For information about determining a MAC address, see the "Determining the MAC Address of a Cisco IP Phone" section.
After you have collected MAC addresses, choose Device > Add a New Device in Cisco CallManager Administration to begin.
For complete instructions and conceptual information about Cisco CallManager, refer to Cisco CallManager Administration Guide and to Cisco CallManager System Guide.
Related Topics
•
•
Adding Phones with BAT
The Cisco Bulk Administration Tool (BAT) is a plug-in application for Cisco 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 MAC address for each phone.
For information about determining a MAC address, see the "Determining the MAC Address of a Cisco IP Phone" section.
For detailed instructions about using BAT, refer to Cisco CallManager Administration Guide and to Bulk Administration Tool Guide for Cisco CallManager.
Related Topics
•
•
•
Configuring the Cisco IP Phone 7960G to Support the Cisco IP Phone 7914 Expansion Module
The Cisco IP Phone 7914 Expansion Module attaches to a Cisco IP Phone 7960G to extend the number or line appearances and/or speed dial buttons.
To configure the Cisco IP Phone 7960G to support the Cisco IP Phone 7914 Expansion Module, perform the following steps.
You might also want to customize the button templates for the Cisco IP Phone 7914 Expansion Module. See the "Modifying Phone Button Templates" section for details.
Procedure
Step 1
The Cisco CallManager Administration page appears.
Step 2
The Find and List Phone page appears. You can search for one or more phones that you want to configure for the Cisco IP Phone 7914 Expansion Module.
Step 3
The Find and List Phone page reappears showing a list of the phones matching your search criteria.
Step 4
The Phone Configuration page appears.
Step 5
Step 6
To add support for a second expansion module, in the Module 2 field, select 7914 14-Button Line Expansion Module.
In the Firmware Load Information section of the page, there are two fields for specifying the firmware load for Modules 1 and 2. You can leave these fields blank to use the default firmware load.
Step 7
A message appears asking you to reset the phone for the changes to take effect. Click OK.
Step 8
Note
Related Topic
