summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2018-03-18 22:43:06 +0100
committerHarald Welte <laforge@gnumonks.org>2018-03-18 22:46:14 +0100
commitbdb3c45a38d5200811637745a941295f1084ef8e (patch)
treeccf17725bfc211c216a01efafccf99ed764a4db8
parent96505f0fa01339ce5d721cc750bdf5480d6e3904 (diff)
msc: Fix TC_cl3_{no,rnd}_payload
It may very well be that the MSC is first accepting the SCCP connection and possibly sending a L3 (error) message before clearing/closing the SCCP connection in case of errors in the COMPL L3 info. Change-Id: I4cf08608413e9e1fb54848849baed79204f5dcd1
-rw-r--r--msc/MSC_Tests.ttcn3
1 files changed, 3 insertions, 0 deletions
diff --git a/msc/MSC_Tests.ttcn b/msc/MSC_Tests.ttcn
index 10f772e..156bdd9 100644
--- a/msc/MSC_Tests.ttcn
+++ b/msc/MSC_Tests.ttcn
@@ -1046,6 +1046,8 @@ private function f_tc_cl3_no_payload(charstring id, BSC_ConnHdlrPars pars) runs
BSSAP.send(ts_BSSMAP_ClearComplete);
BSSAP.receive(BSSAP_Conn_Prim:MSC_CONN_PRIM_DISC_IND);
}
+ [] BSSAP.receive(tr_PDU_DTAP_MT(?)) { repeat; }
+ [] BSSAP.receive(BSSAP_Conn_Prim:MSC_CONN_PRIM_CONF_IND) { repeat; }
[] T.timeout {
setverdict(fail, "Timeout waiting for ClearCommand or SCCP Release");
self.stop;
@@ -1083,6 +1085,7 @@ private function f_tc_cl3_rnd_payload(charstring id, BSC_ConnHdlrPars pars) runs
BSSAP.receive(BSSAP_Conn_Prim:MSC_CONN_PRIM_DISC_IND);
}
[] BSSAP.receive(tr_PDU_DTAP_MT(?)) { repeat; }
+ [] BSSAP.receive(BSSAP_Conn_Prim:MSC_CONN_PRIM_CONF_IND) { repeat; }
[] T.timeout {
setverdict(fail, "Timeout waiting for ClearCommand or SCCP Release");
self.stop;