Repository navigation
Fix ACK retransmissions bypassing the SBC - #3
Merged
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.
Build ACK routing before taking the retransmission snapshot. Replay independent copies without rebuilding headers, preserving the SBC next hop, CSeq, and Via.
Tests cover direct/loose/strict routing, concurrent retries, send failure, and TCP proxy calls with/without 407 authentication. Gateway full race suite passes against the fix.
Sipgo race suite passes excluding three confirmed baseline failures: TestServerTransactionRespondRejectsCRLF, TestTransportLayerClientConnectionReuse, and TestTransportLayerClientConnectionNoReuse.
No release published yet; gateway dependency and upstream PR emiago#369 will follow after merge.