BSC_Tests: fix f_mo_l3_transceive(): relax DLCI matching
Since If4d479a54cad467f53b49065c1c435a4471ac7d2, osmo-bsc started to send more concrete DLCI values on the A/BSSAP interface. In particular, the control channel identification bits now indicate whether it's SDCCH/FACCH or SACCH channel. Let's use '?' as the default DLCI template that we expect to get from the IUT, so those test cases, for which DLCI is not a part of the testing scenario, would not fail. Change-Id: Ida659d53e0d31f9aa0ea2ccccefc94d8c659eb76
This commit is contained in:
parent
04ce4c6047
commit
2ef6a2f7fb
|
@ -4521,7 +4521,7 @@ testcase TC_ho_out_of_this_bsc() runs on test_CT {
|
|||
}
|
||||
|
||||
private function f_mo_l3_transceive(template (value) RslLinkId link_id := ts_RslLinkID_DCCH(0),
|
||||
template (present) OCT1 dlci := '00'O,
|
||||
template (present) OCT1 dlci := ?,
|
||||
octetstring l3 := '0123456789'O)
|
||||
runs on MSC_ConnHdlr {
|
||||
/* The old lchan and conn should still be active. See that arbitrary L3
|
||||
|
|
Loading…
Reference in New Issue