Guest

Cisco Unified Communications Manager (CallManager)

Upgrading Cisco CallManager Release 3.2(2c)

 Feedback

Table Of Contents

Upgrading Cisco CallManager Release 3.2(2c)

Contents

Conventions

Locating Related Cisco CallManager Documentation

Frequently Asked Questions About the Cisco CallManager Upgrade

From which versions of Cisco CallManager can I upgrade to Cisco CallManager Release 3.2(2c)?

How long does it take to upgrade a cluster?

Which server in the cluster do I upgrade first?

How does the upgrade work?

Will I experience call-processing interruptions and a loss of services during the upgrade?

May I remotely upgrade the cluster?

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

What tasks should I perform before I upgrade the cluster?

What additional information should I know before I upgrade?

What tasks should I perform after the upgrade?

Obtaining Device Default Load Information for Cisco CallManager Release 3.0

Backing Up Your Cisco CallManager System and Preserving Your Hard Drives

Performing the Cisco CallManager Release 3.2 Upgrade

Performing Pre-Upgrade Tasks

Disabling AntiVirus and Intrusion Detection System Services

Upgrading the BIOS and Operating System

Installing the Microsoft SQL Server 7.0 Service Pack

Upgrading Cisco CallManager via CD-ROM or the Web

Performing Post-Upgrade Tasks

Enabling Cisco-Approved McAfee Antivirus Services

Verifying Services, Patches, and Hotfixes

Viewing the Component Versions Installed on the Server

Configuring Cisco MOH Audio Translator and Cisco TFTP

Using the Message Waiting Indicator (MWI)

Synchronizing the Message Waiting Indicator

Using the Cisco CallManager Attendant Console

Using the Cisco CallManager Music On Hold Download

Changing the Password for the SQLSvc Account

Drive Mirroring for the MCS-7830, MCS-7835, and IBM xSeries 340 or 342 Server

Reverting to the Previous Configuration After an Upgrade Attempt

Reverting a 3.2 Cisco Device Load to a 3.0 Cisco Device Load

Reconfiguring the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 Server After an Upgrade Attempt

Reconfiguring the MCS-7830, MCS-7835, or IBM xSeries 340 or 342 Server After an Upgrade Attempt

Reverting the Hard Drive After Drive Mirroring Completes

Reverting Upgraded Cisco IP Telephony Applications After You Revert Cisco CallManager

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Upgrading Cisco CallManager Release 3.2(2c)


This document provides reference and procedural information for upgrading the Cisco CallManager cluster. For more information on Cisco CallManager or for information on Cisco IP telephony applications, see the "Locating Related Cisco CallManager Documentation" section.

Contents

This document contains the following topics:

Pre-Upgrade Tasks

Locating Related Cisco CallManager Documentation

Frequently Asked Questions About the Cisco CallManager Upgrade

From which versions of Cisco CallManager can I upgrade to Cisco CallManager Release 3.2(2c)?

How long does it take to upgrade a cluster?

Which server in the cluster do I upgrade first?

How does the upgrade work?

Will I experience call-processing interruptions and a loss of services during the upgrade?

May I remotely upgrade the cluster?

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

What tasks should I perform before I upgrade the cluster?

What additional information should I know before I upgrade?

What tasks should I perform after the upgrade?

Obtaining Device Default Load Information for Cisco CallManager Release 3.0

Backing Up Your Cisco CallManager System and Preserving Your Hard Drives

Upgrade Tasks

Performing the Cisco CallManager Release 3.2 Upgrade

Upgrading the BIOS and Operating System

Installing the Microsoft SQL Server 7.0 Service Pack

Upgrading Cisco CallManager via CD-ROM or the Web

Post-Upgrade Tasks

Post-Upgrade Tasks

Verifying Services, Patches, and Hotfixes

Verifying Services, Patches, and Hotfixes

Viewing the Component Versions Installed on the Server

Configuring Cisco MOH Audio Translator and Cisco TFTP

Using the Message Waiting Indicator (MWI)

Synchronizing the Message Waiting Indicator

Using the Cisco CallManager Attendant Console

Using the Cisco CallManager Music On Hold Download

Reversion Tasks

Reverting to the Previous Configuration After an Upgrade Attempt

Reverting a 3.2 Cisco Device Load to a 3.0 Cisco Device Load

Reconfiguring the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 Server After an Upgrade Attempt

Reconfiguring the MCS-7830, MCS-7835, or IBM xSeries 340 or 342 Server After an Upgrade Attempt

Reverting the Hard Drive After Drive Mirroring Completes

Reverting Upgraded Cisco IP Telephony Applications After You Revert Cisco CallManager

Documentation Resources and Technical Assistance

Obtaining Documentation

Obtaining Technical Assistance

Conventions

Consider the following documentation conventions as you review this upgrade document:


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.

Locating Related Cisco CallManager Documentation

Cisco strongly recommends that you review the following documents before you upgrade:

Release Notes for Cisco CallManager Release 3.2

Cisco provides versions of this document that match the version of the upgrade document.

Cisco CallManager Compatibility Matrix

To ensure continued functionality with interfacing Cisco IP telephony applications after the Cisco CallManager upgrade, refer to the Cisco CallManager Compatibility Matrix, which provides solutions information and workarounds for applications integrated with Cisco CallManager.

Affected applications may include Cisco Conference Connection, Cisco SoftPhone, Cisco uOne, Cisco 186 Analog Telephony Adaptor, Cisco WebAttendant, Cisco Personal Assistant, Cisco Customer Response Applications (CRA), Telephony Application Programming Interface and Java Telephony Application Programming Interface (TAPI/JTAPI) applications, including Cisco- supported and third-party applications, and Cisco Telephony Service Provider (TSP).

This document provides specific information, including compatibility and upgrading guidelines, for Cisco IP Contact Center (IPCC) systems. If you use Cisco CallManager and related Cisco IP telephony applications in a call-center environment, review this document before you begin any upgrade procedures.

Cisco IP Telephony BIOS and Operating System Version Roadmap

This document provides file tracking and BIOS/operating system compatibility information.

Backing Up and Restoring Cisco CallManager Release 3.2

This document describes how to back up Cisco CallManager data and restore the Cisco IP Telephony Applications Server and Cisco CallManager data.

The appropriate Cisco IP telephony application documentation

Locate the release notes, installation/upgrade, and configuration guides for the applications that you have integrated with Cisco CallManager.

Table 1 Quick Reference for URLs 

Related Information and Software
URL

Related Cisco IP telephony application documentation

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

Cisco IP Telephony BIOS and Operating System Roadmap

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

Cisco CallManager Compatibility Matrix

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

Cisco intrusion detection system (IDS) host sensor documentation

http://www.cisco.com/univercd/cc/td/doc/product/iaabu/csids/host/index.htm

Server hardware specifications

http://www.cisco.com/warp/public/779/largeent/avvid/products/infrastructure.html

Operating system download via the web (for upgrades only) and operating system readme documentation

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

Cisco IP telephony application product keys

http://www.cisco.com/warp/customer/788/AVVID/productkey.html


Frequently Asked Questions About the Cisco CallManager Upgrade

Review the following questions and corresponding responses before you upgrade.

From which versions of Cisco CallManager can I upgrade to Cisco CallManager Release 3.2(2c)?

Cisco supports upgrading to Cisco CallManager Release 3.2(2c), a full version of Cisco CallManager, from Cisco CallManager Releases 3.0(12), 3.1(3a), and 3.2(1). To verify whether other versions of Cisco CallManager are compatible for upgrade, click the following URL to refer to the Cisco CallManager Compatibility Matrix, which provides compatibility information and workarounds for applications that are integrated with Cisco CallManager:

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

If your server runs Cisco CallManager Release 2.4, you must upgrade to the latest version of Cisco CallManager Release 3.0 before you can upgrade to a version of Cisco CallManager Release 3.2.

How long does it take to upgrade a cluster?

