Commit Graph

15 Commits

Author SHA1 Message Date
Vadim Yanitskiy c69cb106fd osmo-{bsc,msc}.cfg: eliminate 'periodic location update 30'
This parameter has been deprecated in both osmo-msc and osmo-bsc.

Change-Id: I6d33c6d9c43078ee9961d3b076386188ec45be0f
2020-06-01 01:17:35 +07:00
Pau Espin c3f157b939 Update ttcn3-*/jenkins.sh to log stdout+stderr of process to log file
This way we get VTY parsing failures as well as backtraces upon process
crash.

Related: OS#4212
Change-Id: I3d9f6de638dbc07391a32c6a0cbd469dc5adf2b5
2019-11-20 17:17:45 +01:00
Pau Espin 65bc0ae407 ttcn-*: Fix gsmtap log not enabled
gsmtap log won't be sending any message unless it is allowed by "logging
filter all 1".

Change-Id: Ibf8062c0d962f2572a07623e6f06936df0d42c67
2019-10-04 15:50:50 +02:00
Oliver Smith c2ed5bb201 ttcn3-*: enable GSMTAP logging
Configure each osmo-* program to send GSMTAP log output to the IP of the
docker container, which runs the testsuite (and therefore runs tcpdump).

Related: https://lists.osmocom.org/pipermail/openbsc/2019-June/012946.html
Change-Id: I99e74f6ffb5b7d566cec35995bf067df414968d8
2019-07-10 09:34:39 +02:00
Pau Espin ee49c7ba88 ttcn3-*: Enable extended-timestamp in VTY cfg
Having extended-timestamp allows for easier matching between osmo-*.log
files and pcap traces.

Change-Id: I98cdc0adc24edc966d5648d2c215c6ad7c749209
2019-06-03 17:59:42 +02:00
Harald Welte e0816ed331 ttcn3-msc-tests: Add IuCS for one simulated RNC
We need to update the MSC_Tests.cfg as well as the osmo-stp.cfg
to provsion a virtual RNC link.  As the new RNC uses routing key 2,
we shift the MSC routing key to 3.

Change-Id: I10a249b1a851436fd3c20face6ccc94b304bd3e4
2019-04-30 15:24:16 +00:00
Max af8749c348 MSC: use config file for mncc path
Use config file parameter instead of command line option for MNCC socket
path.

Change-Id: I689cfb3bad09b76859ef7e42c1312c636eebe637
2018-12-12 17:43:35 +01:00
Harald Welte ff3dc6e45f ensure well-formed config files
Change-Id: Id687e63c418e2e955ccbb92f2420a80fc0704ea4
2018-09-26 09:27:38 +00:00
Harald Welte 8e337f0bca ttcn3-msc-test: Add SMPP config bits
Change-Id: I595a1ca2d47667e654f8a0a69bfe98c91ac58d39
2018-04-14 19:40:12 +00:00
Harald Welte c90d07003c ttcn3-msc-test: Disable MM INFO
In the past, MM INFO transmission was broken, so the tests were
written without expecting it.  Now, the bug in osmo-msc has been
fixed.

With the config file enabling it, and the tests not expecting MM INFO,
a lot of them failed. Let's disable MM INFO for now until the tests
can deal with it
2018-03-18 21:38:43 +00:00
Harald Welte 3c34820699 ttcn3-msc-test: fix MNC/MCC to match MSC_Tests.ttcn
We recently introduced verification of the MCC/MNC, and the osmo-msc.cfg
MCC/MNC settings mis-matched those of MSC_Tests.ttcn resulting in lots
of test failures.
2018-03-18 17:06:39 +01:00
Harald Welte c1694826e4 Use new split config file + tcpdump support of osmo-ttcn3-hacks
This uses osmo-ttcn3-hacks Change-Id
I3db452e24e5238aa05254d903739c64d202e61db, which introduces
some shared/common config file as well as per-testcase pcap file
generation.
2018-02-14 19:06:46 +00:00
Harald Welte edcda6b2f3 ttcn3-msc-test: Update osmo-msc.cfg to recent master (removed vty commands) 2018-02-14 09:06:23 +00:00
Harald Welte facbb6575e move every 'test network' to its own IP address space
Ideally we would want to launch a group of containers with their own
private network segment and use the same static IP addresses in those
isolated networks.

The stupidity of docker is requiring unique IPv4 addresses even on
isolated (!) networks.  This means we have to manually give each of our
test setups a different subnet, and then we can at least run one
instance that test in parallel to at most one instance of each other
test.

If this weird reestriction about unique IPv4 addresses didn't exist,
we could start any number of test runs in parallel.
2018-02-06 19:08:45 +01:00
Harald Welte 8fc4202fae Add ttcn3-msc-test container with OsmoMSC test suite 2018-01-27 20:25:10 +01:00