Page Comparison

...

Configuration Article | CA-20201130-TP-16 VDG Sense | Setup | Plugins | RTSP Server Image Added

View file name CA-20201130-TP-16.pdf

Real Time Streaming Protocol (RTSP)

The RTSP protocol is an open protocol which facilitates the transfer of audio and video over an IP network. In order to make Sense video available through RTSP, the RTSP plugin is required. This plugin can supply live and on-demand video through an RTSP interface for up to 32 devices simultaneously. Usage of this plugin requires an API License and a minimum of one Sense management server to be available within the network.

Functionality

When the plugin is active, an RTSP stream can be initiated from several media players through a customized URL. The arguments within this URL sets the way in which the video is transmitted.

...

Note: Transcoding playback data is not supported!

Audio

(supported from VDG Sense version 2.7.3. and higher)

The RTSP plugin is capable of sending audio with the requested video in the following formats:

• ulaw/mlaw

• G.711

• G.722

• G.726

• GmsAmr

• PCM

By default, audio is not send along with the video. To request audio, add the ‘audio’ parameter to the RTSP request, for example:

• rtsp://172.21.240.91/17167089910108338829?device=19&audio=1

NOTE: Audio will not work if the transcode option is used

Authentication

After initiating an RTSP stream, the server will require a username and password. These are identical to those set within the Sense Plugin Manager, please note that the Sense user needs to have sufficient permission for the camera which is requested. Both the username and password are case-sensitive. Figure 3 illustrate the login procedure within VLC media player.

...

Figure 3: Logging in on the RTSP server.

Dual StreamingDualStreaming

By providing a width URI URL parameter, it’s possible to make use of the dual streaming capabilities of a device.

...

• Dual stream url:
  rtsp://<address>/<server-id>?device=<device-id>&width=320
  The width parameter is send to the server, the server determines the correct stream, based on the dual stream setting for the max panel width. No transcoding is performed.

• Explicitly request first stream:
  rtsp://<address>/<server-id>?device=<device-id>&stream=1

• Explicitly request the second stream:
  rtsp://<address>/<server-id>?device=<device-id>&stream=2

Transcoding

The supplied video can be transcoded. In that case the video will always be supplied in JPEG format, and can be adjusted for the required height, width, quality and bandwidth, if specified. This can be accomplished by combining the transcode (do or do not transcode), width (videowidth) and height videoheight) arguments within the URL.

...

Whether to do or do not transcode is identified by the server using a 0 (do not) or 1 (do) value. The video’s height and width are given in pixels.

Examples

• Transcode stream url:
  rtsp://<address>/<server-id>?device=<device-id>&width=320&height=240&transcode=1
  The width, height and transcode parameters are send to the server, the server determines the correct stream, based on the dual stream setting for the max panel width. The stream is transcoded to a JPEG stream with the requested width and height, but it keeps the original aspect-ratio.

• Transcoding over limited bandwidth url:
  rtsp://<address>/<server-id>?device=<device-id>&width=320&height=240&transcode=1&bandwidth=32
  The stream is transcoded to half the requested width and height, balanced over the limited bandwidth, and keeps the original aspect-ratio.
  The resulting frame-rate will differ and be irregular compared to the original frame-rate, due to the load-balancing.

Changelog

• 2.7.3 Audio support added