Commit Graph

11 Commits

Author SHA1 Message Date
Pau Espin dbeec9ec47 ttcn3-bsc-sccplite: Enable color output in log file
Change-Id: I63932a9d2aafad68624aee3e42bef0bd4c2c4717
2019-10-23 17:59:27 +02: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 5f98d0120a sccplite/osmo-bsc.cfg: add bts 3
Have the same amount of bts like in the regular (non-sccplite)
osmo-bsc.cfg, so we can make BSC_Tests.TC_ctrl pass for regular and
sccplite again.

Related: I1c57a04747f5ec004ccf4657954dcb0b003c24fc
Related: Ie2c664ba0f845da644e20e2c919c12d8fc2af6ba (osmo-ttcn3-hacks)
Related: OS#4156
Change-Id: I00547dccf8908d46df4730cb513fe577956d7683
2019-08-20 08:00:15 +00: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
Vadim Yanitskiy b6c3dd787a .../osmo-bsc.cfg: drop deprecated dyn_ts_allow_tch_f
Since Ib2335d02ea545aff837aadd49f15b2fdb418c46e, this VTY option
is deprecated in osmo-bsc, so let's actualize the config files.

Change-Id: I709e1afd2a9cccdc92eec312dff607947a10c299
2019-01-14 21:07:36 +00:00
Neels Hofmeyr 850c89ffa8 osmo-bsc.cfg: inter-bsc HO: add a neighbor identity
This mirrors osmo-ttcn3-hacks change:
"bsc: inter-BSC HO: add TC_ho_out_of_this_bsc, TC_ho_into_this_bsc"
change-id Id22852d4be7f127d827e7a8beeec55db27c07f03

(As well as removal of the 'add' keyword in change-id
I6a83a8d4ba61b87905c6fae457d4b4eb6078dce9 after osmo-bsc change
I143f21f6069d1a86096cc8240cf69eb7ea9c8ac8.)

Related: OS#2283
Change-Id: I077c2ad2ede900ec43f55655bd740651d3bbe83d
2018-09-27 22:22:34 +02:00
Harald Welte ff3dc6e45f ensure well-formed config files
Change-Id: Id687e63c418e2e955ccbb92f2420a80fc0704ea4
2018-09-26 09:27:38 +00:00
Harald Welte 060d47f071 use non-overlapping IP networks for bsc-sccplite and SIP tests
The osmo-sip-connector test is already using 172.18.11.x, let's migrate
sccplite to 172.18.12.x to prevent any conflicts when running both tests
on the same build slave (docker instance).

Change-Id: I96beed1f5e01bdb8e77e20f77a459aa006de10fe
2018-08-24 08:32:59 +02:00
Harald Welte 57b8610ae1 ttcn3-bsc-test: Fix sccplite configuration
Change-Id: I79ac95df2fe973d016706be407ec21853abd7875
2018-06-03 22:54:41 +02:00
Harald Welte da04310dd9 ttcn3-bsc-test: Add SCCPlite configs + jenkins-sccplite.sh
The existing dest config + jenkins.sh test 3GPP AoIP operation,
while the new set of configs + jenkins-sccplite.sh are testing
IPA/SCCPlite operation of osmo-bsc.

Change-Id: Ief0799a8f7d378dc3831e7988c9175166c82eace
2018-05-30 14:28:25 +00:00