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

Add ability to set sequence number for cases where sequence number is not generated locally. #995

Merged
merged 1 commit into from
Oct 2, 2023

Conversation

moorecj
Copy link
Contributor

@moorecj moorecj commented Sep 20, 2023

For cases that do not involve the media being generated locally it is requires that the sequence number be passed along correctly to client connections.

Currently Sipsorcery auto generates sequence numbers when SendRtpRaw is called.

An example of this is a WebRtc media server. If you mark sequential sequence numbers for packets that are not actually sequential it results in distortion on the client side. The client needs to be aware of packets that were lost on the way to the server.

I have added an additional implementation of SendRtpRaw that includes a sequence number. I have attempted to keep the existing methods the same as to not make breaking changes.

Thanks for all the hard work on this project!

… not generated locally. For example webrtc media servers.
@moorecj
Copy link
Contributor Author

moorecj commented Sep 20, 2023

It seems as though this unit test is failing in the current master branch CheckDuplicateBindPortFailsUnitTest

@sipsorcery sipsorcery merged commit c27a197 into sipsorcery-org:master Oct 2, 2023
2 checks passed
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.

2 participants