mirror of https://github.com/sipwise/rtpengine.git
Closes #2238 Plain RTP output kept the egress index in userspace only when its input was RTP/AVP (__sh_noop_index); from SRTP or AVPF input (__sh_savp2avp, __sh_avpf2avp, __sh_savpf2avp) the output handler was a no-op, so such a leg had no egress counter until the kernel took over. With a fixed egress SSRC, the re-base on a change of source reads that counter (ext_seq), found it empty or stale and made the sequence jump under an SSRC that the next hop cannot see change. With a WebRTC client feeding a plain RTP leg that is bridged back to another WebRTC client, the jump reached the far browser, whose SRTP replay protection then dropped audio. These three handlers now use __shio_noop_index like RTP/AVP input does. The cost is the index arithmetic on userspace-forwarded packets; the kernel already keeps the index. Codec-generated packets on such legs (e.g. an audio player) are indexed too, through the same hook. Change-Id: Iae8c14b77f5a052cbcc918ce3f903b7b9dc18c88pull/2241/head
parent
2019ad5aa8
commit
0f8ade7de4
Loading…
Reference in new issue