Pau Espin
1a026a52d3
* Some scenarios like MGW BSC-attached in SCCPlite require handling of 2 MGCP-over-UDP sockets in MGCP Emulation: 1 for regular libosmomgcp-client from osmo-bsc and another one from the forward socket from osmo-bsc (of MGCP-over-IPA messages communicated with MSC). * Old port is kept for backward compatibility with other tests and enabled by default. It's also interesting to keep it because it makes tests without special needs (2 sockets) to use the old port/API which produces simpler code to read and mantain. * Users of the new port have to enable multi_conn_mode parameter and expect to interact with port MGCP_CLIENT_MULTI instead of MGCP_CLIENT, which will offer messages containing information about the UDP connection being used by that message. Change-Id: Ic0ba8c5cde068c07671512a83095d83e28b86746 |
||
---|---|---|
.. | ||
BSC_ConnectionHandler.ttcn | ||
MSC_Tests.cfg | ||
MSC_Tests.default | ||
MSC_Tests.ttcn | ||
MSC_Tests_Iu.ttcn | ||
README.md | ||
expected-results.xml | ||
gen_links.sh | ||
osmo-msc.cfg | ||
osmo-stp.cfg | ||
regen_makefile.sh |
README.md
MSC_Tests.ttcn
- external interfaces
- A: BSSAP/SCCP/M3UA (emulates BSC-side)
- MNCC: MNCC/unix-domain (emulates ext. MNCC side)
- MGW: MGCP (emulates MGW side)
- GSUP (impllements HLR side)
{% dot msc_tests.svg digraph G { rankdir=LR; MSC [label="IUT\nosmo-msc",shape="box"]; ATS [label="ATS\nMSC_Tests.ttcn"];
ATS -> MSC [label="MNCC"]; ATS -> MSC [label="SMPP",style="dashed"]; ATS -> MSC [label="CTRL"]; ATS -> MSC [label="VTY"]; MSC -> ATS [label="GSUP"]; ATS -> STP [label="A BSSAP\nSCCP/M3UA"]; MSC -> STP [label="A BSSAP\nSCCP/M3UA"]; } %}