Zero SSRC are technically invalid, but the code accepts them as valid
and therefore sets up things like crypto contexts for zero SSRCs.
Consequently it's possible to have a zero SSRC first in the list of
SSRCs and other valid SSRCs later in the list, which means we can't use
the presence of a non-zero SSRC first in the list as a flag to determine
whether SSRC tracking is in use or not. Use an explicit flag instead.
Change-Id: I88736e5d6b0f66c58f8d675137231760951e7610
(cherry picked from commit
|
3 years ago | |
|---|---|---|
| .. | ||
| .gitignore | TT#108551 add kernel support for AEAD-AES-GCM | 5 years ago |
| Makefile | TT#23584 Use $(MAKE) instead of make to honor parallel builds | 7 years ago |
| rtpengine_config.h | TT#71950 Fix typos | 6 years ago |
| xt_RTPENGINE.c | TT#189900 use explicit flag to enable kernel SSRC tracking | 3 years ago |
| xt_RTPENGINE.h | TT#189900 use explicit flag to enable kernel SSRC tracking | 3 years ago |
| xt_RTPENGINE.modules.load.d | Add xt_RTPENGINE modules.load.d file to load xt_RTPENGINE on system boot | 10 years ago |