Cisco strongly recommends that you perform all upgrade procedures for the Cisco CallManager and Cisco IP telephony applications within a consecutive time period (within one maintenance window) and that you allot adequate time to perform the upgrade. Cisco strongly recommends that you perform the entire upgrade during off-peak hours.

Before you perform an upgrade, consider the time that it takes to perform pre-/post-upgrade tasks and Cisco IP telephony application upgrades.

Many factors, such as the size of the Cisco CallManager or CDR database or the number of Cisco IP telephony applications that are integrated with Cisco CallManager, affect the time that it takes to upgrade the cluster.

Upgrade Consideration: Allotting Time to Upgrade Cisco CallManager

If you have three servers with 900 devices and no call detailed records (CDRs), the upgrade process takes approximately 3 hours to upgrade Cisco CallManager (excluding Cisco IP telephony application upgrades). The size of your Cisco CallManager or CDR database may increase the time that it takes to complete the upgrade process.

Which server in the cluster do I upgrade first?


Caution With Cisco CallManager Release 3.2(2c), the order for upgrading a cluster changed. Cisco recommends that you upgrade the backup servers before you upgrade the primary servers. Review the following information carefully before upgrading the cluster.

You must upgrade all the servers in the cluster. See Table 2, which describes the upgrade order for the following cluster configurations:

The Cisco CallManager service runs on the publisher database server (two server cluster).

The Cisco CallManager service does not run on the publisher database server.

Table 2 Cluster Upgrade Order 

 
The Cisco CallManager Service Runs on the Publisher Database Server.
 
The Cisco CallManager Service Does Not Run on the Publisher Database Server.

Step 1 

Upgrade the publisher database server. The "Performing the Cisco CallManager Release 3.2 Upgrade" section provides the upgrade procedure for all servers.

When you perform an upgrade, the Cisco CallManager service automatically stops, and the devices that are homed to the publisher server fail over to the subscriber server.

 

Upgrade the publisher database server. The "Performing the Cisco CallManager Release 3.2 Upgrade" section provides the upgrade procedure for all servers.

Step 2 

Upgrade the subscriber.

 

Upgrade the Cisco TFTP server, if it exists separately from the publisher database server.

Step 3 

You completed the Cisco CallManager upgrade. Perform post-upgrade tasks.

 

Upgrade servers that have only Cisco CallManager-related applications (Music on Hold, Cisco IP Media Streaming Application, Cisco Customer Response Applications, etc.) running on them.

Make sure that the Cisco CallManager service does not run on these servers.

Upgrade Consideration: Simultaneously Upgrading Backup Servers and Application Servers in the Cluster

If you choose to do so, you can upgrade the backup server(s) and Cisco CallManager-related application servers at the same time. Before you attempt to perform the upgrades, consider the number of people that are needed to complete the tasks.

Step 4 

Not applicable

 

Upgrade the backup servers.

Upgrade Consideration: Oversubscribing the Backup Servers

If you choose to oversubscribe the backup server(s) during the upgrade, Cisco strongly recommends that you have no more than 5,000 devices registered to the backup server during the upgrade and that you oversubscribe the backup server(s) for no more than a few hours. Cisco strongly recommends that you perform the upgrade during off-peak hours when low call volume occurs (less than 1,000 busy hour call attempts).

Upgrade Consideration: Registering All Devices to the Same Version of Cisco CallManager

If you configured your Cisco CallManager cluster by using approved Cisco configuration standards, which include configuring four primary servers and two backup servers in the cluster, you can minimize call-processing interruptions if you register all devices to servers that are running the same version of Cisco CallManager during the entire upgrade process; i.e., you register all devices to the backup Cisco CallManager servers or the primary Cisco CallManager servers, but not to both types of servers.

Step 5 

Not applicable

 

Upgrade the primary servers that have the Cisco CallManager service running on them.


Caution When you upgrade the primary subscriber(s), call-processing interruptions may occur for up to 30 minutes while the devices attempt to obtain the device loads and register to the upgraded version of Cisco CallManager.

How does the upgrade work?

Using this document, you can upgrade the operating system, BIOS, and Cisco CallManager via CD-ROM or the web. To upgrade via CD-ROM, locate the Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM and the appropriate version of the Cisco CallManager 3.2 Installation and Recovery CD-ROM.

Upgrading the BIOS and Operating System

The operating system upgrade CD-ROM and executable that is available on the web provide the latest Cisco Media Convergence Server (MCS) BIOS, service packs, hotfixes, and the operating system components and services available for your server; to obtain the latest operating system hotfixes, service packs, and components, download the executable instead of using the CD-ROM.

Review the following documentation before you upgrade the operating system:

Cisco IP Telephony BIOS and Operating System Version Roadmap provides information on the latest Cisco-supported BIOS, operating system files, hotfixes, and service packs that are available for web download. This document also provides instructions for verifying versions of operating system hotfixes, service packs, etc.

To obtain this document, click http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/osbios.htm

The operating system readme that is available on the web provides the latest procedures, caveats, and descriptive information that are necessary for upgrading the operating system.

To access the operating system readme documentation, see the "Upgrading the BIOS and Operating System" section.

Upgrading Cisco CallManager

After you upgrade the operating system, you upgrade Cisco CallManager, which autodetects the relationship between the publisher database server and subscriber server.

Table 3 describes the components that you can activate if the CallManager Components window displays.

Table 3 Options That You Can Choose in the CallManager Components Window 

Check Box
Component Activated

Cisco CallManager Components

The Cisco TFTP server, database, and Cisco CallManager service automatically install. When you install the Cisco CallManager service, you automatically install the following services/features/applications:

Cisco CallManager Serviceability Application

Cisco Telephony Call Dispatcher

Cisco CTI Manager

Cisco RIS Data Collector

Logout Service (associated with Cisco CallManager Extended Services)

Cisco CallManager Web Components

You install Cisco CallManager Administration and the database. This web-based graphical user interface (GUI) allows you to perform tasks such as adding users or installing and configuring plugins that are associated with Cisco CallManager.

If you want a standalone database server only (does not have Cisco CallManager installed), check only the Cisco CallManager Web Components check box. With this option, only Cisco CallManager Web Components and the database install on the server.

If you choose not to install Cisco CallManager Web Components at this time, be aware that you will have to reinstall Cisco CallManager if you want Cisco CallManager Administration on the server.

Optional Components

You install the database, Cisco Messaging Interface, and the Cisco IP Voice Media Streamer, which contains the Media Termination Point (MTP), music on hold (MOH), and conference bridge services.


The Cisco CallManager upgrade places services in a stopped state until the upgrade completes. The services that are associated with Cisco CallManager activate and start after the server reboots. For information on starting and stopping services that are associated with Cisco CallManager, refer to the Cisco CallManager Serviceability Administration Guide or to online help in the Cisco CallManager application.


Tip Before the upgrade, disable all third-party Cisco-verified services, for example, antivirus or intrusion detection services, that restart automatically when the server reboots at the end of the upgrade. You must enable these services after the upgrade completes.


Will I experience call-processing interruptions and a loss of services during the upgrade?

When you upgrade a cluster, you have two separate versions of Cisco CallManager running in the cluster at the same time. Be aware that the different Cisco CallManager versions that are running in the cluster will not interact, and may cause call-processing interruptions to occur.

If you configured your Cisco CallManager cluster by using approved Cisco configuration standards, which include configuring four primary servers and two backup servers in the cluster, you can minimize call-processing interruptions if you register all devices to servers that are running the same version of Cisco CallManager during the entire upgrade process; i.e., you register all devices to the backup Cisco CallManager servers or the primary Cisco CallManager servers, but not to both types of servers.

Cisco CallManager places services in a stopped state until the upgrade completes. After the upgrade completes, the services activate and start after the server reboots. For information on starting and stopping services, refer to the Cisco CallManager Serviceability Administration Guide or to online help in the Cisco CallManager application.

May I remotely upgrade the cluster?

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.

