Guest

Cisco Unified Communications Manager (CallManager)

Installing Cisco CallManager Release 3.3(4)

 Feedback

Table Of Contents

Installing Cisco CallManager Release 3.3(4)

Purpose of the Document

Conventions

Locating Related Cisco CallManager Documentation

Contents

Frequently Asked Questions About the Cisco CallManager Installation

How long does it take to perform the Cisco CallManager installation?

How does the Cisco CallManager installation work?

May I install other software besides Cisco CallManager on the server?

May I run a web browser on the server?

May I configure a server in the cluster as a Domain Controller?

What if I encounter problems during the installation?

What preinstallation tasks should I perform?

How do I remove the servers from a domain and join a workgroup?

How do I connect the server to the network?

Performing the Cisco CallManager Release 3.3 Installation

Installing Cisco CallManager on the Publisher Database Server

Installing Cisco CallManager on Subscriber Database Server(s)

Installing Cisco CallManager on the ICS 7750

Install the Cisco CallManager Service Release (when available on cisco.com)

Performing Postinstallation Tasks

Activating Cisco CallManager Services

Configuring DNS

Configuring the Database

Downloading Service Releases and Hotfixes for Ongoing System Management

Viewing the Component Versions That Are Installed on the Server

Configuring Servers with Four Disk Drives to Collect Trace Files

Using the Cisco CallManager Music On Hold Disk or Download

Adding New Subscriber Servers to the Cluster After the Installation

Replacing the Publisher Database Server After the Installation

Verifying and Reinitializing Subscriber Connections

Error Messages

Resolving Name Resolution Failures

Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Installing Cisco CallManager Release 3.3(4)


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.

Use this document in conjunction with documents that are listed in the "Locating Related Cisco CallManager Documentation" section.

Conventions

Consider the following documentation conventions as you review this installation 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.


Timesaver Reader, this tip saves you time as you perform the procedure.


(Required)

This convention indicates that you must perform the procedure. Failing to perform the procedure could cause a total system failure or a loss of data and configuration settings.

(Recommended)

This convention indicates that the procedure is strongly recommended, but not required.

Unless otherwise specified, this document uses base server model numbers. For example references to the MCS-7835 apply to servers including the MCS-7835, the MCS-7835-1000, the MCS-7835-1266, the MCS 7835H-2.4, the MCS-7835I-2.4, MCS-7835H-3.0, MCS-7835I-3.0, the customer-provided DL380, and the customer-provided IBM xSeries 342 and 345.

Locating Related Cisco CallManager Documentation

Cisco strongly recommends that you review the following documents before you perform the Cisco CallManager installation:

Release Notes for Cisco CallManager Release 3.3

This document lists and describes the system requirements, new features, changed information, documentation updates, and open caveats for Cisco CallManager. Cisco provides versions of this document that match the version of the installation document.

Installing the Operating System on Cisco IP Telephony Applications Servers, Version 2000.2.4 (or later)

This document, a companion guide to this installation document, provides procedures for the Cisco Media Convergence Server (MCS), customer-provided Compaq DL320/DL380 servers, and customer-provided IBM xSeries 330, 340, 342, and 345 servers.

This document does not provide operating system installation procedures for any other 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), or Cisco Conference Connection.

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 Features and Services Guide

This document describes how to configure features and services for Cisco CallManager, including Cisco Music On Hold, Cisco CallManager Extension Mobility, and so on.

The Cisco CallManager Serviceability System Guide and Cisco CallManager Serviceability Administration Guide

This document provides descriptions of Cisco CallManager serviceability and remote serviceability and step-by-step instructions for configuring alarms, traces, and other reporting.

Bulk Administration Tool User Guide for Cisco CallManager

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.

Cisco IP Telephony Backup and Restore System (BARS) Administration Guide Version 4.0(2) (or later)

This document describes how to install the utility, configure the backup settings, back up Cisco CallManager data, and restore the data.

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 workarounds for applications that are integrated with Cisco CallManager.

Affected applications may include Cisco Conference Connection, Cisco SoftPhone, Cisco uOne, Cisco 186 Analog Telephony Adapter, Cisco Personal Assistant, Cisco 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).

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 on the latest operating system, SQL Server, and security support updates. Information in this document applies to servers that are running the following Cisco IP telephony applications: Cisco CallManager, Conference Connection, Personal Assistant, 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.

To access related information and software, use Table 1, which provides URLs for software, product keys, and documentation.

Table 1 Quick Reference for URLs 

Related Information and Software
URL

Cisco MCS data sheets

http://www.cisco.com/en/US/products/hw/voiceapp/ps378/index.html

Software-only servers (IBM, HP, Compaq, Aquarius)

http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html

Cisco IP Telephony Operating System, SQL Server, Security Updates

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

Operating system installation, Virtual Network Computing (VNC), and Cisco Media Convergence Server (MCS) Network Teaming Driver documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm

Cisco CallManager Compatibility Matrix

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

Cisco CallManager documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

Cisco CallManager backup and restore documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm

Cisco CallManager service releases

http://www.cisco.com/public/sw-center/sw-voice.shtml

See the "Install the Cisco CallManager Service Release (when available on cisco.com)" section.

Related Cisco IP telephony application documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/index.htm

Cisco Integrated Communications System (ICS) 7750

http://www.cisco.com/univercd/cc/td/doc/product/voice/ics/index.htm


Contents

This document contains the following topics:

Preinstallation Tasks and Information

Locating Related Cisco CallManager Documentation

Frequently Asked Questions About the Cisco CallManager Installation

How long does it take to perform the Cisco CallManager installation?

How does the Cisco CallManager installation work?

May I install other software besides Cisco CallManager on the server?

May I run a web browser on the server?

May I configure a server in the cluster as a Domain Controller?

What preinstallation tasks should I perform?

Installation Tasks and Information

Installing Cisco CallManager on the Publisher Database Server

Installing Cisco CallManager on Subscriber Database Server(s)

Installing Cisco CallManager on the ICS 7750

Install the Cisco CallManager Service Release (when available on cisco.com)

Postinstallation Tasks and Information

Performing Postinstallation Tasks

Activating Cisco CallManager Services

Configuring the Database

Downloading Service Releases and Hotfixes for Ongoing System Management

Viewing the Component Versions That Are Installed on the Server

Using the Cisco CallManager Music On Hold Disk or Download

Adding New Subscriber Servers to the Cluster After the Installation

Replacing the Publisher Database Server After the Installation

Verifying and Re-creating Subscription Connections

Verifying and Reinitializing Subscriber Connections

Installation Error Messages

Error Messages

Documentation Resources and Technical Assistance

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Frequently Asked Questions About the Cisco CallManager Installation

Review the following questions and responses before you complete the Cisco CallManager installation.

How long does it take to perform the Cisco CallManager installation?

