Michael,
> this means that we have both important MTP users available in
> Ethereal, that is great.
Agreed. Of course, porting the ISUP dissector to ANSI is
a-whole-nother-problem, but... ITU users should be pretty happy for
now. :)
> I would suggest not to rely on te the MTP3 dissector for the
> ITU/ANSI decission, because if we use M3UA/SCTP for the transport
> NO MTP3 is involved anymore. This means that a use would have
> to set MTP3 preferences even this protocol is not involved in the stack.
Hmmm... I must admit I am not as familiar with M3UA as I should be. I
had thought that M3UA called MTP3 for protocol payloads, but in looking
now I note that it only does so in certain cases (DATA_1 and DATA_2).
Oh well...
However, I don't really like the idea of having, for example, the same
(but separate) protocol preference in MTP3, SCCP, and ISUP (maybe also
L3MTP-MG, SCCP-MG, and TCAP if someone gets really bored?). I tend to
work in both protocols (okay, also Chinese SS7 and several of the
Japanese variants) and I wouldn't want switching between them to be a
royal pain...
What about having the preference stored in MTP3 but the preference show
up in each protocol? I guess that's easy enough... I'll see how that
works and submit a patch unless anyone has an objection.
Regards,
-Jeff
> > Hello list,
> >
> > As promised long, long ago, here's my SCCP dissector. It does both ITU
> > and ANSI formats (it picks up the preference from the MTP3 dissector).
> > The MTP3 patch is diff'd against CVS.
> >
> > Enjoy,
> > -Jeff
begin:vcard
n:Morriss;Jeff
tel;fax:+1-856-222-9947
tel;work:+1-856-787-2824
x-mozilla-html:FALSE
url:http://www.ulticom.com
org:Ulticom, Inc.;Customer Support
version:2.1
email;internet:jeff.morriss[AT]ulticom.com
title:Senior Support Engineer
adr;quoted-printable:;;Ulticom, Inc.=0D=0A1020 Briggs Rd.=0D=0A;Mount Laurel;NJ;08054;USA
fn:Jeff Morriss
end:vcard
