Real-Time Streaming Protocol: Difference between revisions

Revision as of 20:04, 10 February 2023

Revision as of 11:40, 5 March 2023

Line 18:

==Protocol directives==

While similar in some ways to [[HTTP]], RTSP defines control sequences useful in controlling multimedia playback. While HTTP is [[stateless server|stateless]], RTSP has a state; an identifier is used when needed to track concurrent sessions. Like HTTP, RTSP uses TCP to maintain an end-to-end connection and, while most RTSP control messages are sent by the client to the server, some commands travel in the other direction (i.e. from server to client).

Presented here are the basic RTSP requests. Some typical [[HTTP request]]s, like the OPTIONS request, are also available. The default transport layer [[port number]] is 554<ref name=":0" /> for both [[Transmission Control Protocol|TCP]] and [[User Datagram Protocol|UDP]], the latter being rarely used for the control requests.

Line 36:

=== DESCRIBE ===

: A DESCRIBE request includes an RTSP [[Uniform Resource Locator|URL]] <nowiki>(rtsp://...)</nowiki>, and the type of reply data that can be handled. This reply includes the presentation description, typically in [[Session Description Protocol]] (SDP) format. Among other things, the presentation description lists the media streams controlled with the aggregate URL. In the typical case, there is one media stream each for audio and video streamstreams. The media stream URLs are either obtained directly from the SDP control fields or they are obtained by appending the SDP control field to the aggregate URL.

<pre>

C->S: DESCRIBE rtsp://example.com/media.mp4 RTSP/1.0

Line 116:

=== RECORD ===

: This method initiates recording a range of media data according to the presentation description. The time stamptimestamp reflects the start and end time(UTC). If no time range is given, use the start or end time provided in the presentation description. If the session has already started, commence recording immediately. The server decides whether to store the recorded data under the request URI or another URI. If the server does not use the request URI, the response should be 201 and contain an entity which describes the states of the request and refers to the new resource, and a Location header.

<pre>

C->S: RECORD rtsp://example.com/media.mp4 RTSP/1.0

Line 129:

=== ANNOUNCE ===

The ANNOUNCE method serves two purposes:

: When sent from client to server, ANNOUNCE posts the description of a presentation or media object identified by the request URL to a server. When sent from server to client, ANNOUNCE updates the session description in real- time. If a new media stream is added to a presentation (e.g., during a live presentation), the whole presentation description should be sent again, rather than just the additional components, so that components can be deleted.

{{pre|1=<span class="plainlinks">

C->S: ANNOUNCE rtsp://example.com/media.mp4 RTSP/1.0

Line 155:

=== TEARDOWN ===

: A TEARDOWN request is used to terminate the session. It stops all media streams and frees all session -related data on the server.

<pre>

C->S: TEARDOWN rtsp://example.com/media.mp4 RTSP/1.0

Line 248:

===Server===

* [[Darwin Streaming Server]]: Open-sourced version of QuickTime Streaming Server maintained by Apple.

*[[Feng (program)|Feng]]: Lean and mean streaming server with a focus on rfcRFC compliance.

* [[GStreamer]] based RTSP Server and client.

* [[Helix (project)|Helix DNA Server]]: [[RealNetworks]]' streaming server. Comes in both open-source and proprietary flavors.

Line 262:

*[[YouTube]] implemented a [[mobile web]] front end in June 2007 which serves video through this protocol.<ref>{{cite web |title=YouTube Mobile A Bust! (Getting 3GP/RTSP to work on WM5) |url=https://chrisduke.tv/youtube-mobile-a-bust |website=Chris Duke |access-date=29 May 2021 |date=2007-06-23}}</ref>

Many [[Closed-circuit television|CCTV]] / Security cameras, often called [[IP camera]]s, support RTSP streaming too, especially thesethose with [[ONVIF]] profiles G, S, T.

===Client===

Line 291:

* {{cite web |url=http://www.rtsp.org |archive-url=https://web.archive.org/web/20070306002838/http://www.rtsp.org/ |archive-date=2007-03-06 |title=Real Time Streaming Protocol Information and Updates}}, a central information repository about RTSP.

* {{cite web |url=https://developer.apple.com/quicktime/icefloe/dispatch028.html |archive-url=https://web.archive.org/web/20130501053040/https://developer.apple.com/quicktime/icefloe/dispatch028.html |archive-date=2013-05-01 |title=Tunnelling RTSP and RTP through HTTP}}, A standard solution to help RTSP work through firewalls and web proxies

* "[http://www.codeproject.com/Articles/507218/Managed-Media-Aggregation-using-Rtsp-and-Rtp Managed Media Aggregation using Rtsp and Rtp]", Walks a developer through the implementation of a standards -compliant RtspClient and RtspServer.

{{Digital audio and video protocols}}