The Multi-Protocol server on the DME serves live or stored content using the RTSP/RTP protocol. You can play the stream in StreamPlayer, QuickTime, or VLC using a URL similar to this:

Since the Multi-Protocol server uses a non-standard RTSP port (default 5544), the port number is required in the URL. There are two use cases for serving RTSP. Out-4 should be used for optimal stream stability, but if many simultaneous users are expected, the equivalent Out-3 is preferred. There are three possible protocols used for RTP serving: UDP; TCP using RTSP interleaved; TCP using HTTP tunneling. Out-4 supports all three of these options while Out-3 does not support HTTP tunneling. This difference may determine which RTSP/RTP server to utilize.

This output option requires no explicit configuration on the DME but is available for all live content present on the Multi-Protocol server, whether brought directly into the server or Pulled from the RTP server using an internal In-6. An example of a live publishing point is:

There are two options for serving RTSP. Out-4 is used if the VOD content contains MPEG‑4 Part2 video or PCM audio. Since Out-4 is more generally applicable it is recommended for this use case. Stored content is accessed using the filename of the content. Examples of stored URLs are:

The RTP server on the DME serves RTP files. Play the stream in StreamPlayer, QuickTime, or VLC using a URL similar to this:

Since the Multi Protocol RTP server uses an non-standard RTSP port – default 5544 – normally the port must be explicitly included in the URL.

 

Objective: This use case explains how a stream available on the Multi Protocol server is served to clients that support RTSP streams. Further, this server is commonly used for delivering VOD content.

From a client that supports RTSP RTP streams, enter the RTSP URL, typically: