Skip to content

WEBRTC

media.ingest.webrtc

Description

media.ingest.webrtc describes WebRTC capture from a remote source, initiated by the server. Incoming client publication over WHIP is the separate media.publish.whip feature. The current Sapsan API does not expose a WebRTC client input; publish is not a configuration for this capture mode.

Configuration

The current Sapsan configuration schema has no WebRTC client input, so no YAML configuration is defined for it.

Parameters

The API does not publish remote-server address or connection-negotiation fields for this input.

Authentication

Authentication parameters for a WebRTC client input are not defined. publish_tokens controls incoming publication, not access to a remote source.

Transport options

WebRTC uses connection negotiation and secure media transport. Server-side WHIP and WHEP cover publishing and playback directions; they do not configure a client input.

Supported codecs

Sapsan does not define an accepted-codec list for this input.

Error handling

WHIP session failures belong to publishing. The current API has no separate WebRTC client-input state.

Applying changes

A central API operation for changing a WebRTC client input is not defined.

Counters

The current implementation has no separate WebRTC client-input counters. WHIP publication statistics do not describe this input.

Other details

A WebRTC player or WHIP receiver does not establish availability of a WebRTC client input.

Next steps