Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Unified Communications Manager (CallManager)

Installing Cisco CallManager Release 4.1(3)

Downloads

Table Of Contents

Installing Cisco CallManager Release 4.1(3)

Contents

Conventions

Locating Related Cisco CallManager Documentation

Important Considerations

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?

Which servers does Cisco support for this installation?

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

May I run a web browser on the server?

May I add Cisco CallManager servers as members of a Windows domain?

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

May I use Terminal Services, Virtual Network Computing, and Integrated Lights Out to remotely install the application?

What if I encounter problems during the installation?

Performing the Cisco CallManager Release 4.1 Installation

Performing Preinstallation Tasks

Planning your System

Removing the Servers from a Domain and Join a Workgroup

Connecting the Server to the Network

Disabling Third-Party Applications, Antivirus Services, and Security Agents

Gathering Configuration Information

Installing Cisco CallManager on the Publisher Database Server

Installing Cisco CallManager on Subscriber Database Server(s)

Performing Postinstallation Tasks

Activating Cisco CallManager Services

Configuring DNS

Configuring the Database

Downloading Service Releases and Hotfixes for Ongoing System Management

About Microsoft Patches and Hotfixes

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

Viewing the Component Versions That Are Installed on the Server

Installing a Cisco CallManager Security Agent

Using the Cisco CallManager Music On Hold Disk or Download

Reenabling Third-Party Applications, Antivirus Services, and Security Agents

Adding New Subscriber Servers to the Cluster After the Installation

Replacing the Publisher Database Server After the Installation

Requirement for Installation of Java Virtual Machine

JRE Installation

Verifying and Reinitializing Subscriber Connections

Analyzing Error Messages

Installation 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

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Installing Cisco CallManager Release 4.1(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 with Cisco IP Contact Center Express Edition, or Cisco CallManager with Cisco IP Interactive Voice Response on the same server, refer to the Cisco Customer Response Solutions (CRS) installation documentation for the product keys.

This document includes information about installing Cisco CallManager for the first time, and reinstalling Cisco CallManager, if necessary.

This document applies if you have one server or many servers in a cluster environment.

Contents

This document contains the following topics:

Locating Documents and Information

•Locating Related Cisco CallManager Documentation

•Important Considerations

•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?

–Which servers does Cisco support for this installation?

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

–May I run a web browser on the server?

–May I add Cisco CallManager servers as members of a Windows domain?

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

–May I use Terminal Services, Virtual Network Computing, and Integrated Lights Out to remotely install the application?

Installation Tasks and Information

•Performing Preinstallation Tasks

•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)

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

Verifying and Re-creating Subscription Connections

•Verifying and Reinitializing Subscriber Connections

Installation Error Messages

•Analyzing Error Messages

Documentation Resources and Technical Assistance

•Obtaining Documentation

•Obtaining Technical Assistance

Use this document in conjunction with the 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 4.1

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

This document, a companion guide to this installation document, provides information and procedures on 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 Conference Connection, or one of the products from the Cisco Customer Response Solutions (CRS) platform.

•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 Security Guide

This document provides step-by-step instructions on how to configure and troubleshoot authentication and encryption for Cisco CallManager, Cisco IP Phones, SRST references, and Cisco MGCP gateways.

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

Table 1 lists URLs for software, product keys, and other related 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/ccmcomp.htm

Cisco CallManager documentation

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

Cisco CallManager Security Guide

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/sec_vir/a

e/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/kobayashi/sw-center/sw-voice.shtml

Related Cisco IP telephony application documentation

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


Important Considerations

Before you proceed with the Cisco CallManager installation or upgrade, consider the following requirements and recommendations:

•Cisco CallManager requires a minimum of 1GB of memory on the Cisco CallManager servers. To avoid system problems, such as dropped calls, verify that your servers have a minimum of 1 GB of memory installed. If the installation process detects less than 1GB memory on the publisher server, the installation aborts. The installation process performs a similar check on the Cisco CallManager subscriber server; it allows the installation to continue if it detects less than the minimum requirement.

