Actions
Bug #3143
closedosmo-bts doesn't print helpful error message on unit_id mismatch
Start date:
04/05/2018
Due date:
% Done:
0%
Spec Reference:
Description
a frequent error is that the unit_id settings on osmo-bts and osmo-bsc don't mathc. The BSC prints an error in this case, but the BTS doesn't.
It should be possible to use the "OML uptime" as an indication, though: If OsmoBTS receives an OML disconnect within a few (let's say < 10) seconds of OML uptime, print a message: "BSC closed OML connection, probably our unit_id is unknown to it" or something useful like that.
Updated by stsp almost 6 years ago
- Status changed from New to In Progress
Proposed implementation of above suggestion: https://gerrit.osmocom.org/#/c/8056/
Updated by stsp almost 6 years ago
- Status changed from In Progress to Resolved
Above change has been merged.
Actions
