Thanks Anders and Jim,
I have just had a look at the AMR dissector and it will be
very useful for me in solving this problem - thanks for the tip. Unfortunatly
there is no control information sent to setup the protocol as no control channel
is available in this application. Payload type 96 is always
used.
I will add a preferences page similar to AMR to allow the
dissector to be turned on and off, and I will default it to off. This should
solve the problem.
Thanks,
Mark
Hi,
If
there is control information sent setting up the RTP connection you could use
the mechanism used in the SDP dissector to set up a RTP
converstion
and
transfer data about the Media type used for that
conversation.
The
AMR dissector has a preference setting (default 0 = not used) to dissect a
specified PT as AMR.
Brg
Anders
Hello,
The protocol defines
that this data is always sent with RTP payload type 96 (0x60). My plug-in
currently recognizes all RTP traffic with payload type 96 as belonging to this
protocol. However, payload type 96 is specified by RTP as dynamic and may be
used for other purposes within other protocols. I don't want to issue my plug-in
and then find that data of type 96 that is not Pro-MPEG FEC is then dissected as
such.
Please could
somebody suggest the a mechanism for dealing with this
problem?
Thanks,
Mark
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
