Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide
Monitoring Cisco Unified Communications Manager
Downloads: This chapterpdf (PDF - 392.0KB) The complete bookPDF (PDF - 4.2MB) | Feedback

Monitoring Cisco Unified Communications Manager

Table Of Contents

Monitoring Cisco Unified Communications Manager

Monitoring Cisco Unified Communications Manager

Monitoring Call-Processing Activity

Understanding Call-Processing Logs

Monitoring Services

Understanding Service Logs

Monitoring Devices

Understanding Device Logs

Monitoring CTI Applications, Devices, and Lines

Related Topics


Monitoring Cisco Unified Communications Manager


This chapter contains information on the following topics:

Monitoring Cisco Unified Communications Manager

Monitoring Call-Processing Activity

Understanding Call-Processing Logs

Monitoring Services

Understanding Service Logs

Monitoring Devices

Understanding Device Logs

Monitoring CTI Applications, Devices, and Lines

Monitoring Cisco Unified Communications Manager

RTMT allows you to monitor common information about all nodes on the Cisco Unified Communications Manager cluster in a single monitoring pane. In the callmanager summary window, you can view information on the following predefined object:

Registered Phones

Calls in Progress

Active Gateway, Ports & Channels

Additional Information

See the "Related Topics" section.

Monitoring Call-Processing Activity

The Call Process monitoring category monitors the following items:

Call Activity—You can monitor the number of calls that were attempted, calls that were completed, and calls in progress for a particular Cisco Unified Communications Manager node or for the entire cluster.

Gateway Activity—You can monitor gateway activity for each gateway type. Gateway activity monitoring includes the number of active ports, the number of ports in service, and the number of calls that were completed for each gateway type for a particular Cisco Unified Communications Manager node or for the entire cluster.

Trunk Activity—The system monitors trunk activity by trunk type for a particular node or for the entire cluster. Trunk activity monitoring includes the number of calls in progress and the number of calls that were completed for a particular trunk type.

SDL Queue—SDL queue monitoring monitors the number of signals in the SDL queue and the number of signals that were processed for a particular signal distribution layer (SDL) queue type. The SDL queue types comprise high, normal, low, and lowest queue. You can monitor the SDL queue for a particular node or for the entire cluster.

SIP Activity—The system displays a summary of SIP requests, SIP responses, total number of failed incoming responses (4xx, 5xx, and 6xx), total number of failed outgoing responses (4xx, 5xx, and 6xx), number of retry requests, and number of retry responses.

Table 11-1 provides information about the call processing objects that RTMT monitors, the alert, thresholds, and defaults. For information on Cisco Unified Communications Manager call activity daily reports, refer to Cisco Unified Serviceability Administration Guide.

Table 11-1 Call Processing Category 

Monitored Objects (displayed)
Alert/Threshold/Default

CallsAttempted, CallsCompleted, and CallsInProgress for each Cisco Unified Communications Manager node and cluster.

N/A

CallsAttempted, CallsCompleted, and CallsInProgress of each type of MGCP FXS/FXO/PRI/T1CAS/H.323 gateway, as well as SIP and H.323 Trunks for each Cisco Unified Communications Manager node and cluster.

N/A

Channel/Port Status of each MGCP FXS/FXO/PRI/T1CAS gateway.

N/A

SDL Queue activity on each Cisco Unified Communications Manager node.

N/A

MGCP FXS Gateway—Number of In-Service and Active ports for each Cisco Unified Communications Manager node and cluster.

Route-List exhausted

MGCP FXO Gateway—Number of In-Service and Active ports for each Cisco Unified Communications Manager node and cluster.

Route-List exhausted

MGCP PRI Gateway—Number of In-Service and Active channels for each Cisco Unified Communications Manager node and cluster.

D-Channel out of service

Route List exhausted

MGCP T1CAS Gateway—Number of In-Service and Active ports for each Cisco Unified Communications Manager node and cluster.

Route List exhausted


Additional Information

See the "Related Topics" section.

Understanding Call-Processing Logs

The system accumulates call-processing data in the memory whenever RTMT calls the LogCall API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

The system logs data every 5 minutes for the following counters on the basis of the following calculation:

cmCallsAttempted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

cmCallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

cmCallsInProgress—Average of all the values that were collected in last 5 minutes

gwMGCP_FXS_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

gwMGCP_FXO_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

gwMGCP_PRI_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

gwMGCP_T1_CAS_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

gwH323_CallsAttempted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

gwH323_CallsInProgress—Average of all the values that were collected in last 5 minutes

gwH323_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

trunkH323_CallsAttempted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

