Update prflx candidate if it is explicitly added as a remote candidate #74
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
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.
Consider scenario where we receive binding request from a remote candidate that hasn't been explicitly trickled yet. We will treat it as prflx giving it possibly lower or higher priority than it should have, which may result in different pairs being selected on both sides (remote will have (host, host) pair while we will have (host, prflx) pair).
This was mentioned in #73
This PR updates candidate's type and priority, as well as pair priority and potentially selected_pair_id if needed.
We do a similar thing to what libnice does: https://github.com/libnice/libnice/blob/master/agent/agent.c#L4163-L4176