rob-digitalsamba
New Member
Currently, when a WHIP stream is restarted - either voluntarily via the Stop / Start stream button, or via a glitch, the same SSRC is re-used.
This behaviour is problematic since receivers may assume the stream never stopped: The server or SFU might treat the "new" stream as a continuation of the old one. This can lead to corrupted decoding, dropped packets, or loss of sync. Systems that implement SRTP (secure RTP) with replay protection may reject old/reused SSRCs and sequence numbers.
Is the current behaviour by design? We would suggest to use a new SSRC every time a stream is restarted.
This behaviour is problematic since receivers may assume the stream never stopped: The server or SFU might treat the "new" stream as a continuation of the old one. This can lead to corrupted decoding, dropped packets, or loss of sync. Systems that implement SRTP (secure RTP) with replay protection may reject old/reused SSRCs and sequence numbers.
Is the current behaviour by design? We would suggest to use a new SSRC every time a stream is restarted.