Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

Trace file understanding

Hi again :)

I'm trying to understand SDL trace file. The thing that I don't understand is how to find out what is correct Calling Search Space (CSS) of the calling line/phone? When I collect trace file with RTMT (or open it with notepad), the only thing I can see is something like this: CI=2349238, CSS=858730c4-bd44-blah-blah-blah-blah, aarCSS=, etc.

So... how can I translate this big amount of text behind word CSS into a correct name of existing Calling Search Space?


Re: Trace file understanding

What info are you trying to look for? SDL traces are made mostly for developers to look at. If you are trying to follow call flows and troubleshoot issues then you will want to get just callmanager traces. You won't really find anybody that will be able to read the SDL traces unless they work for Cisco.


Community Member

Re: Trace file understanding

Well, I'm trying to figure it out how SDL trace is related to Calling Search Space names :) I'm employed as an Cisco Certificated Systems Instructor and I'm currently in preparation of TUC (642-426) exam. On the mentioned exam, there are lot of questions that are 100% related to troubleshooting through SDL trace. So I assume I need to learn a little more of SDL tracing so I can maybe do some better troubleshooting, pass the exam and teach my students with more tips:)

I'm just curious, not realy in trouble or real-life problem. If anyone know where I can find more about advanced SDL tracing, please feel free to contact me. And again, if anyone knows how to co-relate CSS from SDL trace (previous post from me) to CSS name, thanks again:)


Re: Trace file understanding

In CCM -SDI- traces you will find in the Digit Analisys line someting like pss="A:B:C"

You will find it looking for dd="9011525557996298" for example, or the number you dialed.

Those are the partitions listed in your CSS.

In SDL traces you may find:

000003519| 06/01/31 17:43:49.770| 001| SdlSig | CcRegisterPartyA | tcc_idle0 | Cdcc(1,100,22,1) | Cc(1,100,21,1) | (1,100,118,1).139-(SEP000BDB41EB10:| [R:NP - HP: 0, NP: 1, LP: 0, VLP: 0, LZP: 0 DBP: 0]CI= 16777220 PSS={4888D2AA-E52A-4502-BFC4-08D0D9F46382} aarCSS= aarEDev=1 fQDN=1003 CallRef=0 OLCap=0 Name=Internal 1003 NamePi=0 CType=3 XferMode= CT=0 ta.ip=4194410688 ta.port=0 reg=REGION_SMITHS cap=5 devType=4 mixCId=0 mediaReq=0 PTPInfo.loc=0 MOH.MRGL= MOH.userMOHID=2 MOH.networkMOHID=1 MOH.suppMOH=0 devName=SEP000BDB41EB10 ctiAct=0 farEndDev=1 cMId=1 devCepn={B0343EBE-7ADB-429A-8443-D5443389F4DC} devLoc=1 actCaps=0 VideoCall=0 VideoCapable=0 CryptoCapCount=0 secureStatus=1 loginUserId= isPathReplacementSupported=0 retriedVideo=0 nwLoc=OnNet

where PSS={4888D2AA-E52A-4502-BFC4-08D0D9F46382} is just the PKID of that CSS in SQL.

I would first recommend learning SDI then move to SDL, normally looking into SDL requires more experience and a deep understanding of CCM modules...that is mostly used here in Cisco.


Community Member

Re: Trace file understanding

Thanks a lot, I will listen to your advice and prepare my course entirely based on SDI trace and maybe a bit of SDL if I can find anything interesting there that I can understand well.


CreatePlease to create content