diff options
| author | Mychaela N. Falconia <falcon@freecalypso.org> | 2023-12-18 03:20:10 +0000 |
|---|---|---|
| committer | Mychaela N. Falconia <falcon@freecalypso.org> | 2023-12-18 03:46:11 +0000 |
| commit | d0880faf795c24709bc87296a3fba406bdd393e0 (patch) | |
| tree | 1c2d8fe0ea52df4eccec9d0c931e980cf0b325d9 /tests | |
| parent | 82fad5dd468cb6fd921478b12653ad633e171ee7 (diff) | |
GSUP: set default ipa-name at application level
Prior to this change, if there was no explicit ipa-name configuration
in OsmoMSC, OsmoHLR would see the GSUP connection as MSC-00-00-00-00-00-00.
However, this default is constructed somewhere deep in IPA libraries
and is not visible to the GSUP client application, in this case OsmoMSC.
This situation creates a problem for SMS-over-GSUP routing: when we get
MT-forwardSM.req from an SMSC, we have to send a GSUP response, and this
response needs to get back to the MT-sending SMSC. Because OsmoHLR
applies only passive routing for these responses, we have to set
source_name when generating MT-forwardSM.res in OsmoMSC - but we cannot
do so if don't know our own IPA name.
Change the default OsmoMSC ipa-name from MSC-00-00-00-00-00-00 to
unnamed-MSC, mirroring OsmoHLR default of unnamed-HLR, and set it
at our application level rather than deep in the libraries.
Related: OS#6135
Change-Id: I7bacd001b81326c32bc262c7d0c0491ded822fa8
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/test_nodes.vty | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/test_nodes.vty b/tests/test_nodes.vty index a1c443589..836de665e 100644 --- a/tests/test_nodes.vty +++ b/tests/test_nodes.vty @@ -171,6 +171,7 @@ mncc-int hlr remote-ip 127.0.0.1 remote-port 4222 + ipa-name unnamed-MSC sgs local-port 29118 local-ip 0.0.0.0 |