tree 1ad7f6bdd515b241cb676187de15e95a70b42bcd
parent 0952b2f28f3126afe439e7451b0816cdaf4544ee
author Holger Hans Peter Freyther <zecke@selfish.org> 1271909297 +0800
committer Holger Hans Peter Freyther <zecke@selfish.org> 1276604656 +0800

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.