Hi, Michael:
There is no problem. But you should test it with your own data captured.
If your ethereal works fine on SCCP layer, it should work on TCAP.
Regards,
Samuel
----- Original Message -----
From: "Michael Tuexen" <Michael.Tuexen@xxxxxxxxxxxxxxxxx>
To: "Samuel Qu" <samuel.qu@xxxxxxxxxx>
Cc: "Jeff Morriss" <jeff.morriss@xxxxxxxxxxx>; <ethereal-dev@xxxxxxxxxxxx>;
"'Kingwel Xie'" <kingwel.xie@xxxxxxxxxx>
Sent: Monday, June 10, 2002 9:38 AM
Subject: Re: [Ethereal-dev] Re: for test
> Samual,
>
> can you provide a small tracefile (send it to
> Michael.Tuexen@xxxxxxxxxxxxxxxxx)?
> I will look into the stuff and see what the problem is.
>
> Best regards
> Michael
>
> On Tuesday, June 11, 2002, at 01:38 AM, Samuel Qu wrote:
>
> > Hi, Jeff:
> >
> > We use M3UA v4. Also there is some modification in SCCP and other
> > layers(?).
> > You can contact Kingwel for details or source code.
> >
> > Regards,
> >
> > Samuel
> >
> > www.utstar.com
> >
> > ----- Original Message -----
> > From: "Jeff Morriss" <jeff.morriss@xxxxxxxxxxx>
> > To: "Samuel Qu" <samuel.qu@xxxxxxxxxx>
> > Sent: Friday, June 07, 2002 3:45 PM
> > Subject: Re: for test
> >
> >
> >>
> >> Samuel,
> >>
> >> Can you tell me settings you're using to test this with? And maybe
> >> what
> >> Ethereal version?
> >>
> >> I have figured out these settings:
> >> - SCTP set to CRC32
> >> - M3UA set to version 6
> >> - MTP3 set to ITU
> >> - SCCP modified to use SIO 9
> >>
> >> and still the data comes out as garbage (even SCCP does not dissect
> >> properly).
> >>
> >> I'm using Ethereal from CVS as of today. What are you using?
> >>
> >> Regards,
> >> -Jeff
> >>
> >> Samuel Qu wrote:
> >>> use this file to test the dissector.
> >>
> >>
> >>
> >> --
> >> Jeff Morriss
> >> Senior Support Engineer
> >> Ulticom, Inc.
> >> Helpdesk: +1-856-787-2765
> >> Fax: +1-856-222-9947
> >
> >
> > _______________________________________________
> > Ethereal-dev mailing list
> > Ethereal-dev@xxxxxxxxxxxx
> > http://www.ethereal.com/mailman/listinfo/ethereal-dev
> >
> >
> Michael.Tuexen@xxxxxxxxxxxxxxxxx