-
Cisco CallManager System Guide, Release 3.3(3)
-
Index
-
Preface
-
Introduction
-
Cisco IP Telephony Overview
-
System Configuration Overview
-
System-Level Configuration Settings
-
Clustering
-
Redundancy
-
Call Admission Control
-
Cisco TFTP
-
Device Support
-
Services
-
Auto-Registration
-
Partitions and Calling Search Spaces
-
Understanding Route Plans
-
Understanding the LDAP Directory
-
Managing User Directory Information
-
Media Resource Management
-
Conference Bridges
-
Transcoders
-
Music On Hold
-
Media Termination Points
-
Cisco Catalyst DSP Resources for Transcoding and Conferencing
-
Voice Mail Connectivity to Cisco CallManager
-
SMDI Voice Mail Integration
-
Cisco Unity Messaging Integration
-
Cisco uOne Voice Messaging Integration
-
Cisco DPA Integration
-
Call Park
-
Call Pickup and Group Call Pickup
-
Cisco IP Phone Services
-
Cisco CallManager Extension Mobility and Phone Login Features
-
Cisco CallManager Attendant Console
-
Custom Phone Rings
-
Cisco IP Manager Assistant
-
Understanding Voice Gateways
-
Cisco IP Phones
-
Computer Telephony Integration
-
Cisco ATA 186
-
Administrative Tools Overview
-
Administrative Accounts and Passwords
-
FeedbackTable Of Contents
Cisco Extension Mobility Logout
Cisco IP Voice Media Streaming Application
Cisco Telephony Call Dispatcher
Service Installation and Configuration
Services Configuration Checklist
Where to Find More Information
Services
Cisco provides several Windows services that are installed during Cisco CallManager installation. You use Cisco CallManager Serviceability to activate and deactivate as well as start and stop the services. After you activate the services, you can configure them by modifying the service parameters. For more information on activating/deactivating and starting/stopping services, refer to the Cisco CallManager Serviceability Administration Guide. For more information about service parameters, refer to "Service Parameters Configuration" in the Cisco CallManager Administration Guide.
This section provides a description of the available services and information on working with these services:
•
Cisco Extension Mobility Logout
•
•
•
•
•
Cisco CallManager
The Cisco CallManager service runs on the Cisco IP Telephony Applications Server to provide software-only call processing as well as signaling and call control functionality. After you install Cisco CallManager, you activate and start the Cisco CallManager service by using Cisco CallManager Serviceability.
You configure your Cisco CallManager by modifying the service parameters in the Service Parameters Configuration window of Cisco CallManager Administration. Cisco provides over 100 service parameters for the Cisco CallManager service. To view a list of parameters and their descriptions, click the "i" button in the upper, right corner of the Service Parameters Configuration window. To view the list with a particular parameter at the top, click that parameter in the window.
You must restart Cisco CallManager after making certain changes in the Cisco CallManager Administration. Table 10-1 lists the changes that require a restart.
Tips
Requirements and Recommendations
•
•
•
Cisco CDR Insert
Cisco CDR Insert reads transferred files, places contents into the call detail record (CDR) database, and removes old files. When you enable CDR collection, Cisco CallManager writes CDRs to flat files on the subscriber databases as calls are made. The Cisco CDR Insert service periodically inserts the records from these files into the publisher centralized SQL database. The Cisco CDR Insert service does not insert a record if the CDRFormat enterprise parameter has a value of Flat. For more information on CDRs and related parameters, see the "Call Detail Records" section on page 38-4.
Requirements and Recommendations
•
•
•
Cisco CTIManager
The Cisco CTIManager service contains the CTI components that interface with applications. With Cisco CTIManager, applications have access to resources and functionality of all Cisco CallManagers in the cluster and have improved failover capability. One or more Cisco CTIManagers can be active in a cluster, but only one Cisco CTIManager can exist on an individual server. An application (JTAPI/TAPI) can have simultaneous connections to multiple Cisco CTIManagers; however, an application can only use one connection at a time to open a device with media termination.
Requirements and Recommendations
•
•
•
•
Cisco Database Layer Monitor
The Cisco Database Layer Monitor service monitors aspects of the database layer as well as call detail records (CDRs). The database layer comprises a set of dynamic link libraries (DLLs) that provide a common access point for applications that need to access the database to add, retrieve, and change data. The Cisco Database Layer Monitor service performs functions such as determining whether the primary server is available during failover, deleting the oldest CDRs when the limit that is defined in the Max CDR Records parameter is reached, logging out phones by using Cisco CallManager Extension Mobility, and moving CDRs from a subscriber to the primary database at a given interval, if needed.
Requirements and Recommendations
•
•
Cisco Extended Functions
The Cisco Extended Functions service supports the Cisco Call Back and Quality Report Tool (QRT) features. Cisco Call Back allows you to receive notification on your Cisco IP Phone when a called party line becomes available. QRT acts as a voice quality and general problem-reporting tool for Cisco IP Phones.
If you run multiple Cisco Extended Functions services within a Cisco CallManager cluster, the service uses an algorithm to determine which service should be active and to order the backup services. The Cisco Extended Functions service with the lowest IP address becomes active. The service with the next lowest IP address becomes the backup to the active service. Any remaining services act as backups to each other, beginning with the service with the next lowest IP address. If you add any new services to the cluster, Cisco Extended Functions restarts the algorithm to determine which service will be active.
Note
To verify the status of the active Cisco Extended Functions service, use the Real-Time Monitoring Tool as described in the Cisco CallManager Serviceability Administration Guide.
For more information about the Call Back feature, refer to the Cisco IP Phone Administration Guide for Cisco CallManager and the Cisco CallManager Features and Services Guide.
For more information about the Quality Report Tool, refer to the Cisco IP Phone Administration Guide for Cisco CallManager, the Cisco IP Phone 7960 and 7940 Series User Guide, and the Cisco CallManager Serviceability Administration Guide.
Requirements and Recommendations
•
•
•
Cisco Extension Mobility Logout
The Cisco Extension Mobility Logout service allows you to define login settings such as duration limits on phone configuration for the Cisco CallManager Extension Mobility feature. The Cisco CallManager Extension Mobility feature allows users within a Cisco CallManager cluster to temporarily configure any Cisco IP Phone 7960/7940 as their own by logging in to that phone. After a user logs in, the phone adopts the user's personal phone number(s), speed dials, services links, and other user-specific properties. After logout, the phone adopts the original user profile. For more information on the Cisco CallManager Extension Mobility feature, see the "Cisco CallManager Extension Mobility and Phone Login Features" section on page 30-1.
Requirements and Recommendations
•
•
•
•
•
Cisco IP Manager Assistant
Cisco Tomcat loads the Cisco IP Manager Service (IPMA), a servlet. Cisco Tomcat identifies an NT service that is installed and started at Cisco CallManager installation. For more information, see the "Cisco IPMA Service" section in the Cisco CallManager Features and Services Guide.
The administrator performs three steps to make Cisco IPMA available for system use:
1.
2.
3.
Service parameters for the Cisco IPMA service comprise two categories: general and clusterwide. Specify clusterwide service parameters once for all Cisco IPMA services. Specify general service parameters for each Cisco IPMA service that is installed. For more information, see the "Setting the Service Parameters for Cisco IPMA" section in the Cisco CallManager Features and Services Guide.
Because the Cisco IPMA service intercepts calls that are made to managers, it requires configuration of partitions, calling search spaces, a route point, and translation patterns. For information on configuring the Cisco IP Manager Assistant feature, see the "Configuration Checklist for Cisco IPMA" section in the Cisco CallManager Features and Services Guide.
Requirements and Recommendations
•
•
Cisco IP Voice Media Streaming Application
The Cisco IP Voice Media Streaming Application provides voice media streaming functionality for Cisco CallManager for use with MTP, conferencing, and music on hold (MOH). The Cisco IP Voice Media Streaming Application relays messages from Cisco CallManager to the IP voice media streaming driver. The driver handles the RTP streaming. The MTP and conference bridge components of the Cisco IP Voice Media Streaming Application support G.711 mu-law and a-law codecs. The MOH component supports G.711 mu-law/a-law, G.729a, and wideband codecs.
When you activate the Cisco IP Voice Media Streaming Application, Cisco CallManager automatically adds the MTP, MOH, and conference devices to the database. By default, the installation program places the executable in the C:\Program Files\Cisco\bin directory.
For more information about MTP, MOH, and conference bridges, see the "Media Termination Points" section on page 20-1, the "Music On Hold" section in the Cisco CallManager Features and Services Guide, and the "Conference Bridges" section on page 17-1.
Requirements and Recommendations
•
•
•
•
Cisco Messaging Interface
The Cisco Messaging Interface allows you to connect a simplified message desk interface (SMDI)-compliant external voice-mail system with the Cisco CallManager. The CMI service provides the communication between a voice-mail system and Cisco CallManager. The SMDI defines a way for a phone system to provide a voice-mail system with the information that is needed to intelligently process incoming calls.
You configure the CMI service parameters to define the following aspects of the CMI service:
•
•
•
Cisco Messaging Interface can take up to 5 minutes to detect and load new parameters. For an instant update, restart Cisco Messaging Interface service. For information on restarting services, see the Cisco CallManager Serviceability Administration Guide.
For a general description of how to integrate an SMDI-compliant voice-mail system with Cisco CallManager, see the "SMDI Voice Mail Integration" section on page 23-1.
Requirements and Recommendations
•
•
•
•
Cisco MOH Audio Translator
The Cisco MOH Audio Translator service converts audio source files into various codecs, so the MOH feature can use them.
The Cisco MOH Audio Translator service automatically translates audio files that you place in the input directory. During installation, the installation program creates this input directory in the following location: c:\Cisco\DropMOHAudioSourceFilesHere. If you want to change the input directory, modify the MOHSourceDirectory service parameter.
After the Cisco MOH Audio Translator service translates the audio files, the Cisco MOH Audio Translator service places the source audio file and the translated file in the output directory on the default MOH TFTP server that was established during the Cisco MOH Audio Translator service installation. To change the output directory, modify the DefaultTFTPMOHFilePath parameter; however, make sure the path points to the default MOH TFTP server. The DefaultTFTPMOHFilePath parameter contains a universal naming convention (UNC) share name that displays in the format \\computer name\directory name.
Caution
When the user assigns or maps the audio source file to an audio source number, the default MOH TFTP server copies the files into one directory and makes them available for the MOH servers. The MOH servers download the audio files in the C:\Program Files\Cisco\MOH directory. For more detailed information on how the MOH feature accesses the files after the Cisco MOH Audio Translator service places them in the output directory, see the "Music On Hold" section in the Cisco CallManager Features and Services Guide.
Requirements and Recommendations
•
•
•
•
•
•
Note
Cisco RIS Data Collector
The Real-time Information Server (RIS) collects, distributes, and maintains real-time Cisco CallManager information and provides an interface through which the Cisco RIS Data Collector service and the SNMP Agent retrieve that information. One RIS exists on each node that contains the Cisco CallManager service. The Cisco RIS Data Collector service provides an interface for applications, such as Cisco CallManager Serviceability and the Cisco CallManager Administration, to retrieve information that is stored in all RIS nodes in the cluster.
Requirements and Recommendations
•
•
Cisco Telephony Call Dispatcher
Telephony Call Dispatcher (TCD) service provides centralized services for attendant consoles and pilot points. For attendant consoles, TCD provides call control functionality, line state information for any accessible line within the Cisco CallManager domain, and caching of directory information. For pilot points, TCD provides automatic redirection to directory numbers that are listed in hunt groups and failover during a Cisco CallManager failure.
For more detailed information on how TCD works with attendant consoles, see the "Understanding the Cisco Telephony Call Dispatcher" section on page 31-10.
For more information on how TCD works with pilot points, see the "Understanding Pilot Points and Hunt Groups" section on page 31-3.
Requirements and Recommendations
•
•
•
•
•
Cisco TFTP
Cisco Trivial File Transfer Protocol (TFTP) builds and serves files that are consistent with the trivial file transfer protocol, a simplified version of FTP. Cisco TFTP serves embedded component executable, ringer files, and device configuration files.
A configuration file includes a list of Cisco CallManagers to which devices (telephones and gateways) make connections. When a device boots, the component queries a Dynamic Host Configuration Protocol (DHCP) server for its network configuration information. The DHCP server responds with an IP address for the device, a subnet mask, a default gateway, a Domain Name System (DNS) server address, and a TFTP server name or address.
The device requests a configuration file from the TFTP server. The configuration file contains a list of Cisco CallManagers and the TCP port through which the device connects to those Cisco CallManagers. For Cisco IP Phone 7960 and 7940 models, the configuration file also contains phone button URL information.
If the device receives the Cisco CallManager name, the device resolves the name by using DNS, and a Cisco CallManager connection opens. If the device does not receive either an IP address or name, the device uses the default server name.
For more information about TFTP, see the "Cisco TFTP" section on page 8-1.
Requirements and Recommendations
•
•
•
•
Service Installation and Configuration
You automatically install all services when you install Cisco CallManager. After installation, use Cisco CallManager Serviceability to activate and start the services that you want to use on your Cisco CallManager servers. After an upgrade, Cisco CallManager starts the services that were previously started on the server.
Note
You can configure your services by setting the appropriate service parameters. If you deactivate a service, Cisco CallManager deletes any updated service parameter values. For information on service parameters, refer to the "Service Parameters Configuration" section in the Cisco CallManager Administration Guide.
Trace Settings
Cisco CallManager Serviceability provides a web-based trace tool to assist you and support personnel in troubleshooting Cisco CallManager problems. You configure trace parameters for Cisco CallManager services that are available on any Cisco CallManager server in the cluster. For more information on configuring and using the trace tool, refer to the Cisco CallManager Serviceability Administration Guide.
Services Configuration Checklist
Table 10-2 lists the steps for installing and configuring services.
Table 10-2 Services Configuration Checklist
Step 1
Activate and start the services that you want to run on your Cisco CallManager servers.
Cisco CallManager Serviceability Administration Guide
Step 2
Configure the appropriate service parameters.
Service Parameters Configuration, Cisco CallManager Administration Guide
Step 3
Troubleshoot problems by using the Cisco CallManager Serviceability trace tool, if needed.
Cisco CallManager Serviceability Administration Guide
Where to Find More Information
Related Topics
•
•
•
•
•
Additional Cisco Documentation
•
•
•
