Guest

Cisco Unified Communications Manager (CallManager)

Installing Cisco CallManager Release 3.1(1)

 Feedback

Table Of Contents

Installing Cisco CallManager Release 3.1(1)

Contents

Introduction

Server Hardware Specifications

Before You Begin the Cisco CallManager Release 3.1 Installation

Connecting a Monitor, Keyboard, and Mouse to the Server

Performing the Cisco CallManager Release 3.1 Installation

Starting the Operating System Installation

Installing the Operating System on the Cisco Media Convergence Servers and Customer-Provided Compaq DL 320 or DL380 Servers

Installing the Operating System on a Customer-Provided IBM xSeries Server

Entering Server Configuration Data and Completing the Operating System Installation

Installing Cisco CallManager and Related Applications

Performing Post-Installation Tasks

Changing Passwords for CCMAdmin and SQLSvc Accounts

Configuring Auto-Registration

Configuring DNS

Configuring the Database

Activating Cisco CallManager Services

Using the Cisco CallManager Music On Hold CD-ROM 3.1

Ongoing Server Management

Re-creating Subscriber Connections

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone


Installing Cisco CallManager Release 3.1(1)


This document describes how to install and configure Cisco CallManager Release 3.1 on the Cisco Media Convergence Server, customer-provided Compaq DL320 and DL380 server, or customer-provided IBM xSeries 330 and 340 server. Cisco requires that any CD-ROM purchased for installation on a customer-provided server be installed on a server meeting approved Cisco configuration standards. For specific information on approved Cisco servers, see the "Server Hardware Specifications" section. For information on IBM xSeries server hardware specifications, click the following URL: http://www.cisco.com/go/swonly/

Use this document in conjunction with the latest versions of the Cisco CallManager Administration Guide, the Cisco CallManager System Guide, the Cisco CallManager Serviceability Administration Guide, online help in the Cisco CallManager application, and the Cisco Documentation CD-ROM. For a list of new features, compatibility caveats, and enhancements in Cisco CallManager Release 3.1, refer to the version of Release Notes for Cisco CallManager Release 3.1 that matches your installation document. You can view this document by clicking the following URL:

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

Contents

This document contains the following topics:

Introduction

Server Hardware Specifications

Before You Begin the Cisco CallManager Release 3.1 Installation

Performing the Cisco CallManager Release 3.1 Installation

Performing Post-Installation Tasks

Ongoing Server Management

Re-creating Subscriber Connections

Obtaining Documentation

Obtaining Technical Assistance

Introduction

Cisco CallManager on the Cisco Media Convergence Server (MCS), customer-provided Compaq DL320 or DL380, or customer-provided IBM xSeries server provides a network business communications system for high-quality telephony over IP networks. After you install Cisco CallManager on your server, the server becomes a Cisco IP Telephony Applications Server. Cisco CallManager along with the Cisco IP Telephony Applications Server enables the conversion of conventional, proprietary, circuit-switched telecommunication systems to multiservice, open LAN systems.

Use the task roadmaps that follow to determine which sections of this document you need to accomplish a desired task.

Before You Install Cisco CallManager

Before you install Cisco CallManager software on any server, see the following sections:

Server Hardware Specifications

Before You Begin the Cisco CallManager Release 3.1 Installation

Connecting a Monitor, Keyboard, and Mouse to the Server

Installing Cisco CallManager

To install Cisco CallManager software on a Cisco MCS, customer-provided Compaq DL320 or DL380 server, or customer-provided IBM xSeries server, complete the following procedures in the order indicated:

Starting the Operating System Installation

Entering Server Configuration Data and Completing the Operating System Installation

Installing Cisco CallManager and Related Applications

Performing Post-Installation Tasks

Post-Installation Tasks

After you complete the installation, perform the following post-installation tasks:

Performing Post-Installation Tasks

Changing Passwords for CCMAdmin and SQLSvc Accounts

Configuring Auto-Registration

Configuring DNS

Configuring the Database

Activating Cisco CallManager Services

Using the Cisco CallManager Music On Hold CD-ROM 3.1


For information on backing up Cisco CallManager data and restoring your Cisco IP Telephony Applications Server, refer to the latest version of Backing Up and Restoring Cisco CallManager Release 3.1. To obtain this document, click the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_1/install/b_r311.htm

For information on upgrading your Cisco CallManager server via the web or CD-ROM, refer to the latest version of Upgrading Cisco CallManager Release 3.1. To obtain this document, click the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_1/install/upgra311.htm

Server Hardware Specifications

This section describes the system specifications for Cisco CallManager Release 3.1 and each of the Cisco Media Convergence Servers and customer-provided servers meeting approved Cisco configuration standards. Table 1 lists system hardware components included with each Cisco MCS product and customer-provided Compaq DL320 or DL380 server. Table 2 lists required system hardware components and part numbers for the IBM xSeries 330 and 340 servers.

Table 1 Cisco Media Convergence Server Hardware Specifications

Component
MCS-78351
MCS-7835-10002
MCS-7830
MCS-7825-8003
MCS-7822
MCS-7820

Intel Pentium III processor

733 MHz

1 GHz

500 MHz

800 MHz

550 MHz

500 MHz

Registered ECC SDRAM

1 GB

1 GB

512 MB 4

512 MB

512 MB

512 MB 4

10/100BaseTX protocol control information unshielded twisted-pair (PCI UTP) controller

X

X

X

X

X

X

Integrated dual-channel wide Ultra SCSI-3 controller

X

X

X

  

  

  

Integrated Ultra ATA/100 controller module (ATA Models)

  

  

  

X

  

  

Integrated wide Ultra2 SCSI adapter

  

  

  

  

X

X

Dual 18.2-GB Ultra3 SCSI hot-plug drives

  

X

  

  

  

  

Dual 18.2-GB Ultra2 SCSI hot-plug drives

X

  

  

  

  

  

Dual 9.1-GB Ultra2 SCSI hot-plug drives

  

  

X

  

  

  

Single 9.1-GB Ultra2 SCSI non-hot-plug drive

  

  

  

  

X

X

Single 20-GB Ultra ATA/100 7,200-rpm non-hot plug "1 drive"

  

  

  

X

  

  

1.44-MB floppy disk

X

X

X

X

X

X

Preinstalled high-speed IDE CD-ROM drive

X

X

X

  

X

X

Removable CD-ROM/diskette drive assembly

  

  

  

X

  

  

Hot-plug redundant 275-watt power supply

X

X

X

  

  

  

180-watt PFC power supply

  

  

  

X

  

  

200-watt power factor corrected, CE mark-compliant power supply

  

  

  

  

X

X

Integrated video card

X

X

X

X

X

X

RAID controller

X

X

X

  

  

  

12/24-GB internal DAT drive

optional

optional

  

  

  

  

1 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, and the customer-provided DL380.

