47dd4944ae
nat: Store the config in the connection instead of the lac
...
This allows that we can print the Nr. next to the lac
and it allows us to change the lac at runtime without
reconnecting the BSC.
2010-06-15 20:24:12 +08:00
530c4b1aad
nat: Print the unknown byte as a integer instead of charachter
...
The value might be a non printable one.
2010-06-15 20:24:11 +08:00
a0df82d48d
nat: Handle CRCX/MDCX/DLCX at the nat
...
* Forward a rewritten msg to the BSS. We change the IP and port
to point to the NAT instead of the core network. We also keep
track of the BSC and the transacition id.
* Handle the case where we have not found a SCCP connection and
need to send a response ourselves.
2010-06-15 20:24:10 +08:00
465313e48c
nat: Look at the assignment command and remember on which timeslot the data is
...
This information will be needed when we are trying to forward
MGCP connections to and from the BSC through the IPA protocol.
2010-06-15 20:24:09 +08:00
23fe7be1ca
sccp: Move the destruction of the sccp connection to a new place
2010-06-15 20:24:09 +08:00
e9be5175ff
nat: Some more input validation... on the paging command.
2010-06-15 20:24:09 +08:00
bae9da49b9
nat: Move paging by lac handling code into the utils file
...
Moving it here means we can more easily test this code, there is one
behaviour change with the code that we only support paging messages
with one LAC and will silently ignore the others.
2010-06-15 20:24:09 +08:00
f8048d9f5c
nat: Assign the connection inside the new helper function.
2010-06-15 20:24:08 +08:00
dcf8a7db43
nat: Move creation of the structs to a separate file
...
This way one can create the bsc_nat structure in unit tests..
2010-06-15 20:24:08 +08:00
Holger Hans Peter Freyther