pi-webrtc

Signaling

這一頁還沒有中文版,以下顯示英文原文。

Before video can flow, the browser and the device must exchange connection details (an SDP offer and answer, and ICE candidates). This step is called signaling. pi-webrtc supports three ways to do it, and you can turn on more than one at the same time.

What it needsGood for
WHEPNothing extra. The device serves it.Watching on the same network, with a standard player
MQTTAn MQTT brokerWatching from anywhere, peer-to-peer, with device control
SFUA LiveKit server, or Cloudflare RealtimeMany viewers at the same time

If none of them is on, pi-webrtc exits, because nobody could reach it. Every option is listed in Configuration.

Pages

  • WHEP: play the stream from a URL. No server needed.
  • MQTT: connect from anywhere through an MQTT broker.
  • SFU: send one stream and let many people watch.
  • TURN: connect when peer-to-peer fails, for example over 4G or 5G.
  • Self-hosted Mosquitto: run your own MQTT broker.
在 GitHub 上編輯此頁

本頁內容