fix(sip): match 2xx ACK across proxy tuples#168
Merged
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
1 participant
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.
Fixes live Chime calls being torn down by Timer H about 32 seconds after the initial INVITE when the dialog ACK arrives through a different proxy tuple. Matching remains constrained by accepted transaction state, Call-ID, From/To tags, INVITE CSeq, and route set. Adds a regression with a new Via stack and different source IP/port while preserving forged-route rejection. Validation: 826 asterisk-sip tests pass; full durable trunk E2E passes, including PIN reject/grant and two-way RTP.