From e15060252da04aaf8c3eb74cb24790c1be2f17b3 Mon Sep 17 00:00:00 2001
From: Andreas Eversberg <jolly@eversberg.eu>
Date: Thu, 20 Jul 2023 18:08:33 +0200
Subject: [PATCH] BSC_Test_ASCI: Fix test to seize or release uplink by MSC

After sending UPLINK SEIZED COMMAND or UPLINK RELEASE COMMAND the timer
must be started, in order to collect data from the outcome of the test.
The test will fail sometimes, if this is not done.

Change-Id: Ic48e9c259b42ee6e030ea5d05b113ce2933e2247
---
 bsc/BSC_Tests_ASCI.ttcn | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/bsc/BSC_Tests_ASCI.ttcn b/bsc/BSC_Tests_ASCI.ttcn
index b4b0173c6..e4a0cca42 100644
--- a/bsc/BSC_Tests_ASCI.ttcn
+++ b/bsc/BSC_Tests_ASCI.ttcn
@@ -169,10 +169,12 @@ private function f_tc_vgcs_vbs_setup(charstring id) runs on MSC_ConnHdlr {
 		    g_pars.asci_test.vgcs_uplink_release) {
 			log("VGCS: sending Uplink Seized Cmd");
 			BSSAP.send(ts_BSSMAP_UplinkSeizedCmd(9, omit, omit, omit));
+			T.start;
 		}
 		if (g_pars.asci_test.vgcs_uplink_release) {
 			log("VGCS: sending Uplink Release Cmd");
 			BSSAP.send(ts_BSSMAP_UplinkRelCmd(9));
+			T.start;
 		}
 		if (g_pars.asci_test.vgcs_uplink_seized or
 		    g_pars.asci_test.vgcs_uplink_release) {