Ethereal-users: Re: [Ethereal-users] SCTP PPID for M3UA.
The SCTP dissector looks at the PPID first and the port number
second. So if the PPID is 0, then the port number should be
2905.
RFC 3332 states:
The SCTP Payload Protocol Identifier value "3" SHOULD be included in
each SCTP DATA chunk, to indicate that the SCTP is carrying the M3UA
protocol.
So I think one of your vendors should fix it...
Nevertheless we have to add SCTP support to the 'Decode as' dialog...
As a start I have added a possibility to chose which upper layer is
used for PPID 0. This should work for you. It is in the svn now.
Best regards
Michael
On Aug 18, 2004, at 6:23 AM, Paul Jeffress wrote:
Hi,
We use SS7 equipment from two vendors, one of which does not use the
standard SCTP PPID of 3, for their M3UA packets. Instead they use 0.
I had a look at sctpppids.h and see
#define NOT_SPECIFIED_PROTOCOL_ID 0
#define IUA_PAYLOAD_PROTOCOL_ID 1
#define M2UA_PAYLOAD_PROTOCOL_ID 2
#define M3UA_PAYLOAD_PROTOCOL_ID 3
#define SUA_PAYLOAD_PROTOCOL_ID 4
Is there any way to cause Ethereal to interpret a PPID of 0 or 3 as
M3UA, so I can decode both my vendors M3UA correctly?.
I also had a look to try and change the code myself, but it's been
toooooo long since I've coded and could not figure it out.
Thanks,
Paul
Paul Jeffress
Voice Architect
Comindico Australia
(Ph) +61 2 8220 6193
(Fx) +61 2 9252 6865
(Mb) +61 410 603 648
, paul1[A T]comindico.com.au
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
