WebRTC sends the media data directly from one browser to another without going through an intermediary server. It reduces latency and enables real-time communication.
Please note WebRTC is available on MCM9000 from version 6.2 onwards.
Source
The Source GUI of WebRTC has the below fields.
| 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/stream1" is a working WebRTC stream, "https://janus.testStream.com" refers to the publishing point URL.?id=10" Please note, currently WebRTC Rx ingest is supported only using the Janus server as publish point. For Tx, please contact the TAG support and get the sample WebRTC client that is tailored to integrate with MCM WebRTC TX. | Stream URL Identifier | Stream identifier string in WebRTC. *For example, if "** 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.testStreammeetecho.com/stream1" is a working WebRTC stream, stream1 refers to the Stream URL identifierjanus&turn=test:test123@52.73.92.16:3478 ** From version 6.3.1 onwards MCM9000 supports Tx configuration, please refer to How to setup WebRTC Rx and Tx. |
Stream URL Identifier | Not applicable for WebRTC. | ||
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. |
Content
The Content functionality of WebRTC is the same as HLS. Please refer to Content to configure.
Miscellaneous
The Miscellaneous functionality of WebRTC is the same as CDI. Please refer to Miscellaneous to configure.
Profiles
The Profiles functionality of WebRTC is the same as SPTS except for RST Running State. Please refer to Profiles to configure.
...
The PIDs\Components GUI of WebRTC doesn't have PID but Components. The Components functionality of WebRTC is the same as RTMP. Please refer to Components to configure.
Scheduler (UTC)
The Scheduler functionality of WebRTC is the same as SPTS. Please refer to Scheduler to configure.