|length of the data following this header |
|response code from server |
|number of items in the 'transports' variable below |
|Time range of the streams that the server will stream. |
|describes the complete "Transport:" line of the server in response to a SETUP RTSP command by the client |
|sequence number |
|the "Session:" field. |
|the "Location:" field. |
|the "RealChallenge1:" field from the server |
|the "Server: field, which can be used to identify some special-case servers that are not 100% standards-compliant. |
|The "timeout" comes as part of the server response to the "SETUP" command, in the "Session: <xyz>[;timeout=<value>]" line. |
|The "Notice" or "X-Notice" field value. |
|The "reason" is meant to specify better the meaning of the error code returned. |
The "Notice" or "X-Notice" field value.
See http://tools.ietf.org/html/draft-stiemerling-rtsp-announce-00 for a complete list of supported values.
the "Server: field, which can be used to identify some special-case servers that are not 100% standards-compliant.
We use this to identify Windows Media Server, which has a value "WMServer/v.e.r.sion", where version is a sequence of digits (e.g. 188.8.131.5272). Helix/Real servers use something like "Helix [..] Server Version v.e.r.sion (platform) (RealServer compatible)" or "RealServer Version v.e.r.sion (platform)", where platform is the output of $uname -msr | sed 's/ /-/g'.
The "timeout" comes as part of the server response to the "SETUP" command, in the "Session: <xyz>[;timeout=<value>]" line.
It is the time, in seconds, that the server will go without traffic over the RTSP/TCP connection before it closes the connection. To prevent this, sent dummy requests (e.g. OPTIONS) with intervals smaller than this value.