ttcn3
/
osmo-ttcn3-hacks
mirror of https://gerrit.osmocom.org/osmo-ttcn3-hacks
10
0
Fork 1
Code Issues Releases Wiki Activity
osmo-ttcn3-hacks/bts/osmo-bts.cfg

89 lines
1.7 KiB
INI
Raw Normal View History

bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
!
! OsmoBTS (0.4.0.446-e0fb) configuration saved from vty
!!
!
bts: Run everything over 127.0.0.1 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
2020-10-20 16:02:49 +00:00
log gsmtap 127.0.0.1
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
logging level set-all debug
bts: Update osmo-bsc.cfg and osmo-bts.cfg Somebody seems to have forgotten to update the osmo-bsc.cfg file here, as osmo-bsc wouldn't even start using the file here. Change-Id: I8453da3bda36912ee42fb0c8d862f75b2065965f
2020-10-10 17:02:54 +00:00
logging filter all 1
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
!
log stderr
logging filter all 1
bts: Update osmo-bsc.cfg and osmo-bts.cfg Somebody seems to have forgotten to update the osmo-bsc.cfg file here, as osmo-bsc wouldn't even start using the file here. Change-Id: I8453da3bda36912ee42fb0c8d862f75b2065965f
2020-10-10 17:02:54 +00:00
logging color 1
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
logging print category 1
logging timestamp 1
logging print extended-timestamp 1
bts: Update osmo-bsc.cfg and osmo-bts.cfg Somebody seems to have forgotten to update the osmo-bsc.cfg file here, as osmo-bsc wouldn't even start using the file here. Change-Id: I8453da3bda36912ee42fb0c8d862f75b2065965f
2020-10-10 17:02:54 +00:00
logging level set-all notice
logging level rsl info
logging level oml info
logging level meas info
logging level pag info
logging level l1c info
logging level dsp info
logging level pcu debug
logging level trx info
logging level lmib debug
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
!
line vty
no login
bts: Run everything over 127.0.0.1 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
2020-10-20 16:02:49 +00:00
bind 127.0.0.1
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
!
e1_input
e1_line 0 driver ipa
e1_line 0 port 0
no e1_line 0 keepalive
phy 0
bts: Run everything over 127.0.0.1 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
2020-10-20 16:02:49 +00:00
osmotrx ip local 127.0.0.1
osmotrx ip remote 127.0.0.1
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
osmotrx fn-advance 20
osmotrx rts-advance 5
instance 0
osmotrx rx-gain 10
bts: Update osmo-bsc.cfg and osmo-bts.cfg Somebody seems to have forgotten to update the osmo-bsc.cfg file here, as osmo-bsc wouldn't even start using the file here. Change-Id: I8453da3bda36912ee42fb0c8d862f75b2065965f
2020-10-10 17:02:54 +00:00
instance 1
osmotrx rx-gain 10
instance 2
osmotrx rx-gain 10
instance 3
osmotrx rx-gain 10
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
bts 0
band DCS1800
ipa unit-id 1234 0
oml remote-ip 127.0.0.11
rtp jitter-buffer 100
paging queue-size 200
paging lifetime 0
uplink-power-target -75
gsmtap-sapi rach
gsmtap-sapi agch
gsmtap-sapi bcch
gsmtap-sapi pch
gsmtap-sapi sdcch
gsmtap-sapi sacch
bts/osmo-bts.cfg: Enable GSMTAP for FACCH on TCH/F and TCH/H Change-Id: I8aa118b733ea36e9ba591de7b935a31bdbe07129
2020-10-20 15:57:31 +00:00
gsmtap-sapi tch/f
gsmtap-sapi tch/h
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
min-qual-rach 50
min-qual-norm -5
!settsc
pcu-socket /tmp/pcu_sock
trx 0
power-ramp max-initial 0 mdBm
bts: Introduce test TC_tx_power_start_ramp_up_bcch This test verifies power ramping (up) is working fine during BTS startup. 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: Ieb7444c6312bbeab64da2732393b3facf3e1f003
2020-06-03 15:31:04 +00:00
power-ramp step-size 8000 mdB
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
power-ramp step-interval 1
phy 0 instance 0
bts: Update osmo-bsc.cfg and osmo-bts.cfg Somebody seems to have forgotten to update the osmo-bsc.cfg file here, as osmo-bsc wouldn't even start using the file here. Change-Id: I8453da3bda36912ee42fb0c8d862f75b2065965f
2020-10-10 17:02:54 +00:00
trx 1
power-ramp max-initial 0 mdBm
power-ramp step-size 8000 mdB
power-ramp step-interval 1
phy 0 instance 1
trx 2
power-ramp max-initial 0 mdBm
power-ramp step-size 8000 mdB
power-ramp step-interval 1
phy 0 instance 2
trx 3
power-ramp max-initial 0 mdBm
power-ramp step-size 8000 mdB
power-ramp step-interval 1
phy 0 instance 3
bts: add configs for running without docker Base on docker-playground.git's ttcn3-bts-test/*.cfg files, change IPs from 172.18.9.* to 127.0.0.* (last octet unchanged). Change-Id: I9eb2bb4599a4e874424f73483d9658a4467b8b8c
2019-08-28 09:29:44 +00:00
ctrl
bts: Run everything over 127.0.0.1 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
2020-10-20 16:02:49 +00:00
bind 127.0.0.1