path: root/msc/MSC_Tests.ttcn
diff options
authorPhilipp Maier <>2019-01-22 15:35:42 +0100
committerPhilipp Maier <>2019-01-22 15:43:34 +0100
commita99ad26639072df8a508aca280100c0d6367627f (patch)
treefcab8df3bb019d592317d69ed2253dc006164123 /msc/MSC_Tests.ttcn
parent3983e70bf35aef7a264e9dbe75433e0eedd5ff1d (diff)
MSC_Tests: individual IMSI for TC_lu_and_mt_sms_paging_and_nothing
The testcase TC_lu_and_mt_sms_paging_and_nothing is currently using an IMSI that ends on 43. The same IMSI is used by TC_mo_cc_bssmap_clear as well. Since TC_lu_and_mt_sms_paging_and_nothing is running before TC_mo_cc_bssmap_clear, the re-use of the IMSI triggers the MSC to continue the paging procedure. The MSC then eventually tries to deliver the SMS from TC_lu_and_mt_sms_paging_and_nothing. This will disturb the execution of TC_mo_cc_bssmap_clear, which then fails. Lets make sure that TC_lu_and_mt_sms_paging_and_nothing uses an individual IMSI that is never used again throught the execution of the testsuite. Change-Id: I66f8310981078dd032c47fcc97810944cf0c856f Related: OS#3762
Diffstat (limited to 'msc/MSC_Tests.ttcn')
1 files changed, 1 insertions, 1 deletions
diff --git a/msc/MSC_Tests.ttcn b/msc/MSC_Tests.ttcn
index b72c580..a8f37bd 100644
--- a/msc/MSC_Tests.ttcn
+++ b/msc/MSC_Tests.ttcn
@@ -2071,7 +2071,7 @@ testcase TC_lu_and_mt_sms_paging_and_nothing() runs on MTC_CT {
var BSC_ConnHdlrPars pars;
var BSC_ConnHdlr vc_conn;
- pars := f_init_pars(43);
+ pars := f_init_pars(1843);
vc_conn := f_start_handler_with_pars(refers(f_tc_lu_and_mt_sms_paging_and_nothing), pars);
f_vty_sms_send(hex2str(pars.imsi), "2342", "Hello SMS");