path: root/src/osmo_gsm_tester/templates
AgeCommit message (Collapse)AuthorFilesLines
2017-08-23Add support for authentication VTY param in msc and bscPau Espin Pedrol2-0/+2
Change-Id: Ie1eb76149d4b006631050f8a1e532fbdbdad6a7f
2017-08-23bts_osmotrx: Support configuring bts addr, trx_remote_ip and launch_trxPau Espin Pedrol1-0/+2
We may want to support running a device which runs its own TRX (osmo-trx or different implementation). Furthermore, this TRX may be available in some specific hwardare rather than on the main unit. This makes it easy to configure OsmoBtsTrx to launch it's own osmo-trx or not. In case it is launched, all IPs are configured correctly to ensure connection can be established. Before this commit, osmo-trx was binding to Now we can support multiple osmo-trx being launched on the main unit. Change-Id: I825ed1fc0c3fe75d196db90c1508283fbd04acf8
2017-08-21Increase log verbosity for osmo-bts-trxPau Espin Pedrol1-1/+2
The log levels changed are useful to understand clock failures we see from time to time in osmo-gsm-tester. See OS-2325. Change-Id: Id74af3ccb2f3db3c1793c7ff7b7a60a534e78e81
2017-08-10osmo-bts-trx config: remove settscNeels Hofmeyr1-1/+0
In osmo-bts change I51aeb17661dfd63ff347f7b2c0d7ffa383ec814c the settsc config item is being removed. To be able to test it, drop the settsc option from the config. Change-Id: I58002a84b6b0104de4fb5c7cade27b263e375c1f
2017-08-09Set osmo-bts pcu-socket config to point to run dirPau Espin Pedrol2-0/+2
Otherwise osmo-bts stores the socket file in /tmp. If an earlier instance doesn't finish cleanly, the file is left there and a new instance will fail to start because it cannot create a new socket file in the same place. Change-Id: I5a1da23c45a4ac496fe765e0d78c52dae3e7808b
2017-08-07cosmetic: osmo-msc.cfg.tmpl: fix indentNeels Hofmeyr1-2/+2
Change-Id: Iefc3b06338cff4f5e51b7b03d9a5f92de18ca86a
2017-08-07aoip: add newly needed osmo-msc point-code configNeels Hofmeyr1-0/+4
OsmoMSC no longer has a hard-coded point-code of 0.0.1. Configure it. Change-Id: I54be984415445e695c583f35c419aed559ac5c84
2017-08-07osmo-bsc.cfg.tmpl: add point code addressesAlexander Couzens1-0/+10
osmo-bsc requires atm to have point code addresses given for msc + bsc Change-Id: I94f8a6892ad7e10001322cbc5a46687c0d532cb2
2017-07-20remove timer section from osmo-{bts,bsc}.cfg.tmplHarald Welte2-22/+0
As described in https://osmocom.org/issues/2380 and related gerrit patch https://gerrit.osmocom.org/#/c/3306 the config files currently contain timers with a 'zero' value, leading to issues. The config file templates used in osmo-gsm-tester suffer actually from exactly the same issue: They basically contain values that were written back to the file based on the default initialization in libbsc, which unfortunately was zero in some cases. Let's remove those values, they are the (bad) default anyway. libbsc patches in the pipeline will introduce reasonable defaults and forbid the use of zero for timers. Change-Id: I8cde29a597a17c2659b3b87268be4b12975f4bef
2017-06-27Revert "osmo-bts-trx config: remove settsc"Neels Hofmeyr1-0/+1
According to pespin, this makes all osmo-bts-trx test runs fail. We will still figure out the details, but for the time being let's go with the known working config. This reverts commit 72ded64705a85df362f918879ddc075d1a0191fe. Change-Id: I57a3db0d060203ad6540c9a3cc7735e273ee0048
2017-06-26osmo-bts-trx config: remove settscNeels Hofmeyr1-1/+0
In osmo-bts change I51aeb17661dfd63ff347f7b2c0d7ffa383ec814c the settsc config item is being removed. To be able to test it, drop the settsc option from the config. Change-Id: I89b35fc587bbac6810511b2317eed24368858f37
2017-06-18Add support for SMPP testingPau Espin Pedrol2-8/+20
As defined in [1], the different related actors are implemented in this commit: ESME and SMSC. SMSC: In Osmocom, the SMSC is currently implemented inside the NITB or the MSC. A new Smsc abstract class is created to shared code between the NITB and the MSC, and also makes it easier for later when the SMSC is splitted. ESMEs can be dynamically added to its configuration in a similar way to how the BTSs are added. ESME: A new class Esme is created which can be used by tests to control an ESME to interact with the SMSC. The ESME functionalities are implemented using python-smpplib. Required version of this library is at least 43cc6f819ec76b2c0a9d36d1d439308634716227, which contains support for python 3 and some required features to poll the socket. This commit already contains a few tests which checks different features and tests the API. Extending tested features or scenarios can be later done quite easily. The tests are not enabled by default right now, because there are several of them in a suite and the ip_address resources are not freed after every tests which ends up in the suite failing due to missing reserved resources. All the tests run alone work though. When the issue is fixed they can then be added to the default list of tests to be run. [1] http://opensmpp.org/specs/SMPP_v3_4_Issue1_2.pdf Change-Id: I14ca3cb009d6d646a449ca99b0200da12085c0da
2017-06-14osmo-bts-trx: set l1c logging level to noticeNeels Hofmeyr1-1/+1
We have sporadic osmo-bts-trx shutdowns with "No clock from osmo-trx" error messages. Around it are L1C logs on level 'notice', so let's log those as well. Related: OS#2325 Change-Id: Ic306d2dd8670550d84e9c446098bccaba147e13b
2017-06-13cosmetic: osmo-stp.cfg: fix indentNeels Hofmeyr1-1/+1
Change-Id: I239fe6da004b840fb805c51e46967c8ba3b0d3f5
2017-06-13aoip: add osmo-stp, now required for aoip runsNeels Hofmeyr1-0/+16
Change-Id: I35d4cb0d173eec240bccc1f3a5965a774b7b3506
2017-06-08osmo-msc: configure HLR addressNeels Hofmeyr1-0/+2
In db59bcf9fcdc5f05fdb9047b905ab497472440bc we added a configured GSUP server address for the osmo-hlr, but the osmo-msc is still trying to connect to In the same way as for mgcpgw, add conf_for_msc() to OsmoHLR, and use that to configure the HLR's address in osmo-msc.cfg. Related: OS#2320 Change-Id: I005aa160c679fc92b248abd762888959bd5b2c55
2017-06-03Use reserved ip address for osmo-hlr GSUP interfacePau Espin Pedrol1-0/+3
Otherwise was being used and we want all interfaces for a specific osmo-hlr instance to use the same IP Requires osmo-hlr change id I79f7a300480f308b21116dd14d1698be38725afd otherwise osmo-hlr won't be able to parse the configuration file. Change-Id: I4e0063abc8de3d739ebd81942b692cc2e75792f1
2017-05-31Use reserved ip address for osmo-mgcpgw VTY interfacePau Espin Pedrol1-0/+3
Otherwise was being used and we want all interfaces for a specific osmo-mgcpgw instance to use the same IP Change-Id: I60dbfbb66458cd333fe07139ee175c94fa1672a7
2017-05-31Use reserved ip address for osmo-bsc ctrl interfacePau Espin Pedrol1-0/+2
Otherwise was being used and we want all interfaces for a specific osmo-bsc instance to use the same IP Change-Id: I38dccac6707bf55f0abcf96e3a9d7d8ec765a156
2017-05-29fix osmo-bts-trx: add config: 'osmotrx tx-attenuation oml'Neels Hofmeyr1-0/+1
Before this, the network opened up by osmo-bts-trx would be invisible through the attenuation of the osmo-gsm-tester hardware, because tx-attenuation would apparently default to 50, meaning maximum attenuation. Change-Id: I1c026b5691033127eef766d82566c39cc070e14a
2017-05-29MSC+BSC: add test api to run OsmoMSC and OsmoBSC with AoIPNeels Hofmeyr4-0/+150
Change-Id: I5842e8f1cba8e8e6bedfc08540efcafe207159cb
2017-05-29config: nitb template: move ip_address to nitb.ip_addressNeels Hofmeyr1-4/+4
It's the NITB's address, so it should go in the nitb.* scope. Change-Id: I71a5ef153b7156b0644253f5aa8a0c848f42ab3b
2017-05-29rename resource nitb_iface to ip_addressNeels Hofmeyr1-4/+4
I would like to use the IP addresses also for OsmoBSC processes, so it is more than clear now that 'nitb_iface' was the wrong naming choice. The only distinction we may need in the future is public versus loopback interface. To add that, we may add a trait to the 'ip_address' resource like: ip_address: - addr: type: public - addr: type: loopback This way we can substitute public vs loopback addresses flexibly (e.g. using scenarios). Change-Id: I3ad583ae7a33f7a7bb56fe78a125f73c56a0e860
2017-05-29nitb config: set: logging color 1, category 1Neels Hofmeyr1-2/+2
Change-Id: Icd9022f5732caac65d16fc49f2ed7833199523de
2017-05-25remove bts_ocpthy.pyNeels Hofmeyr1-45/+0
We're not currently paying attention to the octphy in osmo-gsm-tester. So instead of maintaining dead code, remove the bts_octphy.py; we can re-add when the octphy is implemented properly. Change-Id: Ia5d5750d440ae7019634b51fa1efe7bbb2a1d1e2
2017-05-15Enable GSMTAP on BTS and record it on the main unit NITBPau Espin Pedrol3-0/+37
Change-Id: I057a83bc20c5e664ac1778812452f189166919ba
2017-05-07bts config: tweak logging parametersNeels Hofmeyr3-20/+22
The BTS logs grew exceptionally large because of logging 'level all debug'. Change-Id: I2901bf47a7b12aabcbd416ca7da49db886a061d5
2017-05-04nitb,sysmobts: tweak configNeels Hofmeyr1-1/+1
Set saner MCC+MNC, use more power.
2017-04-13fix octphy, fix conf, improve loggingYour Name2-6/+10
Clearly separate the kinds of BTS hardware the GSM tester knows ('type') from the NITB's bts/type config item ('osmobsc_bts_type' -- not 'osmonitb_...' to stay in tune with future developments: it is the libbsc that needs this). For BTS hardware kinds, use the full name of the binary for osmo driven models: osmo-bts-sysmo, osmo-bts-trx, osmo-bts-octphy. Change-Id: I1aa9b48e74013a93f9db1a34730f17717fb3b36c
2017-04-12octphy (untested); fix regression test expectationsNeels Hofmeyr1-0/+32
Change-Id: Ie9986e0fe49171fb616ce92c3d8652002318f94f
2017-04-08core implementationNeels Hofmeyr3-29/+46
code bomb implementing the bulk of the osmo-gsm-tester Change-Id: I53610becbf643ed51b90cfd9debc6992fe211ec9
2017-03-28initial import0.1Neels Hofmeyr5-0/+164
The original osmo-gsm-tester was an internal development at sysmocom, mostly by D. Laszlo Sitzer <dlsitzer@sysmocom.de>, of which this public osmo-gsm-tester is a refactoring / rewrite. This imports an early state of the refactoring and is not functional yet. Bits from the earlier osmo-gsm-tester will be added as needed. The earlier commit history is not imported.