ttcn3
/
osmo-ttcn3-hacks
mirror of https://gerrit.osmocom.org/osmo-ttcn3-hacks
10
0
Fork 1
Code Issues Releases Wiki Activity

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
This commit is contained in:
Philipp Maier 2019-08-15 14:43:03 +02:00 committed by laforge
parent f45824ad0e
commit d01fc8fefb
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
msc/MSC_Tests.ttcn
View File

@ -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, "fsm.SGs-UE.id.imsi:" & 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 */