•Install the Cisco CallManager software on the publisher server first and then on the subscriber server(s).

•You cannot add a subscriber server to a cluster by installing a previous version of Cisco CallManager and then upgrading the subscriber server to the same version that is running on the publisher server. If you are adding a new subscriber server or replacing a subscriber server on the cluster, you must use the installation CDs with the same Cisco CallManager version that is running on the publisher server.

•Make sure that you are logged in as the administrator on the server before starting the Cisco CallManager installation.

•Install the Cisco CallManager software on one server at a time to ensure that subscriber servers can receive replicate copies of the database from the publisher database server.

•Make sure that the subscriber server that you are installing can connect to the publishing database server during the installation.

•Do not choose cancel after you start the installation. If you choose cancel, you will need to reimage your machine by reinstalling the operating system.

•Because security settings for the Cisco CallManager server are set up by the installation and upgrade script, do not make any adjustments to these predefined settings, or you may experience a significant impact to the functionality of your server.

•When entering passwords for the local Administrator and SA (SQL Server system administrator) accounts, use alphanumeric characters only.

•Enter the same administrator password on all servers in the cluster.

•Install the Cisco CallManager software during off-peak hours or during a maintenance window to avoid impact from call-processing interruptions.

•Do not implement multiple servers in a Cisco CallManager cluster by using a drive that was mirrored or cloned from a single Cisco CallManager server. This results in servers having duplicate Security ID (SID) and impairs Cisco CallManager operations. You must install the Cisco IP telephony operating system and Cisco CallManager software separately on each server by using the Cisco-provided installation disks.

•Do not configure any server in the cluster as a Domain Controller.

•Place the server in a Workgroup before you install the software.

•Configure the server by using static IP addressing to ensure that the server obtains a fixed IP address and that the Cisco IP Phones can register with the application when you plug the phones into the network.

•Do not attempt to perform any configuration tasks during the installation.

•Do not use terminal services to install the Cisco CallManager software

•Do not install any Cisco-verified applications until you complete installing Cisco CallManager on every server in the cluster.

•Cisco provides support for a limited set of applications on the servers where Cisco CallManager is installed. If you are uncertain whether a third-party application is supported, do not install it on the server.

•You must disable third-party, Cisco-verified applications on your servers before starting the Cisco CallManager installation.

•Install a security agent to protect your servers against unauthorized intrusion.

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

•Installing or using Netscape Navigator on the Cisco MCS or the Cisco-approved, customer-provided server causes severe performance problems.

•Carefully read the instructions that follow before you proceed with the installation. See "Performing Preinstallation Tasks" section,"Performing the Cisco CallManager Release 4.1 Installation" section, and "Performing Postinstallation Tasks" section

Frequently Asked Questions About the Cisco CallManager Installation

The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco CallManager installation.

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

The entire installation process, excluding pre- and 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 other supplied software from being installed for general use. The product key comprises alphabetical letters only.

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 the publisher server cannot be authenticated during the installation for any reason, 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.

Cisco CallManager installs the following software packages:

•Sun Microsystem Java Runtime Environment (JRE)

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

Which servers does Cisco support for this installation?

Refer to the Cisco CallManager Compatibility Matrix for a list of servers that Cisco CallManager 4.1(3) supports. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

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 these applications during installation, restoration, and upgrade procedures.

For more information on supported software, click http://www.cisco.com/pcgi-bin/ecoa/Search. In the Solution pane, click IP Telephony. From the Solution Category drop-down list box, choose Operations, Administration, and Maintenance (OAM). Click Search.

•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 can install Cisco CallManager and Cisco Customer Response Solutions (CRS) on the same server. Refer to the CRS installation documentation to obtain the coresident 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, the web-based graphical user interface (GUI) that allows you to perform Cisco CallManager configuration tasks, use a different PC to 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 https://<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 add Cisco CallManager servers as members of a Windows domain?

