aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-bts-test/osmo-bsc.cfg
AgeCommit message (Collapse)AuthorFilesLines
2022-02-10ttcn3-bts-test: move generic config files into a directoryVadim Yanitskiy1-247/+0
Change-Id: I1bc5c51306525c6829e9d8e2991555a99c9b49a2
2021-03-09*/osmo-bsc.cfg: remove obsolete no-op parametersVadim Yanitskiy1-6/+0
Change-Id: Idebf9df98648b3fe8213cae550ce50e9805bac96
2020-07-31ttcn3-bts-test/osmo-bsc.cfg: do not enable CBCH slots by defaultVadim Yanitskiy1-3/+3
As it turns out, test cases from BTS_Tests_SMSCB configure the CBCH slots "on the fly" depending on the test case parameters. This configuration also makes some test cases fail, so let's (re)configure SDCCH8+CBCH timeslots to SDCCH8. Change-Id: I3699450542dc1350971fbf87ad60a330428dec27
2020-07-21ttcn3-bts-test/osmo-bsc.cfg: change pchan config for TRX#1..3Vadim Yanitskiy1-22/+22
The new physical channel configuration will be used in the upcoming multi-transceiver test cases. Rather than having the same logical channel combinations configured for all transceivers, it makes sense to test more deviations. TRX#0 has kept unchanged. == Physical channel configuration == +-------+------------------+------------------+------------------+------------------+ | # / # | TRX#0 | TRX#1 | TRX#2 | TRX#3 | +-------+------------------+------------------+------------------+------------------+ | TS0 | CCCH+SDCCH4 | TCH/F | TCH/H | PDCH | +-------+------------------+------------------+------------------+------------------+ | TS1 | TCH/F | SDCCH8+CBCH | PDCH | TCH/H | +-------+------------------+------------------+------------------+------------------+ | TS2 | TCH/F | PDCH | SDCCH8+CBCH | TCH/H | +-------+------------------+------------------+------------------+------------------+ | TS3 | TCH/F_PDCH | TCH/F_TCH/H_PDCH | PDCH | SDCCH8+CBCH | +-------+------------------+------------------+------------------+------------------+ | TS4 | TCH/F_TCH/H_PDCH | TCH/F_PDCH | SDCCH8 | PDCH | +-------+------------------+------------------+------------------+------------------+ | TS5 | TCH/H | SDCCH8 | TCH/F | TCH/F | +-------+------------------+------------------+------------------+------------------+ | TS6 | SDCCH8 | PDCH | PDCH | PDCH | +-------+------------------+------------------+------------------+------------------+ | TS7 | PDCH | PDCH | PDCH | SDCCH8 | +-------+------------------+------------------+------------------+------------------+ Change-Id: Ib27704dcba3979d69e44065c472b1452eaa11a7a Related: SYS#4868, OS#4546
2020-07-06ttcn3-bts-test/osmo-bsc.cfg: use logging level 'notice' by defaultVadim Yanitskiy1-25/+1
Change-Id: Ib0bfbe0d98ef0d3e6d627e737edbbf013a5f19c0
2020-06-09ttcn3-bts: Update cfg for test TC_tx_power_start_ramp_up_bcchPau Espin Pedrol1-4/+4
The test mentioned above is added in osmo-ttcn3-hacks.git Ieb7444c6312bbeab64da2732393b3facf3e1f003. config files are updated to make sense: * "nominal power" in osmo-bsc.cfg reflects correct default nominal tx power of fake_trx. * "osmotrx tx-attenuation" in osmo-bts.cfg is removed to let osmo-bts use the value received through OML (max_power_red 20). * "power-ramp step-size" in osmo-bts.cfg is increased to speed up the test. There's no good reason to keep it lower. Change-Id: I878d329dde3d2089ee3b68f56271fcb88d210025
2020-06-01osmo-{bsc,msc}.cfg: eliminate 'periodic location update 30'Vadim Yanitskiy1-1/+1
This parameter has been deprecated in both osmo-msc and osmo-bsc. Change-Id: I6d33c6d9c43078ee9961d3b076386188ec45be0f
2020-05-29osmo-bsc.cfg: drop deprecated '11bit_rach_support_for_egprs'Vadim Yanitskiy1-1/+0
EGPRS Packet Channel Request cannot be enabled in 'GPRS only' mode anyway. Moreover, this command was deprecated. Let's just remove it. Change-Id: I03733490d9c4bf78a748d22874e550e015fbab78
2020-05-29osmo-bsc.cfg: drop deprecated 'ip.access rtp-base' parameterVadim Yanitskiy1-1/+0
Change-Id: Ie5494fd08fc7d2277a087ccc9502b5076fa2565b
2020-05-29osmo-bsc.cfg: drop non-existing 'access-list-name bsc-list'Vadim Yanitskiy1-1/+0
In the recent osmo-bsc master, this configuration parameter has been removed, so it fails to start due to "unknown parameter". Change-Id: I8f763a4b35f80f4db637bebdd8e802a835a9fd2d
2020-05-28ttcn3-bts-test: enable 3 additional transceivers for BTS#0Vadim Yanitskiy1-0/+90
This is needed for the forthcoming frequency hopping test cases. Change-Id: Ib5ad31388ae25399ad09739aac3fdcb0b3a1f78b Depends: I86afb55ecc6703ce7a229aaa626223f9331a4778 Related: OS#4546
2020-04-05ttcn3-bts-test/osmo-bsc.cfg: Remove 'nat' from loggingVadim Yanitskiy1-1/+0
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the bogus 'NAT' log category has been removed from osmo-bsc. Change-Id: I266d6f6ed54d1457b1ca63b87fc1c29f6dd40caf
2019-11-20Update ttcn3-*/jenkins.sh to log stdout+stderr of process to log filePau Espin Pedrol1-2/+2
This way we get VTY parsing failures as well as backtraces upon process crash. Related: OS#4212 Change-Id: I3d9f6de638dbc07391a32c6a0cbd469dc5adf2b5
2019-10-31ttcn3-bts-test: remove obsolete vty configPhilipp Maier1-3/+0
The configuration file for osmo-bsc contains obsolete config statements, which cause osmo-bsc to crash. Lets remove those config statements. Change-Id: Ic91e2ee1e9132886cd02535bc84a568d4c25dbb4
2019-10-30osmo-bsc.cfg: remove obsolete logging categories (cc, mgcp)Philipp Maier1-2/+0
The logging categories cc and mgcp are obsolete. The tests still contain logging statements with those categories, which makes osmo-bsc terminate during startup while parsing the configuration file. Change-Id: Ifd6bf46b73420c0443f997ea953318710544b751
2019-10-04ttcn-*: Fix gsmtap log not enabledPau Espin Pedrol1-0/+1
gsmtap log won't be sending any message unless it is allowed by "logging filter all 1". Change-Id: Ibf8062c0d962f2572a07623e6f06936df0d42c67
2019-07-10ttcn3-*: enable GSMTAP loggingOliver Smith1-0/+3
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-06-03ttcn3-*: Enable extended-timestamp in VTY cfgPau Espin Pedrol1-0/+1
Having extended-timestamp allows for easier matching between osmo-*.log files and pcap traces. Change-Id: I98cdc0adc24edc966d5648d2c215c6ad7c749209
2019-05-23ttcn3-bts-test: Fix BSC VTY access from test suiteHarald Welte1-0/+1
Some tests, particularly those for SMSCB, want to access the BSC VTY. This was enabled in the ttcn3 code, but the configs we're using in the docker environment didn't properly refelect that yet. Change-Id: I6b6e8b47bfe85c15fb57a25b649029f872477146
2019-03-21BTS tests: update NSVC config in osmo-bsc.cfgMax1-5/+1
* remove extra NSVC config * use 0.0.0.0 for nsvc 0 The additional nsvc and this particular address are not used for BTS' PCU-related tests in any way and only add confusion. It's likely a result of copy-paste from another test. Change-Id: Ie424107672496df70fc83c8fd6cef99a312fcee7
2019-01-14.../osmo-bsc.cfg: drop deprecated dyn_ts_allow_tch_fVadim Yanitskiy1-1/+0
Since Ib2335d02ea545aff837aadd49f15b2fdb418c46e, this VTY option is deprecated in osmo-bsc, so let's actualize the config files. Change-Id: I709e1afd2a9cccdc92eec312dff607947a10c299
2018-09-26ensure well-formed config filesHarald Welte1-40/+40
Change-Id: Id687e63c418e2e955ccbb92f2420a80fc0704ea4
2018-06-03remove deprecated "dest" config option from config filesHarald Welte1-1/+0
Change-Id: I1073846c04a8466f2ccf501e27cf152df09042c5
2018-04-06ttcn3-bts-test: Configure BTS to have dynamic PDCHHarald Welte1-2/+2
This is required by later versions of the osmo-ttcn3-hacks BTS test suite after Change-Id I2a42531dc5555ab4772d538fda462343605b8feb Change-Id: I229000ce7609845fdf24cafe1f5ec2bfa3f507e8
2018-03-13bts-test: Change logging to file so we get BTS/BSC logs as test resultHarald Welte1-2/+2
2018-03-01Add osmo-bts-test + dependenciesHarald Welte1-0/+196
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-26 20:49:11 +0000