If you want to upgrade the cluster remotely, you must use Virtual Network Computing (VNC), which is available with operating system version 2000.2.3 or later. You must install VNC if you want to use it. For information on installing and using VNC, click the following URL to obtain the documentation:

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

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 tasks should I perform before I upgrade the cluster?

Before you begin the upgrade, complete the following tasks that are described in Table 4:

Table 4 Pre-Upgrade Tasks 

Pre-Upgrade Task
Related Information and Procedures

Verify that you can upgrade from the Cisco CallManager version that you currently run in the cluster.

For the latest information on compatible versions of Cisco CallManager, review the Cisco CallManager Compatibility Matrix by clicking the following URL:

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

Because some versions of Cisco IP telephony applications are not compatible with Cisco CallManager, ensure that you maintain compatibility with other Cisco applications after the Cisco CallManager upgrade.

If compatibility does not exist when Cisco CallManager 3.2(2c) releases, Cisco recommends that you wait to upgrade until compatibility exists.

Refer to the following documentation:

The version of Release Notes for Cisco CallManager 3.2 that matches this upgrade document

The appropriate documentation that is distributed with the Cisco IP telephony applications

Cisco CallManager Compatibility Matrix

If you have not previously upgraded your Cisco CallManager 3.0 system to a 3.1 or 3.2 release, write down the default load information for all devices that are associated with your current Cisco CallManager 3.0 system.

See the "Obtaining Device Default Load Information for Cisco CallManager Release 3.0" section.

See the "Reverting a 3.2 Cisco Device Load to a 3.0 Cisco Device Load" section.

Purge any unused call detail records (CDRs) to prevent timeout of the upgrade and to reduce upgrade time. Cisco recommends storing no more than1.5 million CDRs in the database.

Refer to the Cisco CallManager Serviceability Administration Guide.

Back up your Cisco CallManager data and, if applicable, preserve the hard drives.

See the "Backing Up Your Cisco CallManager System and Preserving Your Hard Drives" section.

Make note of your system configuration. Consider the number and type of devices, Cisco IP telephony applications, and various services that are running on the servers.

For more information on devices and services, refer to the latest version of the Cisco CallManager System Guide and the Cisco CallManager Administration Guide.

Refer to the documentation that accompanies your Cisco IP telephony applications.

To ensure that the upgrade completes successfully, you must disable any security policies that cause the SQLSvc account to lock.

If the Cisco CallManager server exists in a domain, you must disable the Domain Security Policies on the server that acts as the Domain Controller. You also need to disable the Local Security Policies on the local Cisco CallManager server(s), even if the server does not exist in a domain.

You can enable the policies after you upgrade all servers in the cluster.

If you do not disable the security policies, the upgrade fails and requires a new Cisco CallManager installation of the server and a restoration of the last successful backup.

For more information, see the "What additional information should I know before I upgrade?" section.

Verify that you have the compatible hotfixes and service packs installed on the server. If necessary, download operating system hotfixes and service packs.

If necessary, install the latest Microsoft SQL Service 7.0 service pack.

If necessary, install the latest BIOS updates.

For more information, review Cisco IP Telephony BIOS and Operating System Version Roadmap. This document specifies compatible operating system versions and provides information for verifying the versions that exist on the server.

To obtain the document, click the following URL:

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

After you review the document, perform the following procedure: Click http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml. Choose Cisco CallManager Version 3.2 > Download CallManager Cryptographic Software... > Download Cisco 3DES Cryptographic Software under export licensing controls; download the latest Microsoft patches and hotfixes.

If you have third-party, Cisco-verified applications (Cisco AVVID partner applications) installed on the server, you must disable the services.

For example, set all Cisco-approved McAfee antivirus services to Disabled.

You can enable all services after you complete the upgrade.

To review a list of Cisco-verified applications, 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.

To disable antivirus services, see the "Disabling AntiVirus and Intrusion Detection System Services" section.

If you have Cisco IDS host sensor installed on the server, you must stop the following services before the operating system upgrade:

entercept Agent

entercept Watchdog

entercept Notification Manager

entercept Server

You can start the services after you complete the Cisco CallManager upgrade on all servers in the cluster.

For information on how to perform these tasks, click the following URL:

http://www.cisco.com/warp/public/788/AVVID/ids_host_sensor_cm.html

Close all programs before starting the upgrade.

To begin the upgrade, see "Performing the Cisco CallManager Release 3.2 Upgrade" section.


What additional information should I know before I upgrade?

This document assumes that all servers in your cluster are currently in an operational state.

About Software that You Should Not Install on Any Server in the Cluster/About Web Browsers


Caution Be aware that installing or using Netscape Navigator on the Cisco CallManager server can cause severe performance problems. Cisco strongly recommends against installing Netscape Navigator or any other application software on the Cisco CallManager server.

Cisco strongly recommends that you do not run a web browser on the Cisco CallManager server (the server that is running the Cisco CallManager service). Running a web browser on the server causes CPU usage to surge.

Be aware that Cisco does not support third-party software that is installed on any Cisco Media Convergence Server (MCS) or customer-provided server that meets approved Cisco configuration standards.

To access a list of Cisco-verified applications that you can run with Cisco CallManager, see Table 4.

About CDR Analysis and Reporting (CAR)

If you have CAR, formerly known as the Administrative Reporting Tool (ART), running on your system before the upgrade, the upgrade process automatically upgrades CAR. For more information about CAR, refer to the Cisco CallManager Serviceability Administration Guide.

About Service Parameters

If you changed the default value of a service parameter while you were running Cisco CallManager, the default value does not change during the Cisco CallManager 3.2 upgrade process. If you never changed the default value while you were running a previous version of Cisco CallManager, Cisco CallManager updates the parameter value during the Cisco CallManager 3.2 upgrade to match the suggested value that is seen in Cisco CallManager Administration.

About Server Names

Unless otherwise specified in this document, all further references to the MCS-7835 apply to the MCS-7835, which contains a 733-MHz processor, the MCS-7835-1000, which contains a 1-GHz processor, the MCS-7835-1266, which contains a 1.26-GHz processor, and the customer-provided DL380. All further references to the MCS-7825 apply to the MCS-7825, which contains a 800-MHz processor, and the MCS-7825-1133, which contains a 1.2-GHz processor.

About Passwords

To upgrade Cisco CallManager, you must have administrative access privileges on the servers that you upgrade. If necessary, obtain this information before the upgrade.

During the upgrade, the password for the SQLSvc NT account changes. If you have a lockout account policy for your Domain Security Policy or Local Security Policy, be aware that the SQLSvc account locks during the upgrade because the publisher database server receives the new password during the publisher database upgrade while the subscriber servers use the old password. When the subscriber servers attempt to authenticate to the publisher database server, the lockout account policy locks the SQLSvc account, and the upgrade fails, requiring that you reinstall Cisco CallManager on the server and restore the last successful backup.

To ensure that the upgrade completes successfully, you must disable any security policies that cause the SQLSvc account to lock. If the Cisco CallManager server exists in a domain, you must disable the Domain Security Policies on the server that acts as the Domain Controller. You also must disable the Local Security Policies on the local Cisco CallManager server(s), even if the server does not exist in a domain.


Caution Disabling the security policies makes any server in the domain vulnerable to attacks. Immediately after the upgrade of every server in the cluster, re-enable security policies.

Procedure for Domain Controller


Step 1 On the server that acts as the Domain Controller, choose Start > Programs > Administrative Tools > Domain Security Policy > Security Settings > Account Policies > Account Lockout Policy.

Step 2 Locate the Account Lockout threshold policy in the pane and perform the following procedure:

a. Double-click the policy.

b. Enter 0 (the number zero) for the Policy Setting.

c. Click OK.

d. In the Suggested Value Changes dialog box, click OK.

Step 3 To disable the Password Policy, perform the following procedure:

a. Choose Start > Programs > Accessories > Domain Security Policy > Security Settings > Account Policies > Password Policy.

b. Double-click the Passwords must meet complexity requirements policy.