Cisco does not recommend adding Cisco CallManager servers as members of a Microsoft Windows domain. However if your system architecture depends on servers joining a Windows domain, then you must disable the Network Time Protocol (NTP) software that is installed by Cisco CallManager when you add the server as a member of a domain and use Microsoft time service. You must disable the NTP service on every server in your cluster.

Note You must install the server as a member of a workgroup during installation of Cisco CallManager.

Note Do not make any modifications to the installed NTP configuration file (NTP.CONF). Modifications to the NTP.CONF file may result in synchronization problems with CDRs, Traces, Event Logging, and so on. Cisco does not support these modifications.

To disable the Cisco-installed NTP software on a server:

Step 1 Choose Start > Programs > Administrative Tools > Services.

Step 2 Double-click the Network Time Protocol service.

Step 3 In the Startup type field, choose Disabled.

Step 4 Click Stop.

Step 5 Click OK

Caution Every time that you upgrade your server, you must remove the server from the Windows Domain prior to installing the upgrade software.

When you complete your upgrade and you are adding the server to the Windows domain, you must disable the Cisco-installed NTP services again.

If you are joining the server to a Microsoft Windows 4.0 domain, you must also perform an additional procedure for synchronizing time. Refer to How to Synchronize the Time on a Windows 2000-Based Computer in a Windows NT 4.0 Domain at http://www.microsoft.com.

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 Cisco CallManager on the server.

May I use Terminal Services, Virtual Network Computing, and Integrated Lights Out to remotely install the application?

Do not use Terminal Services or Integrated Lights Out (ILO) to install Cisco CallManager Release 4.1(3). Cisco installs Terminal Services, so Cisco Technical Assistance Center (TAC) can perform remote administration and troubleshooting tasks. Cisco does not support upgrades through Terminal Services. Cisco supports ILO for remote management and configuration tasks only

Caution Before the upgrade, Cisco strongly recommends that you disable Terminal Services and immediately reboot the server to prevent remote access to the server. Accessing the server via Terminal Services may cause the upgrade to fail.

After you upgrade the server, you must enable Terminal Services.

If you want to use Virtual Network Computing (VNC) to remotely install Cisco CallManager, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm to obtain the latest version of the VNC document.

Caution If you have installed VNC but do not plan to use it to install Cisco CallManager, disable it to prevent remote access to the server. If you do not disable VNC and a user/administrator accesses the server during the installation, the installation will fail.

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 "Analyzing 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 is not used by Cisco CallManager.

Performing the Cisco CallManager Release 4.1 Installation

This section contains information about the procedures that are used to complete the Cisco CallManager installation. The section includes the following topics:

•Performing Preinstallation Tasks

•Installing Cisco CallManager on the Publisher Database Server

•Installing Cisco CallManager on the Publisher Database Server

•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)

Performing Preinstallation Tasks

For preinstallation tasks that you must complete before the installation, see Table 2.

Table 2 Preinstallation Tasks 

Step
Preinstallation Tasks
Important Notes

Step 1 

Plan your system configuration.

Determine how many Cisco CallManager servers the cluster will contain, which server will house the publisher database, and where backup tasks will be performed.

Determine whether each server will act as a dedicated or coresident server.

See "Planning your System" section

Step 2 

This task applies for reinstallation.

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.7 (or later) on all dedicated and coresident servers.

Use the Cisco IP Telephony Server Operating System OS/BIOS Upgrade Disk that came with the software kit and upgrade the operating system to version 2000.2.7 or later.

Refer to Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm.

Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software page. You can navigate to the site from the Cisco CallManager software page at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 4 

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

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

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 http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 5 

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

See the "Removing the Servers from a Domain and Join a Workgroup" section.

Step 6 

Connect the server(s) to the network.

See the "Installing Cisco CallManager on the Publisher Database Server" section.

