Guy Harris wrote:
>
> The RTSP dissector *does* register particular conversations as
> conversations that should be dissected with the RTP or RTCP dissector
> (see "rtsp_create_conversation()" in "packet-rtsp.c"), so *if*
> NetMeeting sets up the session with RTSP *and* the RTSP packets which do
> so are in the capture *and* the packets in question are recognized by
> the RTSP dissector (see "process_rtsp_request_or_reply()" in the RTSP
> dissector), *then* it should dissect the RTP and/or RTCP packets
This is exactly what I thought. My reference to "active" (a poor choice
of works, but I was not sure what else to use) was really to number two
below. I knew about the non static port numbers, but had not looked at
rtsp_create_conversation(). I guess I overlooked it.
Thanks.
>
> Otherwise, you'd have to
>
> 1) change Ethereal to dissect whatever other protocol is used to
> set up the RTP and RTCP sessions or make it handle whatever
> RTSP packets are used;
>
> 2) add (e.g., with per-protocol preferences for RTP and RTCP, or
> with a UI option to mark a particular conversation as being
> RTP or RTCP, e.g. with a menu item "mark current packet as
> part of a conversation with a paritcular protocol") a
> mechanism to the UI to arrange that Ethereal be able to
> recognize RTP or RTCP packets *without* the help of RTSP.
IIRC, there was some talk of generic code to do this through
preferences. Whatever happened to that?
--john
--
John McDermott, Writer and Consultant
J-K International, Ltd.
V +1 505/377-6293 F +1 505/377-6313
jjm@xxxxxxxxxx