You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a=rtcp-fb:* means that all codecs in this m= section support the RTCP features exposed in this attribute line. Purpose of it is to save space in the SDP by reducing number of a=rtcp-fb lines per m= section. libwebrtc will support this soon so we must be ready in mediasoup-client and libmediasoupclient.
Example: a=rtcp-fb:* transport-cc means that all codecs in this m= section support transport-cc.
NOTE: This is a SDP thing. We transmit ORTC parameters from client to mediasoup and vice-versa. AFAIU we don't need to support this neither in mediasoup side nor in the ORTC parameters, utils and definitions within mediasoup-client and libmediasoupclient.
So basically, when we parse a SDP and generate RtpParameters or RtpCapabilities must be ready to manage a=rtcp-fb:* lines and apply their supported RTCP features into all codecs within the generated RtpParameters or RtpCapabilities. This is just an estimation, things may need to be different.
The text was updated successfully, but these errors were encountered:
(Same as in mediasoup-client: versatica/mediasoup-client#239).
a=rtcp-fb:*
means that all codecs in thism=
section support the RTCP features exposed in this attribute line. Purpose of it is to save space in the SDP by reducing number ofa=rtcp-fb
lines perm=
section. libwebrtc will support this soon so we must be ready in mediasoup-client and libmediasoupclient.Example:
a=rtcp-fb:* transport-cc
means that all codecs in thism=
section supporttransport-cc
.NOTE: This is a SDP thing. We transmit ORTC parameters from client to mediasoup and vice-versa. AFAIU we don't need to support this neither in mediasoup side nor in the ORTC parameters, utils and definitions within mediasoup-client and libmediasoupclient.
So basically, when we parse a SDP and generate
RtpParameters
orRtpCapabilities
must be ready to managea=rtcp-fb:*
lines and apply their supported RTCP features into all codecs within the generatedRtpParameters
orRtpCapabilities
. This is just an estimation, things may need to be different.The text was updated successfully, but these errors were encountered: