To be honest, those particular parts of the trace aren't used very often, at
least not in detail. The device and node may be of interest, but the rest
may not. Full disclosure - I was never a TAC engineer for CUCM.
What you'll probably find more useful to decode SDI traces (forget about
SDL) is TripleCombo or TranslatorX. Translator X works better on Macs, and
Triplecombo on Windows.
http://www.employees.org/~tiryaki/tc/
http://www.employees.org/~pgiralt/TranslatorX/
This is what a large portion of TAC uses to parse through traces and the
makers have been so gracious to make it publicly available. Now decoding it
from here is a totally different story that generally requires intimate
knowledge of the protocol you're looking at, whether it be JTAPI, SCCP, SIP,
H.323, MGCP, or internal CUCM processes. This helps, a lot.
-nick
On Thu, Aug 26, 2010 at 8:37 PM, Ryan West <rwest_at_zyedge.com> wrote:
> Achi,
>
> > -----Original Message-----
> > From: Atsuhiro Nakamura [mailto:a-naka_at_mtf.biglobe.ne.jp]
> > Sent: Thursday, August 26, 2010 8:04 PM
> > To: Ryan West
> > Cc: ccielab_at_groupstudy.com
> > Subject: Re: How to read CUCM SDI Trace?
> >
> > Dear Ryan,
> >
> > Thank you for your comment.
> >
> > Cisco-voip means another mailing group?
> >
> > Could I have the mail address which I should post this to?
> >
>
> cisco-voip mailing list
> cisco-voip_at_puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> HTH,
>
> -ryan
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Thu Aug 26 2010 - 21:00:04 ART
This archive was generated by hypermail 2.2.0 : Wed Sep 01 2010 - 11:20:53 ART