Working with Cisco Unified RTMT

Aurus Blog

This blog is to share our expertise in Cisco UCM, UCCX/UCCE and Cisco Meeting Server

  • Archive

    «   March 2024   »
    M T W T F S S
            1 2 3
    4 5 6 7 8 9 10
    11 12 13 14 15 16 17
    18 19 20 21 22 23 24
    25 26 27 28 29 30 31

Working with Cisco Unified RTMT

Cisco Unified RTMT (Real-Time Monitoring Tool) is used to monitor various CUCM parameters, Performance Counters, and to collect Traces.

Performance Counters contain simple information on the system and devices on the system, such as number of registered phones, number of active calls, number of available conference bridge resources etc.

RTMT requires a PC running Windows or Linux and uses HTTPS and TCP to monitor the Device Status, System Perfomance, Device discovery, CTI Applications in the CUCM cluster.

Not only the CUCM admin can work with RTMT: it’s enough to include any user in the standard Standard CCM Server Monitoring group.

RTMT offers a wide range of features but we won’t review all of them here. In everyday life we need a much smaller number of counters which we will list in the next section.

Useful Performance Counters


General information on the system:

  • Memory Usage
  • CPU Usage
  • HDD Usage

System > System summaryThese parameters give an overview of the system status
The processes running on the serverSystem > Server > ProcessTo understand which process causes the high CP load

General information on CUCM:

  • Registered Phones
  • Call InProgress
  • Active MGCP Ports

Call Manager > Call Manager SummaryThe abrupt changes of these parameters may be a sign of some problem

Call processing activity:

  • Call Activity
  • Gateway Activity
  • Trunk Activity
  • Sip Activity

Call manager > Call ProcessThese graphs give an idea about the total number of calls and the gateway activity

Device information:

  • Phone
  • Gateway Devices
  • H.323 Devices
  • Media Resources
  • SIP Trunk

Call Manager > Device

The very useful information that provides and the detailed parameters of each device.

For example – device models, firmware versions, IP addresses, user association etc.
Conference Bridge resources

Stand Alone Cluster -> node name -> Cisco HW Conference Bridge Device

Stand Alone Cluster -> node name -> Cisco SW Conference Bridge Device

  • HWConferenceActive – the number of active conferences
  • ResourceActive – the number conference participants
  • ResourceAvailable - the number of available resources

Gives an idea about the Conference Bridge activity, but not for each conference


RTMT supports Alerts, which are triggered under certain conditions.

RTMT includes the set of pre-installed Alerts (System > Tools > Alert > Alert Central) which provide a great benefit in terms of a quick inspection of the system.

If you see "alarm" in this list it certainly makes sense to check what caused them.

In addition to pre-installed ones, you can create your own Custom Alerts.

Let's create the Alert, which is triggered when the resources of the Hardware Conference Bridge are over. This one is useful to monitor the availability of CUCM conferencing features Meet-Me, Ad-Hoc and Conference Now (implemented in CUCM 11).

We will use the ResourceAvailable Counter mentioned in the table above.

So, to create Alert:

1. Open the appropriate counter, select it, then right-click on it and choose Set Alert / Properties
2. Select the alarm level and enter its description
3. Set the triggering condition - "Under 1".
4. The next screen allows to set up the Alert frequency. In order to keep e-mail box from being hammered we will choose no more than once per hour.
5. Next step is to configure the e-mail address for notification
6. Do not forget to configure e-mail server properties:
System > Tools > Alert > Config Email Server

That’s it.

Syslog Viewer

Syslog Viewer is the analogue of Windows Event Viewer. If something is wrong with the system it’s one of the first interface to look at.

System > Tools > Syslog Viewer

Syslog Viewer allows you to view the messages from the following logs:

  • System Logs - everything that concerns hardware and OS.
  • Application Logs – CUCM logs
  • Security Logs - user login attempts.

Trace & Log Central

Trace & Log Central collects and displays various traces and log files:

  • CUCM SDL and SDI traces
  • SDI (System Diagnostic Interface) are used for log analysis
  • SDL (Signal Distribution Layer) are mainly used when opening cases in the Cisco Technical Assistance Center (TAC).
  • CUCM application logs (for example, BAT logs)
  • System logs

Trace & Log Central works in the following modes:

  • Remote Browse - displays files directly from remote servers.
  • Collect Files – collects traces and downloads them to the PC with RTMT installed.
  • Query wizard – work with trace files containing the query string.
  • Schedule Collection - scheduled trace collection
  • Local Browse - view traces collected on the local drive
  • Collect Erash Dump
  • Real time Trace - trace view in the real-time

The Trace & Log Central can collect tons of data. You can use the following tools to simplify the SDI files analysis.

Performance Monitor and Data Logging

As already mentioned, Performance monitor contains a lot of different counters.

We have already learned to configure Alert to be triggered on the certain Counter by the right-clicking on the counter.

In addition, we can setup the counter logging – right click on the counter and select

  • Start Counter Logging

Once the logging is configured you’ll be able to view logs with Performance Log Viewer.