Skip to content
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

rtcp: fix FIR parsing #3528

Merged
merged 1 commit into from
Mar 15, 2025
Merged

rtcp: fix FIR parsing #3528

merged 1 commit into from
Mar 15, 2025

Conversation

gdesmott
Copy link
Contributor

FIR RTCP packets sent by GStreamer were not handled by Janus but PLI ones are.

According to https://www.rfc-editor.org/rfc/rfc5104#section-4.3.1 FIR are PSFB packets with FMT=4 so I'm now parsing them as we do with PLI.

@lminiero
Copy link
Member

Adding a new toggle is fine, but I wouldn't remove the check we had, since that was definitely working with other implementations we tested FIR with back then (which is arguable ages ago, before we definitely moved to PLI).

FIR RTCP packets sent by GStreamer were not handled by Janus but PLI
ones are.

According to https://www.rfc-editor.org/rfc/rfc5104#section-4.3.1
FIR are PSFB packets with FMT=4 so I'm now parsing them as we do with
PLI.
@gdesmott
Copy link
Contributor Author

I updated the patch to keep the existing implementation as well then.

@atoppi
Copy link
Member

atoppi commented Mar 14, 2025

LGTM 👍

@lminiero
Copy link
Member

Thanks, merging then! I'll backport that to 0.x as well if it turns out it's needed.

@lminiero lminiero merged commit 3a0a4dd into meetecho:master Mar 15, 2025
8 checks passed
lminiero pushed a commit that referenced this pull request Mar 15, 2025
FIR RTCP packets sent by GStreamer were not handled by Janus but PLI
ones are.

According to https://www.rfc-editor.org/rfc/rfc5104#section-4.3.1
FIR are PSFB packets with FMT=4 so I'm now parsing them as we do with
PLI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants