aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPhilipp Maier <pmaier@sysmocom.de>2018-02-09 10:30:31 +0100
committerHarald Welte <laforge@gnumonks.org>2018-02-10 10:09:28 +0000
commite8f38ed2b3710275164bcf039cae07cc77823bbf (patch)
tree32bc4cc69d7b8b8d3b88bd9109b800c84ac0f381
parent0bef21e64554027426f0de0b1910c1f1d0d6e701 (diff)
BSC: do not flush RSL queue early in TC_chan_rel_a_reset()
When f_expect_chan_rel() is called after receiving the BSSMAP RESET and DISC.ind f_expect_chan_rel() is called. The flush parameter is not set, which means the default flush = true is valid. This leads into an early flush of the RSL Queue and tosses the RSL RELEASE REQUEST we expect, so the test can not pass, even when the BSC sends the RLEASE REQUEST. Looking further up in the code. IPA_RSL[0].clear is called, so the Queue is flushed to get rid of unwanted messages from the IMMEDIATE ASSIGN. There is no need to flush the queue a second time anyway. - Do not flush the RSL queue, set flush=false when calling f_expect_chan_rel() Change-Id: I2962f741e0b13dec08ac6c918d326828beb65a6a
-rw-r--r--bsc/BSC_Tests.ttcn2
1 files changed, 1 insertions, 1 deletions
diff --git a/bsc/BSC_Tests.ttcn b/bsc/BSC_Tests.ttcn
index 24df03f4..086830a6 100644
--- a/bsc/BSC_Tests.ttcn
+++ b/bsc/BSC_Tests.ttcn
@@ -710,7 +710,7 @@ testcase TC_chan_rel_a_reset() runs on test_CT {
[] BSSAP.receive(tr_BSSAP_DISC_ind(dt.sccp_conn_id, ?, ?)) { }
}
- f_expect_chan_rel(0, dt.rsl_chan_nr);
+ f_expect_chan_rel(0, dt.rsl_chan_nr, false);
setverdict(pass);
}