trunkH323_CallsInProgress—Average of all the values collected in last 5 minutes

trunkH323_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

trunkSIP_CallsAttempted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

trunkSIP_CallsInProgress—Average of all the values that were collected in last 5 minutes

trunkSIP_CallsCompleted—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

gwMGCP_FXS_PortsInService—Average of all the values that were collected in last 5 minutes

gwMGCP_FXO_PortsInService—Average of all the values that were collected in lasts 5 minutes

gwMGCP_PRI_SpansInService—Average of all the values that were collected in last 5 minutes

gwMGCP_T1_CAS_SpansInService—Average of all the values that were collected in last 5 minutes

gwMGCP_FXS_ActivePorts—Average of all the values that were collected in last 5 minutes

gwMGCP_FXO_ActivePorts—Average of all the values that were collected in last 5 minutes

gwMGCP_PRI_ActiveChannels—Average of all the values that were collected in last 5 minutes

gwMGCP_T1_CAS_ActiveChannels—Average of all the values that were collected in last 5 minutes

The AMC service logs the call data in windows Performance tool-compatible csv format. The header of the log comprises the time zone information and a set of columns with the previously listed counters for a node. These sets of columns repeat for every node.The following file name format of the Call Log applies: CallLog_MM_DD_YYYY_hh_mm.csv.

The first line of each log file comprises the header.

Additional Information

See the "Related Topics" section.

Monitoring Services

The Service monitoring category monitors the activities of Cisco TFTP requests, heartbeat of different nodes, and database activities.

The Cisco TFTP service builds and serves files that are consistent with the trivial file transfer protocol, which is a simplified version of the File Transfer Protocol (FTP). Cisco TFTP builds configuration files and serves embedded component executables, ringer files, and device configuration files. You can view the total Cisco TFTP requests, requests not found, and requests that were aborted.

The tool (RTMT) monitors the heartbeat of Cisco Unified Communications Managers, Cisco TFTPs, and Cisco Unified CallManager Attendant Console Server services for different nodes. The heartbeat acts as an indicator of the life of whatever it is monitoring. When the heartbeat is lost, a blinking icon appears in the lower, right corner of the RTMT window. To find when the heartbeat loss was detected, click the blinking icon. An e-mail can notify you of the heartbeat loss, if you configure the system to do so.

The database summary provides connection information for each node, such as the change notification requests that are queued in the database, change notification requests that are queued in memory, the total number of active client connections, and the number of devices that are queued for a device reset. Table 11-2 provides information about the service objects that RTMT monitors, the alert, thresholds, and defaults. For information on daily reports for CTI and Cisco TFTP usage statistics, refer to Cisco Unified Serviceability Administration Guide.

Table 11-2 Services Category 

Monitored Objects (displayed)
Alert/Threshold/Default

Number of open devices, lines, CTI connections, and active Cisco Unified Communications Manager links for each CTI Manager.

N/A

TotalTftpRequests and TotalTftpRequestsAborted for each Cisco TFTP server.

N/A

Connection and replication status for each Directory server.

Connection failed.

Replication failed.

Heartbeat rate for each Cisco CallManager, Cisco TFTP, and Cisco CallManager Attendant Console Server services.

Cisco Unified Communications Manager heartbeat rate equals <0.x. Default equals 0.5.

Cisco TFTP heartbeat rate equals <0.x. Default specifies 0.5.

Cisco Unified Communications Manager Attendant Console Server heartbeat rate equals <0.x. Default specifies 0.5.


Additional Information

See the "Related Topics" section.

Understanding Service Logs

The service data accumulates in the memory whenever RTMT calls the LogService API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

The system logs data every 5 minutes for the following counters, based on the following calculation:

ctiOpenDevices—Average of all the values that were collected in last 5 minutes

ctiLines—Average of all the values that were collected in last 5 minutes

ctiConnections—Average of all the values that were collected in last 5 minutes

ctiActiveCMLinks—Average of all the values that were collected in last 5 minutes

tftpRequests—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

tftpAbortedRequests—Cumulative (difference between last collected value and the first collected value in last 5 minutes)

The AMC service logs the service data in csv format. The header of the log comprises the time zone information and a set of columns with the counters that were previously listed for a Cisco Unified Communications Manager. These sets of columns repeat for every node.

The following file name format of the Service Log applies: ServiceLog_MM_DD_YYYY_hh_mm.csv.

The first line of each log comprises the header.

Additional Information

See the "Related Topics" section.

Monitoring Devices

The Device monitoring category provides a summary of devices, device search capability, and a summary of phones.

