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

rtp header extension len not correct #6

Open
fuji246 opened this issue Jan 18, 2016 · 3 comments
Open

rtp header extension len not correct #6

fuji246 opened this issue Jan 18, 2016 · 3 comments

Comments

@fuji246
Copy link
Contributor

fuji246 commented Jan 18, 2016

from rfc3550:

The header extension contains a 16-bit length field that
counts the number of 32-bit words in the extension, excluding the
four-octet extension header (therefore zero is a valid length).

should be
offset += htons (extlen)*4; // skips RTP extension header

@alexcme
Copy link

alexcme commented Sep 17, 2016

Have you tried "-d rtp_byte_offset_in_packet" option?

@koundipoluri
Copy link

-d wont help. -d is used to find the rtp offset from the frame start. He is trying to say according to that Rfc the payload starts later than what is calculated by the current implementation.

@tchebb
Copy link

tchebb commented Feb 20, 2019

ac50693 didn't fix this properly. The extension length is now calculated correctly, but offset never gets skipped past the length bytes which means the decryption starts two bytes two early. An offset += 2; after reading the extension length fixes it.

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

No branches or pull requests

4 participants