Signaling Transparency Demo
Imagine two phones trying to start a private video call. Before they can talk, they must exchange a few "setup notes": what kind of call they want, what formats they can use, and how to reach each other. Those setup notes are called signaling.
When does signaling happen? Right at the start of a call (and sometimes during reconnects). It's like texting "Can you hear me? Here's how to connect" before the real conversation begins. The actual audio/video is sent separately after this setup.
Last updated:
What should you notice?
- Call setup text (SDP)
- Connection options (ICE)
- Security fingerprints (for the transport)
- No audio or video content
- No chat message text
- No end-to-end encryption keys
This is the main point of the demo: a relay server can forward signaling, but it still cannot "read your call," because your call media is separate and (with E2EE) encrypted on the devices.
Change the demo settings
Answer: "Yes - here's what I accept."
ICE candidate: "Try connecting to me this way (address/route)."
Below, you'll see the same signaling object shown in three places (Caller A, relay, Caller B)
plus a dedicated panel showing the exact payload being relayed.
These examples are sanitized and safe-to-publish (not production logs).
Caller A sends
Server relay sees
Caller B receives
What gets relayed
Plain-English glossary
SDP is the "menu" for the call: it lists what each side supports (audio/video formats) and how the secure connection is set up. It's like agreeing on "we'll speak English and use FaceTime-quality video" - not the conversation itself.
ICE is the "map" for how to connect: it tries different network routes so the callers can reach each other, even behind routers and firewalls. TURN is the backup route: a relay that passes encrypted packets when a direct route fails.
Related: Security Hub - Threat model - Logging policy