Table 11-3 provides information about the device objects that RTMT monitors, the alert, thresholds, and defaults, and what kind of reports that RTMT generates for those devices. For information on daily reports on number of registered devices, refer to Cisco Unified Serviceability Administration Guide.

Table 11-3 Devices Category 

Monitored Objects (displayed)
Alert/Threshold/Default

Number of registered phones for each Cisco Unified Communications Manager. This includes all nodes in a cluster.

Total number of registered phones drops by X% in consecutive polls. Default specifies 10%.

Number of registered gateways on each Cisco Unified Communications Manager. This includes all nodes in a cluster.

(Warning) Clusterwide total number of registered gateways decreased in consecutive polls.

(Informational) Clusterwide total number of registered gateways increased in consecutive polls.

Number of registered media devices on each Cisco Unified Communications Manager. This includes all nodes in a cluster.

(Warning) Clusterwide total number of registered media devices decreased in consecutive polls.

(Informational) Clusterwide total number of registered media devices increased in consecutive polls.

Media List exhausted.


The Device Search menu comprises the following items on which you can search: phones, gateway devices, H.323 devices, CTI devices, voice-messaging devices, media resources, hunt lists, and SIP trunks.

You can search on any device in the Cisco Unified Communications Manager cluster and choose the status of the devices, including registered, unregistered, rejected, any status, and devices that are only configured in the database. You can also search by any model, or a specific device model, and set up criteria that include several different attributes. Within the phone search, you can also search on the basis of phone protocol.

RTMT queries RIS to find the matching device. Results display in a table with a row for each matched device, a column for each of the specified attributes, and a time stamp of the device that has been opened/closed and the application that controls the device media.

When you search for a device by choosing the any status option, RTMT does not display a snapshot of the matched device type, but rather it displays data for that device type from the RIS database for all specified Cisco Unified Communications Manager nodes for a period of time. As a result, you may see multiple entries of a device with multiple statuses (Registered, Unregistered, and so on) in RTMT.

When you see multiple entries of a device, the current status of the device reflects the entry that has the latest time stamp. By configuring the RIS Unused Cisco CallManager Device Store Period service parameter for the Cisco RIS Data Collector service in Cisco Unified Communications Manager Administration, you can configure the period of time that the RIS database keeps information on unregistered or rejected device. Refer to Cisco Unified Communications Manager Administration Guide for more information on configuring service parameter.


Tip To find the matching item, RTMT requires that you activate the Cisco RIS Data Collector service in the Service Activation window.


Results display in a table with a row for each matched device, a column for each of the specified attributes, and a time stamp of the device that has been opened/closed and the application that controls the device media.

The phone summary provides information on the number of registered phones, SIP phones, SCCP Phones, partially registered phones, and the number of failed registration attempts.

Additional Information

See the "Related Topics" section.

Understanding Device Logs

The device data accumulates in the memory whenever RTMT calls the LogDevice API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

The data gets logged every 5 minutes for the following counters based on the following calculation:

gatewayDevicesFXS—Average of all the values that were collected in last 5 minutes

gatewayDevicesFXO—Average of all the values that were collected in last 5 minutes

gatewayDevicesPRI—Average of all the values that were collected in last 5 minutes

gatewayDevicesT1—Average of all the values that were collected in last 5 minutes

gatewayDevicesH323—Average of all the values that were collected in last 5 minutes

The AMC service logs the device data in csv format. The header of the log comprises the time zone information and a set of columns with the previously listed counters for a node. These sets of columns repeat for every node.

The following file name format of the Device Log applies: DeviceLog_MM_DD_YYYY_hh_mm.csv.

The first line of each log file comprises the header.

Additional Information

See the "Related Topics" section.

Monitoring CTI Applications, Devices, and Lines

The CTI category monitors CTI Manager activities and provides CTI search capability. With CTI Manager, you can monitor the number of open devices, lines, and CTI connections.

You can specify criteria for the CTI applications, devices, and lines that include CTI status, device name, application pattern, and attributes.


Tip To find the matching item, RTMT requires that you activate the Cisco RIS Data Collector service in the Service Activation window inCisco Unified Serviceability.


Results display in a table with a row for each matched device, a column for each of the specified attributes, and a time stamp of the device that has been opened/closed and the application that controls the device media.

Related Topics

Monitoring Cisco Unified Communications Manager

Monitoring Call-Processing Activity

Understanding Call-Processing Logs

Monitoring Services

Understanding Service Logs

Monitoring Devices

Understanding Device Logs

Monitoring CTI Applications, Devices, and Lines

Working with Cisco Unified Communications Manager Monitoring, page 12-1