diff --git a/msc/MSC_Tests.ttcn b/msc/MSC_Tests.ttcn
index 0372ec7..1767761 100644
--- a/msc/MSC_Tests.ttcn
+++ b/msc/MSC_Tests.ttcn
@@ -6670,6 +6670,10 @@
 	vc_conn.done;
 }
 
+private altstep as_mncc_rx_rtp_create(CallParameters cpars) runs on BSC_ConnHdlr {
+	[] MNCC.receive(tr_MNCC_RTP_CREATE(cpars.mncc_callref));
+}
+
 const charstring REEST_LOST_CONNECTION := "REEST_LOST_CONNECTION";
 const charstring REEST_CLEARED := "REEST_CLEARED";
 
@@ -6734,12 +6738,15 @@
 	 * Apparently osmo-msc currently also sends an MDCX to the CN side, just repeating the same configuration that
 	 * is already in use. This test accepts any number of or even lack of MDCX. */
 	var default ack_mdcx := activate(as_mgcp_ack_all_mdcx(cpars));
+	var default optional_rtp_create := activate(as_mncc_rx_rtp_create(cpars));
 
 	BSSAP.send(ts_BSSMAP_AssignmentComplete(omit, tla, codec));
+
 	/* The call has been fully re-established.
 	 * Let a bit of time pass before hanging up, for everything to settle. */
 	f_sleep(3.0);
 
+	deactivate(optional_rtp_create);
 	deactivate(ack_mdcx);
 
 	/* Hang up the call and clear the new, second A connection */