Project

General

Profile

Actions

Feature #2469

closed

Proper OML MO (managed object) using osmo_fsm

Added by laforge over 6 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
08/29/2017
Due date:
% Done:

100%

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

Related to OsmoBTS - Bug #3782: OML bringup fails for osmo-bts-oc2g on high latency linksNew02/06/2019

Actions
Related to OsmoBTS - Bug #3789: BTS permits OPSTART of MO without attributesResolvedpespin02/07/2019

Actions
Related to OsmoBTS - Bug #3788: OML Set {BTS,RADIO,CHANNEL} Attributes ACK doesn't echo attributes from Set BTS AttributesResolvedlaforge02/07/2019

Actions
Related to OsmoBTS - Bug #3785: OML State Change Event Report contains invalid administrative stateResolvedlaforge02/07/2019

Actions
Related to OsmoBTS - Bug #3790: BTS indicates "Unlocked" state of Radio Carrier on connectResolvedlaforge02/07/2019

Actions
Related to OsmoBTS - Bug #3791: OsmoBTS doesn't include the "IPA Destination IP Address" attribute in "IPA RSL Connect ACK"Resolvedfixeria02/07/2019

Actions
Related to OsmoBTS - Bug #3795: OsmoBTS doesn't ignore unsupported OML "placement"Resolvedlaforge02/09/2019

Actions
Related to OsmoBTS - Bug #3796: OsmoBTS doesn't send proper cause values in NACKNew02/09/2019

Actions
Related to OsmoBSC - Bug #4755: Premature OML Radio Carrier(00,00,ff) OpstartResolvedpespin09/16/2020

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)