Transport and Provider Compatibility Matrix for olcRTC

olcRTC supports four wire transports (datachannel, vp8channel, seichannel, videochannel) and three signaling providers (jitsi, telemost, wbstream). Not every combination is stable — some providers strip or block certain media types, and others require special account privileges for data routing. The matrix below summarises the current state from the E2E test suite.

Compatibility Matrix

Transport	telemost	wbstream	jitsi
`datachannel`	✗	◑	✓
`vp8channel`	✓	✓	◑
`seichannel`	✗	✓	◑
`videochannel`	✓	✓	◑

Legend:

Symbol	Meaning
`✓`	Works — passes E2E tests
`✗`	Does not work / not supported — fails E2E tests
`◑`	Unstable — may work, result flaps between CI runs

Provider Details

Jitsi
Telemost
WbStream

datachannel — ✓ StableDatachannel on Jitsi is implemented on top of the colibri-ws bridge channel. Data is sent as an EndpointMessage{raw} broadcast. This works on any self-hosted or public Jitsi Meet instance without authentication (e.g. https://meet.jit.si/...). Check which instance is reachable in your network by opening it in a browser before configuring.vp8channel, seichannel, videochannel — ◑ UnstableVideo transports expose a sendable VideoTrack through the pion PeerConnection after the Jingle session-accept, but Jicofo requires additional protocol steps (LastN, ReceiverVideoConstraints, source-add) to actually route video between participants. This is why all three video-based transports are marked unstable on Jitsi.

Jitsi + seichannel — separate caveat. SEI NAL units ride inside the H.264 video stream. On some self-hosted Jitsi instances (e.g. meet.egovm.ru), Jicofo periodically cuts or delays upstream video when there is formally no receiver in the room. From olcRTC’s perspective this looks like a seichannel ack timeout even though the PeerConnection is formally alive. In steady state the transport works, but it flaps — a green or red CI result is enough for the test suite. For reliable data transfer over Jitsi, prefer datachannel or vp8channel.

# Stable Jitsi config
auth:
  provider: jitsi
room:
  id: "https://meet.example.org/my-room"
net:
  transport: datachannel

vp8channel — ✓ StableOnly vp8channel passes stably on Telemost.datachannel — ✗ Not supportedThe SCTP data channel was removed from Telemost. The session appears to establish but no data is routed.seichannel — ✗ Not supportedSEI NAL units are not forwarded by Telemost’s media servers.videochannel — ✓ Works but slowvideochannel technically passes, but Telemost’s video relay adds latency, making throughput significantly lower than on other providers.

Do not use datachannel or seichannel with Telemost — both are expected failures in E2E tests.

# Recommended Telemost config
auth:
  provider: telemost
room:
  id: "<room-id-from-telemost>"
net:
  transport: vp8channel
vp8:
  fps: 30
  batch_size: 64

vp8channel, seichannel, videochannel — ✓ StableAll three video-based transports work stably on WbStream in the default guest flow.datachannel — ◑ Requires moderator tokenWbStream issues guest tokens with canPublishData=false. The SCTP data channel opens successfully but routes no bytes — the tunnel appears alive yet is silent. To use datachannel over WbStream, you need an account/moderator token with canPublishData=true set in auth.token.

Granting moderator in the WbStream UI:

Open the participants list in the call.
Click the three-dot menu (⋮) next to the client or server participant entry.
Press the Moderator button.

This must be done for both the server and the client. There is no automatic promotion yet — even if the account token already carries moderator rights, the UI promotion step is still required on both sides.

# WbStream + vp8channel (recommended guest flow)
auth:
  provider: wbstream
room:
  id: "<room-id-from-stream.wb.ru>"
net:
  transport: vp8channel

# WbStream + datachannel (requires moderator token)
auth:
  provider: wbstream
  token: "<account-token-with-canPublishData=true>"
room:
  id: "<room-id-from-stream.wb.ru>"
net:
  transport: datachannel

Required YAML Fields

Regardless of provider or transport, these fields are always required:

YAML Field	What to Enter
`mode`	`srv` on the server, `cnc` on the client, `gen` to generate a room ID
`auth.provider`	`jitsi`, `telemost`, `wbstream`, or `none`
`net.transport`	`datachannel`, `vp8channel`, `seichannel`, or `videochannel`
`room.id`	Room ID or URL (must match on server and client)
`crypto.key` or `crypto.key_file`	Encryption key — 64 hex chars (32 bytes). Generate: `openssl rand -hex 32`
`data`	Always set to `data`
`net.dns`	DNS resolver, e.g. `8.8.8.8:53`

Speed Ranking

Transports differ significantly in throughput. From fastest to slowest:

datachannel

Fastest. Direct SCTP over WebRTC data channel. No encoding overhead.

vp8channel

Fast. Data tunnelled inside VP8 video frames.

seichannel

Moderate. Data in SEI NAL units inside H.264. ACK-based reliability adds latency.

videochannel

Slowest. Requires ffmpeg for encode/decode. Most broadly compatible.

Recommended Combination

Best overall: jitsi + datachannel — stable on any self-hosted or public Jitsi Meet instance, needs no registration, and room creation is instant (just pick a URL). Check which Jitsi instance is reachable in your network using a browser before configuring.Best for commercial / production: wbstream + vp8channel — stable, no special token rights needed in the guest flow, works reliably with WbStream’s infrastructure.

Get Started

Configuration

Reference

Integrations

Transport and Provider Compatibility Matrix for olcRTC

Compatibility Matrix

Provider Details

Required YAML Fields

Speed Ranking

datachannel

vp8channel

seichannel

videochannel

Recommended Combination

Build docs developers (and LLMs) love

Get Started

Configuration

Reference

Integrations

Documentation Index

​Compatibility Matrix

​Provider Details

​Required YAML Fields

​Speed Ranking

datachannel

vp8channel

seichannel

videochannel

​Recommended Combination

Build docs developers (and LLMs) love

Compatibility Matrix

Provider Details

Required YAML Fields

Speed Ranking

Recommended Combination