SNMP monitoring of PRI Channels on MGCP Voice Gateway Router

[swharvey]

We are running Cisco 2821 and 2851 routers with the voice gateway ios bundle. The routers are MGCP based gateways, and we cannot monitor the PRI T1's "active calls" via SNMP polling. We are able to monitor the calls via the Call Mgr Real Time Monitoring Tool (RTMT) but we need to post graphs to our RRD Remstats system. Are there specific OID's or MIB's that can be defined to glean this data from the routers?

Thx

[David Stanford]

To get just the count of VoIP active calls the simplest way is to count

the number of entries that you get in the object cvVoIPCallActiveTable.

Sometimes this may not be accurate so it is good to verify that for each

entry in cvVoIPCallActiveTable, there is an entry in callActiveTable. If

not, drop those ones from the count.

To further refine this to distinguish between calls that are in

connecting, connected or active state you can use the

callActiveCallState in callActiveTable.

The oid used above are as follows :

CISCO-VOICE-DIAL-CONTROL-MIB: "cvVoIPCallActiveTable"

"1.3.6.1.4.1.9.9.63.1.3.2"

DIAL-CONTROL-MIB: "callActiveTable"

"1.3.6.1.2.1.10.21.1.3.1"

DIAL-CONTROL-MIB: "callActiveCallState"

"1.3.6.1.2.1.10.21.1.3.1.1.9"

Also for Historical data, the following looks promising :

CISCO-VOICE-DIAL-CONTROL-MIB: "cvCallHistoryTable"

"1.3.6.1.4.1.9.9.63.1.4.1"

-----B------

To get something similar to the information of the command "sh call

voice active brief" you could do something like what I have below: (have

provided the MIB info next to it, for easier understanding)

H323 leg

pid: pid:200

callActivePeerId.291909790.1 = INTEGER: 200

Answer

callActiveCallOrigin.291909790.1 = INTEGER: answer(2)

205

callActivePeerAddress.291909790.1 = STRING: 205

active

callActiveCallState.291909790.1 = INTEGER: active(4)

tx:/ tx:85515/13681843

callActiveTransmitPackets.291909790.1 = Gauge32: 85692

callActiveTransmitBytes.291909790.1 = Gauge32: 13710323

rx:/ rx:85441/13670560

callActiveReceivePackets.291909790.1 = Gauge32: 85621

callActiveReceiveBytes.291909790.1 = Gauge32: 13699680

For the Telephony leg

pid:1

callActivePeerId.291909815.1 = INTEGER: 1

Originate

callActiveCallOrigin.291909815.1 = INTEGER: originate(1)

93928027

callActivePeerAddress.291909815.1 = STRING: 93928027

active

callActiveCallState.291909815.1 = INTEGER: active(4)

tx:/ tx:85442/13670720

callActiveTransmitPackets.291909815.1 = Gauge32: 85619

callActiveTransmitBytes.291909815.1 = Gauge32: 13699360

rx:/ rx:85515/13681843

callActiveReceivePackets.291909815.1 = Gauge32: 85695

callActiveReceiveBytes.291909815.1 = Gauge32: 13710963

[rdoutt]

We are also looking to perform some call management leveraging this information as you described in your post.  With voice gateways configured for H.323, the callActivePeerAddress table is filled with source and destination numbers, but with MGCP there is no details.  I see from your example that you display data from callActivePeerAddress, namely the string:  93928027.  What would be the reason this table is empty for us with MGCP, but not with H.323?