Harald Welte 54c919ec48 ortp: disable SO_REUSEADDR + SO_REUSEPORT ... ortp >= 0.24.0 doesn't differentiate between SO_REUSEADDR and SO_REUSEPORT, and has both enabled by default. The latter means that we can end up with non-unique port bindings as we will not fail to bind the same port twice. This should have caused visible problems not only when operating multiple osmo-bts on one machine (rare), but also with a single osmo-bts. Once the range (default 16384-17407 ) wraps, there is a risk of new sockets (for new cals) colliding with old ones. As two ports (RTP+RTCP) are used per call, this means every 512 voice calls we expect the BTS to wrap. And from that point onwards there's a risk of overlapping with previously allocated sockets. Change-Id: I4fc9eee561c7958c70c63b4ffdc6cb700b795e28 Closes: OS#4444		2020-03-09 11:24:45 +01:00
..
ipa_recv	use osmo_init_logging2	2018-04-17 14:43:08 +02:00
rtp_test	ortp: disable SO_REUSEADDR + SO_REUSEPORT	2020-03-09 11:24:45 +01:00
subchan_demux	Test parsing of GSM 08.60 frame sync header	2012-10-12 16:24:00 +02:00
Makefile.am	Add rtp_test to show the double-bind bug of OS#4444	2020-03-09 11:24:38 +01:00
e1inp_ipa_bsc_test.c	ipaccess: Simplify handling of ipaccess e1line ts	2018-10-03 12:10:43 +02:00
e1inp_ipa_bts_test.c	ipaccess: Simplify handling of ipaccess e1line ts	2018-10-03 12:10:43 +02:00
ipa_proxy_test.c	use osmo_init_logging2	2018-04-17 14:43:08 +02:00
testsuite.at	Add rtp_test to show the double-bind bug of OS#4444	2020-03-09 11:24:38 +01:00