I'm looking for a mib (more specifically the actual oid) that will give me an active ds0 count on an mgcp pri connected to callmanager (in both ISR's and CMM's). I've done extensive searching on both netpro and google and everytime this question is asked I see the same 4 mibs given as answers:
Problem with those mibs is the first (ISDN-MIB) has no actual realtime data when the l3 is backhauled to CCM (all ds0's report idle even when active) and the problem with the others is two fold...1st there is no single counter that will return total calls active, you have to retrieve each active call separately and then add up the total rows returned...2nd is that when you have devices with multiple PRI's there is no way to get information for an individual interface. The results returned represent data for the entire device and is not broken down on per interface basis.
I guess at the root, I'm looking for a way to get the same information that the RTMT tool gets in it's perfmon counters for calls active on a per interface basis via SNMP. I think to this point people have been focused on collecting that information from the endpoint whereas I believe the solution will involve querrying the CCM server the gateways are registered to.
I could be completely off my rocker but if anyone has any insight into this or an idea of a way this information could be aquired i would greatly appreciate it.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...