osmo-msc/openbsc/src/nat
Holger Hans Peter Freyther 7b7eef62c1 nat: Change MGCP DLCX handling and send dummy MDCX to the BTS.
When setting a new MSC timeslot to a SCCP connection check if
any of the existing connections have this timeslot, if so we will
send a DLCX down the stream to make sure it is closed there, when
we will CRCX this new timeslot we will happily reallocate it.

When the SCCP connection goes away, or we get a DLCX from the
network, or the BSC is gone we will send a DLCX message down the
stream as well.

When we receive a CRCX from the network we will forward the CRCX
as usual and send a dummy MDCX after it.

For the DLCX and the dummy MDCX we send a custom MGCP message
that will not provoke an answer. Even if the downstream MGCP GW
will answer we will ignore it due the dummy transaction id that
is not used anywhere else.

This change should make sure that we close the dowstream endpoint
all the time, even when the DLCX arrives after the SCCP connection
is torndown.
2010-06-15 20:24:16 +08:00
..
bsc_filter.c nat: Allow to send MGCP messages from the BSC to the network 2010-06-15 20:24:10 +08:00
bsc_mgcp_utils.c nat: Change MGCP DLCX handling and send dummy MDCX to the BTS. 2010-06-15 20:24:16 +08:00
bsc_nat.c nat: Change MGCP DLCX handling and send dummy MDCX to the BTS. 2010-06-15 20:24:16 +08:00
bsc_nat_utils.c nat: Change MGCP DLCX handling and send dummy MDCX to the BTS. 2010-06-15 20:24:16 +08:00
bsc_nat_vty.c [nat] Fix the vty option... use the right argument. 2010-06-15 20:24:15 +08:00
bsc_sccp.c nat: Change MGCP DLCX handling and send dummy MDCX to the BTS. 2010-06-15 20:24:16 +08:00