10-17-2009 01:25 AM - edited 03-15-2019 08:07 PM
Can anybody help with trace files. I have a copy of the book IP telephony troubleshooting which helps with some decode of trace files. However it doesn't give the full picture. for example.
The line
wait_AuDisconnectReply - removing MediaManager(1480309) from connection list|<CLID::Beds-Cluster><NID::10.1.250.12><CT::6,100,131,1.15094331
I have found somewhere that The last part that starts with CT: gives a clue as to what other nodes in the cluster are involved with the call.
can anyone help decipher this and also are there any other resources that can help decode traces
Solved! Go to Solution.
10-18-2009 04:35 PM
To know which nodes are involve in a call you use SDL traces, you dont really use the CT field.
SDL shows you when we contact other nodes or process.
To answer you question
In this case CT:
6 means number of CTI ID for server in cluster
100 ccm process
131 instace of process in this case Media Manager
This may change from version to version, but you dont really use the right side of the line when reading cucm traces :) Its misleading most of the times.
the 1.15... is some timer, to be honest not sure what it means and we never use it :) at least for the past 7 years
Like any other trace file you dont really need to understand every single field in each line, but the most important part, some DEs just add extra lines for info or is some just trash does not give you any detail about a call failing, other ERRORs can be normal, unfortunately or fortunately, the experience is the best source of knowledge when reading Cisco CUCM traces, even us working for Cisco in CUCM product we go to IPCBU for SDI/SDL training once in a while.
HTH
10-18-2009 04:35 PM
To know which nodes are involve in a call you use SDL traces, you dont really use the CT field.
SDL shows you when we contact other nodes or process.
To answer you question
In this case CT:
6 means number of CTI ID for server in cluster
100 ccm process
131 instace of process in this case Media Manager
This may change from version to version, but you dont really use the right side of the line when reading cucm traces :) Its misleading most of the times.
the 1.15... is some timer, to be honest not sure what it means and we never use it :) at least for the past 7 years
Like any other trace file you dont really need to understand every single field in each line, but the most important part, some DEs just add extra lines for info or is some just trash does not give you any detail about a call failing, other ERRORs can be normal, unfortunately or fortunately, the experience is the best source of knowledge when reading Cisco CUCM traces, even us working for Cisco in CUCM product we go to IPCBU for SDI/SDL training once in a while.
HTH
10-19-2009 12:32 AM
Many thanks, for the excellent info.
very much appreciated
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide