The getParameters() method of the RTCRtpReceiver interface returns an object describing the current configuration for how the receiver's track is decoded.
An array of objects describing the media codecs that the receiver is ready to use.
This is the subset of codecs that the receiver has indicated it prefers and that the remote endpoint has indicated it is prepared to send.
This parameter cannot be changed once initially set.
Each codec object in the array may have the following properties:
A positive integer indicating the number of channels supported by the codec.
For example, for audio codecs a value of 1 specifies monaural sound, while 2 indicates stereo.
A positive integer specifying the codec's clock rate in Hertz (Hz).
The clock rate is the rate at which the codec's RTP timestamp advances.
Most codecs have specific values or ranges of values they permit.
The IANA maintains a list of codecs and their parameters, including their clock rates.
A string indicating the codec's MIME media type and subtype, specified as a string of the form "type/subtype".
The MIME type strings used by RTP differ from those used elsewhere.
IANA maintains a registry of valid MIME types.
Also see Codecs used by WebRTC for details about potential codecs that might be referenced here.
A string giving the format specific parameters field from the a=fmtp line in the SDP which corresponds to the codec SDP from the remote peer, if the field is present.
If there is no parameters field, this property is left out.
See section 5.8 of the IETF specification for JSEP for more information.
An array of zero or more RTP header extensions, each identifying an extension supported by the sender or receiver.
Header extensions are described in RFC 3550, section 5.3.1. This parameter cannot be changed once initially set.
An RTCRtcpParameters object providing the configuration parameters used for RTCP on the sender or receiver.
This parameter cannot be changed once initially set.