#include <rtsp.h>
Data Fields | |
| int | content_length |
| length of the data following this header | |
| enum RTSPStatusCode | status_code |
| response code from server | |
| int | nb_transports |
| number of items in the 'transports' variable below | |
| int64_t | range_start |
| Time range of the streams that the server will stream. | |
| int64_t | range_end |
| RTSPTransportField | transports [RTSP_MAX_TRANSPORTS] |
| describes the complete "Transport:" line of the server in response to a SETUP RTSP command by the client | |
| int | seq |
| sequence number | |
| char | session_id [512] |
| the "Session:" field. | |
| char | location [4096] |
| the "Location:" field. | |
| char | real_challenge [64] |
| the "RealChallenge1:" field from the server | |
| char | server [64] |
| the "Server: field, which can be used to identify some special-case servers that are not 100% standards-compliant. | |
| int | timeout |
| The "timeout" comes as part of the server response to the "SETUP" command, in the "Session: <xyz>[;timeout=<value>]" line. | |
| int | notice |
| The "Notice" or "X-Notice" field value. | |
| char | reason [256] |
| The "reason" is meant to specify better the meaning of the error code returned. | |
Definition at line 114 of file rtsp.h.
| char RTSPMessageHeader::location[4096] |
number of items in the 'transports' variable below
Definition at line 121 of file rtsp.h.
Referenced by find_transport().
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.
| int64_t RTSPMessageHeader::range_end |
| int64_t RTSPMessageHeader::range_start |
Time range of the streams that the server will stream.
In AV_TIME_BASE unit, AV_NOPTS_VALUE if not used
Definition at line 125 of file rtsp.h.
Referenced by rtsp_read_play().
| char RTSPMessageHeader::real_challenge[64] |
| char RTSPMessageHeader::reason[256] |
| char RTSPMessageHeader::server[64] |
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. 9.0.0.3372). 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'.
| char RTSPMessageHeader::session_id[512] |
the "Session:" field.
This value is initially set by the server and should be re-transmitted by the client in every RTSP command.
Definition at line 135 of file rtsp.h.
Referenced by rtsp_cmd_pause(), rtsp_cmd_play(), rtsp_cmd_setup(), and rtsp_cmd_teardown().
response code from server
Definition at line 118 of file rtsp.h.
Referenced by ff_rtsp_setup_input_streams(), ff_rtsp_setup_output_streams(), rtsp_read_packet(), rtsp_read_pause(), rtsp_read_play(), and rtsp_write_record().
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.
| RTSPTransportField RTSPMessageHeader::transports[RTSP_MAX_TRANSPORTS] |
describes the complete "Transport:" line of the server in response to a SETUP RTSP command by the client
Definition at line 129 of file rtsp.h.
Referenced by find_transport().
1.5.8