3c5127edeb
So far we were often just expecting the message type. Instead expect a release on the proper channel number. While hunting a test error, this confused me for a while, because a missing handler resulted in the release message handled in the wrong place, even though the chan_nr mismatched. Related: SYS#5130 Change-Id: I002c9273a387104bea062dec8879b4e19a72008d |
||
---|---|---|
.. | ||
BSC_Tests.cfg | ||
BSC_Tests.default | ||
BSC_Tests.ttcn | ||
BSC_Tests_CBSP.ttcn | ||
BSC_Tests_LCLS.ttcn | ||
BSC_Tests_VAMOS.cfg | ||
BSC_Tests_VAMOS.ttcn | ||
MSC_ConnectionHandler.ttcn | ||
README.md | ||
README.txt | ||
expected-results.xml | ||
gen_links.sh | ||
osmo-bsc-vamos.cfg | ||
osmo-bsc.cfg | ||
osmo-stp.cfg | ||
regen_makefile.sh |
README.md
BSC_Tests.ttcn
- external interfaces
- A-bis side: RSL (emulates BTS-side client) (OML handled by osmo-bts-omldummy)
- A-side (emulates MSC-side)
- BSSAP/SCCP/M3UA (AoIP)
- BSSAP/SCCP/IPA (SCCPLite)
- MGW side: MGCP (emulates MGW side)
- VTY
- CTRL
- StatsD
{% dot bsc_tests.svg digraph G { graph [label="AoIP", labelloc=t, fontsize=30]; rankdir=LR; { rank=same; BTS; STP; }; BSC [label="IUT\nosmo-bsc",shape="box"]; ATS [label="ATS\nBSC_Tests.ttcn"]; BTS [label="osmo-bts-omldummy\nOML only"];
BTS -> BSC [label="A-bis OML"]; ATS -> BSC [label="A-bis RSL"]; ATS -> BSC [label="CTRL"]; ATS -> BSC [label="VTY"]; BSC -> ATS [label="StatsD"]; ATS -> STP [label="A BSSAP\nSCCP/M3UA"]; BSC -> STP [label="A BSSAP\nSCCP/M3UA"]; } %}
{% dot bsc_tests_sccplite.svg digraph G { graph [label="SCCPLite", labelloc=t, fontsize=30]; rankdir=LR; BSC [label="IUT\nosmo-bsc",shape="box"]; ATS [label="ATS\nBSC_Tests.ttcn"]; BTS [label="osmo-bts-omldummy\nOML only"];
BTS -> BSC [label="A-bis OML"]; ATS -> BSC [label="A-bis RSL"]; ATS -> BSC [label="CTRL"]; ATS -> BSC [label="VTY"]; BSC -> ATS [label="StatsD"]; ATS -> BSC [label="A BSSAP\nSCCP/IPA"]; } %}