The entire installation process, excluding pre-/post-installation tasks, takes 45 to 90 minutes per server, depending on your server type. Before you install Cisco CallManager, consider the size of your cluster.

How does the Cisco CallManager installation work?

Review the following information before you install Cisco CallManager.

Verifying the User Name, Organization Name, and Product Key

Cisco supplies you with a Cisco product key when you purchase a Cisco IP telephony product. The product key, based on a file encryption system, allows you to install only the components that you have purchased, and it prevents installation of other supplied software for general use. The product key comprises alphabetical letters only. It contains no numbers or special characters.

During the operating system installation, you entered the Cisco CallManager product key. The product key allows you to install Cisco CallManager on a server that is designated for Cisco CallManager only.

During the operating system installation, you registered the software product by entering a user and organization name.

During the Cisco CallManager installation, verify that the correct User Name, Organization Name, and product key display. See the latest version of the operating system documentation for more information.

Entering Passwords

During the Cisco CallManager installation, you must enter a valid password for the following accounts:

Windows NT 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 this password is the same on all servers in the cluster. If you change the passwords at any time, you must either log off and log in to the server again, or you must reboot the server and log in to the server.



Caution When entering 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

Private Password Phrase


Caution The installation prompts you for a Private Password Phrase. The installation uses the string that you enter to create a unique, encrypted password. You must enter the same phrase on all servers in the cluster.

Installing the Publisher Database or Subscriber Server

When you install Cisco CallManager, you must determine whether the server will be configured as a publishing database server or a subscriber database 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. 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 databases as needed.

Cisco requires that you first install the publisher database server, so authentication to the database occurs. This decision designates a permanent selection. If you want to reassign the database server type at a later date, you must reinstall Cisco CallManager on the server and choose a different database server type.


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 database server to the local drive on the subscriber server. You must supply the name of the publishing database server and the password for the administrator account on that server. If for any reason the publisher server cannot be authenticated during the installation, the installation will not continue.

You must install one server at a time, or the subscriber servers cannot receive copies of the database from the publisher database server.

During the installation, the following software installs:

Microsoft SQL Server 2000

Microsoft SQL Server 2000 Service Pack 3a (or later)

DC Directory

Cisco CallManager

Installing Cisco CallManager Components and Services

The Cisco CallManager installation automatically installs all services that display in the Service Activation window of Cisco CallManager Serviceability. These services install on every server in the cluster. To review a list of installed services, service definitions, and service considerations, refer to the Cisco CallManager Serviceability Administration Guide and the Cisco CallManager Serviceability System Guide.

The Cisco CallManager installation places services in an inactive state until the installation completes. After the installation completes, you must manually activate the service on each server in which you want the service to run. For information on activating services, refer to the Cisco CallManager Serviceability Administration Guide and the Cisco CallManager Serviceability System Guide.

Providing Configuration Information

Table 2 shows the information that is required for installing Cisco CallManager 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. Locate these lists before you begin the installation.

Table 2 Installation Data for Cisco CallManager

Configuration Data
Your Entry

Workgroup name

                                                                      

Database server

Publisher Server Name

Subscriber(s) Server Name(s)

                                                                                 

Administrator password

(same password on every server in the cluster)

                                                                                   

SA (SQL Server system administrator) password

(same password on every server in the cluster)

                                                          

Directory Manager (DC Directory) password

(same password on every server in the cluster)

                                                           

Private Password Phrase for the Cluster

(same phrase on every server in the cluster)

                                                         



Caution If you change any security or account policies from the default, the installation may fail. For more information on security and account policies, refer to Microsoft documentation.

May I install other software besides Cisco CallManager on the server?


Caution Cisco strongly recommends that you do not install any Cisco-verified applications until you complete the installation on every server in the cluster. If you do not know whether the application is approved for installation, do not install it on the server. Installing unsupported software on the server could cause severe performance problems and call-processing interruptions.

Cisco supports a limited list of applications on the Cisco Media Convergence Server (MCS) or Cisco-approved, customer-provided server. Consider the following information before you install Cisco CallManager:

You may install Cisco-verified applications [Cisco AVVID (Architecture for Voice, Video and Integrated Data) Partner Applications], but you must disable and stop these applications before the Cisco CallManager installation and then reboot the server. Disable and stop these applications during installation, restoration, and upgrade procedures.

Installing or using Netscape Navigator on the Cisco MCS or a Cisco-approved, customer-provided server causes severe performance problems. Cisco strongly recommends against installing Netscape Navigator or any other application software on the Cisco MCS or Cisco-approved customer-provided server.

Cisco strongly recommends that you install a security agent to protect your servers against unauthorized intrusion. Cisco offers two security agent options: Cisco Security Agent (CSA) for Cisco CallManager and Management Center for Cisco Security Agent (CSA MC). For more information, see the "Performing Postinstallation Tasks" section.

You may perform a co-resident installation of Cisco CallManager and Cisco Customer Response Solutions (CRS) on the same server. Refer to the CRS installation documentation to obtain the co-resident installation product key.

Do not install Cisco Unity on any server where Cisco CallManager is installed.

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 Cisco-approved customer-provided server. Running a web browser on the server causes CPU usage to surge.

To access Cisco CallManager Administration, which is the web-based graphical user interface (GUI) that allows you to perform Cisco CallManager configuration tasks, use a different PC to browse in to 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?

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?

If you encounter problems during the installation, Cisco recommends that you take the following actions:

1. During the installation if you receive an error message that displays in a dialog box, see the "Error Messages" section and perform the recommended corrective action.

2. On the server where the problem occurred, obtain and review the log file, ccminst <data/time stamp>.log, from C:\Program Files\Common Files\Cisco\Logs.

Be aware that not all error messages that display in the log file are catastrophic. MSI 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 that you must complete before the installation, see Table 3.

Table 3 Preinstallation Tasks 

Step
Preinstallation Tasks
Important Notes

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

Determine whether each server will act as a dedicated or co-resident 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. 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 distributed system, refer to the Cisco CallManager System Guide.

If you are installing a dedicated server, locate the Cisco CallManager product key in this document. If you are installing Cisco CallManager on a co-resident server, refer to the specific Cisco IP telephony application installation documentation for the co-resident product key.

Step 2 

This task applies for reinstallations.

Configure the server to the state of the original configuration.

If you have hot-swappable drives, make sure that you inserted the appropriate drives into the server and ensure that the drives are functional. Remove any additional hard drives that are in the server.

Step 3 

Make sure that you installed the operating system version 2000.2.3 (or later) on all dedicated and coresident servers.

If you are installing Cisco CallManager on the Cisco MCS, refer to Installing the Operating System on the Cisco Media Convergence Server. To obtain the most recent version of this document, go to Table 1.


Caution Cisco strongly recommends that you do not install any operating system service release until you install Cisco CallManager on every server in the cluster.

Step 4 

