Idea ID 2850423
SIP Trunk CUBE Status/Utilization Monitoring via NNM IPT SPI

Hi All,
Adding OOB policies to enable polling in NNM or in IPT SPI to monitoring following metrics. At this moment we have setup custom pollers to monitor SPI Trunk Status and Trunk Utilization
2.4.2 SIP Trunk Status
SIP trunk status is an important element of CUBE monitoring. This status is not currently available via SNMP (only via CLI as covered in the previous section).
However, there are MIBS that can be used for monitoring active calls. See the chart below. Are these MIBs available in NNMi?
Table 5. CISCO IOS MIBs that Contain Active Call Information
MIB OID Table Name Number of Entries per Call
DIAL-CONTROL-MIB 1.3.6.1.2.1.10.21 callActiveTable 2
CISCO-VOICE-COMMON-DIAL-CONTROL-MIB 1.3.6.1.4.1.9.10.55 cvCommonDcCallActiveTable 2
CISCO-VOICE-DIAL-CONTROL-MIB 1.3.6.1.4.1.9.9.63 cvCallActiveTable 0 (Used for TDM GW calls only)
CISCO-VOICE-DIAL-CONTROL-MIB 1.3.6.1.4.1.9.9.63 cvVoIPCallActiveTable 2
Table 8. Real-Time Trunk Utilization: CISCO-VOICE-DIAL-CONTROL-MIB
OID OID# New/Changed Platform Use/Operation cvVoIPCallActiveTable
1.3.6.1.4.1.9.9.63.1.3.2 Baseline ISR G1, ISR G2, AS5x00, ASR Provides statistics on active VoIP calls, indexed by callActiveSetupTime and callActiveIndex.
cvCallVolume 1.3.6.1.4.1.9.9.63.1.3.8 CUBE 1.4 ISR G1, ISR G2, AS5x00
Total, per-protocol, per-dial-peer and per-interface call active statistics.
Regards,
Kartheek
- Labels:
-
Device Support – Monitoring
-
Other
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.