Deploy or configure a media server that supports WHEP egress (e.g., Cloudflare Realtime, Dolby Millicast, MediaMTX, or a custom SFU).
A WHEP subscriber initiates playback by sending an HTTP POST with an SDP offer (or an empty body for an offer-less flow) to the WHEP endpoint URL; the server responds with an SDP answer.
Include an Authorization header with the appropriate bearer token if the WHEP endpoint requires access control; the token type and format are platform-specific.
The SDP negotiation establishes codec preferences (H.264, VP8, VP9, etc.) and ICE candidates; handle Trickle ICE if the server supports it to reduce connection setup time.
After ICE connection is established, DTLS-SRTP is used for media encryption; no additional media-level encryption configuration is needed by the client.
To disconnect, the WHEP client sends an HTTP DELETE to the resource URL returned in the Location header of the WHEP POST response.
Known gotchas
WHEP is an IETF draft specification; while widely implemented, minor behavioral differences between servers (e.g., offer vs. answer-less flows, ICE restart handling) require testing with your specific server.
WHEP egress latency depends on ICE connectivity; TURN server configuration is required for viewers behind strict firewalls or symmetric NAT.
Some WHEP implementations return the resource URL for DELETE in the Location response header; ensure your client captures and stores this URL for clean session teardown.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp