...
RTSP-codecs
- Video: H.264, VP8, H265 (since build 5.2.1577)
- Audio: AAC, G.711, Speex
Operation flowchart
...
Since build 5.2.801, WCS is running from 'flashphoner' user for security reasons. Threrfore, when WCS is started manually
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /usr/local/FlashphonerWebCallServer/bin
sudo ./webcallserver start |
RTSP server cannot Therefore RTSP server may not be launched because TCP ports in range 0-1000 are ub=navailable privileged and unavailable to non-root users. In In this case RTSP port should be changed, for example
...
Thus, RTSP client can be authenticated by RTSP stream URL, User-Agent, client and server IP address and port.
Custom access key and backend application usage for RTSP playback authentication
Since build 5.2.1008 it is possible to set ccustom authentication key (token) in RTSP URL, for example
...
To adjust RTSP playback parameters, for example, to change audio or video codec, SDP setting file rtsp_server.sdp should be used. Note that this file should contain WCS server IP address.
Playing H265 without transcoding
Since build 5.2.1577 it is possible to play MPEG-TS H265 stream via RTSP. To do this, H265 codec must be set in rtsp_server.sdp file:
| Code Block | ||
|---|---|---|
| ||
v=0
o=- 1988962254 1988962254 IN IP4 0.0.0.0
c=IN IP4 0.0.0.0
t=0 0
a=sdplang:en
a=range:npt=now-
a=control:*
m=audio 0 RTP/AVP 96
a=rtpmap:96 mpeg4-generic/48000/2
a=fmtp:96 profile-level-id=1;mode=AAC-hbr;sizelength=13;indexlength=3;indexDeltaLength=3
a=control:audio
a=recvonly
m=video 0 RTP/AVP 119
a=rtpmap:119 H265/90000
a=control:video
a=recvonly |
| Warning |
|---|
Streams published in H264, VP8, or MPV codecs may not be played as H265! Use this codec to play MPEG-TS H265 streams only |
Dynamic codec detection
Since build 5.2.1592 codecs are detected dynamically for RTSP playback
| Code Block | ||
|---|---|---|
| ||
v=0
o=- 1988962254 1988962254 IN IP4 0.0.0.0
c=IN IP4 0.0.0.0
t=0 0
a=sdplang:en
a=range:npt=now-
a=control:*
m=audio 0 RTP/AVP
m=video 0 RTP/AVP |
In this case, if a stream is published as H264, VP8 or H265, and RTSP client supports the codec, the stream will be played via RTSP without transcoding. Audio codecs are detected by the same way.
Interleaved mode support
Before build 5.2.1609, WCS supported interleaved mode only, in this case both RTSP signaling and RTP traffic go via TCP, therefore some player applications (including VLC) may not play RTSP from WCS with default settings. Since build 5.2.1609, non-interleaved mode is also supported, in this case RTSP signaling goes via TCP, and RTP traffic flows via UDP. Note that non-interleaved mode is less packet loss proof.
Known issues
1. Frame loss and picture artefacts can occur when HD stream is played via RTSP
...