Skip to content

Guard the sync engine against out-of-domain sender reports - #983

Open
frostbyte73 wants to merge 3 commits into
mainfrom
fix/sync-engine-sr-domain-guard
Open

Guard the sync engine against out-of-domain sender reports#983
frostbyte73 wants to merge 3 commits into
mainfrom
fix/sync-engine-sr-domain-guard

Conversation

@frostbyte73

Copy link
Copy Markdown
Member

The new egress sync engine rejects RTCP sender reports whose RTP timestamps are not in the same domain as the track's media stream, GetSessionPTS no longer returns a value it has flagged as abnormal, and the abnormal-result warn is rate-limited

The new egress sync engine rejects RTCP sender reports whose RTP timestamps are not in the same domain as the track's media stream, GetSessionPTS no longer returns a value it has flagged as abnormal, and the abnormal-result warn is rate-limited
devin-ai-integration[bot]

This comment was marked as resolved.

Sender reports that arrive before a track's first media packet bypass the
RTP domain guard, which stays disarmed until lastTS exists. Four of them
are enough to build a ready regression on the wrong domain, and once the
guard arms it rejects the very sender reports whose outliers would
otherwise have forced a rebuild.
devin-ai-integration[bot]

This comment was marked as resolved.

The guard's tests passed unchanged at any threshold from 1s to 30s, so a
retune would not have been caught. In-domain probes now sit at a 4s gap
and a new table row is rejected only below 7s, bounding the value to
[4s, 7s).

Also drops an unreachable zero-time fallback whose only caller always
passes a real timestamp.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants