 Feedback
|
Table Of Contents
Installing Cisco CallManager Release 3.2(2c)
Locating Related Cisco CallManager Documentation
Frequently Asked Questions about the Cisco CallManager Installation
What hardware and CD-ROMs do I receive when I purchase Cisco CallManager?
How long does it take to perform the Cisco CallManager installation?
How does the Cisco CallManager installation work?
What data must I provide to configure the server?
May I install other software besides Cisco CallManager on the server?
May I run a web browser on the server?
May I configure a server in the cluster as a Domain Controller?
What preinstallation tasks should I perform?
How do I connect the keyboard and mouse to the server?
How do I connect the server to the network?
How do I disable Cisco-approved McAfee antivirus services?
Starting the Operating System Installation
Installing the Operating System on Servers When the Hard Drive is Not Blank
Installing the Operating System on Servers When the Hard Drive is Blank
Entering the Product Key and Reviewing the License Agreement
Entering Server Configuration Data and Completing the Operating System Installation
Installing Services and the Publisher Database or Subscriber Server
Installing the Cisco IP Telephony Applications Backup
Performing Post-Installation Tasks
Verifying Services, Patches, and Hotfixes
Viewing the Component Versions Installed on the Server
Changing the Password for the SQLSvc Account
Using the Cisco CallManager Attendant Console
Activating Cisco CallManager Services
Enabling Cisco-Approved McAfee Antivirus Services
Using the F: Drive on the MCS-7845-1400 to Collect Trace Files
Using the Cisco CallManager Music On Hold CD-ROM or Download
Re-creating Subscriber Connections
Obtaining Technical Assistance
Installing Cisco CallManager Release 3.2(2c)
Cisco CallManager Release 3.2 on the Cisco Media Convergence Server (MCS) or approved customer-provided server provides a network business communications system for high-quality telephony over IP networks. After you install Cisco CallManager on the 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 this document as a guide for installing and configuring Cisco CallManager Release 3.2 on the Cisco Media Convergence Server, customer-provided Compaq DL320 and DL380 servers, or customer-provided IBM xSeries 330, 340, and 342 servers. Cisco requires that any CD-ROM purchased for installation on a customer-provided server be installed on a server meeting approved Cisco configuration standards.
Contents
Preinstallation Tasks and Information
•
Locating Related Cisco CallManager Documentation
•
–
–
–
–
–
–
–
–
–
–
Operating System Installation Tasks
•
–
–
–
•
Cisco CallManager Installation Tasks
•
•
Post-Installation Tasks
•
•
•
•
•
•
•
•
•
•
Conventions
Consider the following documentation conventions as you review this installation document:
Note
Caution
Locating Related Cisco CallManager Documentation
Cisco strongly recommends that you review the following documents before you perform the Cisco CallManager installation:
•
This document lists and describes the system requirements, new features, changed information, documentation updates, and open caveats for Cisco CallManager. Cisco provides a version of this document that matches the version of the installation document.
•
The Cisco CallManager Administration Guide provides step-by-step instructions for configuring, maintaining, and administering the Cisco CallManager voice over IP network.
The Cisco CallManager System Guide provides descriptions of the Cisco CallManager system and its components, configuration checklists, and links to associated Cisco CallManager Administration Guide procedures.
•
This document also provides descriptions of Cisco CallManager serviceability and remote serviceability and step-by-step instructions for configuring alarms, traces, and other reporting.
•
This document provides information on using the Bulk Administration Tool (BAT) to perform bulk add, update, and delete operations on phones, users, gateways, and ports.
•
This document describes how to back up Cisco CallManager data and restore the Cisco IP Telephony Applications Server and Cisco CallManager data. This document also provides a list of data that is backed up during the scheduled or user-invoked backup.
•
To ensure continued functionality with interfacing Cisco IP telephony applications after the Cisco CallManager installation, refer to the Cisco CallManager Compatibility Matrix, which provides solutions information and workarounds for applications that are integrated with Cisco CallManager.
Affected applications may include Cisco Conference Connection, Cisco SoftPhone, Cisco uOne, Cisco Unity, Cisco 186 Analog Telephony Adapter, Cisco 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 installation guidelines, for Cisco IP Contact Center (IPCC) systems. If you use Cisco CallManager and related Cisco IP telephony applications in a call-center environment, review this document before you begin any installation procedures.
•
This document provides information on the latest operating system (OS) and BIOS upgrades and patches. Information in this document applies to servers running the following Cisco IP telephony applications: Cisco CallManager, Conference Connection, Personal Assistant, and Cisco Customer Response Applications, etc.
•
Locate the release notes, installation/upgrade, and configuration guides for the applications that you want to integrate with Cisco CallManager.
Note
Click the URLs in Table 1 to navigate to the appropriate documentation and software.
Table 1 Quick Reference for URLs
Related 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 IDS Host Sensor Documentation
http://www.cisco.com/warp/public/788/AVVID/ids_host_sensor_cm.html
Server Hardware Specifications
http://www.cisco.com/warp/public/779/largeent/avvid/products/infrastructure.html
Operating System Download via the Web (for Upgrades Only)
Cisco IP Telephony Application Product Keys
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801149d8.shtml
Frequently Asked Questions about the Cisco CallManager Installation
Review the following questions and responses before you install Cisco CallManager on the server.
What hardware and CD-ROMs do I receive when I purchase Cisco CallManager?
You do not receive a monitor with any Cisco Media Convergence Server (MCS) or approved customer-provided server. The MCS-7830, MCS-7825, and MCS-7835 do not include a keyboard or mouse. During initial startup and configuration of the server and Cisco CallManager, you must supply a monitor and, if necessary, a keyboard and mouse.
Before you begin the installation, carefully review the hardware documentation that accompanies your server. Make sure that you have the appropriate hardware before installing Cisco CallManager. To review the server hardware specifications, click the following URL:
http://www.cisco.com/warp/public/779/largeent/avvid/products/infrastructure.html
All Cisco MCS and Cisco-approved customer-provided servers ship with a blank hard drive. When you install Cisco CallManager Release 3.2, you use the appropriate CD-ROMs, depending on your server type:
•
•
You use this CD-ROM only if servers in the cluster have a previous operating system installation on them. For information on the tasks that CD #2 accomplishes, refer to the version of Upgrading Cisco CallManager Release 3.2 that matches this installation guide.
•
You use only one of the server-specific Cisco IP Telephony Server Operating System Installation and Recovery CD-ROMs that come in your software kit. During the operating system installation, you receive a prompt to insert the appropriate CD-ROM into the CD-ROM drive.
•
•
How long does it take to perform the Cisco CallManager installation?
The entire installation process, excluding pre-/post-installation tasks, takes 60 to 120 minutes per server, depending on your server type. Before you install Cisco CallManager, consider the size of your cluster and the number of Cisco IP telephony applications that you plan to install.
How does the Cisco CallManager installation work?
When you begin the installation, you boot the server from the Cisco IP Telephony Server Operating System Hardware Detection CD-ROM. After the system boots, the Cisco IP Telephony Applications Server QuickBuilder installation utility 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. (See "What data must I provide to configure the server?" section for more information.)
If necessary, Cisco IP Telephony Applications Server QuickBuilder 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:
•
•
•
QFECheck, a program that was created by Microsoft, verifies the hotfixes that are installed on the Windows 2000 operating system.
•
•
Table 2 describes the components that are installed when you choose the options from the CallManager Components window.
Cisco CallManager places services in a stopped state until the installation completes. When you complete the installation, the services activate and start. For information on starting and stopping services, refer to the Cisco CallManager Serviceability Administration Guide or to online help in the Cisco CallManager application.
In a Cisco CallManager distributed system, one server maintains the master, or publisher, database, and all other servers in the cluster maintain subscriber databases. Subscriber databases provide copies of the master database. During normal operation, all Cisco CallManagers in the cluster read data from and write data to the publisher database. Periodically, Cisco CallManager automatically updates the subscriber copies of the database from the publisher database. You install Cisco CallManager first on the publisher database server.
Before you complete the installation, make sure that you configure the publisher database server backup settings by using the Cisco IP Telephony Applications Backup Utility. If you do not configure the backup settings, you cannot restore the Cisco CallManager data in the unlikely event of a catastrophic failure.
What data must I provide to configure the server?
During the installation process, you receive prompts telling you to enter important configuration information about the server, such as the 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 that 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 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 on a server designated for Cisco CallManager 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
The computer name comprises a unique network name of 15 characters or less. It may contain alphanumeric characters or hyphens (-), and must begin with an alphabetical character and end with an alphanumeric character. You should follow your local naming conventions, if applicable.
Caution
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
By default, the phones attempt to connect to the Cisco CallManager using DNS. Therefore, if you use DNS, make sure that 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." Cisco sets the community rights to none for security reasons. If you want to use SNMP with this server, you must configure it.
Terminal Services
Cisco automatically enables Terminal Services during the installation, so Cisco Technical Assistance Center (TAC) can remotely perform administrative and troubleshooting tasks. Cisco does not support installations and upgrades through Terminal Services.
Database server
Determine whether this server will be configured as a publishing database server or as a subscriber database server. This decision designates a permanent selection. If you want to reassign the database server type at a later date, you must reinstall the Cisco CallManager server.
Caution
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 supports password protection. At the end of the installation, a prompt asks you to supply a new password for the system administrator.
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.
May I install other software besides Cisco CallManager on the server?
Consider the following information before you install other software besides Cisco CallManager on the Cisco MCS or the customer-provided server:
•
•
•
•
•
•
Note
May I run a web browser on the server?
Cisco strongly recommends that you do not run a web browser on the Cisco MCS or any approved customer-provided server. Running a web browser on the server causes CPU usage to surge.
To access Cisco CallManager Administration, the web-based graphical user interface (GUI) that allows you to perform Cisco CallManager configuration tasks, browse into the Cisco CallManager server that is running Cisco CallManager Administration and log in with administrative privileges.
Tip
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 preinstallation tasks should I perform?
For preinstallation tasks you must complete before the installation, see Table 4.
Table 4 Preinstallation Tasks
Step 1
Make sure that you have the appropriate hardware before installing the operating system or Cisco CallManager.
Carefully review the hardware documentation that accompanies your server. To review the server hardware specifications for approved customer-provided servers, click the following URL:
http://www.cisco.com/warp/public/779/largeent/avvid/products/infrastructure.html
Step 2
Plan your system configuration.You can distribute the call-processing load for your system across multiple Cisco CallManagers as a single cluster. A cluster comprises a set of Cisco CallManagers that share the same database.
At a minimum, you should determine how many Cisco CallManager servers the cluster will contain, which server will house the publisher database, and where backup tasks will be performed. Additional planning should include a strategy for distributing the devices (such as phones or gateways) among the Cisco CallManagers in the cluster to achieve the type of distribution that you want.
In a Cisco CallManager distributed system, one server maintains the master, or publisher, database, and all other servers in the cluster maintain subscriber databases. Subscriber databases provide copies of the master database. During normal operation, all Cisco CallManagers in the cluster read data from and write data to the publisher database. Periodically, Cisco CallManager automatically updates the subscriber copies of the database from the publisher database.
For more information on planning a Cisco CallManager distribution system, refer to the Cisco CallManager System Guide.
Step 3
Connect a monitor, keyboard, and mouse to the server; then, connect the server to the network.
See the following sections:
•
Step 4
Before you perform Cisco CallManager installation, upgrade, or restoration procedures, you must disable all Cisco-approved McAfee antivirus services. You can enable all antivirus services after you complete the procedures.
See the following sections:
•
Step 5
If you have Cisco IDS Host Sensor installed on the server, you must stop the following services:
•
•
•
•
For information on Cisco IDS Host Sensor, click the following URL:
http://www.cisco.com/warp/public/788/AVVID/ids_host_sensor_cm.html
Step 6
Locate Table 3, which provides specific server configuration information.
See the "What data must I provide to configure the server?" section.
How do I connect the keyboard and mouse to the server?
You do not receive a monitor with any Cisco Media Convergence Server or any approved customer-provided server. 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.
Caution
How do I connect the server to the network?
Make sure that you connect your server to the network before you begin the installation. The special, limited edition of Windows 2000, intended for use with Cisco CallManager only, will not install if you do not connect the server to the network.
The servers in Table 5 contain two network interface cards (NIC), but Cisco CallManager supports only one NIC. When you connect the server to the network, use the NIC connector listed in the table because the other NIC is disabled during the installation.
Table 5 Connecting to the Network
MCS-7825
Use the lower NIC connector.
MCS-7835-1266
Use the NIC 1 connector.
IBM xSeries 330 server
Use the upper NIC connector.
How do I disable Cisco-approved McAfee antivirus services?
To disable the McAfee antivirus services, perform the following tasks:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Performing the Installation
The entire operating system and Cisco CallManager installation process, excluding pre-/post-installation tasks, takes 60 to 90 minutes per server. To perform an operating system and Cisco CallManager installation, see the following sections:
•
–
–
–
•
–
–
Starting the Operating System Installation
In this portion of the installation, which takes about 20 minutes, you will perform the following tasks:
•
•
•
Note
During the 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.
Note
Installing the Operating System on Servers When the Hard Drive is Not Blank
Perform the following steps to begin the operating system installation:
Procedure
Step 1
Step 2
Step 3
Step 4
MCS-7815-1000
Step 5
Step 6
Step 7
Step 8
Step 9
MCS-7825-800
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
MCS-7825-1133
Step 16
Step 17
Step 18
Step 19
Step 20
Step 21
MCS-7835-733 and MCS-7835-1000
Step 22
Step 23
Step 24
Step 25
Step 26
Step 27
Step 28
Step 29
MCS-7835-1266
Step 30
Step 31
Step 32
Step 33
Step 34
Step 35
Step 36
MCS-7845-1400
Step 37
Step 38
Step 39
Step 40
Step 41
Step 42
Step 43
IBM xSeries 330 Server
Step 44
Step 45
Step 46
Step 47
Step 48
IBM xSeries 340 or 342 Servers
Step 49
Step 50
Step 51
Step 52
Step 53
Installing the Operating System on Servers When the Hard Drive is Blank
Perform the following steps to begin the operating system installation:
Procedure
Step 1
Step 2
Step 3
Note
Step 4
a.
b.
c.
d.
e.
f.
g.
Step 5
Caution
a.
b.
c.
d.
e.
Caution
Step 6
Step 7
Step 8
Step 9
Step 10
Entering the Product Key and Reviewing the License Agreement
In this portion of the installation, you will perform the following tasks:
•
•
•
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
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:
•
•
•
•
•
•
•
•
Using the data that you collected in Table 3, complete the following steps to configure each server:
Procedure
Step 1
Step 2
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 that the name that you assign is the permanent server name.
Note
Step 3
Step 4
Step 5
Note
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
Caution
Step 7
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
a.
b.
For example:
172.16.0.10 dallascm1c.
d.
Note
Step 9
Step 10
Caution
Step 11
Step 12
Step 13
If you leave the password fields blank, you cannot install any Cisco IP telephony applications on the server.
Make sure that you enter the same password on all servers in the cluster.
Step 14
Step 15
Begin the Cisco CallManager installation by performing the steps in the"Installing Cisco CallManager" section.
Installing Cisco CallManager
During the installation, which takes about 45 to 90 minutes, you install services, Cisco CallManager Administration, the publisher database or subscriber server, and the Cisco IP Telephony Applications Backup Utility.
Note
Installing Services and the Publisher Database or Subscriber Server
In this portion of the installation, you will perform the following tasks:
•
•
•
Procedure
Step 1
Step 2
Step 3
When Cisco CallManager services are activated, the installation process places them in a stopped state. All services activate and start upon completion of the installation. For information on starting services, refer to the Cisco CallManager Serviceability Administration Guide or to online help in the Cisco CallManager application.
Figure 1 shows an example of the CallManager Components window.
Figure 1 CallManager Components Window
Choose the services that you want to activate in this initial installation; then, click Next.
You must decide whether you are installing the publisher database server or subscriber database server. You must first install Cisco CallManager on the publisher database server. Figure 2 shows an example of the Cisco CallManager Database Distribution window where you establish the publisher-subscriber relationship. If you are installing the subscriber database server, the authentication window prompts you to enter usernames and passwords for a Windows 2000 user with administrative privileges and a SQL Server user with SQL Server administrative privileges on the publishing database server.
Figure 2 Cisco CallManager Database Configuration
Note
Installing Cisco CallManager on the Publisher Database Server
Step 4
Step 5
Step 6
Installing Cisco CallManager on the Subscriber Server
Step 7
Step 8
Step 9
The system connects to the publishing database server.
Step 10
Step 11
Installing the Cisco IP Telephony Applications Backup
The Cisco IP Telephony Applications Backup Utility provides a reliable and convenient way to perform regularly scheduled automatic or user-invoked backups of your Cisco CallManager data.
The Cisco CallManager publisher database contains all the information that you configure with Cisco CallManager Administration, and the database updates each time that you make a change. Cisco CallManager updates directory, and configuration information also updates periodically. Cisco strongly recommends that you make a backup of the Cisco CallManager database, configuration, and directory information by using the Cisco IP Telephony Applications Backup Utility every time that you make changes through Cisco CallManager Administration.
Your Cisco CallManager cluster has only one publisher database, and no necessity exists to back up subscriber database servers containing replicates of the same database. However, you can configure the Cisco IP Telephony Applications Backup Utility to back up more than one Cisco IP Telephony Applications Server, such as publishing database servers of other Cisco CallManager clusters, Cisco uOne servers, or Cisco Administrative Reporting Tool (ART) database servers.
The backup server actually performs the backup operation. It stores the backup data in the backup destination that you specify. Cisco strongly recommends that you specify a tape drive or a network directory as the backup destination, not a local directory. If you choose a network directory as the destination for the backup server, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon that you want to share, click Sharing..., click Share this folder, and then click OK.
The target server contains the data to be backed up. At the end of the Cisco CallManager installation, if a server is configured as a backup server and the Cisco CallManager component is installed on the server, Cisco CallManager automatically adds it to the backup target list.
By default, one file called MCS.sti stores all data that is backed up from the target servers in the target list. The Cisco IP Telephony Applications Restore Utility extracts and restores archived MCS.sti files that you have named and stored properly.
Caution
For more information on the Cisco IP Telephony Applications Backup Utility, refer to Backing Up and Restoring Cisco CallManager Release 3.2.
In this portion of the installation, which takes about 15 minutes, you will complete the following tasks:
•
•
•
Note
Procedure
Step 1
Defining Backup Server
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. Cisco recommends that when you are installing Cisco CallManager on the publisher database server, you choose Backup Server.
Defining Backup Target
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. If you choose Cancel, the backup utility does not install for use.
Step 2
If you chose Server in the previous step, continue with Step 3.
Step 3
Note
Step 4
Figure 3 shows an example of the Destination tab in the Cisco IP Telephony Applications Backup Utility.
Figure 3 Destination Tab in the Cisco IP Telephony Applications Backup Utility Configuration Window
Note
You may click the Tape device radio button only if you have the MCS-7835, IBM xSeries 340, or
xSeries 342 server. Only the MCS-7835, IBM xSeries 340, or xSeries 342 server has 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 5
Step 6
Figure 4 Schedule Tab in Cisco IP Telephony Applications Backup Utility Configuration Window
Step 7
Caution
Step 8
Step 9
Caution
Step 10
Step 11
Note
Step 12
Step 13
Step 14
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.
For post-installation tasks you must complete after the installation, see Table 6.
Table 6 Post-Installation Tasks
Step 1
Verify that services are running on the appropriate servers. Verify that you have installed the latest available patches and hotfixes.
View the components installed on the server.
See the following sections:
•
Step 2
If you want to do so, change the SQLSvc password on all the servers in the cluster.
See the "Changing the Password for the SQLSvc Account" section.
Step 3
Perform auto-registration tasks.
Step 4
If you want to do so, configure DNS.
See the "Configuring DNS" section.
Step 5
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.
Step 6
Activate additional services that you did not activate in the initial installation.
Step 7
Install additional Music on Hold selections via CD-ROM or the web.
See the "Using the Cisco CallManager Music On Hold CD-ROM or Download" section.
Step 8
Enable all Cisco-approved McAfee antivirus services.
See the "Enabling Cisco-Approved McAfee Antivirus Services" section.
Step 9
If you have Cisco IDS Host Sensor installed on the server, you must start the following services:
•
•
•
•
For information on Cisco IDS Host Sensor, click the following URL:
http://www.cisco.com/warp/public/788/AVVID/ids_host_sensor_cm.html
Step 10
If you choose to do so, configure the F: drive for trace file collection.
See the "Using the F: Drive on the MCS-7845-1400 to Collect Trace Files" section.
Step 11
If you have not already done so, back up your Cisco CallManager data.
Refer to Backing Up and Restoring Cisco CallManager Release 3.2.
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:
•
•
•
•
•
•
•
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/public/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 receive a Cisco CallManager support patch CD-ROM in your software kit, insert the CD-ROM into the CD-ROM drive, click the My Computer icon on the desktop, select and review the readme document available on the CD-ROM, and perform the appropriate procedures.
To verify that you have the latest Cisco CallManager updates on the server, click http://www.cisco.com/public/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 the operating system, upgrade, and backup and restore utility. Be aware that Cisco does not report the actual Cisco CallManager version through this program. Most of these components, which are run from the installation 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 using 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
C:\sti\stiver
Step 2
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
Changing the password for the SQLSvc account includes performing the following tasks:
•
•
•
•
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
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 may 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
To disable DNS after installing Cisco CallManager, perform the following steps:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
To change the Cisco CallManager server name to the IP address, perform the following steps:
Procedure
Step 1
Step 2
Step 3
Step 4
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.
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:
•
•
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
To activate additional Cisco CallManager services, or to deactivate existing services, perform the following steps:
Procedure
Step 1
Step 2
Step 3
Step 4
Enabling Cisco-Approved McAfee Antivirus Services
To enable the Cisco-approved McAfee antivirus services, perform the following tasks:
Procedure
Step 1
a.
b.
c.
d.
e.
f.
Step 2
Using the F: Drive on the MCS-7845-1400 to Collect Trace Files
To increase system performance, you can configure service parameters and trace output settings so that trace files write to the F: drive instead of the default C: drive. Using the F: drive allows you to capture more trace files because this drive is set up specifically for trace file collection.
Note
After you configure the server in Cisco CallManager Administration, perform the following procedure for all MCS-7845-1400 in the cluster:
Procedure
Step 1
Step 2
The Service Parameters Configuration window displays.
Step 3
The Service Parameters Configuration window for Cisco CallManager displays.
Step 4
Step 5
Step 6
The Cisco CallManager Serviceability window displays.
Step 7
Step 8
The Trace Configuration window for the service and server displays.
Step 9
Step 10
Step 11
Using the Cisco CallManager Music On Hold CD-ROM or Download
When you install Cisco CallManager on your server, a default music on hold sample automatically installs for customer use. To increase your music on hold (MOH) selection, you may also install the Cisco CallManager Music On Hold CD-ROM that ships with your Cisco IP Telephony Applications Server, or you may download one of two following files via the web:
•
•
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.
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 approved 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.2. 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/warp/public/779/largeent/avvid/products/infrastructure.html
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
Step 2
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
If you determine that one or more subscription connections are broken, you must perform the following actions:
•
•
On each subscriber server, perform the following steps to delete and re-create the subscriptions:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
On the publisher server, perform the following steps to reinitialize the subscriptions and start the replication snapshot agent:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Obtaining Documentation
These 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 this URL:
Translated documentation is available at this 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.
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems, Inc.
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online 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 with these tasks:
•
•
•
•
•
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
•
•
•
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site 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 this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC 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 this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
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). When you call the center, please have available your service agreement number and your product serial number.
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0206R)
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