If you installed operating system version 2000.2.3 or 2000.2.4, use Cisco IP Telephony Server Operating System OS/BIOS Upgrade Disk that came with the software kit or the OS upgrade file from the web to upgrade the operating system to version 2000.2.5 or later.

Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site at Table 1.

Step 5 

Download and install the latest Cisco IP Telephony Server Operating System service release (2000-2-5sr2 or later).

The operating system service releases post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.

For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, go to Table 1.

Step 6 

Before you install Cisco CallManager, make sure that you removed all servers from a NT or an Active Directory Domain.

See the "How do I remove the servers from a domain and join a workgroup?" section.

Step 7 

Connect the server(s) to the network.

See the "How do I connect the server to the network?" section.

Step 8 

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.

Step 9 

About Disabling Cisco-verified Applications

This step applies if you need to reinstall Cisco CallManager.

If you have Cisco-verified applications (Cisco AVVID Partner Applications) or platform agents that are installed on the server, you must disable and stop the services.

The following applications/platform agents may interfere with the Cisco CallManager installation:

Antivirus services

Intrusion detection services

NetIQ services

OEM server agents

Server management agents

VOIP monitoring/performance monitoring

Remote access/remote management agents

About Disabling McAfee Antivirus Services

Before you perform Cisco CallManager installation procedures, you must disable and stop all Cisco-approved McAfee antivirus services. You can enable all antivirus services after you complete the procedures.

Cisco strongly recommends that you do not install any Cisco-verified applications until you have completed the installation on every server in the cluster.


Caution Reboot the server after you disable and stop these applications. Do not start the applications until you complete the Cisco CallManager installation on every server in the cluster. Before you start the installation, verify that none of the services is running.

Step 10 

Locate Table 2, which provides specific information that you need to install Cisco CallManager.

See Table 2.


How do I remove the servers from a domain and join a workgroup?

Convert any servers that exist in the NT Domain or Microsoft Active Directory Domain by performing the following procedure:

Procedure


Step 1 Choose Start > Settings > Control Panel > System.

Step 2 Click the Network Identification tab.

Step 3 Click the Properties button.

Step 4 Click the Workgroup radio button and enter a name, for example, WRKGRP, in the corresponding field.

Step 5 Click OK.

Step 6 When prompted to do so, reboot the server.

Step 7 Log in using the Administrator password.

Step 8 Perform this procedure on every server in the cluster that exists in the NT Domain.

Step 9 Go to the Domain Controller and remove the computer accounts for the Cisco CallManager servers in the cluster.


How do I connect the server to the network?

Before you begin the installation, make sure that you connect your server to the network.

The servers in Table 4 contain two network interface cards (NIC), but the Cisco IP telephony application supports only one NIC. When you connect the server to the network, use the NIC connector that is listed in Table 4 because the other NIC is automatically disabled during the installation.


Note You can implement NIC teaming on servers that support the network teaming driver. For information, refer to the Installing the Cisco Media Convergence Server Network Teaming Driver at http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/driver/hp_team.htm.


Table 4 Connecting to the Network

Server
NIC Connector

MCS-7825

Use the lower NIC connector.

MCS-7835-1266 and MCS-7845-1400

Use the NIC 1 connector.

IBM xSeries 330 server

Use the upper NIC connector.


Performing the Cisco CallManager Release 3.3 Installation

See the following procedures to complete the Cisco CallManager installation:

Installing Cisco CallManager on the Publisher Database Server

Installing Cisco CallManager on Subscriber Database Server(s)

Install the Cisco CallManager Service Release (when available on cisco.com)

Installing Cisco CallManager on the Publisher Database Server

Item Needed: Cisco CallManager Installation and Recovery Disk

For the publisher database server, the installation takes 45 to 90 minutes, depending on the server type. Use the following procedure to perform the installation.


Note For instructions on installing Cisco CallManager on the ICS 7750, see the "Installing Cisco CallManager on the ICS 7750" section.



Caution The installation procedure prompts you to remove the Cisco CallManager Installation and Recovery Disk. Do not remove the disk unless the installation procedure directs you to do so.

Procedure


Step 1 After you install the operating system and log in to the server by using the Administrator account and password, obtain the Cisco CallManager Installation and Recovery Disk and insert it into the drive when you are prompted to do so.

Step 2 To acknowledge that you disabled and stopped or uninstalled all Cisco-verified applications, click Yes.

Step 3 When the Resuming the InstallWizared window displays, click Next.

Step 4 Accept the Cisco CallManager license agreement by clicking the I accept the terms in the license agreement radio button; then, click Next.

Step 5 In the Customer Information window, the User Name and Organization that you entered during the operating system installation automatically display.

Cisco automatically populates the product (CD) key fields with the product key that you entered during the operating system installation. Click Next.

Step 6 In the Setup Type window, the Complete button is chosen; click Next.

Step 7 Cisco requires that you install Cisco CallManager on the publisher database server first, so authentication can occur between the publisher database and subscriber servers.

In the Server Type window, the Publisher is chosen; click Next.


