...
REST-method | Example of REST-query | Example of response | Response statuses | Description | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
/rtsp/startup |
| 409 - Conflict 500 - Internal error | Pull the RTSP stream by the specified URL | ||||||||
/rtsp/find_all |
| 200 – streams found | Find all pulled RTSP-streams | ||||||||
/rtsp/terminate |
| 200 - stream terminated | Terminate the pulled RTSP stream |
...
Parameter name | Description | Example |
|---|---|---|
uri | URL of the RTSP stream | rtsp://myserver.com/live/myStream |
| toStream | Name to set to the stream captured | myRTSPstream |
status | Current status of the stream | PLAYING |
...
In this case, if the IP camera redirects requests to another address, and if client establishes connections separately to this camera and directly to the camera where requests are redirected, it is two different streams for WCS. The pulling agent s are created for every of those streams, and subscribers connect to one of those agents depending on address set on connection establishing.
RTSP pulled stream publishing with a given name
The ability was added to publish RTSP pulled stream with a given name since build 5.2.479. The stream name should be set with toStream parameter of /rtsp/startup REST query, for example
| Code Block | ||||
|---|---|---|---|---|
| ||||
POST /rest-api/rtsp/startup HTTP/1.1
Content-Length: 75
Content-Type: application/json
{
"toStream": "stream1",
"uri": "rtsp://myserver.com/live/myStream"
} |
By default, if toStream paremeter is not set, the stream name will be formed from RTSP URI. If RTSP stream with such URI is already pulled, or teh stream with given name is already exists, server returns 409 Conflict.
If the name is set to the RTSP stream pulled, this stream can be played in CDN by its name (by default, CDN playback is not available for RTSP streams because they always are pulled locally).
Known issues
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
...