Step 7 

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.

Refer to the driver documentation by clicking the following URL:

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

Step 8 

This step applies if you need to reinstall Cisco CallManager.

You must disable and stop all third-party, Cisco-verified, and Cisco-provided, coresident applications that are installed on your server.

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.

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

See "Installing Cisco CallManager on the Publisher Database Server" section

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 9 

Close all web browser windows.

If you have an open browser window, Cisco CallManager will reboot the server after the Sun Microsystem JRE package has been installed.

Step 10 

Locate specific information that you need to install Cisco CallManager.

See the "Gathering Configuration Information" section.


Planning your System

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 coresident 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 coresident server, refer to the specific Cisco IP telephony application installation documentation for the coresident product key.

Removing the Servers from a Domain and Join a Workgroup

Perform the following procedure to convert any servers that exist in the NT Domain or Microsoft Active Directory Domain:

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.

Connecting the Server to the Network

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

The servers in Table 3 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 the table 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 3 Connecting to the Network

Server
NIC Connector

MCS-7825

Use the lower NIC connector.

MCS-7835 and MCS-7845

Use the NIC 1 connector.

IBM xSeries 330 server

Use the upper NIC connector.


Disabling Third-Party Applications, Antivirus Services, and Security Agents

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

•Cisco-provided, coresident applications

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 and start all antivirus services after you complete the procedures.

About Disabling Security Agents

Before you perform Cisco CallManager installation procedures, you must disable and stop all security agents, including Cisco Security Agent for Cisco CallManager. You can enable and start the services after the installation.

For Cisco-Verified, Third-Party Applications

To review a list of Cisco-verified applications that you should disable and stop before the installation, click the following URL: http://www.cisco.com/pcgi-bin/ecoa/Search. In the Solution pane, click IP Telephony. From the Solution Category drop-down list box, choose Operations, Administration, and Maintenance (OAM). Click Search.

Use the following procedure to disable third-party applications, antivirus services, or security agents:

Step 1 Choose Start > Programs > Administrative Tools > Services.

Step 2 Locate the third-party application, antivirus service, or security agent that you want to stop, right-click Cisco Security Agent, and choose Properties.

Step 3 In the Properties window, click the General tab.

Step 4 In the Service Status area, click Stop.

Step 5 From the Startup type drop-down list box, choose Disabled.

Step 6 Click OK.

Gathering Configuration Information

Table 4 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.

Table 4 Installation Data for Cisco CallManager

Configuration Data
Your Entry

Workgroup name

                                                                      

Database server

•Publisher Server Name

•Subscriber(s) Server Name(s)

                                                                                 

Administrator password

(Use the same password on every server in the cluster)

                                                                                   

SA (SQL Server system administrator) password

(Use the same password on every server in the cluster)

                                                          

Directory Manager (DC Directory) password

(Use the same password on every server in the cluster)

                                                           

Private Password Phrase for the Cluster

(Use the same phrase on every server in the cluster)

                                                         


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

Installing Cisco CallManager on the Publisher Database Server

Items Needed: Cisco CallManager Installation, Upgrade, and Recovery Disks 1 and 2

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 Critical third-party components that are required and installed by Cisco CallManager may require multiple reboots during installation, and you may need to manually restart the installation program and reenter the configuration data.

Caution Do not remove the Cisco CallManager Installation, Upgrade, and Recovery Disks until 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, Upgrade, and Recovery Disk 1 of 2 and insert it into the drive.

Note Follow the instructions in the dialog box. On most windows, you can choose Next to proceed with the installation. When prompted to enter a password, remember to record your entry.

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

Step 3 To confirm that you may be prompted to reboot the server and reenter configuration data multiple times for Cisco CallManager to install critical third-party components, click OK.

Step 4 The installation program must update the configuration and restart the server. To proceed with installation, click OK.

Note If you click Cancel, Cisco CallManager will not be installed on your server, and the installation program will not make any changes to your system.

