SETUP or RELEASE retransmission: resend UUI in retransmitted message #8
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
When retransmitting a message, libpri currently does not include User-user Information IE, because storage field was cleared at first transmission. This fix introduces a retransmission cache for information lost after first transmission. It applies to potentially retransmitted messages: SETUP and RELEASE. Resolves: asterisk#7
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.
When retransmitting a message, libpri currently does not include
User-user Information IE, because storage field was cleared at first
transmission.
This fix introduces a retransmission cache for information lost after
first transmission. It applies to potentially retransmitted messages:
SETUP and RELEASE.
Resolves: #7