diff options
| author | Pau Espin Pedrol <pespin@sysmocom.de> | 2018-11-19 17:48:17 +0100 |
|---|---|---|
| committer | Pau Espin Pedrol <pespin@sysmocom.de> | 2018-11-20 16:43:55 +0000 |
| commit | 167cb828665b91ed7d28007abd4a1862ebbb78c9 (patch) | |
| tree | 4cd0af7f41e44d2bea2eb6f04091bd22e73d04e9 /src/osmo-bsc/bts_sysmobts.c | |
| parent | 1dd2775d56b34260b6f7becff4f0c6d4450db2ff (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/bts_sysmobts.c')
| -rw-r--r-- | src/osmo-bsc/bts_sysmobts.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/osmo-bsc/bts_sysmobts.c b/src/osmo-bsc/bts_sysmobts.c index 91d1118c5..253786428 100644 --- a/src/osmo-bsc/bts_sysmobts.c +++ b/src/osmo-bsc/bts_sysmobts.c @@ -48,6 +48,9 @@ int bts_model_sysmobts_init(void) model_sysmobts.name = "sysmobts"; model_sysmobts.type = GSM_BTS_TYPE_OSMOBTS; + /* Unlike nanoBTS, sysmoBTS supports SI2bis and SI2ter fine */ + model_sysmobts.force_combined_si = false; + model_sysmobts.features.data = &model_sysmobts._features_data[0]; model_sysmobts.features.data_len = sizeof(model_sysmobts._features_data); |