msc: allow another reject cause in TC_cm_reest_req_reject
osmo-msc will soon have CM Re-Establishing support, and it will start returning a different reject code instead of GSM48_REJECT_SRV_OPT_NOT_SUPPORTED. In TC_cm_reest_req_reject, there is no previous ongoing connection let alone a voice call, so osmo-msc will return GSM48_REJECT_CALL_CAN_NOT_BE_IDENTIFIED. Related: SYS#5130 Change-Id: I3eebab2b26016fb0ef7bf958208eaba6ae4c7836
This commit is contained in:
parent
60122f8076
commit
49bbb511e7
|
@ -1403,7 +1403,9 @@ private function f_tc_cm_reest_req_reject(charstring id, BSC_ConnHdlrPars pars)
|
|||
var MobileIdentityLV mi := valueof(ts_MI_IMSI_LV(g_pars.imsi));
|
||||
var PDU_ML3_MS_NW l3_info := valueof(ts_CM_REEST_REQ(0, mi));
|
||||
f_cl3_or_initial_ue(l3_info);
|
||||
BSSAP.receive(tr_PDU_DTAP_MT(tr_CM_SERV_REJ(int2oct(32,1))));
|
||||
/* Older osmo-msc returns: GSM48_REJECT_SRV_OPT_NOT_SUPPORTED = 32,
|
||||
* newer osmo-msc with CM Re-Establish support returns: GSM48_REJECT_CALL_CAN_NOT_BE_IDENTIFIED = 38 */
|
||||
BSSAP.receive(tr_PDU_DTAP_MT(tr_CM_SERV_REJ( (int2oct(32,1), int2oct(38,1)) )));
|
||||
f_expect_clear();
|
||||
}
|
||||
testcase TC_cm_reest_req_reject() runs on MTC_CT {
|
||||
|
|
Loading…
Reference in New Issue