mirror of
https://gitea.osmocom.org/cellular-infrastructure/osmo-bsc.git
synced 2025-11-02 21:23:19 +00:00
tests/ctrl/osmo-bsc-neigh-test.cfg: Fix duplicate <LAC,CI> between bts1 and bts2
According to TS23.003, CI should be unique in a LAC.
Previous commit wrongly introduced a while ago a new "bts 2" with same
LAC and CI as "bts 1" in config file.
This makes current tests fails once a hashtable is added to lookup bts
by lac, since the hashtable code does prepend new bts instead of
appending them. As a result, bts 2 is returned instead of bts 1 being
previously returned.
Also change the ARFCN+BSIC since it was also duplicated. It makes not much
sense to have 2 neighbor BTS with same ARFCN+BSIC.
Fixes: 97ed3c8d97
Change-Id: I7d1ebd529e050ecb4c14b9d3523637e4c8c87e1d
This commit is contained in:
@@ -137,9 +137,9 @@ network
|
||||
bts 2
|
||||
type osmo-bts
|
||||
band DCS1800
|
||||
cell_identity 123
|
||||
cell_identity 124
|
||||
location_area_code 0x0001
|
||||
base_station_id_code 55
|
||||
base_station_id_code 56
|
||||
ms max power 15
|
||||
cell reselection hysteresis 4
|
||||
rxlev access min 0
|
||||
@@ -158,7 +158,7 @@ network
|
||||
gprs routing area 6
|
||||
trx 0
|
||||
rf_locked 0
|
||||
arfcn 880
|
||||
arfcn 881
|
||||
nominal power 23
|
||||
! to use full TRX power, set max_power_red 0
|
||||
max_power_red 20
|
||||
|
||||
Reference in New Issue
Block a user