Avoid creating a TCP/TLS listener when listener is not preferred in IP change scenario #3873
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
…f currently no listener, also update docs that bound address setting will be reset.
sauwming
approved these changes
Feb 29, 2024
trengginas
approved these changes
Mar 15, 2024
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.
This PR fixes a bug that IP change may create a TCP/TLS listener when currently no listener is created (e.g: due to
PJSIP_TLS_TRANSPORT_DONT_CREATE_LISTENER). Also updates PJSUA docs that specifies bound address setting will be reset (assuming IP has just changed, so the bound address is no longer valid).Thanks to Marcus Froeschl for the report.