diff --git a/bsc/BSC_Tests.ttcn b/bsc/BSC_Tests.ttcn
index a9d7c9d..6902744 100644
--- a/bsc/BSC_Tests.ttcn
+++ b/bsc/BSC_Tests.ttcn
@@ -9249,10 +9249,6 @@
 	var PDU_BSSAP emerg_setup_data_ind_bssap;
 	timer T := 3.0;
 
-	/* Make sure the CHAN RQD indicates an emergency call (0b101xxxxx). The difference is that osmo-bsc directly
-	 * assigns a TCH lchan and establishing voice for the emergency call will use Mode Modify, not reassignment to
-	 * another lchan. */
-	g_pars.ra := f_rnd_ra_emerg();
 	f_assignment_emerg_setup();
 
 	T.start;
@@ -9316,12 +9312,19 @@
 
 	f_vty_allow_emerg_msc(false);
 	f_vty_allow_emerg_bts(true, 0);
+	/* Make sure the CHAN RQD indicates an emergency call (0b101xxxxx): */
+	pars.ra := f_rnd_ra_emerg();
 	vc_conn := f_start_handler(refers(f_TC_assignment_emerg_setup_deny), pars);
 	vc_conn.done;
 	f_shutdown_helper();
 }
 
-/* EMERGENCY CALL situation #3, allowed globally but forbidden by BTS */
+/* EMERGENCY CALL situation #3, allowed globally but forbidden by BTS.
+ * The RACH req (and hence CHAN RQD) indicate other than emergency call.
+ * Hence BSC only learns about it being an emergency call later during call setup.
+ * If interested in the  ra="emergency call" + deny bts policy case,
+ * see TC_chan_rqd_emerg_deny.
+ */
 testcase TC_assignment_emerg_setup_deny_bts() runs on test_CT {
 	var TestHdlrParams pars := f_gen_test_hdlr_pars();
 	var MSC_ConnHdlr vc_conn;
@@ -9329,13 +9332,14 @@
 	/* Note: This simulates a spec violation by the MS, correct MS
 	 * implementations would not try to establish an emergency call because
 	 * the system information tells in advance that emergency calls are
-	 * not forbidden */
+	 * not allowed */
 
 	f_init(1, true);
 	f_sleep(1.0);
 
 	f_vty_allow_emerg_msc(true);
 	f_vty_allow_emerg_bts(false, 0);
+	/* Note: Here we implicitly leave default g_pars.ra which is different than "emergency call" */
 	vc_conn := f_start_handler(refers(f_TC_assignment_emerg_setup_deny), pars);
 	vc_conn.done;
 	f_shutdown_helper();