New flag to always update the Route Set #278
Open
Conversation
This file contains hidden or 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
Right now, when there's a reINVITe in the middle of a call and the path for said INVITE changes, sofia-sip is not setup to update the route set for the call. This causes that later on requests such as BYEs are sent through the original path eventually resulting in timeouts and weird behavior. This flag gives us the ability to force these route set updates when receiving reINVITEs and should be use with caution as it goes against standard RFC3261 12.2
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.
Right now, when there's a reINVITe in the middle of a call and the path for said INVITE changes, sofia-sip is not setup to update the route set for the call.
This causes that later on requests such as BYEs are sent through the original path eventually resulting in timeouts and weird behavior.
This flag gives us the ability to force these route set updates when receiving reINVITEs and should be used with caution as it goes against standard RFC3261 12.2