TranslatorX
Cisco Unified Communications Manager Trace Tool
TranslatorX allows you to quickly parse through Cisco CallManager trace files and search for Q.931, H.225, SCCP (Skinny), MGCP, or SIP messages. Some parts of TranslatorX are still under development. For example, although SCCP, MGCP, and SIP messages are parsed and searchable, no additional decoding is done on the individual messages. Q.931 and H225 messages however are fully decoded.

You can filter messages by IP address, Direction, Protocol, Message Type, or Call Reference/TCP Handle. For Q.931/H.225 messages TranslatorX can be set to only show calls that had an abnormal disconnect or any abnormal cause code.

Version 8.0(1) adds support for Unified CM version 8.0 and also adds the ability to open a whole folder structure at once. This means you can download traces using the real-time monitoring tool (RTMT) and point TranslatorX to the root folder of traces and the tool will search through all the traces in the folder (provided that you select the checkbox to search subfolders).

TranslatorX is available for MacOS X, Windows 2000/XP/Vista/7, and Linux (requires GTK2 libraries). Download TranslatorX below.

Downloads

Version History

8.6(1)

  • Support for CUCM 8.6 trace files

8.5(1)

  • Support for CUCM 8.5 trace files
  • *NEW* Message Sequence Diagram generation. Filter as you wish then click "Generate Chart" to see a nice MSC of the message flow. Click on any message to see the detailed decoded version.
  • Support for H.245 messages
  • Support for H.225 ASN.1 output
  • Support for Correlating H.245 messages to the associated H.225 messages. If you filter by call reference for H.225, you will get the associated H.245 messages
  • Various bug fixes
  • Better SCCP to IP Address correlation. Doesn't require keepalives to be enabled. You should pretty much never see not found for an IP address anymore.
  • Call List support. There is a separate window that shows you a call list derived from CDR data printed in the CCM traces. CDR must be enabled for this to work.
  • If you double-click on a call in the call list, you will get the full CDR data dump for the call (todo: include CMR data) with many fields decoded for you
  • Generate Filter based on Call. From the call list you can click a call and select Generate Filter. This will automatically generate a filter for the two call legs of the call listed in the CDR for the timeframe listed in the CDR. Note that this works best in 8.0 and later which have call reference information listed in the CDR. For any record that does not have call ref data, right now I only filter for the timeframe of the call for the IP address of the device, so it may include more than just messages for that one call. I've got some more work to do in this area to do some heuristic analysis based on the data in the CDR to generate a better filter, but this is pretty good for now.

Support

TranslatorX is not a Cisco TAC-supported tool, however we welcome any suggestions on improving the application and and would like to know about any problems you may experience while using TranslatorX. Please send all feedback to TranslatorX@cisco.com.

Last modified Mon, Aug 22, 2011 by Paul Giralt.