VBrick dme, Руководство администратора

Страница: 67 / 219

Configure a DME Stream
DME Admin Guide 55
Out-1 > Serve (RTMP)
Live streams content can be served via unicast RTMP. Note that the port generally will not
have to be defined in the URL provided the default port 1935 is used. You can play the
stream in a Flash player using a URL similar to the following:
rtmp://server:port/application/publishing_point
For live streams the publishing point is the stream name and the application is typically
“live”. For stored the publishing point is the file name and the application is “vod”. No
explicit configuration of this option is required.

To configure a server (RTMP) output:
Objective : This use case is typically used to allow Flash clients using RTMP streaming to
acquire a live stream or a VOD stream.
1. Enter the RTMP URL information in the embedded Flash client with an application of
live or vod depending on the type of content served.
Input and Output DME Streams
O u t - 2 > Se rv e T S v ia R T SP
You can serve available live streams and stored files via unicast RTSP/TS. Note that the port
must be explicitly identified in the URL. The port required is the Multi Protocol server port -
default 5544.
Live
No explicit configuration of this option is required. All live streams in Multi-Protocol server
are available for serving via an appropriate URL. Generally only Transport streams
containing H.264 video are supported, but for transport streams which are brought into the
DME using a transport stream protocol and are transmitted using transport stream protocol,
any codec will be supported. This allows support of MPEG-2 video in transport stream for
this use case. There are number of possible formats for the URLs. The recommended URL
format includes “
ts
” in the URL path:
rtsp://<dme_ip_address:port>/ts/<stream_name>
Alternate URLs are available for backward compatibility. These URLS are not
recommended. If the stream has been provided using a TS push only (In-4) the following
URLs are acceptable:
rtsp://<dme_ip_address:port>/<stream_name>_ts
rtsp://<dme_ip_address:port>/ts/<stream_name>_ts
rtsp://<dme_ip_address:port><stream_name>?ForceTS
rtsp://<dme_ip_address:port><stream_name>_ts>?ForceTS
rtsp://<dme_ip_address:port>/ts/<stream_name>?ForceTS
rtsp://<dme_ip_address:port>/ts/<stream_name>_ts>?ForceTS
If the stream has been provided using another Input use cases, the following URLs are legal:
rtsp://<dme_ip_address:port><stream_name>?ForceTS
rtsp://<dme_ip_address:port>/ts/<stream_name>?ForceTS