-
Notifications
You must be signed in to change notification settings - Fork 363
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
Parsing header extension #1492
Labels
Comments
Hello @LairCortex, Apologies for the delay. Yes, currently we do not parse the header extension of RTP packets. I understand that this might allow the stream to play at all due to a parsing error? Are you trying to utilize the RTP header extension data within your player or is the issue that content is not playing because the RtpPacket parsing logic chokes on the custom data? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good afternoon! Our server adds additional information to header extension RtpPacket according to protocol 5.3.1 (https://datatracker.ietf.org/doc/html/rfc3550#section-5.3.1). We noticed that you do not use header extension parsing because of this the collection of information for display does not work correctly. Can you tell us if this functionality is planned to be implemented in the near future? Or maybe you can offer a solution that we can use in our company?
The text was updated successfully, but these errors were encountered: