Start media bridge at 183 early media instead of waiting for 200 OK#142
Merged
shenjinti merged 1 commit intorestsend:mainfrom Feb 27, 2026
Merged
Conversation
Track buffers go stale during the 6+ second gap between bridge creation (183 early media) and bridge start (200 OK). By the time forward_track starts reading, track.recv() delivers 0-1 buffered packets then stops. Fix: call bridge.start() immediately at 183 creation time. The start() guard (AtomicBool swap) prevents double-starting when 200 OK arrives. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> (cherry picked from commit 26445699b4126babae7dd461be9882051a4b9271)
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
3 participants
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 cherry-picks davidcforbes/rustpbx@2644569 to address #136.