Product Documentation

Cisco VoIP Monitoring

Last updated on 28 February, 2020

Overview

​Cisco offers many devices that utilize VoIP (Voice over Internet Protocol). Using the LogicMonitor Cisco VoIP package, you can monitor a variety of VoIP server/client traffic as captured by call management systems such as CUBE (Cisco Unified Border Element), including connections, redirects, retries, and errors.

Compatibility

The DataSources in the Cisco VoIP package monitor metrics that are exposed by CISCO-VOICE-DIAL-CONTROL-MIB and CISCO-SIP-UA-MIB. A system must respond to at least one of these MIBs in order for the various DataSources to apply to it and begin monitoring metrics.

LogicMonitor’s Cisco VoIP package is confirmed to be compatible with any device that has the CUBE feature enabled, including:

  • Cisco Integrated Services Router (ISR) devices
  • Cisco Aggregation Services Routers (ASR) devices

Setup Requirements

Import LogicModules

From the LogicMonitor Repository, import all Cisco VoIP LogicModules, which are listed in the LogicModules in Package section of this support article.

Add Devices Into Monitoring

Add your Cisco VoIP system into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Enabling SNMP

LogicMonitor uses SNMP to query Cisco VoIP systems for metrics and, therefore, SNMP must be configured on the Cisco device. For instructions on how to configure SNMP, see the Cisco SNMP Configuration Guide for instructions.

Entering SNMP Credentials as Properties

In order to monitor a Cisco VoIP system, LogicMonitor must possess the appropriate SNMP credentials to successfully run SNMP queries. This requires setting these credentials as properties on the resource from within the LogicMonitor interface. As discussed in Defining Authentication Credentials, the SNMP properties that must be set vary depending upon the version of SNMP in use.​

LogicModules in Package

​LogicMonitor’s package for Cisco VoIP consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

Note: The DataSources in this package that feature “SIP” in their names are accessing metrics from CISCO-SIP-UA-MIB. All other DataSources are accessing CISCO-VOICE-DIAL-CONTROL-MIB.

Display Name

Type

Description
addCategory_CiscoSIP PropertySource Identifies whether the device responds to CISCO-SIP-UA-MIB.
addCategory_CiscoVoiceDialControl PropertySource Identifies whether the device responds to CISCO-VOICE-DIAL-CONTROL-MIB.
Cisco SIP Overview DataSource Informational overview about calls from/to SIP clients
Cisco SIP Traffic DataSource Summary of SIP traffic.
Cisco SIP Connections DataSource Monitors active SIP connections and TCP/UDP errors.
Cisco SIP Global Fail DataSource Global fail statistics.
Cisco SIP Client Errors DataSource Summary of client errors received.
Cisco SIP Server Errors DataSource Summary of SIP server errors.
Cisco SIP Successes DataSource Monitors the number of OK and Accepted messages.
Cisco SIP Redirect DataSource Returns the number of redirects.
Cisco SIP Retries DataSource Statistics on SIP retries.
Cisco Call Rate DataSource Monitors general call rate statistics.
Cisco Connection Call Volume DataSource Indicates number of active calls for a call connection type on the voice gateway.
Cisco Call Volume Interfaces DataSource Call active statistics per interface on devices.
Cisco Call Volume Peers DataSource Summary of call volume by dial-peer for devices.

This integration package does not include predefined datapoint thresholds (i.e. no alerts will trigger based on collected data). This is because the technology owner has not provided KPIs that can be reliably extended to the majority of users. In order to receive alerts for collected data, you’ll need to manually create custom datapoint thresholds, as discussed in Tuning Static Thresholds for Datapoints.

In This Article