Feature #2469
Proper OML MO (managed object) using osmo_fsm
Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
08/29/2017
Due date:
% Done:
0%
Spec Reference:
Description
The BTS 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 over 1 year ago
- Related to Bug #3782: OML bringup fails for osmo-bts-oc2g on high latency links added
#2 Updated by laforge over 1 year ago
- Related to Bug #3789: BTS permits OPSTART of MO without attributes added
#3 Updated by laforge over 1 year ago
- Related to Bug #3788: OML Set {BTS,RADIO,CHANNEL} Attributes ACK doesn't echo attributes from Set BTS Attributes added
#4 Updated by laforge over 1 year ago
- Related to Bug #3785: OML State Change Event Report contains invalid administrative state added
#5 Updated by laforge over 1 year ago
- Related to Bug #3790: BTS indicates "Unlocked" state of Radio Carrier on connect added
#6 Updated by laforge over 1 year ago
- Related to Bug #3791: OsmoBTS doesn't include the "IPA Destination IP Address" attribute in "IPA RSL Connect ACK" added
#7 Updated by laforge over 1 year ago
- Related to Bug #3795: OsmoBTS doesn't ignore unsupported OML "placement" added
#8 Updated by laforge over 1 year ago
- Related to Bug #3796: OsmoBTS doesn't send proper cause values in NACK added
#9 Updated by laforge about 1 year ago
- Priority changed from Normal to Low
