bsc: Add TC_err_84_unknown_msg to check if unknown RR message triggers RR STATUS

... as declared in TS 24.008 Section 8.4

Change-Id: I4f81b955567d2a33ead350ed312c4c4f6dd7ed8a
This commit is contained in:
Harald Welte 2018-01-31 23:36:25 +01:00
parent e3bd658abf
commit e9e02e4556
1 changed files with 22 additions and 0 deletions

View File

@ -1511,6 +1511,27 @@ testcase TC_err_82_short_msg() runs on test_CT {
}
/* 24.008 8.4 Unknown message must trigger RR STATUS */
private function f_tc_err_84_unknown_msg(charstring id) runs on MSC_ConnHdlr {
f_est_single_l3(ts_RRM_UL_REL('00'O));
timer T := 3.0
alt {
[] RSL.receive(tr_RSL_DATA_REQ(g_chan_nr, ?, decmatch tr_RRM_RR_STATUS)) {
setverdict(pass);
}
[] BSSAP.receive { setverdict(fail, "unexpected BSSAP"); }
[] T.timeout { setverdict(inconc); }
}
}
testcase TC_err_84_unknown_msg() runs on test_CT {
var MSC_ConnHdlr vc_conn;
f_init(1, true);
f_sleep(1.0);
vc_conn := f_start_handler(refers(f_tc_err_84_unknown_msg), testcasename());
vc_conn.done;
}
control {
/* CTRL interface testing */
@ -1579,6 +1600,7 @@ control {
execute( TC_unsol_ass_compl() );
execute( TC_unsol_ho_fail() );
execute( TC_err_82_short_msg() );
execute( TC_err_84_unknown_msg() );
}
}