The server reboots.

Step 5 Log in to the server by using the Administrator account and password.

Step 6 When the Installation Welcome window displays, click Next.

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

Step 8 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 9 In the Setup Type window, the Complete button is chosen; click Next.

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

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

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 that 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 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 11 In the Administrator password window, enter the local Windows administrator password. Click Next.

Step 12 Enter the Private Password Phrase for the cluster; confirm the private password 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 nonalphanumeric special characters: { } . < > : ? / | \ ` ~ ! @ $ ^ & * ( ) _ - +.

Step 13 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 14 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 15 Now that the Cisco CallManager and other included software are ready to be installed, click Install. The Cisco CallManager installation takes about 30 to 45 minutes, depending on your server type.

Note The progress of the status bar may reset as each software package is being installed and as the installation program configures your machine. You may see the installation program reset the status bar multiple times. Do not reboot the server unless the installation prompts you to do so.

Step 16 When prompted, insert Cisco CallManager Installation, Upgrade, and Recovery Disk 2 of 2 and click OK.

The installation program continues to install files on your server. Continue to wait while the installation completes.

Note Do not use Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2 on another server until you complete the installation process on this server. Before you complete the installation, the installation program prompts you to reinsert Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2.

Step 17 When prompted, insert Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2 again and click OK.

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

The restart server dialog box displays.

Step 19 To restart the server, click Yes.

Note You cannot install Cisco CallManager on a subscriber server until you reboot the publisher server.

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

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

Step 22 If you are installing Cisco CallManager on subscriber server(s), go to "Installing Cisco CallManager on Subscriber Database Server(s)" section. 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)

Note You cannot add a subscriber server to a cluster by installing a previous version of Cisco CallManager and then upgrading the subscriber server to the same version that is running on the publisher server. If you are adding a new subscriber server or replacing a subscriber server on the cluster, you must use the installation CDs with the same Cisco CallManager version that is running on the publisher server.

Note Critical third-party components that are required and installed by Cisco CallManager may require multiple reboots during installation, and you may need to manually restart the installation program and reenter the configuration data.

Items Needed: Cisco CallManager Installation, Upgrade, and Recovery Disks 1 and 2

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 Do not remove the Cisco CallManager Installation, Upgrade, and Recovery Disks until 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, Upgrade, and Recovery Disk 1 of 2 and insert it into the drive.

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

Step 3 To confirm that you might be prompted to reboot the server and re-enter configuration data multiple times in order for Cisco CallManager to install critical third-party components, click OK.

Step 4 The installation program must update the configuration and restart the server. To proceed with installation, click OK.

Note If you click Cancel, Cisco CallManager will not be installed on your server, and the installation program will not make any changes to your system.

The server reboots.

Step 5 Log in to the server by using the Administrator account and password.

Step 6 When the Installation Welcome window displays, click Next.

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

Step 8 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. In the status of the ping command, verify that the IP address 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 9 The Complete radio button is chosen; click Next.

Step 10 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 11 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 12 Enter the Private Password Phrase for the cluster; confirm the private password 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 13 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 14 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.

Note The progress of the status bar may reset as each software package is being installed and as the installation program configures your machine. You may see the installation program reset the status bar multiple times. Do not reboot the server unless the installation prompts you to do so.

Step 15 When prompted, insert Cisco CallManager Installation, Upgrade, and Recovery Disk 2 of 2 and click OK.

The installation program continues to install files on your server. Continue to wait while the installation completes.

Note Do not use Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2 on another server until you complete the installation process on this server. Before you complete the installation, the installation program prompts you to reinsert Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2.

Step 16 When prompted, insert Cisco CallManager Installation, Upgrade, and Recovery Disk 1 of 2 again and click OK.

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

Step 18 To restart the server, Click Yes.

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

Step 20 Log in by using the Administrator account and password.

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

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 Post-installation Tasks 

Post-installation Tasks
Important Notes

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