WebRTC enables content distribution without going through an intermediary server or through a Janus server for one-to-many distribution, with very low latency.
WebRTC Tx configuration is available on MCM9000 from version 6.3.1 onwards.
Please follow the steps to configure WebRTC.
WebRTC Rx through Janus Server
Navigate to Sources → Scan and scan WebRTC source.
2. Once the WebRTC source is scanned and visible under Sources → Configuration, please ensure to specify the Stream URL Identifier.
Fields | Description |
Display Name | A user-defined name for caption display on the mosaic and system messages. |
User Name/UUID | Unique username for the channel; used for SNMP traps and emails. |
Access Type | Desired Type of channel source (WebRTC). |
Enable Recording | Allows recording whenever a recordable event is encountered. |
Publish Point URL | Publish point URL string in WebRTC. *For example, if "https://janus.testStream.com/1" is a working WebRTC stream, "https://janus.testStream.com" refers to the publishing point URL. Please note, currently WebRTC Rx ingest is supported only using the Janus server as publish point. ** From version 6.2.2 onwards MCM9000 supports, TURN server support for Amagi WebRTC. Publish point URL for TURN server is in the format : <url>&turn=user:password@<turn-ip>:<turn-port> For example, https://janus.conf.meetecho.com/janus&turn=test:test123@52.73.92.16:3478 |
Stream URL Identifier | Stream identifier string in WebRTC. *For example, if "https://janus.testStream.com/stream1" is a working WebRTC stream, stream1 refers to the Stream URL identifier. |
Network | The NIC used to intercept the source. |
Latency | Specify the latency (in ms). |
Service Type | Service type settings (SD/HD/Radio, etc.); used for system resource allocation. Service type refers to the number of hardware resources that should be allocated for monitoring the channel. Service type is usually measured by SD point (0.5,1,5,10,20...) depending upon the required hardware allocation which is usually detected during the scan. |
Tally Settings | Configure tally settings for a specific source. |
Note | General notes about the channel. **From version 5.7.0 onwards MCM9000 supports channels rotation at 90 or 270 degree, enabling potrait view. Please refer to Potrait view of a channel for detailed description. **From version 6.0.6 onwards MCM9000 supports #SLIDE# option in the "Note" field for sources that has frame interval greater than 2 seconds. |
WebRTC Tx
WebRTC Tx configuration is available on MCM9000 version 6.3.1 onwards.
**** Please note WebRTC Tx direct from the MCM is limited to 5 output streams per MCM, standard MCM resource calculations apply when using a Janus server.”
WebRTC Tx can be configured by the following two ways:
1. WebRTC Tx with a Janus Server
Navigate to Outputs → Configuration, open an existing output or create a new output. Under the Encoder tab, ensure that the Codec Type is H.264 and GOP Mode is Static, IP Frames. WebRTC does not support B Frames.
** Please note the codec, GOP, destination URL, and ports might differ for the Janus Server configuration based on your application.
Under the Auxiliary Streams tab, fill in the Tx Publish Point URL in the Zixi/SRT Publish Point in the following format rtp://<Janus_ip_address>:<port>, select network NIC, enable, and click on Submit. No other senders are required to be enabled.
Enable the output to start streaming to the Janus server.
2. WebRTC Tx Direct from the MCM
Navigate to Outputs Configuration, Create a new output or open an existing output.
Under the Encoder tab, ensure that the Codec Type is H.264 and GOP Mode is Static, IP Frames. WebRTC does not support B Frames.
Click on Submit and enable the output.
Once output is enabled the WebRTC player can negotiate the stream with the MCM.
Network Requirements
WebRTC Tx Direct requires an SDP file to be shared with the WebRTC player. No additional MCM ports need to be opened. The SDP file default MCM path is ‘<MCM IP>/files/video/rtc_<encoder UUID>.sdp’. The SDP file will enable the player to pull the stream from the MCM.
** Please note on MCM version 6.3.1 there is a known issue for AWS cloud deployments only. The SDP file expires after 10 minutes and no new streams can be pulled from the MCM. Active streams will continue to work. As a work around, disable/enable the output. This issue will be resolved in a future release.