fix of rtp socket binding

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Andreas Eversberg andreas at eversberg.eu
Mon Aug 20 06:51:57 UTC 2012


hi,

after having solved an LCR issue, i patched rtp_proxy.c the same way, 
because it has the same issue.

1. when next_udp_port (in rtp_socket_bind) reaches 0xfffe, the bind 
process will fail next time.
2. if rtp_sub_socket_bind of rtp socket succeeds and rtp_sub_socket_bind 
of rtcp socket fails, the rtp socket must be re-created, because it 
cannot not be bound again to the next higher port.
3. the port range will not wrap arround and start at 0, but at 
RTP_PORT_BASE. (after reaching RTP_PORT_MAX)

andreas


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20120820/e58f20a5/attachment.ksh>


More information about the OpenBSC mailing list