diff options
authorPhilipp Maier <>2019-08-15 14:43:03 +0200
committerlaforge <>2019-08-18 17:13:20 +0000
commitd01fc8fefb7eaecafdedb96dde3b4d91b08fe6a7 (patch)
parentf45824ad0e907bd27b8bc3c57f0d762fe8e51017 (diff)
MSC_Tests: do not send an SGsAP-MO-CSFB-INDICATION when testing MT-Call
The TTCN3 tests MSC_Tests.TC_bssap_lu_sgsap_lu_and_mt_call and MSC_Tests.TC_sgsap_lu_and_mt_call initate an MT-CSFB call for testing purposes, but they also send an SGsAP-MO-CSFB-INDICATION to make the MS come back to LTE. This is wrong. SGsAP-MO-CSFB-INDICATION just informs the VLR that the UE has initiated a MO CSFB call on the LTE side. On MT CSFB calls this message should not appear. Lets remove it. Related: SYS#4624 Change-Id: I2e9fda4fe97866c4cbc77224ba1930ca81411fd6
1 files changed, 0 insertions, 3 deletions
diff --git a/msc/MSC_Tests.ttcn b/msc/MSC_Tests.ttcn
index c463dd5..7499456 100644
--- a/msc/MSC_Tests.ttcn
+++ b/msc/MSC_Tests.ttcn
@@ -4980,9 +4980,6 @@ private function f_mt_lu_and_csfb_call(charstring id, BSC_ConnHdlrPars pars, boo
/* Make sure that subscriber is still present and the SGs association is in tact (ref-counting) */
f_ctrl_get_exp(IPA_CTRL, "" & hex2str(g_pars.imsi) & ".state", "SGs-ASSOCIATED");
- /* Finally simulate the return of the UE to the 4G network */
- SGsAP.send(ts_SGsAP_MO_CSFB_IND(pars.imsi));
/* Test for successful return by triggering a paging, when the paging
* request is received via SGs, we can be sure that the MSC/VLR has
* recognized that the UE is now back on 4G */