SNMP OID for monitoring number of SIP calls on CUBE

[Erick Bergquist]

Is there a OID anyone knows of to get the # of active calls on a SIP CUBE gateway?

This is for a 3825 router with 12.4.24T4 IOS.  I've been through the forums, dial-control-mib, voice-dial-control-mib and the OIDs in those return values for each call. I am just looking for a way to monitor the total # of active calls over time.

With older setup with PRI gateways, I was able to monitor via SNMP the number of active channels on a T1.

[Jeson Chelleth]

Refer to this link:

http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6790/gatecont/ps5640/white_paper_c11-613550_ps10536_Products_White_Paper.html

Go to:

Table 8. Real-Time Trunk Utilization: CISCO-VOICE-DIAL-CONTROL-MIB

We have OID cvCallVolume (OID # is 1.3.6.1.4.1.9.9.63.1.3.8)

=> Giving Total call active statistics, based on per-protocol, per-dial-peer and per-interface.

A snapshot summary of overall call active  statistics on the platform is given by the  cvCallVolConnTotalActiveConnections (1.3.6.1.4.1.9.9.63.1.3.8.2) OID.

And as per your question, SIP(2) call statistics are in the CvCallVolConnActiveConnection.2 (1.3.6.1.4.1.9.9.63.1.3.8.1.1.2.2) OID

For more details refer to the section as mentioned above...

Hope this helps...

[Erick Bergquist]

Hi,

Thanks. Those OIDs report nothing back for me. If I back the last value off on the first OID then I get a whole slew of values, but I am looking for just a total count of active calls like I was getting with a PRI circuit.

SNMP does work and respond on this router with other MIBs. It is a 3825 running IOS version 12.4(24)T3.

root@nagios ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3.8.1.1.2

root@nagios ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3.8.11.2

root@nagios ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3.8.2

root@nagios ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 .1.3.6.1.4.1.9.9.63.1.3.8.2

root@nagios ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3.8

root@nagios ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 .1.3.6.1.4.1.9.9.63.1.3.8

[Jeson Chelleth]

Hello,

I don't see you did a walk for 1.3.6.1.4.1.9.9.63.1.3.8.1.1.2.2 OID. This was for SIP calls, did you try this one?

[Erick Bergquist]

I believe I did earlier, as well as some other SIP Call Counter MIBs from the MIB document, but they all return

no values.

root@nagios ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 .1.3.6.1.4.1.9.9.63.1.3.8.1.1.2.2 ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3.8.1.1.2.2 ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3.8.1.1.2 ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3.8.1.1 ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3.8

root@nagios

root@nagios

root@nagios

root@nagios

When I back off enough, I start to get info.

root@nagios ~$snmpwalk -v 1 -c snmpstring 172.16.1.2 1.3.6.1.4.1.9.9.63.1.3
SNMPv2-SMI::enterprises.9.9.63.1.3.3.0 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.63.1.3.4.0 = Gauge32: 100
SNMPv2-SMI::enterprises.9.9.63.1.3.5.0 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.63.1.3.6.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.63.1.3.7.0 = INTEGER: 2

[Kelly McCoy]

What happens when you do a "show sip call summary"? Do you see calls present there?

[Jeffrey Jones]

So anyway to get the whole call history, I have tried the tables but they say its not supported.

or is there a way to almost do a cdr of the sip calls downloaded to a tftp server?

Thanks

JJ

[issofunky]

I spent too much time walking the mib to get to this...but I hope I can spare some of you the time.

2900 running 15.2(2)

1.3.6.1.4.1.9.9.63.1.3.8.4.1.1.10001 for UAC (actual calls from CUBE out to SIP Peer

1.3.6.1.4.1.9.9.63.1.3.8.4.1.2.10002 for UAS between CUBE and CUCM

1.3.6.1.4.1.9.9.63.1.3.8.4.1.2.90002 for UAS between CUBE and Internal UA making the calls.

Note CUBE does transcode ....so you might want to also look up H323 / PRI / SCCP.

What you monitor depends on what that CUBE is doing in your environment.