c. Click the Disabled radio button that displays in the dialog box; click OK.


Procedure for Local Cisco CallManager Server(s)


Step 1 On the local Cisco CallManager server(s), choose Start > Programs > Administrative Tools > Local Security Policy > Security Settings > Account Policies > Account Lockout Policy.

Step 2 Locate the Account Lockout threshold policy in the pane and perform the following procedure:

a. Double-click the policy.

b. Enter 0 (the number zero) for the Policy Setting.

c. Click OK.

d. In the Suggested Value Changes dialog box, click OK.

Step 3 To disable the Password Policy, perform the following procedure:

a. Choose Start > Programs > Accessories > Local Security Policy > Security Settings > Account Policies > Password Policy.

b. Double-click the Passwords must meet complexity requirements policy.

c. Click the Disabled radio button that displays in the dialog box; click OK.


What tasks should I perform after the upgrade?

To ensure that your Cisco CallManager system and Cisco IP telephony applications function properly, Cisco strongly recommends that you review the "Performing Post-Upgrade Tasks" section.

Obtaining Device Default Load Information for Cisco CallManager Release 3.0


Caution Device loads in Cisco CallManager Release 3.0 exist in .cnf format whereas device loads in Cisco CallManager Release 3.1 and 3.2 exist in .bin format. If you choose to revert to Cisco CallManager Release 3.0, the devices will not boot properly unless they are running the 3.0 loads prior to the Cisco CallManager reversion. To revert your system, you must have the device default load information for Cisco CallManager Release 3.0.

To obtain the device default load information for your Cisco CallManager Release 3.0 system, perform the following procedure:

Procedure


Step 1 On the publisher database server, choose Start > Programs > Cisco CallManager 3.0 > Cisco CallManager 3.0 Administration and log in with administrator privileges.

Step 2 From the CallManager Administration window, choose System > Device Defaults.

Step 3 While viewing the Device Defaults Configuration window, write the load information for the devices that are currently associated with your Cisco CallManager 3.0 system in Table 5, which already includes the first four digits of the eight-digit load. This information reflects the device default load information that is associated with the Cisco CallManager 3.0 version that is currently running on your system.

Step 4 File this information, so you can easily access it in the future.


Note To revert from Cisco CallManager Release 3.2 to a previous Cisco CallManager 3.0 release, you must retain the device default load information that is associated with the Cisco CallManager 3.0 version that is running on your system. See the "Reverting to the Previous Configuration After an Upgrade Attempt" section for more information.



Use Table 5 in conjunction with the "Obtaining Device Default Load Information for Cisco CallManager Release 3.0" section. Fill in the device default load information for Cisco CallManager Release 3.0. The first four digits of an eight-digit load already appear in the table. Make sure to file this information after you complete the table.

Table 5 Device Default Load Information 

Device Type
Load Information

IP Phones 7960/7940

P003

IP Phone 7910

P004

IP Phones 12 S/SP/12 SP+/30 VIP

P002

IP Phone 30 SP+

P001

IP Phone 7935

P005

Analog Access

A001

Analog Access WS-X6624

A002

Digital Access+

D003

Digital Access WS-X6608

D004

Conference Bridge WS-X6608

C001

Media Termination Point WS-X6608

M001

14-Button Line Expansion Module

S001


Backing Up Your Cisco CallManager System and Preserving Your Hard Drives

After you write down the device default load information, you perform the backup. Cisco CallManager comes with the Cisco IP Telephony Applications Backup Utility. This utility provides a reliable and convenient way to perform regularly scheduled, automatic backups of Cisco CallManager data.


Note Cisco recommends that you obtain a spare hard drive before completing the following procedure; however, you do not have to use a separate drive to preserve the hard drive.



Note You must always mirror drives in the MCS-7845 in pairs.


Perform the following steps to back up Cisco CallManager data and preserve the hard drives:

Procedure


Step 1 Perform a Cisco CallManager backup on the publisher database server.

For instructions on backing up Cisco CallManager data, refer to latest version of Backing Up and Restoring Cisco CallManager Release 3.2 or the Cisco CallManager installation guide that matches your Cisco CallManager installation CD-ROM.

Step 2 Save the MCS.sti file from the backup server to a tape drive or network directory.

Step 3 If you are backing up the MCS-7820, MCS-7822, MCS-7825, or customer-provided IBM xSeries 330 server, begin the upgrade by completing the steps in the "Performing the Cisco CallManager Release 3.2 Upgrade" section.

If you are backing up the MCS-7830, MCS-7835, MCS-7845 or customer-provided IBM xSeries 340 or 342 server, power off the publisher database server and continue to Step 4.

Step 4 For all servers except the MCS-7845, remove the hard drive from Slot 1 and label the drive with the machine name, slot number, and current version of Cisco CallManager. For the MCS-7845, remove the drives from slot 1 and 3.

Step 5 Power on the system. If you have the MCS-7830 or MCS-7835, or MCS-7845, the system automatically prompts you to press F1 or F2. If you have the customer-provided IBM xSeries 340 or 342 server, the system automatically prompts you to press F2, F4, F5, or F10.

Step 6 To enable interim recovery mode on the MCS-7830, MCS-7835, or MCS-7845, press F2 and go to Step 7; to enable interim recovery mode on the customer-provided IBM xSeries 340 or 342 server, press F5 and go to Step 8.

Step 7 This step applies only for the MCS-7830, MCS-7835, or MCS-7845. When prompted, press F1 to continue.

Step 8 If a spare hard drive is not available, go to Step 10. If a spare hard drive is available, perform the following steps (The MCS-7845 requires two spare hard drives):

a. After Windows 2000 finishes booting, insert the spare hard drive in Slot 1. The second drive for slot 3 on the MCS7845 should not be inserted until after the mirror process is complete for the drive inserted in slot 1.

b. For the MCS-7830, MCS-7835, or MCS-7845, choose Start > Programs > Compaq Systems Tools > Compaq Array Configuration Utility. When the Array Configuration Utility Warning window opens, click OK.


Note If you cannot find the Compaq Array Configuration Utility, go to the Control Panel by choosing Start > Settings > Control Panel.


For the customer-provided IBM xSeries 340 or 342 server, choose Start > Programs > ServeRaid Manager> ServeRaid Manager.

c. Watch the status bar in the lower, right corner to determine when the drive-mirroring process completes. Once the MCS-7845 drive in slot 1 is complete insert the next drive into slot 3. The mirror process will launch automatically once the drive is inserted into slot 3.

Step 9 Repeat Step 3 through Step 8 for each server in the cluster.

Step 10 Begin the upgrade by completing the steps in the "Performing the Cisco CallManager Release 3.2 Upgrade" section.


Performing the Cisco CallManager Release 3.2 Upgrade

After you finish the Cisco IP Telephony Applications backup, you choose to upgrade via the web or CD-ROM. The following sections apply to the upgrade:

Pre-Upgrade Tasks, Table 4

Disabling AntiVirus and Intrusion Detection System Services

Upgrading the BIOS and Operating System

Installing the Microsoft SQL Server 7.0 Service Pack

Upgrading Cisco CallManager via CD-ROM or the Web

Performing Post-Upgrade Tasks

Performing Pre-Upgrade Tasks

Make sure that you have performed all pre-upgrade tasks in Table 4 before you upgrade the operating system and Cisco CallManager.

Disabling AntiVirus and Intrusion Detection System Services

To disable the McAfee antivirus services, perform the following tasks:

Procedure


Step 1 Choose Start > Settings > Control Panel > Administrative Tools > Services.

Step 2 From the Services window, right-click one of the antivirus services; i.e, Network Associates Alert Manager, Network Associates McShield, or Network Associates Task Manager, and choose Properties.

Step 3 Verify that the General tab displays in the Properties window.

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

Step 5 Click OK.

Step 6 Perform Step 1 through Step 5 for all Cisco-approved McAfee antivirus services; i.e., Network Associates Alert Manager, Network Associates McShield, and Network Associates Task Manager.


If you installed Cisco IDS sensor host agents on the server, Cisco strongly recommends that you disable the following services:

entercept Agent

entercept Watchdog

entercept Notification Manager

entercept Server


Caution If Cisco-verified antivirus or intrusion detection software is not currently installed on the server, Cisco strongly recommends that you do not install the software until you complete the entire upgrade/installation of all servers in the cluster.

Upgrading the BIOS and Operating System

The operating system upgrade CD-ROM and executable that is available on the web provide latest service packs, hotfixes, and operating system components and services that are available for your server; if you want the latest operating system hotfixes, service packs, and components, download the executable instead of using the CD-ROM.

Review the following documentation before you upgrade the operating system:

Cisco IP Telephony BIOS and Operating System Version Roadmap provides information on the latest Cisco-supported BIOS, operating system files, hotfixes, and service packs that are available for web download. This document also provides instructions for verifying versions of operating system hotfixes, service packs, etc.

To obtain this document, click http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/osbios.htm

The operating system readme that is available on the web provides the latest procedures, caveats, and descriptive information that is necessary for upgrading the operating system.

To obtain the operating system upgrade executable, hotfixes, and service packs and the corresponding readme documentation, perform the following procedure:

Procedure for Obtaining the Operating System Upgrade Executable, Service Packs (Operating System and Microsoft SQL Server 7.0), and Hotfixes


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

Step 2 Choose Cisco CallManager Version 3.2 > Download...CallManager Cryptographic Software... > Download Cisco 3DES Cryptographic Software under export licensing controls.

Step 3 Download the readme document for the file.

The readme file provides procedures, caveats, and descriptive information for installing the files.

Step 4 Using the readme file as a reference, install the files.

Step 5 Perform this procedure on every server in the cluster.


Installing the Microsoft SQL Server 7.0 Service Pack

For Microsoft SQL Server service pack version 4 or later

If you have not already done so, install Microsoft SQL Server 7.0 service pack 4 or a later version of the service pack, if available on the web, before you upgrade Cisco CallManager. For information on installing the service pack, see the "Procedure for Obtaining the Operating System Upgrade Executable, Service Packs (Operating System and Microsoft SQL Server 7.0), and Hotfixes" section.

Upgrading Cisco CallManager via CD-ROM or the Web

Review the following information before upgrading Cisco CallManager:

During the upgrade process, Cisco CallManager services automatically stop, so the software can be upgraded. The services then restart at the end of the process. Because of this brief interruption, call-processing services temporarily stop. You should notify your users that telephone service will be interrupted during this time; to minimize call-processing interruptions, Cisco strongly recommends that you perform the Cisco CallManager and Cisco IP telephony application upgrades within a consecutive time period (within one maintenance window) during off-peak hours.

You must have administrative access privileges on the servers to upgrade Cisco CallManager.

Via CD-ROM or the web, perform the upgrade by completing the following steps:

Procedure


Step 1 If you have not already done so, disable all Cisco-approved McAfee antivirus services through the Control Panel by completing the procedure in the "Disabling AntiVirus and Intrusion Detection System Services" section.

Step 2 If you have Cisco IDS host sensor installed on the server, you must stop the services that are described in the"Disabling AntiVirus and Intrusion Detection System Services" section.

Step 3 If you have not already logged into the server after the operating system upgrade, log in to the server by using the Administrator account and password.

Step 4 Depending on your upgrade method (via CD-ROM or the web), perform the following procedure:

a. If you want to upgrade via CD-ROM, locate the Cisco CallManager 3.2(2c) Installation and Recovery CD-ROM and insert it into the CD-ROM drive; then, go to Step 5.

b. If you want to upgrade via the web, click http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

c. Click Cisco CallManager Version 3.2.

d. Download the Cisco CallManager 3.2(2c) upgrade file to your hard drive.

e. Note the location where you save the downloaded file.

f. Double-click the downloaded file to begin the installation.

Step 5 When the Cisco Product Activation dialog box opens, click Yes.

Step 6 In the Welcome to the Cisco CallManager Installation Wizard window, enter your Windows administrative password and click Next.

Step 7 If the CallManager Components window opens, check the check boxes of the components that you want to run on the server. For information on available components and standalone database servers, see the "How does the upgrade work?" section. Choose the services that you want to activate; then, click Next.

To add or remove services after you complete the upgrade, refer to the "Activating Cisco CallManager Services" section in the latest version of Installing Cisco CallManager Release 3.1.

Figure 1 shows an example of the CallManager Components window.

Figure 1 CallManager Components Window


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.


Step 8 The CallManager Database Configuration window opens. Cisco CallManager autodetects whether you are upgrading the publisher database server or subscriber database server. If you are upgrading the publisher database server, Cisco CallManager automatically chooses I am upgrading/installing the CallManager publisher database server. Click Next and go to Step 10.

Figure 2 demonstrates Cisco CallManager autodetection of the publisher database server.

Figure 2 Cisco CallManager Publisher Database Server Autodetection

Step 9 If a publisher database server already exists and you are configuring a subscriber database server, Cisco CallManager automatically chooses I am upgrading/installing the CallManager Subscriber. By default, the publisher database server that is associated with the subscriber displays in the hostname publisher database server field. You may choose another publisher database server by clicking Browse.

If the Cisco CallManager installation chose I am upgrading/installing the CallManager Subscriber, enter the username and password for a Windows 2000 user with administrative privileges and a SQL Server username and password with SQL Server administrative privileges on the publishing database server. Enter the account information in the appropriate fields as prompted and then click Next. The system connects to the publishing database server.

Step 10 Now that the Cisco CallManager and other included software are ready to be installed, click Next. This part of the installation takes about 30 to 90 minutes.

Step 11 When the dialog box opens, click OK to acknowledge that you need to configure a partition and calling search space for Message Waiting on and off directory numbers.


Caution When entering passwords for the local Administrator and SA (SQL Server system administrator) accounts, do not use the apostrophe. Enter the same Administrator password for the publisher database server and all subscribers in the cluster, so Cisco CallManager database replication occurs.

Step 12 A prompt asks you to enter a new password for the SA (SQL Server system administrator) account. Enter a new password of at least five characters in the New Password field and then enter it in the Retype Password field. Click OK.

Step 13 A message indicates that the password changed successfully. Click OK.

Step 14 When prompted, reboot the server.

Step 15 See the "Performing Post-Upgrade Tasks" section to complete post-upgrade tasks.


Performing Post-Upgrade Tasks

After you complete the upgrade, perform the appropriate tasks as described in Table 6:

Table 6 Post-Upgrade Tasks 

Post-Upgrade Task
Related Information and Procedures

If you disabled security policies for the Domain Security Policy and the security policies for the Local Security Policy before the upgrade, enable the policies to ensure that your system is not vulnerable to attacks.

See the "What additional information should I know before I upgrade?" section for more information.

If you have not already done so, set all Cisco-approved McAfee antivirus services to Enable through the Control Panel.


Caution If you need to upgrade co-resident applications that run on the server, be aware that enabling the antivirus or intrusion detection system services may cause problems with the application upgrade. Cisco recommends that you disable the services each time that you perform a Cisco IP telephony application upgrade and then enable the services immediately after the upgrade.

See the "Enabling Cisco-Approved McAfee Antivirus Services" section.

If you have Cisco IDS host sensor installed on the server, you must start the following services, if you have not already done so:

entercept Agent

entercept Watchdog

entercept Notification Manager

entercept Server

For information on the Cisco IDS host sensor, click the following URL:

http://www.cisco.com/warp/public/788/AVVID/ids_host_sensor_cm.html

Verify that all services started. Verify that you can place and receive a call across gateways. Verify that all Cisco IP telephony applications that are integrated with Cisco CallManager run properly.

Make note of the number of devices that you support in the Cisco CallManager cluster.

See the "Verifying Services, Patches, and Hotfixes" section.

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

Refer to the Cisco CallManager Compatibility Matrix, which provides compatibility information and workarounds for applications that are integrated with Cisco CallManager.

If you need to do so, upgrade the Cisco IP telephony applications that are integrated with your Cisco CallManager system.


Caution Cisco recommends that you disable the services for every Cisco IP telephony application upgrade and then enable the services immediately after the upgrade.

Refer to the Cisco CallManager Compatibility Matrix by clicking the following URL:

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

Refer to the appropriate Cisco IP telephony application documentation.

If you run Cisco TFTP service and the Cisco MOH Audio Translator service on two separate servers in the cluster, you must ensure that the server with the Cisco MOH Audio Translator service can access and has write privileges to the server where the Cisco TFTP service runs.

See the "Configuring Cisco MOH Audio Translator and Cisco TFTP" section.

If you have never upgraded to Cisco CallManager Release 3.2, make sure that you configure partitions and calling search space for Message Waiting Indicator (MWI).

With every version of Cisco CallManager Release 3.2, you must synchronize the Message Waiting Indicator to be able to see the red indicator on the Cisco IP Phone.

For information on configuring the partitions and calling search space for MWI, see the "Using the Message Waiting Indicator (MWI)" section.

See the "Synchronizing the Message Waiting Indicator" section. For more information on resetting MWI, refer to the appropriate documentation that supports your voice-mail system.

Cisco strongly recommends that you download and use the Cisco CallManager Attendant Console.

For more information on this product, see the "Using the Cisco CallManager Attendant Console" section.

If necessary, upgrade Cisco TAPI, Cisco JTAPI, Cisco TSP (for the voice-mail system), the Cisco TSP for Cisco SoftPhone, and the plugin for the Cisco WebAttendant client.

You must upgrade the Telephony Application Programming Interface and Java Telephony Application Programming Interface (TAPI/JTAPI) client software on any application server or client workstation on which TAPI/JTAPI applications are installed. If you do not upgrade the TAPI/JTAPI client, your application will fail to initialize.

The following information applies if you have integrated a Cisco Unity system with Cisco CallManager. TSP makes the voice-mail ports available to Cisco Unity. To ensure that Cisco Unity integrates properly with Cisco CallManager, you may need to upgrade the TSP that is associated with the voice-mail system. To ensure that you upgrade to the appropriate TSP release, refer to the Cisco CallManager Compatibility Matrix.

Refer to the Cisco CallManager Compatibility Matrix for more compatibility information.

For information on installing plugins, refer to the Cisco CallManager Administration Guide.

If you choose to do so, change the SQLSvc password on all servers in the cluster.

See the "Verifying Services, Patches, and Hotfixes" section.

Back up your Cisco CallManager data and, if applicable, preserve the hard drives.

See the "Drive Mirroring for the MCS-7830, MCS-7835, and IBM xSeries 340 or 342 Server" section.

To start a backup now, right-click the backup icon in the Windows 2000 system tray. Choose Start Backup Now. The backup begins immediately.

To locate the log files for the backup, use Windows Explorer to browse to the following folder: C:\Winnt

For more information on the backup utility, refer to Backing Up and Restoring Cisco CallManager Release 3.2.

Verify the version of hotfixes and service packs that are installed on the server.

Remember to perform ongoing server management by downloading the latest hotfixes, service packs, and Cisco CallManager support patches that are available on the web.

The operating system readme document that is available on the web provides procedures, caveats, and a descriptive overview for upgrading the operating system, service packs, and hotfixes. To access the operating system readme documentation, see the "Upgrading the BIOS and Operating System" section.


Enabling Cisco-Approved McAfee Antivirus Services

To enable the Cisco-approved McAfee antivirus services, perform the following tasks:

Procedure


Step 1 After you log in to the server, enable all Cisco-approved McAfee antivirus services through the Control Panel by completing the following procedure:

a. Choose Start > Settings > Control Panel > Administrative Tools > Services.

b. From the Services window, right-click one of the antivirus services; i.e., Network Associates Alert Manager, Network Associates McShield, or Network Associates Task Manager, and choose Properties.

c. Verify that the General tab displays in the Properties window.

d. From the Startup type drop-down list box, choose Automatic.

e. Click OK.

f. In the Services window, right-click the antivirus service and click Start.

Step 2 Perform Step 1 to enable all Cisco-approved McAfee antivirus services; i.e., Network Associates Alert Manager, Network Associates McShield, and Network Associates Task Manager.


Verifying Services, Patches, and Hotfixes

To confirm that the upgrade completed successfully, verify that all services that are listed in your Services window are running. Choose Start > Programs > Administrative Tools > Services and verify the following services:

Cisco CallManager

Cisco Database Layer Monitor

Cisco IP Voice Media Streaming Application

Cisco Messaging Interface

Cisco RIS Data Collector

Cisco TFTP

DC Directory Server

Depending on which services you have installed on your system, some services shown in the preceding list may not appear in your Services window.

After you install Cisco CallManager, QFECheck, a Microsoft program that was installed with the Cisco-provided operating system, verifies that you have the latest Microsoft patches and hotfixes running on your system. If your server does not have the latest hotfixes, click http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml. Choose Cisco CallManager Version 3.2 > Download CallManager Cryptographic Software... > Download Cisco 3DES Cryptographic Software under export licensing controls; download the latest Microsoft patches and hotfixes.

To verify that you have the latest Cisco CallManager updates on the server, click http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml; click Cisco CallManager Version 3.2 and locate the latest support patches and readme documents in the download table. Download the appropriate support patches on the server.

Viewing the Component Versions Installed on the Server

The stiver.exe program reports the current version of all installation components, including such components as the operating system, upgrade, and backup and restore utility. Be aware that Cisco does not report the actual Cisco CallManager version through this program. Recognize that most of these components, run from the installation CD-ROMs during the initial installation, no longer exist on the system.

The version for OS Image equals your operating system CD-ROM version number. The version of OS Image will change only if you do a new installation with the Cisco IP Telephony Server Operating System Hardware Detection CD-ROM (CD #1).

The version for stiOSUpg.exe equals the version of the operating system upgrade that you last ran either via CD-ROM or via the web. When Cisco updates and releases the Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2), the version of stiOSUpg changes.

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:\sti\stiver

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


Configuring Cisco MOH Audio Translator and Cisco TFTP

If you run the Cisco TFTP service and the Cisco MOH Audio Translator service on two separate servers in the cluster, perform the following configuration tasks. These tasks ensure that the server with the Cisco MOH Audio Translator can access and has write privileges to the server where the Cisco TFTP service runs.


Note Before you perform this procedure, make sure that you have configured and added both servers to the Cisco CallManager database. For information on how to perform this task, refer to the Cisco CallManager Administration Guide.


Procedure


Step 1 From Cisco CallManager Administration, choose Service > Service Parameters.

Step 2 Choose the primary server where the Cisco CallManager service runs.

Step 3 Choose Cisco IP Voice Media Streaming App.

Step 4 Change the Default TFTP MOH IP Address field to the name of the server where the Cisco TFTP service runs; then, click Update.

Step 5 Choose Service > Service Parameters.

Step 6 Choose the primary server where the Cisco CallManager service runs.

Step 7 Choose Cisco MOH Audio Translator.

Step 8 Change the DefaultTFTPMOHFilePath to \\<Name of service where the Cisco TFTP runs>\TFTPPATH.

Step 9 Make sure that the Cisco MOH Audio Translator service can access and has write privileges to the server where the TFTP service runs.

Step 10 Locate the server where the Cisco MOH Audio Translator service runs.

Step 11 Perform the following procedure on the server:

a. Choose Start> Programs > Administrative Tools > Computer Management > Local Users and Groups > Users.

b. Right-click the Users folder and choose New User.

c. Enter the user name; for example, mohuser

d. Enter the password, and confirm the password. Click Create.

e. Uncheck the User must change password at next logon check box.

f. Choose Start > Programs > Administrative Tools > Computer Management > Local Users and Groups > Groups.