Note The publisher database server 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 server. 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 server 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 database server before you try to authenticate to it. If you are using Domain Name System (DNS), use a fully qualified domain name (for example, `hostname.cisco.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.



Caution When entering 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.

Step 8 In the Administrator password window, enter your Windows administrative password. Click Next.

Step 9 Enter the Private Password Phrase for the cluster; confirm the password and click Next.

The private password phrase contains 1 to 15 characters. This phrase may contain English lower-case letters, English upper-case letters, westernized Arabic numerals, and the following non-alphanumeric special characters: { } . < > : ? / | \ ` ~ ! @ $ ^ & * ( ) _ - +.

Step 10 In the SQL Password window, perform the following procedure:

a. Enter the SA (SQL Server system administrator) password.

b. Press the Tab key.

c. To confirm the password, enter the password again; then, click Next.

Step 11 In the Cisco Directory Password window, perform the following procedure:

a. Enter the Directory Manager password.

b. Press the Tab key.

c. To confirm the password, enter the password again; then, click Next.

Step 12 Now that the Cisco CallManager and other included software are ready to be installed, click Install. This part of the installation takes about 30 to 45 minutes, depending on your server type.

The status bar in the window indicates the progression of the installation. Microsoft SQL Server 2000, Microsoft SQL Server 2000 Service Pack 3a (or later), DC Directory, and Cisco CallManager install. Continue to wait while the installation completes.

Step 13 When the Cisco CallManager installation completes, click Finish to exit the wizard.

The restart server dialog box displays.

Step 14 To restart the server, click Yes.

Step 15 After the server reboots, remove the disk from the drive.

Step 16 Log in to the server by using the Administrator password.

Step 17 If you are not installing Cisco CallManager on the subscriber server(s), go to "Performing Postinstallation Tasks" section.


Installing Cisco CallManager on Subscriber Database Server(s)

Item Needed: Cisco CallManager Installation and Recovery Disk

After you install Cisco CallManager on the publisher database server, you install the application on the subscriber database servers. For each subscriber database server, the installation takes 45 to 90 minutes, depending on the server type.


Caution Perform the installation on one server at a time. This process ensures that the subscriber server(s) can receive a copy of the database from the publisher database server.


Caution The installation procedure prompts you to remove the Cisco CallManager Installation and Recovery Disk. Do not remove the disk unless the installation procedure directs you to do so.

Procedure


Step 1 After you install the operating system and log in to the server by using the Administrator account and password, obtain the Cisco CallManager Installation and Recovery Disk and insert it into the drive when you are prompted to do so.

The installation preparation takes approximately 10 minutes to complete.

Step 2 To acknowledge that you disabled/uninstalled all Cisco-verified applications, click Yes.

Step 3 When the Resuming the InstallWizard window displays, click Next.

Step 4 Accept the Cisco CallManager license agreement by clicking the I accept the terms in the license agreement radio button; then, click Next.

Step 5 In the Customer Information window, the User Name and Organization that you entered during the operating system installation automatically display.

Cisco automatically populates the product key fields with the product key that you entered during the operating system installation. Click Next.


Note The publisher database server functions 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 server. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server, so the installation can continue. The installation process necessitates this connection, so the publisher database server 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 database server before you try to authenticate to it. If you are using Domain Name System (DNS), use a fully qualified domain name (for example, `hostname.cisco.com') with the ping command. In the status of the ping command, verify that the IP address that is displayed is the IP address of the publisher database server. If the ping command is not successful, you can also try to access the publisher database server from all subscriber servers by choosing Start > Run, entering \\<Publisher Server Name>\C$, and then by clicking OK. You do not need to enter a user name and password. Mapping to the drive without entering a user name and password ensures that the passwords on the publisher and subscriber servers match. If the subscriber database server cannot access the publisher server, you must exit the installation program, fix the problem, and begin the installation process again on the subscriber server.


Step 6 The Complete radio button is chosen; click Next.

Step 7 In the Server Type window, perform the following procedure:

a. Click the Subscriber radio button.

b. Enter the computer name of the publisher database server.


Caution If you enter the IP address or fully qualified DNS of the publisher database server, the installation fails.

c. Click Next.


Caution When entering 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.

Step 8 In the Administrator password window, enter the local Windows administrator password.

This password must match the Windows administrator password that is used on the publisher database server.

Click Next.

Step 9 Enter the Private Password Phrase for the cluster; confirm the phrase, and click Next.

The private password phrase contains 1 to 15 characters. This phrase may contain English lower-case letters, English upper-case letters, westernized Arabic numerals, and the following non-alphanumeric special characters: { } . < > : ? / | \ ` ~ ! @ $ ^ & * ( ) _ - +.

This private password phrase must match the Private Password Phrase that you entered on the publisher database server.

Step 10 In the SQL Password window, perform the following procedure:

a. Enter the SA (SQL Server system administrator) password.

This password must match the SA password that is used on the publisher database server.

b. Press the Tab key.

c. To confirm the password, enter the password again; then, click Next.

Step 11 Now that the Cisco CallManager and other included software are ready to be installed, click Install. This part of the installation takes about 30 to 45 minutes, depending on your server type.

The status bar in the window indicates the progression of the installation. Microsoft SQL Server 2000, Microsoft SQL Server 2000 Service Pack 3a (or later), DC Directory, and Cisco CallManager install. Continue to wait while the installation completes.

Step 12 When the Cisco CallManager installation completes, click Finish to exit the wizard.

Step 13 To restart the server, click Yes.

Step 14 After the server reboots, remove the disk from the drive.

Step 15 Log in using the Administrator account and password.

Step 16 After you install Cisco CallManager on all subscriber server(s), go to the "Performing Postinstallation Tasks" section.


Installing Cisco CallManager on the ICS 7750

This section describes the procedure for installing Cisco CallManager on the ICS 7750. For detailed instructions on performing system software tasks on the Cisco ICS 7750, refer to Installing System Software Release 2.6.0 and Cisco CallManager Release 3.3(x) on the Cisco ICS 7750. To obtain the most recent version of this document, see Table 1.


Step 1 Install ICS System Software 2.6.2 by using one of the following methods:

Use the Cisco ICS 7750 System Software CD-ROM for Release 2.6.2 (or later).

Install system software release 2.6.0 and upgrade to system software release 2.6.2 (or later) by using one of the following methods:

Use the Cisco ICS 7750 System Software CD-ROM for Release 2.6.2 (or later)

To download the release, click http://www.cisco.com/public/sw-center/sw-voice.shtml and navigate to the Cisco ICS software site. Download the upgrade file, S77a-Upgrade-<version>.exe; for example, S77a-Upgrade-2.6.2.exe (or later).

Step 2 If you have not already done so, upgrade the SPE to Cisco-provided operating system 2000.2.5 (or later) by downloading the operating system web file that is available on the cryptographic website. To obtain the most recent version of the operating system upgrade readme documentation, see Table 1.


Note After you install ICS System Software release 2.6.2, the operating system version on the SPE310 is 2000.2.3. The operating system upgrade readme instructs you to run either stiVer.exe or MCSver.exe to verify the current operating system level. You do not need this step on the ICS 7750 after you install ICS System Software version 2.6.2.


Step 3 Install Cisco CallManager 3.3(4) on the Cisco ICS 7750. For more information, see the "Performing the Cisco CallManager Release 3.3 Installation" section.

Step 4 Install the latest operating service release (2000.2.5sr2 or later).

Step 5 Install appropriate Microsoft SQL Server 2000 service packs and OS upgrades, as specfied in http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/osbios.htm.

Step 6 Install the latest Cisco CallManager service release. For more information, "Install the Cisco CallManager Service Release (when available on cisco.com)" section.

Step 7 Install the latest Microsoft patches and hotfixes.

Refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, see Table 1.


Install the Cisco CallManager Service Release (when available on cisco.com)

After you install this version of Cisco CallManager on all servers in the cluster, Cisco strongly recommends that you install the latest Cisco CallManager service release on all servers in the cluster. These service releases provide additional bug fixes for your system.

Be aware that Cisco CallManager service releases are cumulative. Cisco rolls bug fixes into the next Cisco CallManager release.


Tip Make sure that you install the same version of the service release on every server in the cluster.


To obtain the latest Cisco CallManager service release, perform the following procedure:

Procedure


Step 1 Click http://www.cisco.com/public/sw-center/sw-voice.shtml.

Step 2 Click Cisco CallManager Version 3.3.

The Cisco CallManager 3.3 software site displays.

Step 3 Locate and download the readme document for the service release.

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 service release on every server in the cluster where Cisco CallManager is installed.

Step 5 Perform other postinstallation tasks.


Performing Postinstallation Tasks

After installing 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. Perform these tasks for each server that you install and complete them before or after the other servers in the cluster are installed.

For post-installation tasks that you must complete after the installation, see Table 5.

Table 5 Postinstallation Tasks 

Postinstallation Tasks
Important Notes

Activate Cisco CallManager services that you want to run on each server in the cluster.


Caution Do not activate Cisco CallManager services in the Microsoft Services window or the Microsoft Computer Management window. You must activate Cisco CallManager services in Cisco CallManager Serviceability.

Refer to the following documents:

Cisco CallManager Serviceability Administration Guide

Cisco CallManager Serviceability System Guide

See the "Activating Cisco CallManager Services" section.

Configure DNS.

See the "Configuring DNS" section.

Configure the database.

See the "Configuring the Database" section.

To manage your system, install the backup utility that is available on the web and configure the backup settings.

Remember to back up your Cisco CallManager data daily.

Refer to Cisco IP Telephony Backup and Restore System (BARS) Administration Guide Version 4.0(2) (or later). To obtain the most recent version of this document, see Table 1.

To manage your system, install the latest service release and hotfixes that are available on CCO.

View the components that are installed on the server.

See the following sections:

Downloading Service Releases and Hotfixes for Ongoing System Management

Viewing the Component Versions That Are Installed on the Server

If you want to do so, you can configure the trace drive for trace file collection on servers with four drives.

See the "Configuring Servers with Four Disk Drives to Collect Trace Files" section.

Install additional Music on Hold selections via disk or the web.

See the "Viewing the Component Versions That Are Installed on the Server" section.

If you want to do so, install and configure Cisco Customer Response Solutions (CRS) on the server.

Refer to the compatible CRS installation documentation.

The locale, English_United_States, installs automatically on the server. To upgrade existing locales or to add new locales to the server, install the Cisco IP Telephony Locale Installer.

Click the following URL to obtain the locale and the installer documentation:

http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr-locale-33

If necessary, you can add a subscriber server to the cluster after the installation.

See the "Adding New Subscriber Servers to the Cluster After the Installation" section.

If necessary, you can replace the publisher database server.

See the "Replacing the Publisher Database Server After the Installation" section.


Activating Cisco CallManager Services

Even though all Cisco CallManager services install on each server in the cluster, you must manually activate the services that you want to run on each server in the cluster.


Caution Do not start and stop Cisco CallManager services through the Microsoft Computer Management window or the Microsoft Services window. Starting and stopping Cisco CallManager services through these windows cause problems with the Cisco CallManager database.

You must activate Cisco CallManager services through Cisco CallManager Serviceability. For service recommendations and more information, refer to Cisco CallManager Serviceability Administration Guide and Cisco CallManager Serviceability System Guide.

Configuring DNS

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. If you need more information on domain naming conventions, refer to Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of this document, see Table 1.

To configure DNS after installing Cisco CallManager, perform the following steps:

Procedure


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.


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. In Cisco CallManager Serviceability, activate the services that you want to run on each server in the cluster.

2. Configure system-level settings, such as Cisco CallManager Groups.

3. Design and configure your dialing plan.

4. Configure media resources for conferences, music on hold, and so on.

5. Install and configure your chosen voice-messaging system.

6. Configure system-wide features, Cisco IP Phone services, Cisco CallManager Extension Mobility, Cisco CallManager Attendant Console, and Cisco IP Manager Assistant.

7. Install and configure the gateways.

8. Enable computer telephony integration (CTI) application support; then, install and configure the desired CTI applications.

9. 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 the Cisco CallManager application.

Downloading Service Releases and Hotfixes for Ongoing System Management

For ongoing management, perform the following tasks:

Verify that you have installed the latest Microsoft patches and hotfixes (About Microsoft Patches and Hotfixes).

Verify that you have installed the latest Cisco CallManager service release (About Cisco CallManager Service Releases).

About Microsoft Patches and Hotfixes

Refer to Installing the Operating System on the Cisco IP Telephony Applications Server for more information. To obtain this document, see Table 1.

About Cisco CallManager Service Releases

See "Install the Cisco CallManager Service Release (when available on cisco.com)" section.

Viewing the Component Versions That Are Installed on the Server

The mcsver.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, 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 by 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:

Procedure


Step 1 Use Windows Explorer to browse to the following folder:

C:\utils\mcsver

Step 2 View the versions of the components that are running on your server.


Configuring Servers with Four Disk Drives to Collect Trace Files

To increase system performance, you can configure service parameters and trace output settings, so that trace files write to the drive labeled "Trace" instead of the default C: drive. Using the trace drive allows you to capture more trace files because this drive is set up specifically for trace file collection.

Perform the following procedure for all servers in the cluster with four disk drives:

Procedure


Step 1 Determine which drive is labeled "Trace" by double-clicking My Computer.

Step 2 In Cisco CallManager Administration, choose Application > Cisco CallManager Serviceability.

The Cisco CallManager Serviceability window displays.

Step 3 Choose Trace > Configuration.

Step 4 From the Server pane on the left side of the Trace Configuration window, click the server name or IP address of the four-disk drive server.

Step 5 Click the Cisco CallManager service.

The Trace Configuration window for the service and server displays.

Step 6 In the upper, right corner of the window, click the SDL Configuration link.

Step 7 In the Trace Directory Path field under Trace Output Settings, change the default from the C: drive to the drive letter of the trace drive.

Step 8 Click Update.

Step 9 Perform this procedure on all servers with four disk drives in the cluster.


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 two files via the web:

ciscocm-MusicOnHold, which is a set of wav files that provides the entire music selection from the disk

ciscocm-MusicOnHoldSampler, which is a small set of files that offers a sample of music that is 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 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:


Caution If you changed any NT Service passwords on the servers in the cluster, you must use the password utility to reset the passwords to the default by using the Admin Utility. The installation fails if you do not perform this task.

1. Install the operating system on the subscriber server(s) by using the Cisco-provided operating system disks and the operating system documentation.

2. Verify that you configured name resolution, for example, DNS, before you install Cisco CallManager.

3. 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 correctly, so authentication to the publisher database server can occur.

4. Upgrade to the version of Cisco CallManager that currently runs in the cluster.

5. Install the same Cisco CallManager service release and operating system hotfixes/service patch that you have applied to the existing cluster.

Replacing the Publisher Database Server After the Installation

To replace an existing server, perform the following steps:

1. If you are replacing a server with four drives, Cisco recommends that you set the trace directory path on the server to the default C: drive before you backup your server.

2. Install the operating system and the Cisco CallManager software on the replacement server as if it were a new installation by using the Cisco-provided operating system disks and the operating system documentation.

3. Upgrade to the version of the Cisco CallManager that you want to restore.

4. If necessary, reinstall the Cisco IP telephony applications, plugins, and service releases to the version that is compatible with the backed up version of Cisco CallManager.

5. To obtain the locales that were used prior to the restoration, reinstall the Cisco IP Telephony Locale Installer.

6. Restore the backup data to the new server and reboot the server.

To restore the data, you must have backup data stored on tape or on a network directory, not on the local directory of the existing or failed server.

7. Verify that the data was restored to the new server.

8. If your server has four drives, you can configure the trace drive for trace file collection.

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 copy 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.

Procedure


Step 1 Open SQL Server Enterprise Manager by choosing Start > Programs > Microsoft SQL Server 2000 > 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).

Error Messages

The following error messages may display in dialog boxes (not the log file) during the installation. You can obtain and review the log file, ccminst <data/time stamp>.log, from C:\Program Files\Common Files\Cisco\Logs.

Table 6 Installation Error Messages 

Error Message
Reason
Corrective Action

You must provide the Computer Name of the publisher server. IP addresses or fully qualified DNS names are not allowed.

You must not enter periods (.) when you enter the publisher database server name.

Reenter the information correctly.

You must provide the publisher server name when installing a subscriber.

This error message displays when you install Cisco CallManager on the subscriber server and do not provide the publisher database server name.

Reenter the information correctly.

You have entered an invalid product key. Please re-enter the key.

You entered an invalid product key.

See the Cisco CRS installation documentation to obtain the Cisco CRS product keys. See this document for the Cisco CallManager product key.

You must enter a password.

This message displays when you do not enter a password, but the application requires a password for the installation to occur.

Enter the correct password.

The passwords that you entered do not match.

This error message displays when you enter a password more than one time, but the password that you enter does not match the password on the server.

Enter the same password on all servers in the cluster.

The password that you entered is not valid.

You entered an invalid password.

Enter the correct password.

You must enter a phrase from 1 to 15 characters in length. This phrase may contain English lower-case letters, English upper-case letters, Westernized Arabic Numerals, and the following Non-alphanumeric "special characters" { } . < > : ? / | \ ` ~ ! @ $ ^ & * ( ) _ - +

You entered invalid characters for the private password phrase.

Enter valid characters.

Pending file operations are occurring. Reboot the server and then install Cisco CallManager.

Pending file operations are occurring.

Reboot the server and then install Cisco CallManager.

You are not logged on as `Administrator'. You must log in by using local Administrator user name and password to install Cisco CallManager.

You did not log in to the server with the local Administrator user name and password.

Log in to the server with the local Administrator user name and password.

Windows 2000 Server is not installed. Install Windows 2000 Server before you install Cisco CallManager.

You did not install the appropriate version of the operating system.

Make sure that you installed the operating system version 2000.2.3 (or later) on all dedicated and coresident servers. Upgrade to 2000.2.5 (or later) and install the latest service release (2000-2-5sr2 or later) before installing Cisco CallManager.

Windows 2000 Service Pack 3 or later is not installed. You must have Windows 2000 Service Pack 3 or later installed before you install Cisco CallManager.

You did not install the appropriate version of the operating system.

Make sure that you installed the operating system version 2000.2.3 (or later) on all dedicated and coresident servers. Upgrade to 2000.2.5 (or later) and install the latest service release (2000-2-5sr2 or later) before installing Cisco CallManager.

You must install CallManager by double clicking CCMSetup.exe.

You tried to install Cisco CallManager by double clicking the msi file that is part of the Cisco CallManager package.

Double-click the CCMSetup.exe.

You must apply SQL 2000 Service Pack 3 (or later) before proceeding with this installation.

You did not install Microsoft SQL 2000 Service Pack 3.

Install Microsoft SQL 2000 Service Pack 3, and perform the Cisco CallManager upgrade.

You do not have administrator privileges. You must have administrator privileges to install Cisco CallManager.

You do not have administrative privileges.

Log in to the server with an account that has administrative privileges.

If you have installed intrusion detection or anti-virus protection software, you must stop and disable these applications from the Services Control console before you continue with the Cisco CallManager installation. All other installed third-party applications must be uninstalled before proceeding with the Cisco CallManager installation. Failure to follow these directives could result in un-recoverable errors. Would you like to proceed?

This message always displays to alert the administrator of the requirements.

If you have Cisco-verified applications (Cisco AVVID Partner Applications) or platform agents that are installed on the server, you must disable/uninstall them and stop the services.

Because the <BUILDVERSION> of this Cisco CallManager MSI package is not compatible with the Cisco CallManager setup file (ccmsetup.exe), make sure that you are using the ccmsetup.exe that was distributed with this version of Cisco CallManager. The installation will now abort.

The MSI package is not compatible with the Cisco CallManager setup file.

Use the ccmsetup.exe file that was distributed with this version of Cisco CallManager.

The Same System Recovery flag was detected. Same Server Recovery is required for upgrades from Cisco CallManager 3.1 or 3.2 to Cisco CallManager 3.3. Are you upgrading a Cisco CallManager 3.1 or 3.2 publisher database server to Cisco CallManager 3.3?

You chose the same server recovery option when you installed the operating system.

If you are upgrading from Cisco CallManager 3.1 or 3.2 to Cisco CallManager 3.3(4), refer to the Upgrading Cisco CallManager document for that release.

If you are installing Cisco CallManager on a publisher server for the first time, click No and continue with the installation.

If you are installing Cisco CallManager on a subscriber server for the first time, click No and continue with the installation.

Note If you click Yes, the installation program configures your server as a publisher.

The installation has detected that the server exists in a domain. When a server exists in a domain, authentication between servers may fail or the non-default domain security policies may be too restrictive for the Cisco CallManager installation to build critical NT Accounts during an upgrade. Failure to remove the server from the domain and add to a workgroup may cause upgrade errors, upgrade failures, or a total system failure, which includes a loss of data and a complete reinstallation of Cisco CallManager. Would you like to proceed?

The server exists in a domain.

Before you continue the installation, Cisco strongly recommends that you remove all servers in the cluster from the domain.

This release of Cisco CallManager is not supported on this server model. The installation will now abort.

You cannot install this version of Cisco CallManager on this server.

Refer to the Cisco CallManager Compatibility Matrix for a list of servers on which you can install this version of Cisco CallManager. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm.

The installation program does not have enough disk space on the C drive to complete the installation. The installation program requires that you have 3.0 gigabytes of disk space available on your server. Make at least 3.0 gigabytes of disk space available and restart the installation.

You do not have enough disk space on the C drive of your server to install Cisco CallManager.

Make enough disk space available on the C drive and restart the installation.

This package is for upgrades of existing Cisco CallManager installations only.

You attempted to use the Cisco CallManager web download file to install Cisco CallManager.

Use the disks that came with the software kit to install Cisco CallManager

A newer version of Cisco CallManager is already installed.

This message displays when you attempt to install a previous version of Cisco CallManager after a successful installation of a later version.

Remove the disk from the drive.

Cisco CallManager install did not complete successfully. Review the log file for more information.

The Cisco CallManager installation failed.

Obtain and examine the log file.

Unable to locate MSI package associated with this bootstrapper.

You did not copy all the files that came with the Cisco CallManager installation package to the server.

Copy the complete installation package to the server and rerun the Cisco CallManager installation.

Error opening MSI package

Cisco CallManager Setup cannot find the MSI package.

This message displays if you encounter a media problem; insert the disk again.

This package has already been installed.

This message displays when you attempt to install the same version of Cisco CallManager again after a successful installation.

Remove the disk from the drive.

An unexpected error occurred.

An error occurred during the Cisco CallManager Setup.

Obtain and examine the log file.

An unexpected error occurred while creating the log directory.

The installation could not create the log file directory.

Verify that security policies on the server are not restrictive.

The local security policy "Restrict CD-ROM access to locally logged-on user only" is enabled. This setting interferes with the Cisco CallManager installation. Please disable this setting using the Local Security Policy utility, reboot, and rerun the Cisco CallManager installation.

The "Restrict CD-ROM access to locally logged-on user only" local security policy is enabled on your server.

Disable this setting by using the Local Security Policy utility, reboot, and rerun the Cisco CallManager installation.

For more information, see the "Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy" section.

Failure occurred trying to get DBNAME value from registry. Aborting Cisco CallManager installation.

The installation could not read DBNAME value from registry on the local machine.

Reboot the server and rerun the Cisco CallManager installation.

Failure occurred trying to validate the format of DBNAME value. Aborting Cisco CallManager installation.

The registry contains an invalid format of the DBNAME value. This error only occurs if you have manually modified this value.

Make sure that the DBNAME value is in the format CCM0xxx, where x stands for any digits.

Current OS version does not meet minimum requirements. Aborting Cisco CallManager install.

Cisco CallManager Release 3.3(4) requires Cisco-provided operating system version 2000.2.5 (or later) and the service release 2000-2-5sr2 (or later.)

Refer to Cisco Compatibility Matrix to review which versions are compatible for installation. To access the document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm.

Installing Cisco CallManager using Terminal Services is not allowed. Install will now abort.

Cisco does not support Terminal Services for Cisco CallManager installations, upgrades, or configuration tasks.

Cisco Technical Assistance Center (TAC) uses Terminal Services for remote management and troubleshooting tasks.

If you want to use Virtual Network Computing (VNC), see Table 1 to obtain the most recent version of the documentation.

Failed to launch <name of executable>, aborting install.

The installation attempted to launch the executable, and the launch failed.

Obtain and examine the log file. You may have a media problem.

Failure occurred trying to determine if Cisco Directory install succeeded. Aborting Cisco CallManager install.

The DC Directory installation failed.

Obtain and examine the log file.

The Cisco CallManager installation detected an error while copying files. Stop all platform agents and Cisco-verified applications, and restart the installation. For more information, refer to the Upgrading Cisco CallManager document.

The Cisco CallManager installation failed to copy files to your server.

Stop all platform agents and Cisco-verified applications, and restart the installation. For more information, see the "What preinstallation tasks should I perform?" section.

Failure occurred during the Cisco CallManager installation. Please look at the Cisco CallManager installation log file for details. Aborting Cisco CallManager installation.

The Cisco CallManager installation failed.

Obtain and examine the log file.

The password of [X] does not match the password on the publisher [Y]. For details, review the log file [Z].

The username and/or password of the user installing Cisco CallManager on the subscriber server does not match the username and/or password on the publisher database server.

Make sure that you entered the correct publisher server name and that the username and password on the publisher and subscriber match.

Because no network connectivity exists or you entered the incorrect publisher server name, the installation could not verify the password of [X] against the publisher [Y]. For details, review the log file [Z].

During Subscriber installation, this error occurs if no network connection exists between the subscriber and publisher database servers or you did not enter the correct name of the publisher database server.

Verify the connection between the publisher database server and subscriber server and make sure that you entered the correct publisher database server name.

Either the password of [X] does not match the password on the publisher [Y], or a network connectivity error occurred. For details, review the log file [Z].

One of the following problems occurred:

No network connectivity exists between the publisher database server and the subscriber server.

The username and/or password of the user installing Cisco CallManager on the subscriber server does not match the username and/or password on the publisher database server.

You entered the incorrect publisher database server name.

Do each of the following tasks:

Verify the connection between the publisher database server and subscriber server.

Make sure you installed Cisco CallManager on the publisher database server and subscriber server using the Administrator username and password.

Make sure you entered the correct publisher database server name.

The private password phrase does not match the private password phrase on the publisher [X]. For details, review the log file [Y].

During the subscribe server installation, one of the following problems occurred:

The passwords of the NT service accounts did not match.

You entered the incorrect publisher database server name

You entered a different private password phase on the publisher database server than you did on the subscriber server.

Do each of the following tasks:

Make sure that a trusted connection exists between the subscriber server and the publisher database server.

Make sure that you entered the correct publisher database server.

Make sure you entered the same private password phrase that you entered on the publisher database server.

Either passwords do not match or a network connectivity error occurred.

During the subscriber server installation, one of the following errors occurred:

Network connectivity failed.

You entered NT service account password that does not match the password on the publisher database server.

You did not enter the correct name of the publisher database server.

Do all of the following tasks:

Verify the connection between the subscriber and publisher database servers.

Make sure that you enter the same NT service account password that you entered on the publisher database server.

Make sure that you enter the correct publisher database server name.

The installation failed to verify the Cisco CallManager version that runs on the publisher database server. Cancel the installation, and review the log file at C:\Program Files\ Common Files\Cisco\Logs\ CCMUIInst.log.

During subscriber server installation, this error occurs if no network connection exists between the subscriber and publisher database servers or if you did not enter the correct name of the publisher database server.

Verify the connection between the publisher database server and subscriber database server and make sure that you entered the correct publisher database server name.

The Cisco CallManager version that you are installing on this subscriber does not match the version running on the publisher database server. Cancel the installation and ensure the publisher is upgraded to this Cisco CallManager version before you continue.

You attempted to install a different version of Cisco CallManager on the subscriber database server than you installed on the publisher database server.

Install the same version of Cisco CallManager on the subscriber database server that you installed on the publisher database server.

Indexing directory data did not finish. After you complete the installation, review the log file. C:\dcdsrvr\log\DirInstallValidation.log.

The installation could not determine whether the DC Directory completed the indexing of its data.

Continue with installation. At the end of the installation, reboot the server when prompted to do so. After you reboot the server, bring up the services control and wait for DC Directory Server to have a status of started.

If this is a publisher database server, you can install Cisco CallManager on the subscriber database servers.

If this is a subscriber database server, go to a command window and enter dcdrepcl trigger all. Depending on the number of users that are configured in your system, the service may be in the starting state for a long time before changing to a started state.

The Cisco CallManager installation failed to stop <list of services> service(s). Please reboot the server, manually stop the service(s), and rerun the Cisco CallManager installation program.

The installation program failed to stop the services during installation.

Reboot the server, manually stop the service(s), and rerun the Cisco CallManager installation program.

The installation encountered an unknown error while trying to resolve the Publisher server name [X]. For more information, review the log file CCMInstUI.log.

The name resolution of the publisher server failed.

Verify that you entered the publisher server name correctly. To verify the hosts file, see the "Resolving Name Resolution Failures" section.

The installation could not resolve the Publisher server name [X] to a valid IP address. Verify that you entered the correct publisher server name, and review the log file CCMInstUI.log for more information.

You entered the wrong publisher server name, or the hosts file has the wrong information.

Verify that you entered the publisher server name correctly. To verify the hosts file, see the "Resolving Name Resolution Failures" section.

The installation successfully resolved the Publisher server name [X] to IP address [Y] but could not resolve the IP address back to a host name.

The reverse name resolution of the Cisco CallManager publisher server failed.

Verify that you entered the publisher server name correctly. To verify the hosts file, see the "Resolving Name Resolution Failures" section.

The installation successfully resolved the Publisher server name [X] to IP address [Y] and resolved the IP address back to the host name [Z]. The resolved host name does not match the server name that you entered.

The publisher server name that you entered does not match the server name that the installation program retrieved after completing forward and reverse name resolution.

Verify that you entered the publisher server name correctly. To verify the hosts file, see the "Resolving Name Resolution Failures" section.

Because mapped network drives exist on the server, the installation could not verify the password of [x] against the publisher [y]. Disconnect all the mapped drives, reboot the system, and rerun the installation. For details, review the log file [z].

The installation could not verify that the password on the subscriber server matches the password on the publisher database server.

Disconnect all the mapped drives, reboot the system, and rerun the installation.

Because mapped network drives exist on the server, the installation could not verify the private password phrase against the publisher [y]. Disconnect all the mapped drives, reboot the system, and rerun the installation. For details, review the log file [z].

The installation could not verify that the private password phrase on the subscriber server matches the private password phrase on the publisher database server.

Disconnect all the mapped drives, reboot the system, and rerun the installation.


Resolving Name Resolution Failures

Cisco CallManager requires NetBIOS and IP name resolution. An incorrect WINS (NetBIOS) or DNS (IP) configuration could result in a service outage.

To resolve name resolution failures, consult with your network administrator to confirm NetBIOS and IP name resolution within the entire network, which includes local device IP configurations, local device name resolution (LMHOSTS and HOSTS), network-based name resolution systems (WINS and DNS) and DHCP systems.


Note Cisco recommends that you use either local or network-based name resolution and not both at the same time.



Note If you use local name resolution and you change the IP address of any server, you must update the LMHOSTS and HOSTS files of every affected server within the network accordingly. For the changes to take effect, either reboot each affected server or complete the tasks in Step 4.



Note If you use a network-based name resolution and you change the IP address of any server, you must update the WINS and DNS (including RARP) systems. For the changes to take effect, either reboot each affected server or complete the tasks in Step 4.



Step 1 Obtain the IP address, hostname, and DNS suffix of each server in the cluster by using the ipconfig /all and hostname commands on each server.

Step 2 Populate the hosts files on each server in the cluster with the names and IP addresses of all servers in the cluster. Find the hosts files in c:\winnt\system32\drivers\etc.

The following example illustrates a hosts file where cm1 represents the hostname and mydomain.com represents the default DNS suffix or connection-specific DNS suffix from the ipconfig /all command output.

127.0.0.1 localhost
1.3.5.9 cm1 cm1.mydomain.com
1.2.4.8 cm2 cm2.mydomain.com

Step 3 Populate the lmhosts files on each server in the cluster with the names and IP addresses of all servers in the cluster. Find the lmhosts files in c:\winnt\system32\drivers\etc.

The following example illustrates a lmhosts file where cm1 represents the hostname.

1.3.5.9 cm1 #PRE
1.2.4.8 cm2 #PRE

Step 4 For the changes to take effect, issue the following commands on each server:

ipconfig /flushdns
nbtstat -R


Note Be aware that the letter "R" is case sensitive in the command.


Step 5 Confirm the changes were successfully loaded by performing the following procedures:

a. Examine the output of nbtstat -c

The names of all other servers in the cluster should appear with a life of -1. The names appear multiple times.

The following example represents the output of the nbtstat -c command:

Example 1 NetBIOS Remote Cache Name Table

Name
 
Type
Host Address
Life [sec]

CM2

<03>

UNIQUE

1.3.5.9

-1

CM2

<00>

UNIQUE

1.3.5.9

-1

CM2

<20>

UNIQUE

1.3.5.9

-1

CM1

<03>

UNIQUE

1.2.4.8

-1

CM1

<00>

UNIQUE

1.2.4.8

-1

CM1

<20>

UNIQUE

1.2.4.8

-1


b. Examine the output of ipconfig /displaydns. You should have at least one forward and one reverse entry for every server in the cluster. The following example contains two forward entries and two reverse entries per server.

Forward Entries

cm1.mydomain.com.
------------------------------------------------------
Record Name . . . . . : cm1.mydomain.com
Record Type . . . . . : 1
Time To Live  . . . . : 30682708
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . :
>                     1.2.4.8
cm1.
------------------------------------------------------
Record Name . . . . . : cm1
Record Type . . . . . : 1
Time To Live  . . . . : 30682708
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . :
>                     1.2.4.8

Reverse Entries

8.4.2.1.in-addr.arpa.

------------------------------------------------------

Record Name . . . . . : 8.4.2.1.in-addr.arpa
Record Type . . . . . : 12
Time To Live  . . . . : 30682708
Data Length . . . . . : 4
Section . . . . . . . : Answer
PTR Record  . . . . . :
>                     cm1
Record Name . . . . . : 8.4.2.1.in-addr.arpa
Record Type . . . . . : 12
Time To Live  . . . . : 30682708
Data Length . . . . . : 4
Section . . . . . . . : Answer
PTR Record  . . . . . :
cm1.mydomain.com

Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy

If you receive the error message that the local security policy "Restrict CD-ROM access to locally logged-on user only" is enabled, you must disable the setting, reboot the server, and rerun the Cisco CallManager installation. Use the following procedure to disable the security policy.

Procedure


Step 1 To open the Local Security Policy utility, choose Start > Programs > Administrative Tools > Local Security Policy.

Step 2 Expand the Local Policies folder in the left pane and choose the Security Options folder.

Step 3 In the right pane, choose the Restrict CD-ROM access to locally logged-on user only policy and press Enter.

The Local Security Policy dialog box displays.

Step 4 Choose the Disabled radio button and click OK.

Step 5 Exit the Local Security Policy utility.

Step 6 Reboot the server.

Step 7 Restart the Cisco CallManager installation.


Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco Technical Support Website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco Technical Support Website is available 24 hours a day, 365 days a year. The Cisco Technical Support Website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

http://www.cisco.com/tac/caseopen

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

http://www.cisco.com/go/marketplace/

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html