bsc: add Coord_PT to communicate between components
This is used by upcoming BSC_Tests.TC_cm_reestablishment(). Related: SYS#5130 Change-Id: I093ca7f66a3106a75e409ad8ea03e7db3c3cb165
This commit is contained in:
parent
21c1cffcec
commit
d36a82fd8a
|
@ -431,6 +431,11 @@ altstep as_Media() runs on MSC_ConnHdlr {
|
|||
[] as_Media_mgw();
|
||||
}
|
||||
|
||||
type port Coord_PT message
|
||||
{
|
||||
inout charstring;
|
||||
} with { extension "internal" };
|
||||
|
||||
/* this component represents a single subscriber connection at the MSC.
|
||||
* There is a 1:1 mapping between SCCP connections and RAN_ConnHdlr components.
|
||||
* We inherit all component variables, ports, functions, ... from RAN_ConnHdlr */
|
||||
|
@ -441,6 +446,7 @@ type component MSC_ConnHdlr extends RAN_ConnHdlr, RSL_DchanHdlr, MGCP_ConnHdlr,
|
|||
/* procedure port back to our parent (RAN_Emulation_CT) for control */
|
||||
port RAN_PROC_PT RAN;
|
||||
port TELNETasp_PT BSCVTY;
|
||||
port Coord_PT COORD;
|
||||
|
||||
/* Proxy MGCP-over-IPA and MGCP-over-UDP */
|
||||
port IPA_MGCP_PT MGCP_MSC_CLIENT;
|
||||
|
|
Loading…
Reference in New Issue