Harald Welte
5ebf798131
When the test is executed outside of docker, having to manage all those different IP addresses while manually starting programs can be quite cumbersome. Let's just run everything over localhost, like we always do with other tests. Now the only cumbersome command to start is trxcon, as it defaults to only one TRX and adding additional TRX is rather complicated: ./fake_trx.py --trx TRX1@127.0.0.1:5700/1 --trx TRX2@127.0.0.1:5700/2 --trx TRX3@127.0.0.1:5700/3 Change-Id: Iea8519685da7d73696ce9cc2541e93c45c099828 |
||
---|---|---|
.. | ||
BTS_Tests.cfg | ||
BTS_Tests.default | ||
BTS_Tests.ttcn | ||
BTS_Tests_LAPDm.ttcn | ||
BTS_Tests_OML.ttcn | ||
BTS_Tests_SMSCB.ttcn | ||
BTS_Tests_perf.ttcn | ||
README.md | ||
expected-results.xml | ||
gen_links.sh | ||
osmo-bsc.cfg | ||
osmo-bts.cfg | ||
regen_makefile.sh |
README.md
BTS_Tests.ttcn
- external interfaces
- A-bis side: RSL (emulates BSC-side server)
- Um side: L1CTL to control MS
- PCU side: pcu_socket
- VTY
- CTRL
{% dot bts_tests.svg digraph G { rankdir=LR; { rank=same; BTS, BSC}; BTS [label="IUT\nosmo-bts-trx",shape="box"]; ATS [label="ATS\nBTS_Tests.ttcn"]; BSC [label="osmo-bsc\nOML only"]; BTS -> fake_trx [label="bursts"]; fake_trx -> trxcon [label="bursts"]; trxcon -> ATS [label="GSM MAC blocks"];
BTS -> BSC [label="A-bis OML"]; BTS -> ATS [label="A-bis RSL"];
ATS -> BTS [label="pcu_sock"]; ATS -> BSC [label="VTY"]; ATS -> BTS [label="CTRL"]; } %}