Feature #2470
Proper OML MO (managed object) using osmo_fsm
Start date:
08/29/2017
Due date:
% Done:
100%
Spec Reference:
Description
The BSC side of the TS 12.21 managed objects is a big hack. Having proper finite state machines as outlined in TS 12.21 for each MO would be a great win.
Related issues
History
#1 Updated by laforge almost 3 years ago
- Project changed from OpenBSC to OsmoBSC
- Category deleted (
libbsc)
#2 Updated by laforge almost 3 years ago
- Category set to A-bis OML
#3 Updated by laforge over 2 years ago
- Related to Bug #34: ipaccess init code needs proper state machines added
#4 Updated by laforge over 2 years ago
- Related to Bug #3000: OsmoBSC issues "RSL Connect" command too early -> race conditions added
#5 Updated by laforge over 1 year ago
- Related to Bug #3782: OML bringup fails for osmo-bts-oc2g on high latency links added
#6 Updated by pespin about 1 month ago
- Related to Bug #4755: Premature OML Radio Carrier(00,00,ff) Opstart added
#8 Updated by pespin 4 days ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Initial implementation for OML NM objects has been merged in osmo-bsc.git, see commits 12e15479d69b226ea1fb6a2f2a478b6df3dd6682..7c02e4cfd5d664ff8491f3f42107440642b80af5
I think this ticket can be closed and specific issues be handling in each of the related existing tickets.
