What this add-on enables
WebRTC is offered as a browser playback output for USD 20 per 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.
Current playback uses WebSocket signaling compatible with the server and a compatible player, such as OvenPlayer. It is not a WHEP endpoint. This guide also does not enable WHIP ingest or publishing from a browser camera.
1. Check channel compatibility
- You need an active video plan and WebRTC enabled on the channel. TestDrive+ does not automatically activate every add-on; ask support for a WebRTC test.
- WebRTC cannot be combined with LL-HLS or Transcoder on the same channel in the current configuration. WebRTC Cam is a separate option with its own restrictions.
- LL-HLS requires enablement on a compatible channel and origin. Do not convert an HLS URL to LL-HLS by changing its filename.
- Size concurrency and transfer for your event. The WebRTC add-on does not automatically increase every plan limit.
Before changing options on a channel in use, confirm the effect on your player and destinations with support. Validate the configuration in a test 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. Use codecs and a profile compatible with the channel’s WebRTC mode; a signal playing through HLS does not prove WebRTC compatibility.
- 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.
A successful signaling connection does not guarantee that media traffic reaches the device. Firewalls, VPNs, corporate networks and connection routes can affect playback. Confirm your channel’s network requirements with support; do not assume a network works simply because it allows HTTPS browsing.
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 and agree capacity with support. One test session does not demonstrate how the entire audience will behave.
- Prepare an alternative HLS URL or player if you need a playback backup, and test how to switch to it. HLS availability does not imply automatic switching.
Less than one second is a target affected by capture, encoder, distance, network and device. It is not a guarantee for every viewer. This guide explains how to measure; it does not report tests run against production.
Troubleshooting common problems
| Symptom | What to check |
|---|---|
| The WebRTC option is missing | Channel enablement, plan and restrictions with Transcoder, LL-HLS or WebRTC Cam. |
| 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.