We have both the smsCDA and the imsi_list translation in the
MO-ForwardSM-Arg, and have to put both in one matching function, as in
the case of multiple matching functions only one of them will be
This module is able to match a SCCP message against a given
Destination-GT prefix and checks if the message contains an
Invoke(SRI-for-SM). If both conditions are true, it alters the TT from
whatever it may currently be to 3.
This is used for SMS special routing cases at the STP.
we cannot store persistent/dynamically created state like the references
to our SCCP MASQ state tables in the application environment, as the
environment gets cleared and re-initialized by the
application_controller on osmo_util:reload_config().
So now we use named_tables instead to ensure persistency accross
The mgw_nat_sup supervisor now starts one mgw_nat_usr process for each
MSC-STP link defined in the configuration file. However, the actual
translation/mangling/masquerading configuration as well as runtime state
like allocated SCCP mappings is global/shared between all signalling
Furthermore, a new mgw_nat_adm process is introduced to ensure config
file reloading (formerly handled by the single mgw_nat_usr) does not
have to run in the supervisor (and risk crashing it).