Configure WebRTC WHEP egress on a media server for low-latency viewer playback

Steps

1. Deploy or configure a media server that supports WHEP egress (e.g., Cloudflare Realtime, Dolby Millicast, MediaMTX, or a custom SFU).
2. 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.
3. Include an Authorization header with the appropriate bearer token if the WHEP endpoint requires access control; the token type and format are platform-specific.
4. 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.
5. After ICE connection is established, DTLS-SRTP is used for media encryption; no additional media-level encryption configuration is needed by the client.
6. To disconnect, the WHEP client sends an HTTP DELETE to the resource URL returned in the Location header of the WHEP POST response.