02-27-2014 09:20 AM - edited 03-16-2019 09:56 PM
Hi,
does anybody know an application they is able to interpret the Calllogs Tracefiles?
Open these files with notepad or any other text editor application is not user friendly.
Best regards
Stefan
02-27-2014 11:18 AM
I used Triple Combo tool before. Unfortunately, it seems the webpage was shutdown or something, since I'am receving error 404.
The link was: http://www.employees.org/~tiryaki/tc/
You can still see the the cached webpage from Google.
I could upload the program later (if I can find it in my old notebook).
02-27-2014 12:40 PM
Hi Tomas,
when i`m using Tripel Combo the result is that this tool can not interpret the Calllog files.
Maybe i`m using it in a wrong way.
Best regards
Stefan
02-27-2014 11:52 AM
Hello
Have you tried translatorX .
http://translatorx.cisco.com
Sent from Cisco Technical Support iPhone App
02-27-2014 12:43 PM
Hi Nadeem,
the first choise was to use translatorX but i`m getting the error
No Q931 or H225 message found in calllogs_XXXXXXXXX
Can you advise me how to interpret the files with translatorX.
Best regards
Stefan
02-28-2014 07:26 AM
does that logs contain the q.931/h225 messages while capturing? did you try to filter with Q.931/h225?
can you please attach the logs.
Br,
Nadeem
Please rate all useful post.
02-28-2014 07:51 AM
Hi Nadeem,
The logs does not contain such messages as Q931 H225.
The trace file i have fetched via RTMT --> Traces --> Callmanager from the CUCM 9.1.2
Since CUCM version 8.5 or 8.6, i can´t remember, the calllogs are always part of the SDL or SDI logs, but as a seperat file.
Here are a short snip of the content,
2013/10/23 16:43:06.221|CC|SETUP|26994965|26994971|0035202510528|3700|991009
2013/10/23 16:43:06.227|CC|OFFERED|26994965|26994971|0035202510528|3700|991009|10.112.72.6|UCCXp_991009
2013/10/23 16:43:06.229|CC|RELEASE|26994969|0|0
2013/10/23 16:43:09.050|CC|SETUP|26994972|26994973|0017620252087|2272|2272
2013/10/23 16:43:09.056|CC|OFFERED|26994972|26994973|0017620252087|2272|2272|10.112.72.6|SEPB4A4E3D65886
2013/10/23 16:43:15.611|CC|RELEASE|26994957|26994958|16
2013/10/23 16:43:17.978|CC|RELEASE|26994965|26994971|16
2013/10/23 16:43:24.807|CC|SETUP|26994974|26994977|0062171880767|4222|2282
2013/10/23 16:43:24.812|CC|OFFERED|26994974|26994977|0062171880767|4222|2282|10.112.72.6|SEP08D09F9E68CA
2013/10/23 16:43:34.124|CC|REJECT|26994960|26994961|1483|||1
2013/10/23 16:43:46.471|CC|RELEASE|26994947|26994954|16
2013/10/23 16:44:17.167|CC|SETUP|26994982|26994983|003741404382|4700|4700
2013/10/23 16:44:17.173|CC|OFFERED|26994982|26994983|003741404382|4700|4700|10.112.72.6|AFH_BRD
2013/10/23 16:44:17.182|CC|SETUP|26994982|26994985|003741404382|4700|991007
2013/10/23 16:44:17.187|CC|OFFERED|26994982|26994985|003741404382|4700|991007|10.112.72.6|UCCXp_991007
2013/10/23 16:44:17.189|CC|RELEASE|26994983|0|0
2013/10/23 16:44:19.160|CC|REJECT|26994978|26994979|1483|||1
2013/10/23 16:44:20.116|CC|RELEASE|26994986|26994987|16
2013/10/23 16:44:23.684|CC|RELEASE|26994982|26994985|16
2013/10/23 16:44:38.155|CC|RELEASE|26994974|26994977|16
2013/10/23 16:44:38.876|CC|RELEASE|26994972|26994973|16
2013/10/23 16:45:05.259|CC|REJECT|26994988|26994989|1483|||1
2013/10/23 16:45:30.216|CC|SETUP|26994994|26994997|001727595485|2277|4000
2013/10/23 16:45:30.223|CC|OFFERED|26994994|26994997|001727595485|2277|4000|10.112.72.6|CiscoVM2-VI1
2013/10/23 16:45:33.404|CC|RELEASE|26994994|26994997|16
2013/10/23 16:45:50.310|CC|REJECT|26994991|26994992|1483|||1
2013/10/23 16:45:52.630|CC|SETUP|26995000|26995001|005119088873|99961|99961
2013/10/23 16:45:52.636|CC|OFFERED|26995000|26995001|005119088873|99961|99961|10.112.72.8|Caseris
2013/10/23 16:45:52.637|SIPT|26995001|TCP|OUT|10.112.72.4|5060|Caseris|10.112.12.66|5060|1,100,12,120.1^*^*|1106311|cf229580-2671e120-4d0-448700a@10.112.72.4|INVITE
2013/10/23 16:45:52.642|SIPT|26995001|TCP|IN|10.112.72.4|5060|Caseris|10.112.12.66|60224|1,100,13,25500.2^10.112.12.66^*|1106312|cf229580-2671e120-4d0-448700a@10.112.72.4|100 Trying
Best regards
Stefan
02-28-2014 08:29 AM
Hello
From Call Manager 9.0 onwards, There is a new concept of CUCM traces called interleave tracing. The SDI and SDL traces have been combined into one file for various reason and aspect. The look and feel of these traces is similar to SDL yet there are several things that one needs to get used to while reading traces in this version. Traces for the CUCM are now only written to the SDL folder / filers. There will be no SDI traces available seperately.
Since there is no messages/call information contain in the call logs of q.931 and h225 this tool will give you an error. Try capture the logs again and check the information and then try to open with this tool again.
Br,
Nadeem
Please rate all useful post.
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