2 The same Cisco-approved hardware configuration standards apply for both the MCS-7835-1000 and the customer-provided Compaq DL380.

3 All references to the MCS-7825 in this document apply to the MCS-7825-800, which contains a 800-MHz processor, and the customer-provided Compaq DL320. The same Cisco-approved hardware configuration standards apply for both the MCS-7825-800 and the customer-provided Compaq DL320.

4 The MCS-7830 and MCS-7820 require memory upgrades to meet the 512-MB RAM minimum specification. The MCS-7830 is optionally upgradable to

4 1 GB.


Before you begin the installation, carefully review the IBM hardware documentation that accompanies your server. Make sure that you have the appropriate hardware before installing Cisco CallManager. For more information on IBM xSeries server hardware specifications or to navigate to the IBM website, click the following URL: http://www.cisco.com/go/swonly/


Note Use the preceding URL to contact IBM for driver, BIOS, and firmware upgrades.


Table 2

Component
IBM xSeries 330
IBM xSeries 340

Intel Pentium III processor

800 MHz1

1000 MHz1

Registered ECC SDRAM

512 MB2

1 GB

10/100BaseTX protocol control information unshielded
(PCI UTP) controller(s)

X

X

Integrated wide Ultra160 SCSI controller(s)

X

X

Dual 18.2-GB Ultra160 SCSI hot-plug drives

  

X

ServeRaid-4L Ultra160 SCSI

  

X

Single 18.2-GB Ultra160 SCSI non-hot-plug drive

X

  

1.44-MB floppy disk

X

X

Preinstalled high-speed IDE CD-ROM drive

X

X

Removable CD-ROM/Diskette drive assembly

X

X

Hot-plug redundant 270-watt power supply

  

X

200-watt PFC, CE mark-compliant power supply

X

  

xSeries Cable Chain Tech Kit

X

  

Integrated video card

X

X

20/40-GB internal DAT drive

  

optional

1 The IBM xSeries 330 and xSeries 340 require the minimum processing speed stated in the table.

2 Both the IBM xSeries 330 and xSeries 340 require memory upgrades to meet the minimum RAM specifications stated in the table.


Hardware Specifications for the IBM xSeries Servers

Before You Begin the Cisco CallManager Release 3.1 Installation


Note For instructions on how to mount the server and connect it to a power source, refer to the documentation shipped with the server.


You do not receive a monitor with any Cisco Media Convergence Server, customer-provided Compaq DL320 or DL380, or IBM xSeries server. The MCS-7820 and MCS-7822 include a keyboard and mouse, but the MCS-7830, MCS-7825, and MCS-7835 do not. During initial startup and configuration of the server and Cisco CallManager, you must supply a monitor and, if necessary, a keyboard and mouse.

The Cisco Media Convergence Server, customer-provided Compaq DL320 or DL380, and IBM xSeries server ship with a blank hard drive. When you install Cisco CallManager Release 3.1, you use four of the following seven CD-ROMs, depending on your server type:

Cisco IP Telephony Server Operating System Hardware Detection CD-ROM (CD #1), required for all servers

Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2), required for upgrades via CD-ROM; installs Windows 2000 Service Pack 2, IIS Security Update, and IIS Security Update 2

