these lines show the date/time, traceType (CCM) and Process (StationInit, etc...) along with alot of other information that details phone ip, ccm ip, clusterID....more
StationD: - is a message from callManager to an IP phone
StationInit: - is a message from an IP phone to callManager
DigitAnalysis: - is callManager doing digit matching on the digits entered for making a call against the dialPlan
you may notice that the IP Phone does nothing unless callManager tells it to.
typical phone call includes:
1) ip phone goes off-hook. sends a StationInit message to callManager that it is off-hook.
2) callManager sends a StationD message to the phone to play DialTone.
3) the ip phone begins to play dialTone until a button is pressed or timesout to a busySignal.
4) upon user pressing a button, ip phone sends a StationInit message to callManger with the button pressed.
5) callManger sends a StationD message to the phone to stop playing dialTone.
6) callManager performs a digit analysis to see if the dialPlan has an entry for the digit(s) entered. this continues until callManager finds a dialPlan match and forwards the call to the appropriate endpoint or finds no match and sends a StationD message to the ip phone to play FastBusy tone.
7) once callManager finds a match it performs call Setup with the two endpoints involved. (usually an ip phone & gateway or ip phone & ip phone.) these messages include OpenReceiveChannel and startMediaTransmission, among many others depending on the call leg.
8) once you see startMediaTransmission from both endpoints, callManager leaves the conversation and the two endpoints communicate directly with each other. (startMediaTransmission means that all call setup is completed and the devices can begin sending RTP streams to each other)
there are many more processes involved among possibly many different endpoints and procedures. cannot tell you all here.
an excellent book to learn as much as possible is Cisco Press: 'Troubleshooting Cisco IP Telephony".
there are also ways to know which messages belong to which call and/or callLeg. these are TCP handles and callIDs uses in the messages which are explained in the book mentioned above as well.
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...