RTSP Pull (Beta)

From version 0.10.4, RTSP Pull input is supported as a beta version. The supported codecs are H.264, AAC(ADTS). Supported codecs will continue to be added.

This function pulls a stream from an external RTSP server and operates as an RTSP client.

Configuration

RTSP Pull is provided through OriginMap configuration. OriginMap is the rule that the Edge server pulls the stream of the Origin server. Edge server can pull a stream of origin with RTSP and OVT (protocol defined by OvenMediaEngine for Origin-Edge) protocol. See the Clustering section for more information about OVT.

<VirtualHosts>
		<VirtualHost include="VHost*.xml" />
		<VirtualHost>
			<Name>default</Name>

			<Domain>
				<Names>
					<Name>*</Name>
				</Names>
			</Domain>
			
			<Origins>
				<Origin>
					<Location>/app_name/rtsp_stream_name</Location>
					<Pass>
						<Scheme>rtsp</Scheme>
						<Urls><Url>192.168.0.200:554/</Url></Urls>
					</Pass>
				</Origin>
			</Origins>
		</VirtualHost>
	</VirtualHosts>

For example, in the above setup, when a player requests "ws://ome.com/app_name/rtsp_stream_name" to stream WebRTC, it pulls the stream from "rtsp://192.168.0.200:554" and publishes it to WebRTC.

If the app name set in Location isn't created, OvenMediaEngine creates the app with default settings. The default generated app doesn't have an OPUS encoding profile, so to use WebRTC streaming, you need to add the app to your configuration.

Publish

The pull-type provider is activated by the publisher's streaming request. And if there is no client playing for 30 seconds, the provider is automatically disabled.

According to the above setting, the RTSP pull provider operates for the following streaming URLs.

Last updated