Cisco IP Telephony Server Operating System Installation and Recovery CD-ROM (CD #3)

Cisco IP Telephony Server Operating System Installation and Recovery CD-ROM (CD #4)

Cisco IP Telephony Server Operating System Installation and Recovery CD-ROM (CD #5)


Note You will use only one of the Cisco IP Telephony Server Operating System Installation and Recovery CD-ROMs (either CD #3, #4, or #5). During the operating system installation, you receive a prompt to insert the appropriate CD-ROM into the CD-ROM drive.


Cisco CallManager 3.1 Installation and Recovery CD-ROM (not numbered), required for upgrades, backups, restorations, and installations on all servers

Cisco CallManager Music On Hold 3.1 CD-ROM (not numbered)

Before you begin installing Cisco CallManager for a distributed call-processing system, you should plan your system configuration.You can distribute the call-processing load for your system across multiple Cisco CallManagers as a single cluster. A cluster comprises a set of Cisco CallManagers that share the same database.

In a Cisco CallManager distributed system, one server maintains the master, or publisher, database, and all others in the cluster maintain subscriber databases. Subscriber databases provide replicates 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.

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 you want. For more information on planning a Cisco CallManager distribution system, refer the Cisco CallManager System Guide or online help in the Cisco CallManager application.


Note Make sure you connect your server to the network before you begin the installation. The special, limited edition of Windows 2000, intended for use with Cisco CallManager only, will not install if you do not connect the server to the network.



Note The MCS-7825 contains two network interface cards (NIC), but Cisco CallManager only supports one NIC. When you connect the server to the network, use the lower NIC connector because the upper connector is disabled during the installation.

The IBM xSeries 330 server contains two network interface cards (NIC), but Cisco CallManager only supports one NIC. When you connect the server to the network, use the upper NIC connector because the lower connector is disabled during the installation.



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.

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

When you begin the installation, you boot the server from the Cisco IP Telephony Server Operating System Hardware Detection CD-ROM (CD #1). After the system boots, the Cisco IP Telephony Applications Server QuickBuilder installation utility, located on the CD-ROM, loads automatically and guides you through the installation process. Cisco IP Telephony Applications Server QuickBuilder performs several preinstallation tasks including preparing your server hard drive and loading server configuration information. If necessary, it upgrades your system BIOS to a recommended version to support Windows 2000. Cisco IP Telephony Applications Server QuickBuilder then automatically installs the following software applications:

Microsoft Windows 2000 Server, intended for use with Cisco CallManager only, does not fully function for general use.

Microsoft SQL Server 7.0 Standard Edition, Service Pack 2

DC Directory 2.4

Cisco CallManager Release 3.1

With the appropriate CD-ROM in place, the server automatically begins installing the operating system, essential software, and Cisco CallManager, prompting you to insert the Cisco CallManager 3.1 Installation and Recovery CD-ROM when necessary. When you choose the CallManager Components option from the CallManager Components window, the Cisco TFTP Server, database, and Cisco CallManager service automatically install. When you choose to install the Cisco CallManager service, you automatically install the following services/features:

Cisco CallManager Serviceability Application

Cisco Telephony Call Dispatcher

Cisco CTI Manager

Cisco RIS Data Collector

Cisco User Logout Service

When you choose to install Cisco CallManager Web Components, you install the web application, Cisco CallManager Administration. This application allows you to perform tasks like adding Cisco CallManager users or installing and configuring plugins associated with Cisco CallManager. When you choose to install the Optional Components, you install 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. When Cisco CallManager services activate, the installation process places them in a stopped state. After the installation completes, the services activate and start. For information on starting and stopping services, refer to the Cisco CallManager Administration Guide or to online help in the Cisco CallManager application.

During the installation process, you receive prompts telling you to enter important configuration information about the server, such as the server name and IP address.You can complete the initial power up more efficiently if you gather all the necessary configuration information before beginning the installation process. The following information applies:

Cisco 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 you have purchased, and it prevents other supplied software from being installed for general use. The product key comprises alphabetical letters only. It contains no numbers or special characters. Table 3 on page page 10 shows the product key, and it also appears in each step procedure where you are prompted to enter it.

The product key provided in this document allows you to install Cisco CallManager Release 3.0 and 3.1 only. To install another Cisco IP telephony product, you must purchase the product and obtain the appropriate product key.

User and organization name

Registering the software product that you are installing requires user and organization name.

Computer name

Assign a unique network name of 15 characters or less for this server. It may contain alpha and numeric characters, hyphens (-), and underscores (_), and it must begin with an alphabetical character. You should follow your local naming conventions, if applicable.


Caution Due to a restriction in Microsoft SQL Server 7.0, you cannot change the Windows 2000 computer name after installation. If the computer name is changed, you must reinstall the server. Make sure the name that you assign is the permanent server name.

Workgroup

This entry records the name of the workgroup of which this computer is a member. A workgroup comprises a collection of computers that have the same workgroup name. Ensure this entry of 15 characters or less follows the same naming conventions as the computer name.

Domain suffix

Always enter the Domain Name System (DNS) domain suffix in the format "mydomain.com" or "mycompany.mydomain.com." If you are not using DNS, use a fictitious domain suffix, such as acme.com.

TCP/IP properties

Assign an IP address, subnet mask, and default gateway. Because the IP addresses that you assign are permanent properties, you should not change them after installation.

Cisco recommends choosing static IP information, which ensures that the Cisco CallManager server obtains a fixed IP address. With this selection, Cisco IP phones can register with Cisco CallManager when you plug the phones into the network.

If you choose to use Dynamic Host Configuration Protocol (DHCP), Cisco Technical Assistance Center (TAC) insists that you reserve an IP address for each Cisco CallManager server in the DHCP server scope. This action prevents the release or reassignment of IP addresses. If you do not reserve IP addresses through the DHCP server scope, the DHCP server may assign a different address to the Cisco CallManager server if the server is disconnected from, and then reconnected to, the network. To return the Cisco CallManager server to its original IP address, you would have to reprogram the IP addresses of the other devices on the network. For information on DHCP option settings, refer to the Cisco CallManager Administration Guide.

Domain Name System (DNS)

Identify a primary DNS server for this optional field.


Caution Before you begin installing multiple servers in a cluster, you must have a name resolution method in place, such as Domain Name System (DNS), Windows Internet Name Server (WINS), or local naming using a configured lmhosts file. If you use DNS, make sure the DNS server contains a mapping of the IP address and hostname of the server that you are installing before you begin the installation. If you use local name resolution, ensure the lmhosts file is updated on the existing servers in the cluster before beginning the installation on the new subscriber server; then, you must add the same information to the lmhosts file on the new server during installation, as instructed in the procedure.

By default, the phones attempt to connect to the Cisco CallManager using DNS. Therefore, if you use DNS, make sure the DNS contains a mapping of the IP address and the fully qualified domain name of the Cisco CallManager server. If you do not use DNS, use the server IP address instead of a server name for the phones to register with the Cisco CallManager. If you choose not to use DNS, install Cisco CallManager normally and then refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application for information on changing the server name.

Windows 2000 Simple Network Management Protocol (SNMP) agent

The Windows 2000 SNMP agent provides security through the use of community names and authentication traps. All SNMP implementations universally accept the default name "public." You should change this name to limit access.

Database server

Determine whether this server will be configured as a publishing database server or a subscriber database server. This decision designates a permanent selection. If you want to reassign the database server type at a later date, you must reinstall the Cisco CallManager server.


Caution If you are configuring a subscriber database server, make sure 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 the server that you are installing can connect to the publishing database server during the installation. This connection facilitates copying the publisher database from the publisher server to the local drive on the subscriber server. You must supply the name of the publishing database server and a username and password with administrator access rights on that server. If the publisher server cannot be authenticated during the installation for any reason, the installation will not continue.

Backup server or target

Determine whether this server will be configured as a backup server or a backup target.

The backup server actually performs the backup operation. It stores the backup data in the local directory, local tape drive, or network directory that you specify. If you choose a network directory as destination for the backup server, the directory must be shared in Windows 2000. A backup target contains the data to be backed up. You can choose more than one target but only one server. If a server is configured as a backup server, Cisco CallManager will automatically add it to the backup target list.

New password for the system administrator

Cisco CallManager Release 3.0 and later support password protection. At the end of the installation, a prompt asks you to supply a new password for the system administrator.


Note You must enter the same Administrator password for the publisher and all subscribers in the cluster, so Cisco CallManager database replication occurs.


Table 3 shows the configuration information required for installing software on your server. Complete all fields unless otherwise noted. Gather this information for each Cisco CallManager server that you are installing in the cluster. Make copies of this table and record your entries for each server in a separate table. Have the completed lists with you when you begin the installation.

Table 3 Configuration Data for Cisco IP Telephony Application Servers Running Cisco CallManager

Configuration Data
Your Entry

Cisco Product key

BTOO VQES CCJU IEBI

User name

                                                          

Name of your organization

                                                         

Computer name

                                                          

Workgroup

                                                            

NT domain (optional)

                                                         

DNS Domain suffix

                                                               

Current time zone, date, and time

                                                                    

SNMP community name

                                                                       

DHCP parameters

Cisco recommends that you program a fixed IP address in TCP/IP properties for the server instead of using DHCP.

TCP/IP properties (required if DHCP is not used)

IP address

Subnet mask

Default gateway

                                                                      

DNS servers (optional)

Primary

Secondary

WINS servers (optional)

Primary

Secondary

                                                                         

Database server (specify one)

Publisher

Subscriber

If you are configuring a subscriber server, supply the username and password of the publishing database server:

username of publisher

password of publisher

                                                                                 

Backup (specify one or both)

Server

Target

                                                                                  

New system administrator password

                                                                                       


Connecting a Monitor, Keyboard, and Mouse to the Server

You do not receive a monitor with any Cisco Media Convergence Server or IBM xSeries server. The MCS-7820 and MCS-7822 include a keyboard and mouse, but the MCS-7830, MCS-7825, and MCS-7835 do not. You must supply a monitor and, if necessary, a keyboard and mouse to use during initial startup and configuration of the server and Cisco CallManager.

Plug the mouse and keyboard into the standard mouse and keyboard connectors marked on the back of the server. Plug the monitor cable into the monitor connector on the back of the server.

Performing the Cisco CallManager Release 3.1 Installation

The entire installation process, excluding post-installation tasks, takes 60 to 90 minutes per server. To perform an installation on a Cisco Media Convergence Server or customer-provided server meeting approved Cisco configuration standards, see the following sections:

Starting the Operating System Installation

Entering Server Configuration Data and Completing the Operating System Installation

Installing Cisco CallManager and Related Applications

Starting the Operating System Installation

In this portion of the installation, which takes about 20 minutes, you will perform the following tasks:

Connect a monitor, keyboard, and mouse to the server and insert Cisco IP Telephony Server Operating System Hardware Detection CD-ROM (CD #1).

Choose the type of installation (new, recovery, upgrade) that you plan to perform.

Enter the Cisco Product key.

Read and agree to the terms in the End User License Agreement.


Caution Before installation, the process erases the server hard drive and all data and configuration information, if present. If you are installing Cisco CallManager on an existing server and you want to preserve the data on the hard drive, do not perform this procedure.

During installation, the server reboots several times. Do not power off the server at any time during this process, unless instructed. Any unexpected power interruption during the installation process could prevent proper completion of the configuration and might prevent the operating system from restarting.

During the Cisco IP Telephony Applications Server QuickBuilder installation, the server performs several system reboots. To perform an installation, make sure the server is turned off and perform the following steps:

Installing the Operating System on the Cisco Media Convergence Servers and Customer-Provided Compaq DL 320 or DL380 Servers

Perform the following steps to begin the operating system installation:

Procedure


Step 1 If necessary, connect a monitor, keyboard, and mouse to the server as described in "Connecting a Monitor, Keyboard, and Mouse to the Server" section.

Step 2 Locate Cisco IP Telephony Server Operating System Hardware Detection CD-ROM (CD #1).

Step 3 Depending on your server, perform the following procedure:

For an Existing Server

If you are installing a server that has had a previous installation, insert the CD-ROM into the CD-ROM drive and then restart the system immediately. Then, go to Step 5.

For a New Server

If you are installing a new server, you will need to boot from the CD-ROM. This means that you must power up the server and then insert the CD-ROM early in the startup process.

Once you insert the CD-ROM into the CD-ROM drive, complete the following task:

a. For the MCS-7820 or MCS-7822, go to Step 7.

b. For the MCS-7835 or MCS-7830, go to Step 9.

c. For the MCS-7825, go to Step 4.


Note The first time you start up a new server, you will not see any indication that the startup process is operating normally. The startup on a new server takes longer than on preinstalled servers. You may wait as long as 3 minutes before you receive a video connection.


Step 4 If you are installing a new MCS-7825, the ROM Based Setup configuration begins prior to reading the Operating System Installation and Recovery CD-ROM.


Caution Cisco strongly recommends choosing the following selections from the ROM Based Setup Utility screens. Other selections may impact the stability of Cisco CallManager. If you inaccurately choose a selection from one of the ROM Based Setup Utility screens, press F9 during the bootup process to return to the ROM Based Setup Utility and correct the selection.

a. The first ROM Based Setup Utility screen offers a language selection menu. Press Enter to choose English. Choosing a language other than English does not change the language seen during the installation process. English remains the only supported language at this time.

b. The second ROM Based Setup Utility screen lists several operating system choices. Using the arrow keys, choose Windows 2000 from the operating systems selection menu. Press Enter. Windows 2000 remains the only supported operating system.

c. Because the third ROM Based Setup Utility screen is preset at the factory, you cannot alter it. Press ESC to close the menu and continue.

d. On the fourth ROM Based Setup Utility screen, enter the correct date and time and then press Enter.

e. On the final ROM Based Setup Utility screen, a message states that the system configuration is complete. Press F10 to exit the utility and automatically reboot the system.

f. To proceed with the installation, go to Step 6.

Step 5 If your server is not new (the hard drive is not blank), the Cisco IP Telephony Applications Server QuickBuilder welcome window opens. Click Next.

Step 6 The Type of Installation window opens. Choose New Installation or Server Replacement and then click Next.

On an existing MCS-7825 (the hard drive is not blank), a second New Installation or Server Replacement window opens. Click Next.

Step 7 The next window displays a warning that your configuration and data will be overwritten. Click Next.

Step 8 When a message prompts you to cycle the system power, turn the server off. Wait 10 seconds and then power up the server. The startup may take several minutes.

Step 9 If the New Installation and Replacement window opens, click Next.

Step 10 If the Configuration Process window opens with a message about hardware detection, click Next. The system reboots automatically.

Step 11 If you are installing the MCS-7820, MCS-7822, or MCS-7825, go to Step 13. If you are installing the MCS-7830 or MCS-7835, a second Configuration Process window opens with a message about conducting an initial hardware configuration. Click Next. The system reboots again automatically.

Step 12 When a message prompts you to power off and on the server to complete the installation, turn the server off. Wait 10 seconds and then power up the server.

Step 13 Enter your product key BTOO VQES CCJU IEBI; then, click Next.

Step 14 The End User License Agreement window opens. Read through the contents of the agreement. If you consent to the terms of the agreement, click I Agree. If you do not consent, you must terminate the installation by clicking Exit.

Step 15 Depending on the state of your server, the Server Replacement Option window may or may not appear. If it does appear, make sure the I am recovering a system from backup check box is unchecked and then click Next. If this window does not appear, go to Step 16.

Step 16 In the Ready to Complete Installation window, click Next. This process takes about 1 minute to complete.

You do not need to reboot the system before entering server configuration data. Continue configuring the server by completing the steps in "Entering Server Configuration Data and Completing the Operating System Installation" section.


Installing the Operating System on a Customer-Provided IBM xSeries Server

Perform the following steps to begin the operating system installation:

Procedure


Step 1 If necessary, connect a monitor, keyboard, and mouse to the server as described in "Connecting a Monitor, Keyboard, and Mouse to the Server" section.

Step 2 Locate Cisco IP Telephony Server Operating System Hardware Detection CD-ROM (CD #1).

Step 3 Insert CD #1 into the CD-ROM drive as soon as you can do so. This means that you must power up the server and then insert CD #1 early in the startup process.


Note The first time you start up a new server, you will not see any indication that the startup process is operating normally. The startup on a new server takes longer than on preinstalled servers. You may wait as long as 3 minutes before you receive a video connection.


Step 4 If you see the post startup error message about memory upgrades, you must perform the following procedure:

a. The Post Startup Error(s) window displays a message about memory upgrades. Using the arrow keys, choose Continue and then press Enter.

b. If the Configuration Error window appears, use the arrows keys to choose Continue; then, press Enter.

c. The Configuration/Setup Utility window displays a variety of configuration options. Using the arrows keys, choose Save Settings. Press Enter.

d. The Save Settings window displays a message about saving the current settings. Press Enter to continue.

e. You automatically return to the Configuration/Setup Utility window. Using the arrows keys, choose Exit Setup and then press Enter.

f. When the Exit Setup window displays, use the arrow keys to choose Yes, exit the Setup Utility. Press Enter. The system reboots automatically.

g. With a new server, the IBM BIOS upgrade utility runs; then, the server reboots automatically. If your server is new (the hard drive is blank), go to Step 7. If your server is not new (the hard drive is not blank), continue to Step 5.

Step 5 If your server is not new (the hard drive is not blank), the Cisco IP Telephony Applications Server QuickBuilder welcome window opens. Click Next.

Step 6 If the Type of Installation window opens, choose New Installation or Server Replacement and then click Next.

On an existing IBM xSeries 330 or 340 server (the hard drive is not blank), a second New Installation or Server Replacement window opens. Click Next.

Step 7 The Configuration Process window displays a warning that your configuration and data will be overwritten or that your data does not exist. Click Next. The system automatically reboots.

Step 8 Enter your product key BTOO VQES CCJU IEBI; then, click Next.

Step 9 The End User Server License Agreement window opens. Read through the contents of the agreement. If you consent to the terms of the agreement, click I Agree. If you do not consent, you must terminate the installation by clicking Exit.

Step 10 Depending on the state of your server, the Server Replacement Option window may or may not appear. If it does appear, make sure the I am recovering a system from backup check box is unchecked and then click Next. If this window does not appear, go to Step 11.

Step 11 In the Ready to Complete Installation window, click Next. This process takes about 2 minutes to complete.

You do not need to reboot the system before entering server configuration data. Continue configuring the server by completing the steps in "Entering Server Configuration Data and Completing the Operating System Installation" section.


Entering Server Configuration Data and Completing the Operating System Installation

In this portion of the installation, which takes about 30 minutes, you will perform the following tasks:

Enter your user name, name of organization, computer name and DNS suffix.

Join an NT domain or remain a workgroup member.

Choose the appropriate time zone, date, and time.

Enter the server IP address, subnet mask, and default gateway.

Enter the primary and secondary IP addresses for DNS and WINS (or configure LMHosts).

Change the default community public name to ensure security within the Windows 2000 Simple Network Management Protocol (SNMP) agent.

Enable or disable Telnet and Terminal services.

Insert the Cisco IP Telephony Server Operating System Installation and Recovery CD-ROM (CD #3, CD #4, or CD #5) to complete the installation of the Windows 2000 operating system.

Using the data that you collected in Table 3, complete the following steps to configure each server:

Procedure


Step 1 The Cisco IP Telephony Applications Server Configuration Wizard begins. Click Next to continue.

Step 2 After the Cisco Registration window opens, enter your user name, the name of your organization, a computer name, and DNS suffix; then, click Next.


Caution Ensure the computer name comprises a unique network name of 15 characters or less. It may contain alpha and numeric characters, hyphens (-), or underscores (_) and must begin with an alphabetical character. The workgroup name follows the same naming conventions as the computer name.

Due to a restriction in Microsoft SQL Server 7.0, you cannot change the Windows 2000 computer name after installation. If the computer name is changed, you must reinstall the server. Make sure the name that you assign is the permanent server name.


Note Ensure the DNS domain suffix is entered in the format "mydomain.com" or "company.mydomain.com." If you are not using DNS, use a fictitious domain suffix, such as acme.com.


Step 3 You choose to become a workgroup member or to join an NT domain. If you want to join a domain, enter the NT domain name and the username and password of a user with administrator privileges on this server; then, click OK.

Step 4 Choose the appropriate time zone for the server. Set the current date and time; then, click Next.

Step 5 The Static Dynamic IP Address window opens. Cisco recommends that you choose Use the following IP address when prompted about the method used to configure the IP information.


Note Cisco recommends choosing static IP information, which ensures that the Cisco CallManager server obtains a fixed IP address. With this selection, Cisco IP phones can register with Cisco CallManager when you plug the phones into the network.

If you choose to use DHCP, Cisco Technical Assistance Center (TAC) insists that you reserve an IP address for each Cisco CallManager server in the DHCP server scope. This action prevents the release or reassignment of IP addresses. If you do not reserve IP addresses through the DHCP server scope, the DHCP server may assign a different address to the Cisco CallManager server if the server is disconnected from, and then reconnected to, the network. To return the Cisco CallManager server to its original IP address, you would have to reprogram the IP addresses of the other devices on the network. For information on DHCP option settings, refer to the Cisco CallManager Administration Guide.


Step 6 Enter the server IP address, subnet mask, and default gateway in the appropriate fields.


Caution If you are installing multiple servers in a cluster, you must have a name resolution method in place. If you are not using DNS or WINS, you must configure local name resolution by updating the lmhosts file with IP address and hostname information for every server in your cluster, as instructed in Step 8.

Step 7 If you are using DNS or WINS, click the Use the following DNS and WINS server addresses radio button; then, enter the IP addresses of the primary and secondary DNS servers and primary and secondary WINS servers. Click Next and continue to Step 9.

If you are not using DNS, leave the DNS and WINS fields empty. Make sure that the Use the following DNS and WINS server addresses radio button is chosen, so you can configure local name resolution; then, click Next.

Step 8 If you did not enter DNS or WINS server information in the previous window, and if you are installing multiple servers in a cluster, you must configure local name resolution by updating the lmhosts file, so it contains a mapping of the IP address and hostname of each server in the cluster. Perform the following steps to configure the lmhosts file:

a. In the LMHost window, check the Check if you want to edit LMHosts file check box.

b. Enter the IP Address and Server Name.

For example:

172.16.0.10 dallascm1

c. Click Add Server.

d. Click Next to continue.


Note The Windows 2000 SNMP agent provides security through the use of community names and authentication traps. All SNMP implementations universally accept the default name "public." You should change this name to limit access.


Step 9 To ensure security within the Windows 2000 SNMP agent, Cisco recommends that you change the default public community name. Enter a new name and then click Next.

Step 10 The installation process enables Telnet and Terminal services automatically. If you want, you can disable these services; then, click Next.

Step 11 The CD-ROM drive automatically opens. Remove CD #1 from the CD-ROM drive and insert the Cisco IP Telephony Server Operating System Installation and Recovery CD-ROM (CD #3, CD #4, or CD #5, depending on your server) into the CD-ROM drive. The configuration process continues automatically after detection of the appropriate CD-ROM. The server begins an installation and reboot process that takes about 6 minutes to complete.

Step 12 The CD-ROM drive automatically opens. When prompted, remove CD #3, CD #4, or CD #5 and press any key to reboot. Windows 2000 setup begins and takes about 10 minutes to complete. Do not power down the server or press any keys during setup.


Continue configuring the server by following the steps in "Installing Cisco CallManager and Related Applications" section.

Installing Cisco CallManager and Related Applications

In this portion of the installation, which takes about 45 minutes, you will perform the following tasks:

Insert the Cisco CallManager 3.1 Installation and Recovery CD-ROM.

Choose the services you want to activate.

Choose whether you are installing a publisher or subscriber database server.

Configure the Cisco IP Telephony Applications Backup Utility settings.

Perform the following steps to complete the installation:

Procedure


Step 1 When prompted to do so, insert the Cisco CallManager 3.1 Installation and Recovery CD-ROM. The installation script automatically continues loading from the CD-ROM.

Step 2 In the Welcome to the Cisco CallManager Installation Wizard window, click Next.

Step 3 In the CallManager Components window, choose the services that you want to activate in this initial installation; then, click Next. When Cisco CallManager services are activated, the installation process places them in a stopped state. All services activate and start upon completion of the installation. For information on starting services, refer to the Cisco CallManager Administration Guide or to online help in the Cisco CallManager application.


Note The following information applies to the services in the CallManager Components window. The Cisco IP Voice Media Streamer contains the Media Termination Point (MTP), music on hold (MOH), and conference bridge services. To add or remove services later, refer to the "Activating Cisco CallManager Services" section.



Caution You automatically install the database with any selection from the CallManager Components window. 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 selection, only Cisco CallManager Web Components and the database install on the standalone database 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, the GUI-based web application, on the server.

Figure 1 shows an example of the CallManager Components window.

Figure 1 CallManager Components Window


Note The publisher database serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database. If you are configuring a subscriber database server, make sure the server you are installing can connect to the publishing database server before the installation can continue. This connection is necessary because the subscriber server attempts to connect to the publisher server, so that the publisher database can be copied from that server to the local drive on the subscriber server. To make sure a good connection exists between the servers, issue a ping command from the subscriber server to the publisher server before you try to authenticate to it. If you are using DNS, use a fully qualified domain name (for example, `hostname.acme.com') with the ping command. If the ping command is not successful, you must exit the installation program, fix the problem, and begin the installation process again.


Step 4 You must decide whether you are upgrading the publisher database server or subscriber database server. If you are upgrading the publisher database server, choose I am upgrading/installing the CallManager Publisher. Click Next and go to Step 5.

Figure 2 shows an example of the Cisco CallManager Database Distribution window.

Figure 2 Cisco CallManager Database Distribution

If a publisher database already exists and you are configuring a subscriber database server, choose I am upgrading/installing the CallManager Subscriber. By default, the publisher database server associated with the subscriber displays in the hostname publisher field. You may choose another publisher by clicking Browse. After you choose the appropriate publisher, click Next and go to Step 5.

Step 5 Either the Directory Server Configuration window or the Authentication to the Publishing Database window opens, depending on which server you chose in Step 4. If you chose I am upgrading/installing the CallManager Publisher, the Directory Server Configuration window opens and prompts you for the Directory Manager password. Enter the password in the Password field; then, enter the same password again in the Confirm Password field. Click Next, and go to Step 6.

If you chose I am upgrading/installing the CallManager Subscriber, an authentication window opens and prompts you to enter usernames and passwords for a Windows 2000 user with administrative privileges and a SQL Server user with SQL Server administrative privileges on the publishing database server. Enter the account information in the appropriate fields as prompted and then click Next, and go to Step 6. The system connects to the publishing database server.

Figure 3 shows an example of the authentication window.

Figure 3 Authentication to Publishing Database

Step 6 You have completed the configuration of Cisco CallManager and the database server. The Cisco CallManager and other included software are ready to be installed. Click Next. This part of the installation takes about 30 minutes.

Step 7 The Cisco IP Telephony Applications Backup Utility Setup loads automatically. You must specify whether this server will act as a backup target or the backup server during the backup and restore operation.

The backup server actually performs the backup operation. It stores the backup data in the directory or tape drive destination that you specify. If a server is configured as a backup server, Cisco CallManager automatically adds it to the backup target list.

A backup target acts as a server that contains data to be backed up. You can choose more than one target, but you can choose only one server.

Choose either Server or Target and then click OK.


Note Cisco strongly recommends that you use the Cisco IP Telephony Applications Backup Utility to perform backups and that you use no third-party backup software. However, if you do not want to use the Cisco IP Telephony Applications Backup Utility, complete the installation as instructed and then stop the service called "stiBack for Cisco IP Telephony Applications." To stop the service, choose Start > Run, enter services.msc /s, choose the service in the main window, and click Stop Service.


Step 8 If you chose Target in the previous step, a message appears indicating that the setup is complete. You will need to configure this server as a Cisco CallManager target on the backup server. Click OK and then go to Step 16.

If you chose Server in the previous step, continue with Step 9.

Step 9 In the Backup Utility Configuration window, add the name of any additional Cisco CallManager servers you want to back up by clicking Add, entering the server name, and then clicking OK. Click Delete to remove servers from the target list. If you want to add a remote server, you must install it and connect it to the network before you add it to the target list. A prompt asks you to enter a username and password with administrator access rights on the remote server and then click Verify.


Note The Backup Utility attempts to connect to the remote server. If the remote server is not found, the authentication fails. The server name remains in the target list but may not be accessible.


Step 10 Click the Destination tab. Choose a destination location where the backup data will be stored. You must choose a destination for backups that are to be performed. No default destination setting exists.

Figure 4 shows an example of the Destination tab in the Cisco IP Telephony Applications Backup Utility.

Figure 4 Destination Tab in the Cisco IP Telephony Applications Backup Utility Configuration Window


Note If you choose a network directory as the backup destination, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click on the directory folder icon that you want to share, click Sharing..., click Share this folder, and then click OK.

You may click the Tape device radio button only if you have a MCS-7835 or IBM xSeries 340 server. Only the MCS-7835 and IBM xSeries 340 server have a tape drive available. You must click Network directory or Tape device to use the Cisco IP Telephony Applications Restore Utility on your server.


Step 11 Choose Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network or local directory, you can enter the path and directory name or choose it from a browse box by clicking Browse. For network directories, you must supply a username and password with administrator access rights on that server. In the tape device box, only tape drives configured in Windows NT or Windows 2000 appear. To add new devices, click Add device....

Step 12 Click the Schedule tab. Figure 5 shows an example of the Schedule tab in the Cisco IP Telephony Applications Backup Utility Configuration window.

Figure 5 Schedule Tab in Cisco IP Telephony Applications Backup Utility Configuration Window

Step 13 Choose the days and times that you want the backup to run. The default is 2:00 am Tuesday through Saturday. You can also choose the length of the system log in days; then, click OK.


Caution You should schedule Cisco CallManager backups to occur during off-peak hours because CPU utilization is high during the backup process.

Step 14 The Performance tab allows the operating system to modify the allocation of CPU resources during the backup process. Click the Performance tab to prioritize when the backup service (stiBack.exe) will run during the next backup. Three options, Low, Normal, and Below Normal appear in the window. Before you click one of the three options, consider the following information:

a. Clicking the Normal radio button accepts the default priority associated with the Windows 2000 or Windows NT 4.0 server.

b. Clicking the Below Normal radio button ensures that configured services remain responsive while the backup occurs. When you click this option, which is available only on a Windows 2000 server, be aware that your backup may take longer than the Normal setting.

c. Clicking the Low radio button ensures that configured services remain completely responsive during the backup. Be aware that your backup may take longer than the Normal of Below Normal setting.

If you do not click one of the performance radio buttons, the Normal radio button serves as the default priority for the backup service (sti.Back.exe) that runs on the Windows 2000 or Windows NT 4.0 server during the next backup.

Step 15 To save your settings and exit the Backup Utility Configuration, click OK.


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 and all subscribers in the cluster, so that Cisco CallManager database replication occurs.

Step 16 A prompt asks you to enter a new password for the local Administrator account. Enter the new password in the New Password field and then enter it in the Retype Password field. Click OK.

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


Note Do not lose or forget this password. If you do, you will not be able to reconfigure the server.


Step 18 A message indicates that both passwords changed successfully. Click OK.

Step 19 Eject the CD-ROM from the CD-ROM drive, and if you want to reboot the system now, click Yes when prompted.

You have completed the Cisco CallManager installation process. Your server now becomes a Cisco IP Telephony Applications Server. See the "Performing Post-Installation Tasks" section to complete post-installation tasks.


Performing Post-Installation 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.

This section explains how to perform the following operations:

Changing Passwords for CCMAdmin and SQLSvc Accounts

Configuring Auto-Registration

Configuring DNS

Configuring the Database

Activating Cisco CallManager Services

Using the Cisco CallManager Music On Hold CD-ROM 3.1

Besides performing the preceding tasks, you need to verify that you have the latest Microsoft patches and hotfixes running on your system. To verify and download these items, click the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr

After you have performed these tasks and your Cisco CallManager is operational, you should back up your Cisco CallManager data. For information on backing up Cisco CallManager data, refer to the latest version of Backing Up and Restoring Cisco CallManager Release 3.1.

Changing Passwords for CCMAdmin and SQLSvc Accounts

The Cisco CallManager Release 3.1 installation creates two user accounts: CCMAdmin and SQLSvc. At installation, each user account receives a unique and secure default password. If you want, you may change these passwords after the installation.


Caution Make sure you set the same password for all the CCMAdmin accounts and the same password for all the SQLSvc accounts for each server in the cluster.

CCMAdmin

The CCMAdmin user provides a common administrator login account for all Cisco CallManagers in the cluster. For example, if you are logged in as CCMAdmin, you can view all the services in all the servers in the cluster in one Control Center window. To have access to all servers in the cluster simultaneously, you must ensure the password for CCMAdmin is identical on every server in the cluster.

To change the CCMAdmin password, perform the following steps:

Procedure


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

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

Step 3 Right-click on CCMAdmin and choose Set Password.

Step 4 Enter the new password in the New Password and Confirm Password fields and click OK.


SQLSvc

Only the Microsoft SQL Server service can use the SQLSvc account. The server uses it as the core account for server-to-server interaction by the Cisco CallManager system. For the service to function properly, ensure the password for the SQLSvc account is identical on all servers in the cluster.

The default SQLSvc password that is set up during installation provides an encrypted password that is unique to the cluster. It is identical on all servers in the cluster. If you change the password, make sure the passwords are identical on all servers in the cluster.


Caution Each time 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.

Perform the following steps to change the SQLSvc password:

Procedure


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

Step 2 Choose the Users folder 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 on the Services icon located in Services and Applications. The services display in the main window.

Step 7 Right-click MSSQLServer and choose Properties.

Step 8 Click the Log On tab.

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

Step 10 Right-click SQLServerAgent and choose Properties.

Step 11 Click the Log On tab.

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

Step 13 Right-click stiBack for Cisco IP Telephony Applications and choose Properties.

Step 14 Click the Log On tab.

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

Step 16 For the password changes to take affect, stop and start the preceding services: MSSQLServer, SQLServerAgent, and stiBack for Cisco IP Telephony Applications. Refer to the latest version of the Cisco CallManager Administration Guide for information on how to perform this task.

Step 17 Close the Computer Management window.

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

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

Step 20 Right-click DBL and choose Properties.

Step 21 Click the Identity tab.

Step 22 In the New Password and Confirm Password fields, enter the same password as in Step 4 and click OK.

Step 23 Right-click DBL and choose Shut Down.

Step 24 Right-click DBL and choose Start.

Step 25 Close the Computer Services window.


Configuring Auto-Registration

You can configure Cisco CallManager to automatically assign directory numbers to the phones. Directory number assignment occurs sequentially starting with the number that you specify as the starting directory number and ending with the number that you specify as the ending directory number. For example, if the range of directory numbers that you specify is 1000 through 2000, Cisco CallManager assigns the phones directory numbers of 1000, 1001, 1002, and so on, until the ending directory number of 2000 is reached. For more information on configuring Auto-Registration, refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.

Configuring DNS

Although DNS or WINS should be used during the installation of multiple Cisco CallManagers, Cisco strongly recommends against using a DNS name resolution server in a Cisco CallManager production environment unless you are confident about the reliability and availability of your DNS server and network structure.

If you use a DNS server, your call-processing system depends on the accessibility of that server. For example, if the DNS server goes down or the connection between it and the Cisco CallManager is broken, the phones must rely on cached server name information. If the phones have been reset and have lost their cached information, they might be unable to resolve the DNS name of the Cisco CallManager server, and call processing may be interrupted.

To prevent this situation, Cisco recommends that you disable DNS after installation and change the Cisco CallManager server name to an IP address using the procedures that follow.


Caution If you want to use DNS on your Cisco CallManager system, make sure that the Reverse DNS Lookup function is configured and enabled. This action is necessary whether you use the IP address or the DNS name for your Cisco CallManager server name.

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

Procedure


Step 1 Choose Start > Settings > Network and Dial-up Connections.

Step 2 Right-click Local Area Connection and choose Properties.

Step 3 Choose Internet Protocol (TCP/IP).

Step 4 Click Properties.

Step 5 Click Advanced.

Step 6 Click the DNS tab.

Step 7 Remove any entries in the DNS server addresses list by choosing the entry and clicking Remove.

Step 8 Uncheck the Register the connection's address with DNS check box.

Step 9 Click OK.


To change the Cisco CallManager server name to the IP address, perform the following steps:

Procedure


Step 1 Choose Start > Programs > Cisco CallManager 3.1 > CallManager Administration and log in with administrator privileges.

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

Step 3 From the list of Cisco CallManagers on the left, choose the server you are configuring.

Step 4 Edit the contents of the DNS or IP Address field, so that it contains the server IP address. Click Update.


Configuring the Database

After installing Cisco CallManager, you can use Cisco CallManager Administration to begin configuring the database. The Cisco CallManager database contains information and parameters relating to the system as a whole, to connected devices, and to individual users. For more information about configuring the Cisco CallManager database, refer to the Cisco CallManager Administration Guide, the Cisco CallManager System Guide, or online help in the Cisco CallManager application.

Activating Cisco CallManager Services

Although Cisco CallManager services were installed on your server during the installation process, only those that you chose during the installation were activated.


Caution Do not deactivate the Cisco CallManager service using the following procedure. If it is inadvertently deactivated, contact the Cisco Technical Assistance Center (TAC). See the "Technical Assistance Center" section at the end of this document for more information.

To activate additional Cisco CallManager services, or to deactivate existing services, perform the following steps:

Procedure


Step 1 Choose Start > Programs > Cisco CallManager > Cisco Service Configuration.

Step 2 Choose the check box for each Cisco CallManager service that you want to activate. If a service is currently activated and you uncheck it, Cisco CallManager shuts it down, removes it from the service registration table, and makes it unavailable for use. Click Apply.

Step 3 Click Exit.

Step 4 After you activate a service, you must start it. For information on starting services, refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.


Using the Cisco CallManager Music On Hold CD-ROM 3.1

When you install Cisco CallManager Release 3.1 on your server, a default music on hold sample automatically installs for customer use. To increase your music on hold (MOH) selection, you may also install the Cisco CallManager Music On Hold CD-ROM 3.1 that ships with your Cisco IP Telephony Applications Server, or you may download one of two zip files via the web. You may download the file, ciscocm-MusicOnHold.3-1.zip, which is a set of wav files providing the entire music selection from the CD-ROM; or, you may download the file, ciscocm-MusicOnHoldSampler.3.1.zip, which is a small set of files offering a sample of music available on the CD-ROM. Cisco recommends that you store these files locally on a server that does not run Cisco CallManager. For information on creating audio sources through the Music On Hold feature, refer to the latest version of the Cisco CallManager Administration Guide and the latest version of the Cisco CallManager System Guide.

The Cisco CallManager Music On Hold CD-ROM 3.1 contains ready-to-use MOH loops, music, and voice prompts designed for use with the music on hold (MOH) feature. All music samples and voice prompts on the CD-ROM are 16-bit PCM sampled at 16 KHz. All samples and prompts can play with good audio quality in 7960/7940 wideband mode.

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

Ongoing Server Management

The Compaq Insight Management Agent or the IBM UM Services, both SNMP agent extensions, allow you to monitor and manage the specific components of your server, such as CPU, virtual memory, and disk usage. They also monitor server temperature, fan status, power supplies, and NIC information.

On Cisco Media Convergence Servers and customer-provided Compaq servers, the drivers upgrade when you insert the latest version of the Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2) into the CD-ROM drive. For information on how to use CD #2, refer to the latest version of Upgrading Cisco CallManager Release 3.1. For driver, BIOS, or firmware upgrades on the IBM xSeries servers, contact the hardware manufacturer directly or navigate to the IBM website through the following URL: http://www.cisco.com/go/swonly/

After you install Cisco CallManager, you need to verify that you have the latest Microsoft patches and hotfixes running on your system. To verify and download these items, click the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr

Re-creating Subscriber Connections

If the connections between the publishing Cisco CallManager database and the subscribers within a cluster are broken for any reason, you cannot replicate the database to the subscribers. If you suspect a problem with subscriber connections, you should verify the status of the subscriptions or the jobs. On the publisher server, perform the following steps to verify the status of the subscribers and jobs:

Procedure


Step 1 Open SQL Server Enterprise Manager by choosing Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.

Step 2 To see the status of subscriptions, choose the Pull Subscriptions folder located in the following path: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<publication name>.

To see the status of jobs, choose the Jobs folder located in the following path: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Management/SQL Server Agent.

The Expired Subscription Cleanup service could display a red `x' under normal operation; however, if a red `x' appears next to a subscriber name or a job name other than Expired Subscription Cleanup, assume the subscriber connection is broken. You must reinitialize it.


Note The event log on the subscriber server lists SQL Server Agent errors. To view the event log, choose Start > Programs > Administration tools > Event Viewer on the subscriber server.



If you determine that one or more subscription connections are broken, you must perform the following actions:

On each subscriber server, delete and then re-create the subscriptions.

On the publisher server, reinitialize the subscriptions and start the replication snapshot agent.

On each subscriber server, perform the following steps to delete and re-create the subscriptions:

Procedure


Step 1 Open SQL Server Enterprise Manager by choosing Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.

Step 2 In the following path, choose the Pull Subscriptions folder: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<the publisher database name>.

Step 3 In the main window, right-click the subscription name and choose Delete. Click Yes to confirm.

Step 4 Right-click the Pull Subscription folder and choose New Pull Subscription....

Step 5 The Welcome to the Pull Subscription Wizard window opens. Click Next.

Step 6 If your publisher server does not appear in the publication list, click Register Server. Enter the name of the publisher server in the Server field and choose Use SQL Server authentication. Enter the SQL Server system administrator username (sa) and the password in the appropriate fields and then click OK. When your server appears in the list, go to Step 7.

Step 7 Double-click the publisher server and choose the publication name that matches the database you are configuring. Click Next.

Step 8 In the Specify Sychronization Agent Login window, choose By impersonating the SQL Server Agent account and then click Next.

Step 9 In the Specify Immediate-Updating Subscriptions window, choose Yes, make this an immediate-updating subscription and click Next.

Step 10 In the Password and Confirm password fields, enter the password for the SA (SQL Server system administrator) user.

Step 11 In the Initialize Subscription window, choose Yes, Initialize the schema at the Subscriber and click Next.

Step 12 In the Set Distribution Agent Schedule window, choose Continuously and click Next.

Step 13 In the Start Required Services window, click Next.

Step 14 Click Finish.


On the publisher server, perform the following steps to reinitialize the subscriptions and start the replication snapshot agent:

Procedure


Step 1 Open SQL Server Enterprise Manager by choosing Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.

Step 2 In the following path, choose the name of the publisher database that you are configuring: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<the publisher database name>Publications.

Step 3 In the main window, right-click the subscription name and choose Reinitialize all Subscriptions. Click Yes to confirm.

Step 4 In the following path, choose the Snapshot Agents folder: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Replication Monitor/Agents.

Step 5 Right-click the publication name that matches the database name you are configuring; then, click Start.


Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

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

http://www.cisco.com

http://www-china.cisco.com

http://www-europe.cisco.com

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships 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, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

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:

Attn Document Resource Connection
Cisco Systems, Inc.
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. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

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

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

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

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

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

P1 and P2 level problems are defined as follows:

P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.