Table Of Contents
Installing Cisco CallManager Release 3.2(3)
Product Key for Cisco CallManager: BTOO VQES CCJU IEBI
Note The Cisco CallManager product key, which you enter during the operating system installation, allows you to install Cisco CallManager on a server that is dedicated solely to that application. If you want to install Cisco CallManager and Cisco Customer Response Solutions (CRS) on the same server, refer to the CRS installation documentation for the product keys.
Purpose of the Document
Use this document to perform the following tasks:
•Install Cisco CallManager for the first time
•Reinstall Cisco CallManager, if necessary
This document applies if you have one server or many servers in a cluster environment.
Cisco requires that any disk purchased for installation on a customer-provided server be installed on a server that meets approved Cisco configuration standards.
Note Unless otherwise specified in this document, all references to the MCS-7835 apply to the MCS-7835, which contains a 733-MHz processor, the MCS-7835-1000, which contains a 1-GHz processor, the MCS-7835-1266, which contains a 1.26-GHz processor, the MCS-7835I-2.4-EVV1, the MCS-7835H-2.4-EVV1, and the Cisco-approved, customer-provided DL380 servers.
Note Unless otherwise specified in this document, all references to the MCS-7825 apply to the MCS-7825, which contains an 800-MHz processor, the MCS-7825-1133, which contains a 1.13-GHz processor, and the MCS-7825H-2.2-EVV1.
Preinstallation Tasks and Information
Consider the following documentation conventions as you review this document:
Blue Text—To quickly navigate to a section or URL, click text that appears in blue.
Note Reader, take note. Notes contain helpful suggestions or references to material not covered in the publication.
Caution Reader, be careful. You may do something that could result in equipment damage or loss of data.
Tip Reader, perform this task to save time or to improve efficiency.
This convention indicates that you must perform the procedure.
Cisco recommends that you perform the procedure.
Locating Related Cisco CallManager Documentation
Cisco strongly recommends that you review the following documents before you perform the Cisco CallManager installation:
•Installing the Operating System on Cisco IP Telephony Applications Servers
This document provides procedures for installing the operating system on Cisco IP Telephony Applications Servers. This document does not provide Cisco IP telephony application installation procedures. Refer to this document before you install Cisco CallManager, Cisco Personal Assistant, Cisco Customer Response Solutions (CRS), Cisco Conference Connection, or Cisco Emergency Responder.
•Release Notes for Cisco CallManager Release 3.2
This document lists and describes the system requirements, new features, changed information, documentation updates, and open caveats for Cisco CallManager. Cisco provides a version of this document that matches the version of the installation document.
•Cisco CallManager Administration Guide and Cisco CallManager System Guide
The Cisco CallManager Administration Guide provides step-by-step instructions for configuring, maintaining, and administering the Cisco CallManager voice over IP network.
The Cisco CallManager System Guide provides descriptions of the Cisco CallManager system and its components, configuration checklists, and links to associated Cisco CallManager Administration Guide procedures.
•Cisco CallManager Serviceability Administration Guide and Cisco CallManager Serviceability System Guide
This document also provides descriptions of Cisco CallManager serviceability and remote serviceability and step-by-step instructions for configuring alarms, traces, and other reporting.
•Cisco Bulk Administration Tool User Guide
This document provides information on using the Bulk Administration Tool (BAT) to perform bulk add, update, and delete operations on phones, users, gateways, and ports.
•Using Cisco IP Telephony Applications Backup Utility, Version 3.5.18 (or later)
This document describes how to back up Cisco CallManager data and restore the Cisco IP Telephony Applications Server and Cisco CallManager data. This document also provides a list of data that is backed up during the scheduled or user-invoked backup.
•Cisco CallManager Compatibility Matrix
To ensure continued functionality with interfacing Cisco IP telephony applications after the Cisco CallManager installation, refer to the Cisco CallManager Compatibility Matrix, which provides compatibility information and workarounds for applications that are integrated with Cisco CallManager.
Affected applications may include Cisco Conference Connection, Cisco SoftPhone, Cisco uOne, Cisco Unity, Cisco 186 Analog Telephony Adapter, Cisco Personal Assistant, Cisco Customer Response Solutions (CRS), Telephony Application Programming Interface and Java Telephony Application Programming Interface (TAPI/JTAPI) applications, including Cisco-supported and third-party applications, and Cisco Telephony Service Provider (TSP).
This document provides specific information, including compatibility and installation guidelines, for Cisco IP Contact Center (IPCC) systems. If you use Cisco CallManager and related Cisco IP telephony applications in a call-center environment, review this document before you begin any installation procedures.
•Cisco IP Telephony Operating System, SQL Server, Security Updates
This document provides information for tracking Cisco-supported operating system, SQL Server, and security updates. Information in this document applies to servers that are running the following Cisco IP telephony applications: Cisco CallManager, Conference Connection, Personal Assistant, and Cisco Customer Response Applications/Solutions, and Cisco Emergency Responder.
•The appropriate Cisco IP telephony application documentation
Locate the release notes, installation/upgrade, and configuration guides for the applications that you want to integrate with Cisco CallManager.
•Release Notes for Cisco CallManager 3.2(x) on the Cisco ICS 7750
This document provides installation/upgrade procedures and other information that is related to running Cisco CallManager 3.2 on the Cisco ICS 7750.
Click the URLs in Table 1 to navigate to the appropriate documentation and software.
Frequently Asked Questions About the Cisco CallManager Installation
Review the following questions and responses before you install Cisco CallManager on the server.
How long does it take to perform the Cisco CallManager installation?
The entire installation process, excluding pre-/post-installation tasks, takes 60 to 120 minutes per server, depending on your server type. Before you install Cisco CallManager, consider the size of your cluster and the number of Cisco IP telephony applications that you plan to install.
How does the Cisco CallManager installation work?
For information on the operating system that Cisco CallManager uses, refer to Installing the Operating System on the Cisco IP Telephony Applications Server. See Table 1.
After you install the operating system, Cisco IP Telephony Applications Server QuickBuilder automatically installs the following software applications:
•Microsoft SQL Server 7.0 Standard Edition, Service Pack 4
•Cisco IP Telephony Applications Backup Utility
Table 2 describes the components that are installed when you choose the options from the CallManager Components window.
Cisco CallManager places services in an inactive state until the installation completes. When you complete the installation, the services activate and start. For information on starting and stopping services, refer to the Cisco CallManager Serviceability Administration Guide or to online help in the Cisco CallManager application.
About the Publisher Database and Subscriber Servers
Determine whether this server will be configured as the publisher database server or as a subscriber database server. This decision designates a permanent selection. If you want to reassign the database server type at a later date, you must reinstall the Cisco CallManager server.
In a Cisco CallManager distributed system, one server maintains the master, or publisher, database, and all other servers in the cluster maintain subscriber databases. You always install the publisher database server first. Subscriber databases provide copies of the master database. During normal operation, all Cisco CallManagers in the cluster read data from and write data to the publisher database. Periodically, Cisco CallManager automatically updates the subscriber copies of the database from the publisher database. You install Cisco CallManager first on the publisher database server.
Caution If you are configuring a subscriber database server, make sure that the publishing database server for that cluster is installed, connected to the network, and configured properly to work as a distributed system.When configuring a subscriber database server, ensure that the server that you are installing can connect to the publishing database server during the installation. This connection facilitates copying the publisher database from the publisher server to the local drive on the subscriber server. You must supply the name of the publishing database server and a username and password with administrator access rights on that server. If the publisher server cannot be authenticated during the installation for any reason, the installation will not continue.
During the Cisco CallManager installation, you must enter a valid password for the following accounts:
•Local Administrator account
If you plan to install Cisco CallManager on the Cisco Media Convergence Server (MCS), you established this password during the operating system installation. If you left the password blank during the operating system installation, or if you enter the wrong password during the Cisco CallManager installation, you cannot install Cisco CallManager on the server.
Tip Verify that the account password is the same on all servers in the cluster. If it is not the same password, the installation fails.
Caution When you enter passwords for the local Administrator and SA (SQL Server system administrator) accounts, enter alphanumeric characters only. The account password must match on every server in the cluster.
•SA (SQL Server system administrator) account
•Directory Manager (DC Directory) account
About the Backup Utility
The Cisco CallManager installation prompts you to configure the server either as the backup server or as a backup target. If you want to use the backup utility, one server in the cluster must act as the backup server, which is the server that invokes the backup. Backup target(s) serve as the source for the data, which is the server where the data exists before the backup.
You do not need to back up subscriber servers, but Cisco strongly recommends that you perform regularly scheduled backups for the publisher database server. If you do not install the utility and configure the backup settings, you cannot restore the Cisco CallManager data in the unlikely event of a catastrophic failure.
For information on how to configure the backup utility, refer to Using Cisco IP Telephony Applications Backup Utility, Version 3.5.18 (or later). See Table 1 to obtain the document.
What data must I provide to configure the server?
During the installation process, you receive prompts telling you to enter important configuration information about the server, such as the publisher database server computer name and passwords. You can complete the initial power up more efficiently if you gather all the necessary configuration information before beginning the installation process.
Table 3 shows the configuration information that is required for installing software on your server. Complete all fields unless otherwise noted. Gather this information for each Cisco CallManager server that you are installing in the cluster. Make copies of this table and record your entries for each server in a separate table. Have the completed lists with you when you begin the installation.
May I install other software besides Cisco CallManager on the server?
Cisco supports a limited list of applications on the servers where Cisco CallManager is installed.
Disabling Third-Party, Cisco-Verified Applications (Required)
Caution To successfully complete installation, upgrade, or restoration procedures, you must disable all Cisco-verified applications/services on every server in the cluster.
Disabling platform agents and services, such as performance monitoring (for example, NetIQ), antivirus (Cisco-approved McAfee services), intrusion detection (Cisco IDS), and remote management services, ensures that the installation does not encounter issues that are associated with these services.
Consider the following information before you install other software besides Cisco CallManager on the Cisco MCS or the customer-provided server:
•Installing or using Netscape Navigator on the Cisco MCS or the approved customer-provided server causes severe performance problems. Cisco strongly recommends against installing Netscape Navigator on the Cisco MCS or Cisco-approved, customer-provided server.
•You can install a compatible version of Cisco Customer Response Applications, which you must purchase separately from Cisco CallManager.
•Do not install Cisco Unity, Cisco Conference Connection, Cisco Personal Assistant, or Cisco Emergency Responder on the server where Cisco CallManager is installed.
•Cisco recommends that you install the Cisco IDS Host Console on a standalone server designated for that software. You can install Cisco IDS Host Agents on servers where Cisco CallManager is installed. To access information on Cisco IDS Host Sensor, see Table 1.
May I run a web browser on the server?
Cisco strongly recommends that you do not run a web browser on the Cisco MCS or any approved customer-provided server. Running a web browser on the server causes CPU usage to surge.
To access Cisco CallManager Administration, the web-based graphical user interface (GUI) that allows you to perform Cisco CallManager configuration tasks, browse into the Cisco CallManager server that is running Cisco CallManager Administration and log in with administrative privileges.
Tip To browse into the server, enter http://<CM-server-name>/CCMAdmin/main.asp, where <CM-server-name> equals the name of the server, in the Address bar in the web browser.
May I configure a server in the cluster as a Domain Controller?
Caution Cisco strongly recommends that you do not configure any server in the cluster as a Domain Controller. If you configure any server in the cluster as a Domain Controller, you cannot upgrade or reinstall Cisco CallManager on the server.
What if I encounter problems during the installation?
Cisco recommends that if you encounter problems during the installation, obtain and review the following log files:
•C:\Program Files\Common Files\Cisco\Logs\CCMBackup<Date><Time>.log
Tip Be aware that not all error messages that display in the log file are catastrophic. The installation generates error messages in the log file for many reasons; for example, attempts to access a service that Cisco CallManager does not use.
What preinstallation tasks should I perform?
For preinstallation tasks you must complete before the installation, see Table 4.
Table 4 Preinstallation Tasks
Step Preinstallation Tasks Important Notes
Make sure that you have the appropriate hardware before installing the operating system or Cisco CallManager.
Carefully review the hardware documentation that accompanies your server. To review Cisco MCS hardware specifications, see Table 1.
Plan your system configuration.You can distribute the call-processing load for your system across multiple Cisco CallManagers as a single cluster. A cluster comprises a set of Cisco CallManagers that share the same database.
At a minimum, you should determine how many Cisco CallManager servers the cluster will contain, which server will house the publisher database, and where backup tasks will be performed. Additional planning should include a strategy for distributing the devices (such as phones or gateways) among the Cisco CallManagers in the cluster to achieve the type of distribution that you want.
In a Cisco CallManager distributed system, one server maintains the master, or publisher, database, and all other servers in the cluster maintain subscriber databases. Subscriber databases provide copies of the master database. During normal operation, all Cisco CallManagers in the cluster read data from and write data to the publisher database. Periodically, Cisco CallManager automatically updates the subscriber copies of the database from the publisher database.
For more information on planning a Cisco CallManager distribution system, refer to the Cisco CallManager System Guide.
Connect the server to the network.
If your server supports the Cisco Media Convergence Server Network Teaming Driver, you can install and configure this driver, if you choose to do so.
To obtain the installation and configuration document, see Table 1.
Before you perform Cisco CallManager installation, upgrade, or restoration procedures, you must disable and stop all Cisco-verified applications/services. You can enable and start all applications/services after you complete the procedures.
For example, you must disable and stop Cisco-verified McAfee antivirus services. You must disable and stop services associated with Cisco IDS Host Sensor.
See the following sections:
Verify that you have installed the operating system by using the Cisco-provided operating system disks.
To obtain the document, see Table 1.
Locate Table 3, which provides specific server configuration information.
How do I connect the server to the network?
Make sure that you connect your server to the network before you begin the installation. The special, limited edition of Windows 2000, intended for use with Cisco CallManager only, will not install if you do not connect the server to the network.
The servers in Table 5 contain two network interface cards (NIC), but Cisco CallManager supports only one NIC. When you connect the server to the network, use the NIC connector that is listed in the table because the other NIC is disabled during the installation.
Caution Make sure that you locate and connect the server to the appropriate NIC. Connecting the server to the wrong NIC connector causes problems to occur.
How do I disable Cisco-approved McAfee antivirus services?
To disable the McAfee antivirus services, perform the following tasks:
Step 1 Choose Start > Settings > Control Panel > Administrative Tools > Services.
Step 2 From the Services window, right-click one of the antivirus services; i.e., Network Associates Alert Manager, Network Associates McShield, or Network Associates Task Manager, and choose Properties.
Step 3 Verify that the General tab displays in the Properties window.
Step 4 From the Startup type drop-down list box, choose Disabled.
Step 5 Click Apply.
Step 6 Click OK.
Step 7 In the Services window, right-click the antivirus service and click Stop.
Performing the Installation
The entire Cisco CallManager installation process, excluding pre-/post-installation tasks, takes 60 to 120 minutes per server. To perform a Cisco CallManager installation, see the following sections:
Disable Third-Party, Cisco-verified Applications (Required If Installed)
Before you install the operating system or Cisco CallManager, Cisco strongly recommends that you disable all third-party, Cisco-verified applications/services that are installed.
For a list of applications or services that may affect the installation, see the "May I install other software besides Cisco CallManager on the server?" section.
For information on how to disable Cisco-verified McAfee antivirus services, see the "How do I disable Cisco-approved McAfee antivirus services?" section.
For information on how to disable other applications or services, refer to the documentation that accompanies the product.
Install the Operating System (Required)
To install the operating system, refer to Installing the Operating System on the Cisco IP Telephony Applications Server. See Table 1 for information on how to obtain the document.
Install Cisco CallManager (Required)
During the installation, you install services, Cisco CallManager Administration, the publisher database or subscriber server, and the Cisco IP Telephony Applications Backup Utility. This section provides procedures for the following topics:
Note If you need Cisco CallManager installation and backup/restore information for the Cisco Integrated Communications System (ICS) 7750, refer to the latest version of the Cisco ICS 7750 Getting Started Guide and the Cisco ICS 7750 Release Notes.
Installing Services and the Publisher Database or Subscriber Server
In this portion of the installation, you will perform the following tasks:
•Insert the Cisco CallManager 3.2 Installation and Recovery Disk.
•Choose the services that you want to activate on the server.
•Choose whether you are installing a publisher or subscriber database server.
Step 1 When prompted to do so, insert the Cisco CallManager 3.2 Installation and Recovery Disk. The installation script automatically continues loading from the disk.
Caution Do not remove the disk unless the installation or this document prompt you to do so. Removing the disk at an inappropriate time causes the installation to fail.
Step 2 In the Welcome to the Cisco CallManager Installation Wizard window, click Next.
Step 3 The CallManager Components window opens, displaying the default selections. For information on available components and standalone servers, see Table 2.
When Cisco CallManager services are activated, the installation process places them in a stopped state. All services activate and start upon completion of the installation. For information on starting services, refer to the Cisco CallManager Serviceability Administration Guide or to online help in the Cisco CallManager application.
Figure 1 shows an example of the CallManager Components window.
Figure 1 CallManager Components Window
Choose the services that you want to activate in this initial installation; then, click Next.
You must decide whether you are installing the publisher database server or subscriber database server. You must first install Cisco CallManager on the publisher database server. Figure 2 shows an example of the Cisco CallManager Database Distribution window where you establish the publisher-subscriber relationship. If you are installing the subscriber database server, the authentication window prompts you to enter usernames and passwords for a Windows 2000 user with administrative privileges and a SQL Server user with SQL Server administrative privileges on the publishing database server.
Figure 2 Cisco CallManager Database Configuration
Note The publisher database serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server before the installation can continue. The installation process necessitates this connection, so the publisher database can be copied to the local drive on the subscriber server. To make sure a good connection exists between the servers, issue a ping command from the subscriber server to the publisher server before you try to authenticate to it. If you are using DNS, use a fully qualified domain name (for example, `hostname.acme.com') with the ping command. If the ping command is not successful, you must exit the installation program, fix the problem, and begin the installation process again.
Installing Cisco CallManager on the Publisher Database Server
Step 4 If you are installing the publisher database server, choose I am upgrading/installing the CallManager Publisher. Click Next.
Step 5 The Directory Server Configuration window opens and prompts you for the Directory Manager password. Enter the password in the Password field.
Step 6 Enter the same password again in the Confirm Password field. Click Next, and go to Step 10.
Installing Cisco CallManager on the Subscriber Server
Step 7 If a publisher database already exists and you are configuring a subscriber database server, choose I am upgrading/installing the CallManager Subscriber.
Step 8 You may choose another publisher by clicking Browse. After you choose the appropriate publisher database server, click Next.
Step 9 The authentication window prompts you to enter usernames and passwords for a Windows 2000 user with administrative privileges and a SQL Server user with SQL Server administrative privileges on the publishing database server. Enter the account information in the appropriate fields; then, click Next, and go to Step 10.
The system connects to the publishing database server.
Step 10 You can now install Cisco CallManager. Click Next. This part of the installation takes 30 to 90 minutes, depending on the options that you have chosen.
Step 11 The Cisco IP Telephony Applications Backup Utility Setup loads automatically after Cisco CallManager installs. If you click the Cancel button when the Setup window loads, the backup utility does not install for use. Continue with the installation by performing the steps in "Installing the Cisco IP Telephony Applications Backup" section.
Installing the Cisco IP Telephony Applications Backup
For information and procedures on how to install and configure the backup utility, refer to Using Cisco IP Telephony Applications Backup Utility, Version 3.5.18 (or later). See Table 1.
Verifying and Reinitializing Subscriber Connections
If the connections between the publisher database server and the subscribers within a cluster are broken for any reason, you cannot replicate the database to the subscribers.
Verifying the Status of the Subscription
In the Enterprise Manager, a red X icon next to the subscription indicates that the subscription is broken.
Reinitializing the Subscription/Starting the Replication Snapshot Agent
If you determine that one or more subscription connections are broken, as indicated by the red X icon next to the subscriptions, reinitialize the subscriptions and start the replication snapshot agent on the publisher database server.
Step 1 Open SQL Server Enterprise Manager by choosing Start > Programs > Microsoft SQL Server 7 > Enterprise Manager.
Step 2 In the following path, choose the name of the publisher database that you are configuring: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<the publisher database name>Publications.
Step 3 In the main window, right-click the subscription name and choose Reinitialize all Subscriptions. Click Yes to confirm.
Step 4 In the following path, choose the Snapshot Agents folder: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Replication Monitor/Agents.
Step 5 Right-click the publication name that matches the database name that you are configuring; then, click Start.
In rare cases, the reinitialization of the subscriptions may not work. If you determine that the previous procedure did not work as expected, contact the team that provides technical assistance for this product; for example, your Cisco AVVID Partner or the Cisco Technical Assistance Center (TAC).
Performing Post-Installation Tasks
After you install Cisco CallManager on your server, you must set some configuration parameters for Cisco CallManager and perform other post-installation tasks before you can begin using it.
For post-installation tasks that you must complete after the installation, see Table 6.
Enabling Cisco-Verified McAfee Antivirus Services
To enable the Cisco-approved McAfee antivirus services, perform the following tasks:
Step 1 After you log in to the server, enable all Cisco-approved McAfee antivirus services through the Control Panel by completing the following procedure:
a. Choose Start > Settings > Control Panel > Administrative Tools > Services.
b. From the Services window, right-click one of the antivirus services; i.e., Network Associates Alert Manager, Network Associates McShield, or Network Associates Task Manager, and choose Properties.
c. Verify that the General tab displays in the Properties window.
d. From the Startup type drop-down list box, choose Automatic.
e. Click OK.
f. In the Services window, right-click the antivirus service and click Start.
Step 2 Perform Step 1 to enable all Cisco-approved McAfee antivirus services; i.e., Network Associates Alert Manager, Network Associates McShield, and Network Associates Task Manager.
Verifying Services, Patches, and Hotfixes
For ongoing management, Cisco recommends that you monitor and install the following items:
Cisco CallManager-Related Services
To confirm that the installation completed successfully, verify that all services that are listed in your Services window are running. Choose Start > Programs > Administrative Tools > Services and verify the following services:
•Cisco Database Layer Monitor
•Cisco IP Voice Media Streaming Application
•Cisco Messaging Interface
•Cisco RIS Data Collector
•DC Directory Server
Depending on which services you have installed on your system, some services shown in the preceding list may not appear in your Services window.
Operating System Support Patches
To verify and install operating support patches, refer to Installing the Operating System on the Cisco IP Telephony Applications Servers. See Table 1.
Cisco CallManager Support Patches
If you receive a Cisco CallManager support patch disk in your software kit, insert the disk into the drive, click the My Computer icon on the desktop, select and review the readme document available on the disk, and perform the appropriate procedures.
Cisco strongly recommends that you install the latest Cisco CallManager 3.2 support patch on all servers in the cluster. These support patches provide additional utilities and bug fixes for your system.
Be aware that Cisco CallManager support patches are cumulative. Cisco always rolls these utilities and bug fixes into the next Cisco CallManager release.
Tip Make sure that you install the same version of the support patch on every server in the cluster.
To obtain the latest Cisco CallManager support patch, perform the following procedure:
Step 1 Click http://www.cisco.com/public/sw-center/sw-voice.shtml.
Step 2 Click Cisco CallManager Version 3.2.
The Cisco CallManager 3.2 software page displays.
Step 3 Locate and download the readme document for the support patch.
The readme file provides procedures, caveats, and descriptive information for installing the files.
Step 4 Using the readme file as a reference, install the Cisco CallManager support patch on every server in the cluster where Cisco CallManager is installed.
Step 5 Perform other post-installation tasks.
Viewing the Component Versions Installed on the Server
The stiver.exe program reports the current version of all installation components, including the operating system, upgrade, and backup and restore utility. Be aware that Cisco does not report the actual Cisco CallManager version through this program. Most of these components, which are run from the installation disks during the initial installation, no longer exist on the system.
The version for OS Image equals your operating system disk version number. The version of OS Image will change only if you do a new installation using the Cisco IP Telephony Server Operating System Hardware Detection Disk.
Perform the following procedure to view the component versions that are installed on the server:
Step 1 Use Windows Explorer to browse to the following folder:
Step 2 View the versions of the components that are running on your server.
Configuring the Database
After installing Cisco CallManager, you use Cisco CallManager Administration to begin configuring the database. The Cisco CallManager database contains information and parameters that relate to the system as a whole, to connected devices, and to individual users. The following list describes a few tasks that you must perform in Cisco CallManager Administration or Cisco CallManager Serviceability:
1. Configure system-level settings, such as Cisco CallManager Groups.
2. Design and configure your dialing plan.
3. Configure media resources for conferences, Music On Hold, etc.
4. Install and configure your chosen voice-mail system.
5. Configure system-wide features, such as Cisco IP Phone services and Cisco CallManager Attendant Console.
6. Install and configure the gateways.
7. Enable computer telephony integration (CTI) application support; then, install and configure the desired CTI applications.
8. Configure and install the phones; then, associate users with the phones.
For more information about configuring the Cisco CallManager database, refer to the Cisco CallManager Administration Guide, the Cisco CallManager System Guide, or online help in Cisco CallManager Administration.
Cisco strongly recommends that you configure DNS on every server in the cluster where Cisco CallManager is installed. Cisco uses DNS to resolve the server name to an IP address, so servers can interact in the cluster.
Caution When you configure DNS, make sure that you configure and enable the Reverse DNS Lookup function.
The DNS suffix for the connection field must contain the DNS domain information where the server exists as a member.
When multiple DNS domains exist in a single Cisco CallManager cluster or the Backup Network Directory Location exists in a different DNS domain, you must correctly enter the domain information in the Append these DNS suffixes (in order): field.
To configure DNS after installing Cisco CallManager, perform the following steps:
Step 1 Choose Start > Settings > Network and Dial-up Connections.
Step 2 Right-click Local Area Connection and choose Properties.
Step 3 Choose Internet Protocol (TCP/IP).
Step 4 Click Properties.
Step 5 Click Advanced.
Step 6 Click the DNS tab.
Step 7 Click the Add button that is underneath the DNS server addresses in order of use pane.
Step 8 In the dialog box, enter the IP address of the DNS server and click Add.
Step 9 Check the Register the connection's address with DNS check box, if it is not already checked.
Step 10 Click OK.
Step 11 Perform this procedure on every server in the cluster that has Cisco CallManager installed.
Disabling the Hyper-Threading Technology (HTT) on the IBM xSeries 345 Server
When HTT is enabled, this technology causes Cisco CallManager performance to decrease. Cisco strongly recommends that you disable this technology on the IBM xSeries 345 server. Perform the following procedure to disable HTT:
Step 1 Reboot the server.
Step 2 When the IBM logo displays and you see a list of prompts in the lower, left corner of the monitor, press F1 for Configuration/Setup.
Step 3 When the Configuration/Setup Utility window displays, press the arrow keys to choose Advanced Setup; press Enter.
Step 4 Press the arrow keys to choose CPU Options; press Enter.
Step 5 Press the arrow keys to choose Hyper-Threading Technology; then, press the arrow keys to choose Disabled.
Step 6 Press Esc.
Step 7 Press Esc.
Step 8 Press the arrow keys to choose Save Settings; then, press Enter.
Step 9 Press Enter to continue.
Step 10 Press the arrow keys to choose Exit Setup; then, press Enter.
Step 11 Press Enter.
Using the F: Drive on the MCS-7845-1400 to Collect Trace Files
To increase system performance, you can configure service parameters and trace output settings, so trace files write to the F: drive instead of the default C: drive. Using the F: drive allows you to capture more trace files because this drive is set up specifically for trace file collection.
After you configure the server in Cisco CallManager Administration, perform the following procedure for all MCS-7845-1400 in the cluster:
Step 1 After you open Cisco CallManager Administration, choose Service > Service Parameters.
Step 2 From the Server drop-down list box, choose the server name or IP address of the MCS-7845-1400.
The Service Parameters Configuration window displays.
Step 3 From the Service drop-down list box, choose Cisco CallManager. If the drop-down list box does not display "Cisco CallManager," click the service in the pane on the left side of the window and then click Insert.
The Service Parameters Configuration window for Cisco CallManager displays.
Step 4 Locate the parameter, SdlTraceFilePath, and change the parameter value from the C: drive to the F: drive.
Step 5 Click Update.
Step 6 From Cisco CallManager Administration, choose Application > Cisco CallManager Serviceability.
The Cisco CallManager Serviceability window displays.
Step 7 Choose Trace > Configuration.
Step 8 From the Server pane on the left side of the Trace Configuration window, click the server name or IP address of the MCS-7845-1400 that you chose in Step 2.
The Trace Configuration window for the service and server displays.
Step 9 In the File Name field under Trace Output Settings, change the default from the C: drive to the F: drive.
Step 10 Click Update.
Step 11 Perform this procedure on all MCS-7845-1400 in the cluster.
Activating Cisco CallManager Services
Although Cisco CallManager services were installed on your server during the installation process, only those that you chose during the installation were activated.
Caution Do not deactivate the Cisco CallManager service by using the following procedure. If it is inadvertently deactivated, contact the Cisco Technical Assistance Center (TAC).
To activate additional Cisco CallManager services, or to deactivate existing services, perform the following steps:
Step 1 Choose Start > Programs > Cisco CallManager > Cisco Service Configuration.
Step 2 Choose the check box for each Cisco CallManager service that you want to activate. If a service is currently activated and you uncheck it, Cisco CallManager shuts it down, removes it from the service registration table, and makes it unavailable for use. Click Apply.
Step 3 Click Exit.
Step 4 After you activate a service, you must start it. For information on starting services, refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.
Using the Cisco CallManager Music On Hold Disk or Download
When you install Cisco CallManager on your server, a default music on hold sample automatically installs for customer use. To increase your music on hold (MOH) selection, you may also install the Cisco CallManager Music On Hold Disk that ships with your Cisco IP Telephony Applications Server, or you may download one of two following files via the web:
•ciscocm-MusicOnHold, which is a set of wav files providing the entire music selection from the disk
•ciscocm-MusicOnHoldSampler, which is a small set of files offering a sample of music available on the disk
For information on the MOH feature, refer to the latest version of the Cisco CallManager Administration Guide and the latest version of the Cisco CallManager System Guide.
As a Cisco CallManager user, you can use any of the contents of the disk/files with music on hold. Because of licensing restrictions, you must not distribute the Cisco CallManager Music on Hold disk/files to anyone else, and you must not use it for any other purpose.
Adding New Subscriber Servers to the Cluster After the Installation
If you need to add servers to the cluster, perform the following tasks:
1. If you changed any NT Service passwords on the servers in the cluster, you must reset the passwords to the default. The installation fails if you forget to perform this task.
2. Install the operating system on the subscriber server(s) by using the Cisco-provided operating system disks and the operating system documentation.
3. Verify that you configured name resolution, for example, DNS, before you install Cisco CallManager.
4. Install Cisco CallManager on the subscriber server(s) by using the Cisco CallManager Installation and Recovery Disk.
Make sure that you enter the publisher database server name (computer name) correctly, so authentication to the publisher database server can occur.
5. Upgrade to the version of Cisco CallManager that currently runs in the cluster.
6. Install the same Cisco CallManager support patch and operating system hotfixes/service patch that you have applied to the existing cluster.
Replacing the Publisher Database Server after the Installation
For more information on performing this task, refer to Using the Cisco IP Telephony Backup Utility, Version 3.5.18 (or later). See Table 1.
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from this URL:
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
You can find instructions for ordering documentation at this URL:
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments to firstname.lastname@example.org.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems, Inc.
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Cisco TAC Website
You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:
•Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in the design, development, and operation of public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
•Training—Cisco offers world-class networking training, with current offerings in network training listed at this URL:
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0208R)
Copyright © 2003, Cisco Systems, Inc.
All rights reserved.