msc: add a COORD port for inter-component coordination
Also provide a blank receive template for CallParameters which is
needed to receive a CallParameters record via the COORD port.
Will be used by MSC_Tests.TC_call_re_establishment in
Ifdff5573eeb3b3d41e8599b9b0228411d2576864
Change-Id: Iba3a5304fa40159bc2c31cdc3a71ee56ed08bd12
diff --git a/msc/BSC_ConnectionHandler.ttcn b/msc/BSC_ConnectionHandler.ttcn
index cf4e846..2f270ca 100644
--- a/msc/BSC_ConnectionHandler.ttcn
+++ b/msc/BSC_ConnectionHandler.ttcn
@@ -63,11 +63,18 @@
import from TCCConversion_Functions { function f_strstr };
+type port BSC_ConnHdlr_Coord_PT message
+{
+ inout charstring, CallParameters;
+} with { extension "internal" };
+
+
/* this component represents a single subscriber connection */
type component BSC_ConnHdlr extends RAN_ConnHdlr, MNCC_ConnHdlr, GSUP_ConnHdlr, MGCP_ConnHdlr, SMPP_ConnHdlr, CTRL_Adapter_CT, SGsAP_ConnHdlr {
var BSC_ConnHdlrPars g_pars;
timer g_Tguard := 60.0;
port TELNETasp_PT MSCVTY;
+ port BSC_ConnHdlr_Coord_PT COORD;
}
type record BSC_ConnHdlrNetworkPars {
@@ -959,6 +966,35 @@
got_osmux_count := 0
};
+template CallParameters tr_CallParams := {
+ called_party := ?,
+ transaction_id := ?,
+ mo_call := ?,
+ bearer_cap := ?,
+ emergency := ?,
+ mncc_callref := *,
+ mncc_bearer_cap := ?,
+ mncc_rtp_ip := ?,
+ mncc_rtp_port := ?,
+ bss_rtp_ip := ?,
+ bss_rtp_port := ?,
+ mss_rtp_ip := *,
+ mss_rtp_port := *,
+ got_crcx_count := ?,
+ mgw_conn_1 := ?,
+ mgw_conn_2 := ?,
+ rtp_payload_type := ?,
+ rtp_sdp_format := ?,
+ mgw_drop_dlcx := ?,
+ stop_after_cc_setup := ?,
+ ran_clear_when_alerting := ?,
+ expect_release := ?,
+ mgcp_call_id := *,
+ mgcp_ep := ?,
+ use_osmux := ?,
+ got_osmux_count := ?
+};
+
/* Allocate a call reference and send SETUP via MNCC to MSC */
function f_mt_call_initate(inout CallParameters cpars)
runs on BSC_ConnHdlr {