...
Name | Description | Example |
|---|---|---|
| localStreamName | Name to set to the stream on server | test |
| transport | Transport to use | srt |
| uri | Endpoint URI to publish the stream | udp://192.168.1.39:31014 |
| localMediaSessionId | Stream media session Id | 32ec1a8e-7df4-4484-9a95-e7eddc45c508 |
| status | Stream status | CONNECTED |
| hasAudio | Stream has audio track | true |
| hasVideo | Stream has video track | true |
| record | Stream is recording | false |
| timeout | Maximum media data receiving timeout, ms | 90000 |
| maxTimestampDiff | Maximum stream timestamps difference, ms | 90000 |
allowedList | Client addresses list which are allowed to publish the stream |
|
Audio only or video only publishing
...
A separate UDP port is opened for every MPEG-TS publishing session to accept client connection (for SRT only) and receive media traffic. Due to security reasons, since build 5.2.1299, the stream will be stopped on server if client stops publishing (like WebRTC one), and publisher can't connect and send traffic to the same port. All the stream viewers will receive STREAM_STATUS.FAILED in this case. A new REST API query should be used to renew the stream publishing, with the same name if necessary.
Publishers restriction by IP address
Since build 5.2.1314 it is possible to restrict client IP addresses whic are allowed to publish MPEG-TS stream using REST API /mpegts/startup query parameter
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"localStreamName":"mpegts-stream",
"transport":"udp",
"allowedList": [
"192.168.0.100",
"172.16.0.1/24"
]
} |
The list may contain both exact IP adresses and address masks. If REST API query contains a such list, only the clients with IP addresses matching the list can publish the stream.
Known issues
1. When MPEG-TS stream publishing via UDP is stopped at server side via REST API query /mpegts/terminate , publishing encoder still sends media data
...