g. Click Administrators; add the user name by clicking Add. After you complete the task, click OK.

h. Choose Start > Programs > Administrative Tools > Computer Management > Services.

i. Right-click the Cisco MOH Audio Translator service; choose Properties.

j. From the Log on tab, click This account.

k. Enter the user name in the user name field; enter the password in the password field.

l. Restart the service.

Step 12 Locate the server where the Cisco TFTP service runs and repeat Step 11.


Note On the server where the Cisco TFTP service runs, make sure that you enter the same user name and password that you entered for the server with Cisco MOH Audio translator service.


Step 13 Drag and drop a new wave file in the DropMOHAudioSourceFilesHere directory on the server where the Cisco MOH Audio Translator service runs.

Step 14 Configure the new wave file to be used when devices are put on hold.

Step 15 Verify that the new file plays properly. If it does not play properly, perform Step 16 and Step 17.

Step 16 Verify that c:\Program Files\Cisco\MOH directory has the codec version for the Cisco Music On Hold server of the wave file.

Step 17 Verify that c:\Program Files\Cisco\TFTPPath and c:\Program Files\Cisco\TFTPPath\MOH directories on the server where the Cisco TFTP service runs have all codec versions of the new wave file and the Cisco Music On Hold directory has the .xml file.

For more information about the Cisco Music On Hold Audio Translator and Cisco TFTP services, refer to the Cisco CallManager Administration Guide and the Cisco CallManager System Guide.


Using the Message Waiting Indicator (MWI)

During the upgrade, the migration program identifies the first Cisco Unity port record and assigns the calling search space from the record to the migrated MWI on and MWI off numbers. If you use a voice-mail system other than Cisco Unity or if you use more than one Cisco Unity voice-mail system, you must manually assign the MWI on and off directory numbers to a partition and a calling search space, if applicable, through Cisco CallManager Administration. Cisco requires that you perform this procedure only one time after you upgrade to Cisco CallManager 3.2.

Procedure


Step 1 On the primary Cisco CallManager server, choose Start > Programs > Cisco CallManager 3.2 > Cisco CallManager 3.2 Administration and log in with administrative privileges.

Step 2 From the Feature Menu, choose Voice Mail > Message Waiting.

The Message Waiting Configuration window displays. The Message Waiting Configuration window allows you to define Message Waiting Indicator on and off directory numbers that are used by a directly connected voice-mail system to determine whether to set or clear a message-waiting indication for a particular Cisco IP Phone.

Step 3 From the list on the left side of the window, choose the Message Waiting Directory Number that matches the MWI number that was on prior to the upgrade. A green icon indicates that the directory number is a Message Waiting Indicator on number.

Step 4 Choose the correct partition and calling search space, if any, for the Message Waiting Directory Number.

The calling search space for the MWI on directory number determines the devices that this MWI directory number controls. Choose a calling search space that has access to the partitions of all directory numbers that control the Message Waiting Indicator. For example, if the lines on the phone exist in a partition named "Phones," choose the calling search space for the MWI on directory number that includes the "Phones" partition.

Step 5 Click the Update button to save the changes.

Step 6 From the list on the left of the window, choose the Message Waiting Directory Number that matches the MWI number that was off prior to the upgrade. A red icon indicates that the directory number is a Message Waiting Indicator off number.

Step 7 Choose the correct partition and calling search space, if any, for the Message Waiting Directory Number.

The calling search space for the MWI off directory number determines the devices that this MWI directory number controls. Choose a calling search space that has access to the partitions of all directory numbers that control the Message Waiting Indicator.

Step 8 Click the Update button to save the changes.

For more information on MWI, refer to the latest version of the Cisco CallManager Administration Guide and the latest version of the Cisco CallManager System Guide.


Synchronizing the Message Waiting Indicator

All Cisco CallManager Release 3.2 upgrades cause the Message Waiting Indicator on your Cisco IP Phone to display incorrectly. When you upgrade the publisher database server or the server that is running the Cisco Messaging Interface service, the upgrade does not save MWI configuration settings that are associated with the red indicator that displays on the phone.

To ensure that the red indicator displays after the upgrade, you must synchronize the Message Waiting Indicator through your chosen voice-mail system. Synchronizing MWI ensures that you can retrieve messages that are sent during the upgrade process. For information on synchronizing MWI, refer to the appropriate documentation that supports your voice-mail system.

Using the Cisco CallManager Attendant Console

Cisco strongly recommends that you download and use the Cisco CallManager Attendant Console with this version of Cisco CallManager.

Like Cisco WebAttendant, Cisco CallManager Attendant Console, a client-server application, allows you to set up Cisco IP Phones as attendant consoles. Employing a graphical user interface, the attendant console uses speed-dial buttons and quick directory access to look up phone numbers, monitor line status, and direct calls. A receptionist or administrative assistant can use the attendant console to handle calls for a department or company, or another employee can use it to manage his own telephone calls.

The attendant console installs on a PC with IP connectivity to the Cisco CallManager system. The attendant console works with a Cisco IP Phone that is registered to a Cisco CallManager system (one attendant console for each phone that will be used as an attendant console). Multiple attendant consoles can connect to a single Cisco CallManager system.

The application registers with and receives call-dispatching services from the Cisco Telephony Call Dispatcher (TCD) services on the Cisco CallManager.

For information on downloading and using Cisco CallManager Attendant Console, refer to the latest versions of the following documentation:

Cisco CallManager Attendant Console Installation and Administration Guide

Cisco CallManager Attendant Console User Guide

Using the Cisco CallManager Music On Hold Download


Note This section applies if you have never downloaded the Cisco CallManager Music On Hold files from the web or used the Cisco CallManager Music On Hold CD-ROM.


When you initially install Cisco CallManager on your server, a default music on hold audio file sample automatically installs for customer use. To increase your music on hold (MOH) selection, you may download one of the following two files via the web:

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

ciscocm-MusicOnHoldSampler, which is a small set of files that offers a sample of music that is available on the CD-ROM

For information on the MOH feature, refer to the latest version of the Cisco CallManager Administration Guide and the latest version of the Cisco CallManager System Guide.

As a Cisco CallManager user, you can use any of the contents of the CD-ROM/files with music on hold. Because of licensing restrictions, you must not distribute the Cisco CallManager Music on Hold CD-ROM/files to anyone else, and you must not use it for any other purpose.

Changing the Password for the SQLSvc Account

The Cisco CallManager installation creates the SQLSvc account. At installation, the account receives a unique and encrypted default password that is unique to the cluster. This identical password applies on all servers in the cluster because the servers use the SQLSvc account as the core account for server-to-server interaction in the Cisco CallManager system. If you decide to change the password, make sure that the password for the SQLSvc account is identical on all servers in the cluster.


Caution Each time that you upgrade Cisco CallManager, the SQLSvc passwords reset to the original default. To retain your custom password, you must change the passwords again on all servers in the cluster after each upgrade.

Changing the password for the SQLSvc account includes performing the following tasks:

Changing the SQLSvc user account password (Step 1 through Step 5)

Changing the password for all services that use the SQLSvc account (Step 6 through Step 11)

Changing the SQLSvc password for DBL found in the COM+Applications folder (Step 12 through Step 18)

Performing all steps on every server in the cluster (Step 1 through Step 18)

Procedure


Step 1 Choose Start > Programs > Administrative Tools > Computer Management.

Step 2 Choose the Users folder that is located in the following path: System Tools/Local Users & Groups. The users display in the main window.

Step 3 Right-click SQLSvc and choose Set Password.

Step 4 In the New Password and Confirm Password fields, enter the new password and click OK.

Step 5 A window confirms that the password changed successfully. Click OK.

Step 6 Click the Services icon that is located in Services and Applications. The services in Table 7 display in the main window.

Table 7 Changing Password for Services That Use the SQLSvc Account

Service
Note

Cisco Database Layer Monitor

You must restart the service after you change the password.

