The bulk of your initial Cisco CallManager configuration comes in adding Cisco IP Phones to the SQL database. After you add the phones to the database, you can manage and configure them through the Cisco CallManager interface. You can add the phones to the database using one of three methods:
This chapter discusses the manual and automatic methods of adding IP Phones to the database. BAT is covered in Chapter 7, "Cisco Bulk Administration Tool."
Manual IP Phone and Directory Number Configuration
Manually adding new IP Phones to the network is often tedious, but it can constitute a large part of day-to-day voice network management. The Bulk Administration Tool (BAT) allows you to add a large number of IP Phones to the Cisco CallManager database at once, but BAT is not appropriate for adding or modifying a single IP Phone for a new employee.
Cisco CallManager uses the IP Phone MAC address to track the phone in the voice network. Cisco CallManager ties all IP Phone configuration settings to the IP Phone MAC address. Before you can perform any configuration on a Cisco IP Phone through Cisco CallManager, you must find the MAC address of that IP Phone. Use the following guidelines to locate a MAC address:
You can continue the Cisco IP Phone configuration on the Cisco CallManager configuration after you have the MAC address of the IP Phone, as follows:
Step 1. |
In Cisco CallManager Administration, choose Device > Phone to open the Find and List Phones window. |
Step 2. |
Choose Add a New Phone in the upper-right corner of the window. |
Step 3. |
Choose the model of the IP Phone from the drop-down menu, and click Next. |
Step 4. |
At a minimum, you must configure the MAC Address, Device Pool, and Phone Button Template fields; then click Insert. |
Step 5. |
Cisco CallManager prompts you to add a DN for line 1; then click OK. |
Step 6. |
When the Directory Number Configuration window appears, enter the DN of the IP Phone in the appropriate field, and click Insert. |
Figures 5-9 and 5-10 illustrate the IP Phone and directory number configuration screens, respectively.
Figure 5-9. Cisco CallManager IP Phone Configuration
Figure 5-10. Cisco CallManager Directory Number Configuration
Automatic IP Phone Registration
Auto-registration allows Cisco CallManager to issue extension numbers to new IP Phones, which is similar to the way in which the Dynamic Host Control Protocol (DHCP) server issues IP addresses. When a new IP Phone boots and attempts to register with Cisco CallManager for the first time, Cisco CallManager issues an extension number from a configured range. After Cisco CallManager issues the extension, it records the extension number to the MAC address mapping in the SQL database.
Although auto-registration simplifies the process of deploying a new IP telephony network, it is an option that is available only in some new IP telephony deployments. Because administrators deploy most IP telephony networks as a migration from a PBX environment, users have existing telephone extensions. These existing telephone extensions typically map to Direct Inward Dial (DID) numbers from the Public Switched Telephone Network (PSTN) and cannot change. Therefore, these IP telephony deployments usually use manual configuration rather than auto-registration.
You should carefully evaluate auto-registration before implementing it because its use can pose a security risk to the network. Auto-registration allows anyone with physical access to the voice network to connect an IP Phone and use it, regardless of whether they are authorized. For this reason, many organizations, as part of their security policy, disable the use of auto-registration or use auto-registration in a secure staging environment for initial Cisco CallManager configuration.
Complete these steps to configure the Cisco CallManager server to support auto-registration:
Step 1. |
From Cisco CallManager Administration, choose System > Cisco CallManager. |
Step 2. |
From the list of Cisco CallManager servers, select the server that you want to support auto-registration. |
Step 3. |
Under the Auto-Registration Information Configuration section, enter the appropriate DN range in the Starting and Ending Directory Number fields. |
Step 4. |
Ensure that the Auto-registration Disabled on this Cisco CallManager check box is unchecked. |
Step 5. |
Click Update to save your changes. |
Figure 5-11 shows the auto-registration configuration window.
Figure 5-11. Cisco CallManager Auto-Registration Configuration
Installing Cisco CallManager automatically sets device defaults. You cannot create new device defaults or delete existing ones, but you can change the default settings. Use device defaults to set the default characteristics of each type of device that registers with a Cisco CallManager. The device defaults for a device type apply to all auto-registered devices of that type within a Cisco CallManager cluster. You can set the following device defaults for each device type to which they apply:
When a device auto-registers with a Cisco CallManager, it acquires the device default settings for its device type. After a device registers, you can update its configuration individually to change the device settings.
Complete these steps to update the device defaults:
Step 1. |
In Cisco CallManager Administration, choose System > Device Defaults to open the Device Defaults Configuration window. |
Step 2. |
In the Device Defaults Configuration window, modify the appropriate settings for the device that you want to change. |
Step 3. |
Click Update to save the changes in the Cisco CallManager configuration database. |
Step 4. |
Click the Reset icon to the left of the device name to reset all the devices of that type and load the new defaults on all Cisco CallManager servers in the cluster. If you choose not to reset all devices of that type, only new devices that are added after you change the device defaults receive the latest defaults. |
Caution
Updating device load files and performing a phone reset can affect a large number of devices and cause significant WAN utilization as firmware files are sent to remote phones. Cisco recommends saving these large device resets for network off-hours.
Case Study Device Pool Design |
Part I: Cisco CallManager Fundamentals
Introduction to Cisco Unified Communications and Cisco Unified CallManager
Cisco Unified CallManager Clustering and Deployment Options
Cisco Unified CallManager Installation and Upgrades
Part II: IPT Devices and Users
Cisco IP Phones and Other User Devices
Configuring Cisco Unified CallManager to Support IP Phones
Cisco IP Telephony Users
Cisco Bulk Administration Tool
Part III: IPT Network Integration and Route Plan
Cisco Catalyst Switches
Configuring Cisco Gateways and Trunks
Cisco Unified CallManager Route Plan Basics
Cisco Unified CallManager Advanced Route Plans
Configuring Hunt Groups and Call Coverage
Implementing Telephony Call Restrictions and Control
Implementing Multiple-Site Deployments
Part IV: VoIP Features
Media Resources
Configuring User Features, Part 1
Configuring User Features, Part 2
Configuring Cisco Unified CallManager Attendant Console
Configuring Cisco IP Manager Assistant
Part V: IPT Security
Securing the Windows Operating System
Securing Cisco Unified CallManager Administration
Preventing Toll Fraud
Hardening the IP Phone
Understanding Cryptographic Fundamentals
Understanding the Public Key Infrastructure
Understanding Cisco IP Telephony Authentication and Encryption Fundamentals
Configuring Cisco IP Telephony Authentication and Encryption
Part VI: IP Video
Introducing IP Video Telephony
Configuring Cisco VT Advantage
Part VII: IPT Management
Introducing Database Tools and Cisco Unified CallManager Serviceability
Monitoring Performance
Configuring Alarms and Traces
Configuring CAR
Using Additional Management and Monitoring Tools
Part VIII: Appendix
Appendix A. Answers to Review Questions
Index