I'm trying to prove that a disruption in service a few days ago was due to all our PRI channels being in use. Symptom to users was fast-busy when trying to place calls.
We did have full tracing turned on while the disruption occurred. I've collected the trace logs for the period in question for the Call Manager service. But I'm wondering what I should be looking for within the log files to be confident that the issue was due to all the PRI channels being in use. I would think that there should be some tell-tale entry in the log file indicating this - but I don't know what it would look like.
if you have the CUCM traces as i believe you do, then you'll need to start counting the setups and teardowns on that particular PRI.
what the messages look like depends of the protocol, MGCP or H323. but if you have it, it's just a matter of looking in X time period how many setups and how many teardowns were made to get the actual number of calls active in a given time
you can try using VLT or the triple combo to make it easier and not look directly at the txt in wordpad
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...