SCTP transport support #46
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
poroh
reviewed
Oct 16, 2019
rezerbit
force-pushed
the
sctp_transport
branch
from
54ed7fe
to
5349bb4
Compare
…_message_oriented
|
Thanks a lot for your contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
Thank you for your work. We use your library in our project and it helps us a lot!
But for some of connections we have to use SCTP protocol. This seems like a common requirement in telecomunication industry.
This pull request simply adds SCTP related "constants". No real logic changes were neccesary. SCTP is simply a "reliable" transport in SIP terms (as far as we understand).