Actions
Bug #5538
closedOsmoBSC assumes more features from OsmoBTS than it announces
Start date:
04/21/2022
Due date:
% Done:
100%
Spec Reference:
Description
OsmoBSC prints log entries like:
Get Attributes Response: reported feature 'PAGING_COORDINATION' is not supported, while we thought it is.
This is due to features being assumed to be supported by OsmoBSC in bts_model_osmobts_init(), but not being announced by OsmoBTS. At time of writing, these are assumed:
osmo_bts_set_feature(&model_osmobts.features, BTS_FEAT_GPRS); osmo_bts_set_feature(&model_osmobts.features, BTS_FEAT_EGPRS); osmo_bts_set_feature(&model_osmobts.features, BTS_FEAT_PAGING_COORDINATION); osmo_bts_set_feature(&model_osmobts.features, BTS_FEAT_IPV6_NSVC); osmo_bts_set_feature(&model_osmobts.features, BTS_FEAT_CCN);
OsmoBTS has multiple bts_model_init() functions, where it seems we should mark the same features as supported as expected by OsmoBSC after carefully verifying that everything still works as expected.
OsmoBSC sometimes checks for the features of the model (osmo_bts_has_feature(bts->model->features, ...)), sometimes for the features actually reported by the BTS (osmo_bts_has_feature(bts->features, ...)).
Actions