SQLServerAgent

This service restarts when you restart the MSsQLServer service.

MSSQLServer

After you change the password, you must restart the service.

Restarting MSSQLServer automatically restarts SQLServerAgent.


Step 7 Using Table 7 as a guide, right-click the service and choose Properties.

Step 8 Click the Log On tab.

Step 9 In the Password and Confirm Password fields, enter the same password that you entered in Step 4 and click OK.

Step 10 Restart the service, if necessary, by clicking the service and then clicking Restart.

Step 11 After you change the password for all services, close the Computer Management window.

Step 12 Choose Start > Programs > Administrative Tools > Component Services.

Step 13 Choose the COM+Applications folder that is located in the following path: Component Services/Computers/My Computer. The applications display in the main window.

Step 14 Right-click DBL and choose Properties.

Step 15 Click the Identity tab.

Step 16 In the New Password and Confirm Password fields, enter the same password that you entered in Step 4 and click OK.

Step 17 Right-click DBL and choose Shut Down.

Step 18 Close the Computer Services window.

Step 19 Perform Step 1 through Step 18 on all servers in the cluster.


Drive Mirroring for the MCS-7830, MCS-7835, and IBM xSeries 340 or 342 Server

Perform the following procedure only if you did not use a spare hard drive during the backup of Cisco CallManager data. Make sure that the system functions properly before performing the following procedure. Run your Cisco CallManager system for several days to verify that no problems exist. After you verify the services, you must reinsert the hard drives that you removed prior to installation.

To reinsert the hard drives, complete the following steps:


Note Cisco recommends that you perform the drive-mirroring process after regular business hours. You should notify your users that telephone service may be interrupted during this time.


Procedure


Step 1 Start with the publisher database server. Place the hard drive that was removed during the preinstallation steps back into Slot 1.

Step 2 Perform the following task that applies to your specific server:

a. For the MCS-7830 or MCS-7835, choose Start > Programs > Compaq Systems Tools > Compaq Array Configuration Utility. When the Array Configuration Utility Warning window opens, click OK.

For the customer-provided IBM xSeries 340 or 342 servers, choose Start > Programs > ServeRaid Manager> ServeRaid Manager.

b. Watch the status bar in the lower, right corner to determine when the drive-mirroring process completes.

Step 3 Repeat Step 1 and Step 2 for each server in the cluster.


Note If you want to revert the hard drive, see "Reverting the Hard Drive After Drive Mirroring Completes" section.



Reverting to the Previous Configuration After an Upgrade Attempt

In the unlikely event of an upgrade failure, or if you prefer an earlier version of Cisco CallManager, perform the following steps to return the Cisco IP Telephony Applications Server to the configuration that was in effect prior to the upgrade.

Reverting a 3.2 Cisco Device Load to a 3.0 Cisco Device Load

This section applies if you upgraded from the latest release of Cisco CallManager Release 3.0 and you want to revert to Cisco CallManager Release 3.0.


Caution Device loads in Cisco CallManager Release 3.0 exist in .cnf format whereas device loads in Cisco CallManager Release 3.1 and 3.2 exist in .bin format. If you choose to revert to Cisco CallManager Release 3.0, the devices will not boot properly unless they are running the 3.0 loads prior to the Cisco CallManager reversion. To revert your system, you must have the device default load information for Cisco CallManager Release 3.0.

Procedure


Step 1 Locate the device default load information that is associated with the Cisco CallManager Release 3.0 that was previously running on your system before the upgrade attempt. See Table 5 for more information.

Step 2 On the publisher database server, choose Start > Programs > Cisco CallManager > CallManager Administration and log in with administrator privileges.

Step 3 From the CallManager Administration window, choose System > Device Defaults.

Step 4 On the Device Defaults Configuration window, enter the device default load information from Table 5 in the appropriate Load Information fields.

Step 5 To reset the devices, click Update.

To continue the reversion, see the "Reconfiguring the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 Server After an Upgrade Attempt" section or the "Reconfiguring the MCS-7830, MCS-7835, or IBM xSeries 340 or 342 Server After an Upgrade Attempt" section for information on how to reconfigure your server.


Reconfiguring the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 Server After an Upgrade Attempt

To reconfigure the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 server after an upgrade attempt, perform the following procedure:

Procedure


Step 1 Reinstall Cisco CallManager. For installation instructions, refer to the Cisco CallManager installation document that matches your initial Cisco CallManager installation CD-ROM. Navigate to the appropriate Cisco CallManager installation documents by clicking the following URL:

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

Step 2 Perform the necessary upgrade(s) to match the most recent backup.


Note To revert to the pre-upgrade configuration, you must restore the version of Cisco CallManager that was in effect when the last successful backup occurred.


Step 3 Revert the system to the pre-upgrade configuration by using the Cisco IP Telephony Applications Restore Utility. For more information on the Cisco IP Telephony Applications Restore Utility, refer to latest version of Backing Up and Restoring Cisco CallManager Release 3.2 or the Cisco CallManager installation guide that matches your Cisco CallManager installation CD-ROM.


Reconfiguring the MCS-7830, MCS-7835, or IBM xSeries 340 or 342 Server After an Upgrade Attempt

To reconfigure the MCS-7830, MCS-7835, or IBM xSeries 340 or 342 server after an upgrade attempt, perform the following procedure:

Procedure


Step 1 Shut down the server.

Step 2 Remove the hard drive from Slot 0. Put the hard drive that was removed prior to the upgrade into Slot 1.

Step 3 Power on the system. If you have the MCS-7830 or MCS-7835, the system automatically prompts you to press F1 or F2. If you have the customer-provided IBM xSeries 340 or 342 server, the system automatically prompts you to press F2, F4, F5, or F10.

Step 4 To enable interim recovery mode on the MCS-7830 or MCS-7835, press F2 and go to Step 5; to enable interim recovery mode on the customer-provided IBM xSeries 340 or 342 server, press F5 and go to Step 6.

Step 5 This step applies only for the MCS-7830 or MCS-7835. When prompted to do so, press F1 to continue.

Step 6 Repeat Step 1 through Step 5 for each server in the cluster.

Step 7 Verify that all services in your Services window are running properly. See the "Performing Post-Upgrade Tasks" section for information on verifying services.

Step 8 Replace the hard drive in Slot 0 and allow the drive-mirroring process to complete.


Reverting the Hard Drive After Drive Mirroring Completes

If you want to revert a hard drive after drive mirroring is complete, you must remove the server from the domain and then add it back to the domain. You must have rights to join the server to the domain before you perform this 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 WRKGRP in the corresponding field.

Step 5 Click OK.

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

Step 7 Log in with administrative privileges.

Step 8 Perform Step 1 through Step 3.

Step 9 Click the Domain radio button and enter the domain name for the server.

Step 10 Click OK.

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


Reverting Upgraded Cisco IP Telephony Applications After You Revert Cisco CallManager

If you reverted the cluster to a 3.1 version of Cisco CallManager, you can revert upgraded Cisco IP telephony applications that are integrated with Cisco CallManager to the appropriate version that is compatible with the reverted Cisco CallManager. To revert the product, perform the following procedure:

Procedure


Step 1 Locate the version of Release Notes for Cisco CallManager that matches the version to which you reverted the cluster.

Step 2 Identify the appropriate telephony product and version in the Compatibility Matrix of the release notes.

Step 3 From the application server or client workstation, if applicable, browse into the reverted 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.


Step 4 From the Application menu, choose Install Plugins.

Step 5 Click the appropriate plugin, as seen in the following list:

Cisco WebAttendant for Cisco WebAttendant

Cisco Telephony Service Provider for Cisco SoftPhone

Cisco JTAPI for any application that interfaces with Cisco CallManager by using JTAPI

Step 6 Follow the prompts in the window to complete the installation.


Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

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

http://www.cisco.com

Translated documentation is available at the following URL:

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

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

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

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco Systems, Inc.
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

http://www.cisco.com/register/

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

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

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

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

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.