What this add-on enables
WebRTC is offered as a browser playback output for USD 20/month per channel, in addition to the video plan. Publishing can continue over RTMP or SRT and the standard HLS URL remains available. The add-on does not include a bidding, chat or video-conferencing application.
Playback uses WebSocket signaling (wss://) with a compatible player, such as OvenPlayer; it is not a WHEP endpoint. Publishing still arrives over RTMP or SRT from your encoder.
1. Check channel compatibility
- You need a paid video plan with the WebRTC add-on on the channel. The free plan lets you validate your encoder, connection and player, but it does not include WebRTC.
- LL-HLS is a separate add-on at USD 20/month per channel, with its own URL in the panel.
- Size the plan transfer for your audience and event length.
If the channel is already in use, turn on WebRTC outside broadcast hours and test playback before the live event.
2. Publish a test signal over RTMP or SRT
- Copy the ingest address and credentials for your encoder from the panel.
- Send a signal with video, audio and a visible clock, using the codec profile shown in the panel.
- Confirm that the channel receives the signal. Check encoder CPU load, audio continuity and network stability before testing the browser.
3. Connect a compatible player
- Get the channel’s WebRTC playback option from the panel. If no WebRTC address or configuration appears, confirm enablement with support.
- Use the provided player or an integration compatible with the server signaling. Keep the supplied address and parameters; do not replace WSS with HTTPS or append /whep.
- Open the player on an HTTPS page in a compatible browser. First test with a user clicking play: autoplay policies can block audio.
- If you configured playback protection, preserve its access parameters. Do not embed the publishing password or token in the player.
WebRTC uses UDP traffic in addition to signaling: firewalls, VPNs and strict corporate networks can block it. If part of your audience is on corporate networks, test from them and offer the HLS player as an alternative.
4. Check latency and the playback experience
- Validate video, audio, synchronization and reconnection on the browsers and phones planned for the event.
- Compare the source’s visible clock with the received video. Repeat several times and record the encoder, resolution, network, device, browser and time.
- Separate startup time from delay during playback. Switching networks or resuming a tab can produce a different experience.
- Rehearse with representative concurrency; for a large event, size capacity with an expert.
- Keep the channel’s HLS player at hand as an alternative and decide how to switch to it during the event.
Up to 0.3 s is WebRTC playback latency under suitable conditions; capture, encoder, distance and the viewer’s network add their share.
Troubleshooting common problems
| Symptom | What to check |
|---|---|
| The WebRTC option is missing | That the WebRTC add-on is active on the channel. |
| The address returns an error or will not start | Current panel URL and a player compatible with WebSocket signaling. Do not substitute a WHEP or WHIP URL. |
| Connects, but there is no video | Input signal, codecs, player negotiation and network access for media traffic. Compare another browser and network. |
| Video works, but audio does not | Audio track, compatible codec, volume and autoplay policies. Try clicking play. |
| Works on one network but fails on another | Firewall, VPN and policies on the affected network. Give support the network type and error; do not permanently disable network security as a workaround. |
| HLS works, but WebRTC does not | WebRTC enablement, player configuration, codecs and network requirements. The protocols use different delivery paths. |
For support, collect the channel ID, date and time with time zone, browser and operating system, network, encoder and error description. Redact tokens and credentials from logs. If the event involves bids or timed decisions, the application must handle its own confirmations; do not base them solely on video delay.