Closed atoppi closed 6 months ago
FYI the ccfb
attribute is now being negotiated, however pion is putting a a=rtcp-fb:X ack ccfb
line even if the feedback is not being reigstered on the mediaEngine (e.g. NOT calling ConfigureCongestionControlFeedback
).
Is this a regression or an intended behavior?
@atoppi I believe that is wrong. We should probably only respond with a rtcp-fb if we locally we support it!
Your environment.
What did you do?
Trying to negotiate RFC 8888
a=rtcp-fb:* ack ccfb
feedback with a media server (Janus) that is offering the feature.What did you expect?
Pion parses the attribute and adds it to the SDP answer
What happened?
Pion can not parse the attribute due to the presence of wildcard
*
(as requested by RFC 8888). https://github.com/pion/sdp/blob/9704a3f4fd5e01af9faceea50d9b1561c623c900/util.go#L171-L173The problem is that the parsing helper is expecting a PT number, whereas the RFC 8888 mandates a wildcard: