Real-time Streaming Protocol (RTSP)

RTSP is used to set up real-time media streams, e.g. ones using RTP and RTCP.

History

RTSP was first specified in RFC2326.

Protocol dependencies

Example traffic

XXX - Add example traffic here (as plain text or Wireshark screenshot).

Wireshark

The RTSP dissector is fully functional over TCP, but currently doesn't handle RTSP-over-UDP.

Preference Settings

There are four preference settings affecting RTSP.

RTSP TCP Port:

This preference specifies the first of the TCP ports on which the RTSP dissector will check for traffic. The default is 554.

Alternate RTSP TCP Port:

This preference specifies the second of the TCP ports on which the RTSP dissector will check for traffic. The default is 8554.

Reassemble RTSP headers spanning multiple TCP segments:

When this preference is enabled, then the RTSP dissector will reassemble the RTSP header if it has been transmitted over more than one TCP segment. Although it is unusual for headers span multiple segments, it's not impossible, and this should be checked if you expect to view the contents of the RTSP conversation.

Reassemble RTSP bodies spanning multiple TCP segments:

When this preference is enabled, then the RTSP dissector will reassemble the RTSP body if it has been transmitted over more than one TCP segment.

Example capture file

This capture file is 8MB in size, and isn't recognised by the current version of Wireshark as being in a valid format...

Display Filter

A complete list of RTSP display filter fields can be found in the display filter reference

Capture Filter

You cannot directly filter RTSP protocols while capturing. However, if you know the TCP port used (see above), you can filter on that one.

Discussion

RTSP (last edited 2008-04-12 17:51:26 by localhost)