a2d59c6e6e
Add three tests which exercise MSC behaviour when a CIPHER MODE COMPLETE command lacks the optional chosenEncryptionAlgorithm IE. Check for behaviour with A5/1, A5/3, and A5/1 + A5/3 configured in the network, and expect the location update to succeed. These tests pass on master, but they should somehow verify the cipher the MSC ends up using. I am not quite sure how to do that. Would inspecting the MSC's VTY be a reasonable approach? How could his be done by code which runs on BSC_ConnectionHandler? Change-Id: I1a2a126795c544613a7a87e238e1fc8c4e943885 Related: OS#2872 |
||
---|---|---|
.. | ||
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"]; } %}