From 558183f3dc7d4f17b937f978db1b1cab8da040da Mon Sep 17 00:00:00 2001 From: Pau Espin Pedrol Date: Fri, 2 Oct 2020 16:20:00 +0200 Subject: OML: Stay compatible with older osmo-bts versions Older osmo-bts versions (before FSMs) tended to mimic broken behavior from nanoBTS. As so, we detect it because SiteMGr becomes Enabled by default as in nanoBTS, and hence we can manage them also by expecting no Offline state and sending Opstart (and hence finally transitting to Enabled) during Dependency state. Change-Id: Iaa036a2936f609b9b9721b2b4ad8d6deaf023f42 --- include/osmocom/bsc/bts.h | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'include') diff --git a/include/osmocom/bsc/bts.h b/include/osmocom/bsc/bts.h index a9d57a380..284a932cb 100644 --- a/include/osmocom/bsc/bts.h +++ b/include/osmocom/bsc/bts.h @@ -364,6 +364,12 @@ struct gsm_bts_model { /* BTS Site Manager */ struct gsm_bts_sm { struct gsm_abis_mo mo; + /* nanoBTS and old versions of osmo-bts behaves this way due to + broken FSMs not following TS 12.21: they never do + Dependency->Offline transition, but they should be OPSTARTed + nevertheless during Dependnecy state to work. This field is + used by all dependent NM objects. */ + bool peer_has_no_avstate_offline; }; /* One BTS */ -- cgit v1.2.3