Holger Hans Peter Freyther 1afe7c7fe5 osmux: Remember the allocated CID and make sure it is released ... There appears to be a leak of CIDs: <000b> mgcp_osmux.c:544 All Osmux circuits are in use! There are paths that a CID had been requested and never released of the NAT. Remember the allocated CID inside the endpoint so it can always be released. It is using a new variable as the behavior for the NAT and MGCP MGW is different. The allocated_cid must be signed so that we can assign outside of the 0-255 range of it. Fixes: OW#1493		2015-10-12 09:11:25 +02:00
..
Makefile.am	nat: Use RAND_bytes instead of /dev/urandom	2015-07-01 08:34:16 +02:00
bsc_filter.c	nat: Remember the original dest local reference in the parsed struct	2013-09-03 15:04:43 +02:00
bsc_mgcp_utils.c	osmux: Remember the allocated CID and make sure it is released	2015-10-12 09:11:25 +02:00
bsc_nat.c	vty: Change the return type from enum to int	2015-09-24 15:39:30 +02:00
bsc_nat_ctrl.c	filter: Remove nat from bsc_nat_acc_lst and replace with msg	2015-05-03 21:42:28 +02:00
bsc_nat_filter.c	filter: Move the con_type into the filter_state	2015-05-03 22:09:02 +02:00
bsc_nat_rewrite.c	adopt recent IPA related symbol rename	2014-08-20 23:47:56 +02:00
bsc_nat_rewrite_trie.c	64bit: Fix compiler warnings in regard to 64bit	2015-08-03 12:01:44 +02:00
bsc_nat_utils.c	nat: Factor out the config by token search	2015-07-01 08:16:40 +02:00
bsc_nat_vty.c	osmux: Enforce Osmux only global and per BSC configuration	2015-10-12 09:11:25 +02:00
bsc_sccp.c	…
bsc_ussd.c	filter: Move the con_type into the filter_state	2015-05-03 22:09:02 +02:00