jolly has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33718 )
Change subject: BSC_Tests_ASCI: Do not expect UPLINK BUSY message ......................................................................
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 --- M bsc/BSC_Tests_ASCI.ttcn 1 file changed, 19 insertions(+), 4 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/18/33718/1
diff --git a/bsc/BSC_Tests_ASCI.ttcn b/bsc/BSC_Tests_ASCI.ttcn index 78e4356..ebf8407 100644 --- a/bsc/BSC_Tests_ASCI.ttcn +++ b/bsc/BSC_Tests_ASCI.ttcn @@ -213,8 +213,9 @@ 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 @@ 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!");