converted to 1.6 markup
This capture file isn't recognized by Wireshark as a known capture file type because it's apparently a QuickTime movie file, not a capture.
|Deletions are marked like this.||Additions are marked like this.|
|Line 45:||Line 45:|
|This capture file is 8MB in size, and isn't recognised by the current version of Wireshark as being in a valid format...
Real-time Streaming Protocol (RTSP)
RTSP was first specified in RFC2326.
XXX - Add example traffic here (as plain text or Wireshark screenshot).
The RTSP dissector is fully functional over TCP, but currently doesn't handle RTSP-over-UDP.
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
A complete list of RTSP display filter fields can be found in the display filter reference
Show only the RTSP based traffic:
You cannot directly filter RTSP protocols while capturing. However, if you know the TCP port used (see above), you can filter on that one.
Capture RTSP traffic over the default port (554):
tcp port 554
Capture RTSP traffic over the alternate port (8554):
tcp port 8554
RFC2326 Real Time Streaming Protocol (RTSP)