ttcn3
/
osmo-ttcn3-hacks
mirror of https://gerrit.osmocom.org/osmo-ttcn3-hacks
10
0
Fork 1
Code Issues Releases Wiki Activity

BSC_Tests_ASCI: Do not expect UPLINK BUSY message 

There is no UPLINK BUSY message sent by BSC, if the talker
requests/establishes the uplink. Due to timing reason, the message is
sent by the BTS itself towards the MS.

Change-Id: I2e3b866eca174ae212ea986980d508e48e31fa57
This commit is contained in:
Andreas Eversberg 2023-07-07 12:09:00 +02:00 committed by laforge
parent c0870e5a08
commit 5e3dd362f6
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
bsc/BSC_Tests_ASCI.ttcn
View File

@ -213,8 +213,9 @@ private function f_tc_vgcs_vbs_setup(charstring id) runs on MSC_ConnHdlr {
setverdict(fail, "VGCS: No uplink request as expected!");
return;
}
if (not uplink_busy) {
setverdict(fail, "VGCS: Uplink not busy as expected!");
/* UPLINK BUSY is automatically sent by BTS, but not by BSC. */
if (uplink_busy) {
setverdict(fail, "VGCS: Uplink set to busy, this is not expected!");
return;
}
log("VGCS: Uplink requested and uplink marked busy as expected!");
@ -226,8 +227,9 @@ private function f_tc_vgcs_vbs_setup(charstring id) runs on MSC_ConnHdlr {
setverdict(fail, "VGCS: No uplink request confirm as expected!");
return;
}
if (not uplink_busy) {
setverdict(fail, "VGCS: Uplink not busy as expected!");
/* UPLINK BUSY is automatically sent by BTS, but not by BSC. */
if (uplink_busy) {
setverdict(fail, "VGCS: Uplink set to busy, this is not expected!");
return;
}
log("VGCS: Uplink established and uplink marked busy as expected!");