Format parameters (a=fmtp:) carrying codec-specific configuration.
What problem this solves
Codecs often need extra parameters beyond rtpmap (Opus FEC, H.264
profile-level-id). Those arrive as a=fmtp: lines tied to a payload type.
This struct holds the fmtp string for inspection or rewrite during SDP
negotiation.
Examples include Opus minptime, H.264 profile-level-id, and FEC toggles.
Wire form: a=fmtp:<format> <param>=<value>;...
RFCs
- RFC 8866 pt.6
Summary
Types
@type t() :: %XMediaLib.SDP.Fmtp{ parameters: String.t(), payload_type: non_neg_integer() }
Payload type and format-specific parameter string.
Fields
:payload_type- RTP payload type the parameters apply to:parameters- semicolon-separatedkey=valuelist as a single string