diff options
| author | Pau Espin Pedrol <pespin@sysmocom.de> | 2023-08-25 19:22:25 +0200 |
|---|---|---|
| committer | laforge <laforge@osmocom.org> | 2023-08-26 07:27:15 +0000 |
| commit | db017f49ae289897a83c14a97a0d0619188e973c (patch) | |
| tree | 0fb6a28b49908dc54f5e8e7e967557f6dfd21790 /mme | |
| parent | 7bedcf84f8bcbb78da52fa5ac022a876ebdd034b (diff) | |
DIAMETER_Emulation: Support forwarding messages identified by ete_id to a client component
This is useful in the scenarios where the client component submits a
IMSI-based transaction such as AIR, but its answer (AIA) contains no
IMSI (as per what's specified in TS 29.272 5.2.3.1). As a result, the
received AIA message would be enqueued in the DIAMETER_UNIT.
With this new feature, the test can create an expect using the
End-to-End Identifier of the message it is going to transmit, and
receive the answer in the same DIAMETER_CLIENT port the request was
transmitted, even if it contains no IMSI.
Related: OS#5757
Change-Id: I25e44146d2c49e308c1fb490b499e70ac6045f2f
Diffstat (limited to 'mme')
| -rw-r--r-- | mme/MME_Tests.ttcn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mme/MME_Tests.ttcn b/mme/MME_Tests.ttcn index 17a4d60d..cc753777 100644 --- a/mme/MME_Tests.ttcn +++ b/mme/MME_Tests.ttcn @@ -361,7 +361,7 @@ friend function f_init_handler(ConnHdlrPars pars, float t_guard := 30.0) runs on g_Tguard.start(t_guard); activate(as_Tguard()); if (DIAMETER_PROC.checkstate("Connected")) { - f_diameter_expect(g_pars.ue_pars.imsi); + f_diameter_expect_imsi(g_pars.ue_pars.imsi); } if (SGsAP_PROC.checkstate("Connected")) { /* Route all SGsAP mesages for our IMSIto us */ |