path: root/include
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 /include
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 'include')
1 files changed, 4 insertions, 0 deletions
diff --git a/include/osmocom/bsc/gsm_data.h b/include/osmocom/bsc/gsm_data.h
index 4d8a4d090..ba52c99b5 100644
--- a/include/osmocom/bsc/gsm_data.h
+++ b/include/osmocom/bsc/gsm_data.h
@@ -756,6 +756,9 @@ struct gsm_bts_model {
void (*config_write_trx)(struct vty *vty, struct gsm_bts_trx *trx);
void (*config_write_ts)(struct vty *vty, struct gsm_bts_trx_ts *ts);
+ /* Should SI2bis and SI2ter be disabled by default on this BTS model? */
+ bool force_combined_si;
struct tlv_definition nm_att_tlvdef;
/* features of a given BTS model set via gsm_bts_model_register() locally */
@@ -1046,6 +1049,7 @@ struct gsm_bts {
/* SI related items */
int force_combined_si;
+ bool force_combined_si_set;
int bcch_change_mark;
/* Abis NM queue */