Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
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.
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:
From the LogicMonitor Repository, import all Cisco VoIP LogicModules, which are listed in the LogicModules in Package section of this support article.
Add your Cisco VoIP system into monitoring. For more information on adding resources into monitoring, see Adding Devices.
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.
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.
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.
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
