-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parser can not read attributes with wildcards #172
Comments
atoppi
changed the title
Parser can read attributes with wildcards
Parser can not read attributes with wildcards
Mar 5, 2024
Sean-Der
pushed a commit
to thebongy/sdp
that referenced
this issue
Mar 29, 2024
According to Chrome PSA: https://groups.google.com/g/discuss-webrtc/c/Y_h2B-NOzW0 rtcp-fb:* might start getting sent by chrome in M112. This was rolled back but may land again in M114 according to maintainers. Also, according to https://webrtc.googlesource.com/src.git/+/8155227/#F0 Chrome may plan on sending both rtcp-fb:* and rtcp-fb:<int> variants for some time to allow migration in downstream projects. This change correctly parses the wildcard case to add the feedback to all payload types found in the SDP, to maintain compatibility with Pion. Resolves pion#172
FYI the |
@atoppi I believe that is wrong. We should probably only respond with a rtcp-fb if we locally we support it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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).sdp/util.go
Lines 171 to 173 in 9704a3f
The problem is that the parsing helper is expecting a PT number, whereas the RFC 8888 mandates a wildcard:
The text was updated successfully, but these errors were encountered: