...
are differ, then two RTSP connections will be created if streams from both URLs are requested.
Stream capture authentication
WCS supports RTSP stream capture authentication by user name and password, user data should be set in stream URL, for example
| Code Block | ||||
|---|---|---|---|---|
| ||||
rtsp://user:password@hostname/stream |
If name or password contains any special characters, they should be escaped such as
| Code Block | ||||
|---|---|---|---|---|
| ||||
rtsp://user:p%40ssword@hostname/stream |
Where
- user is user name
- p@ssword is password with character '@', it is escaped in URL.
Known issues
1. A stream containing B-frames does not play or plays with artifacts (latencies, lags)
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
10:13:06,815 WARN AAC - AudioProcessor-c6c22de8-a129-43b2-bf67-1f433a814ba9 Dropping AAC frame that starts with 0, 119056e500 |
4. All the characters in a stream name, that are not allowed in URI, should be escaped
Symptoms: RTSP stream is not played with 'Bad URI' error
Solution: any character that is not allowed in URI, should be escaped in stream URL, for example
| Code Block | ||||
|---|---|---|---|---|
| ||||
rtsp://hostname/c@@lstream/channel1 |
should be set as
| Code Block | ||||
|---|---|---|---|---|
| ||||
rtsp://hostname/c%40%40lstream/channel1 |