path: root/src/osmo-bsc/system_information.c
diff options
authorPau Espin Pedrol <pespin@sysmocom.de>2018-11-19 17:48:17 +0100
committerPau Espin Pedrol <pespin@sysmocom.de>2018-11-20 16:43:55 +0000
commit167cb828665b91ed7d28007abd4a1862ebbb78c9 (patch)
tree4cd0af7f41e44d2bea2eb6f04091bd22e73d04e9 /src/osmo-bsc/system_information.c
parent1dd2775d56b34260b6f7becff4f0c6d4450db2ff (diff)
bsc: Enable force-combined-si on nanoBTS by default
Some nanoBTS firmwares (if not all) are known to not work properly with SI2ter. If BSC enables SI2ter through RSL, SI3 bit announcing SI2ter available will be forwarded by nanoBTS to MS, but will still only send SI2 message instead of expected SI2ter during TC=5 (see GSM 05.02 sec 6.3.4 "Mapping of BCCH data"). As a result, some MS won't allow registering to the network. To avoid this kind of scenario, enable force-combined-si by default on nanoBTS while still allowing to overwrite the feature through VTY. Other BTS models are kept with force-combined-si disabled by default as usually, since they seems to be working fine when SI2ter is enabled. Related: OS#3063 Change-Id: Ide6e8967de0eedc9e2bcaf4414aaa537b009d72d
Diffstat (limited to 'src/osmo-bsc/system_information.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/src/osmo-bsc/system_information.c b/src/osmo-bsc/system_information.c
index 0148ac389..0a441dc46 100644
--- a/src/osmo-bsc/system_information.c
+++ b/src/osmo-bsc/system_information.c
@@ -327,7 +327,7 @@ int bts_uarfcn_add(struct gsm_bts *bts, uint16_t arfcn, uint16_t scramble, bool
static inline int use_arfcn(const struct gsm_bts *bts, const bool bis, const bool ter,
const bool pgsm, const int arfcn)
- if (bts->force_combined_si)
+ if (bts->force_combined_si_set ? bts->force_combined_si : bts->model->force_combined_si)
return !bis && !ter;
if (!bis && !ter && band_compatible(bts, arfcn))
return 1;