https://osmocom.org/https://osmocom.org/favicon.ico?16647414092019-02-06T11:59:50ZOpen Source Mobile CommunicationsOsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=132452019-02-06T11:59:50Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-1 priority-lowest" href="/issues/3782">Bug #3782</a>: OML bringup fails for osmo-bts-oc2g on high latency links</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=132732019-02-07T19:19:14Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3789">Bug #3789</a>: BTS permits OPSTART of MO without attributes</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=132752019-02-07T19:19:28Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed" href="/issues/3788">Bug #3788</a>: OML Set {BTS,RADIO,CHANNEL} Attributes ACK doesn't echo attributes from Set BTS Attributes</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=132772019-02-07T19:19:33Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed" href="/issues/3785">Bug #3785</a>: OML State Change Event Report contains invalid administrative state</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=132792019-02-07T19:44:17Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3790">Bug #3790</a>: BTS indicates "Unlocked" state of Radio Carrier on connect</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=132812019-02-07T19:47:09Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed" href="/issues/3791">Bug #3791</a>: OsmoBTS doesn't include the "IPA Destination IP Address" attribute in "IPA RSL Connect ACK"</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=132962019-02-09T07:45:42Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3795">Bug #3795</a>: OsmoBTS doesn't ignore unsupported OML "placement"</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=132982019-02-09T07:48:46Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-1 priority-lowest" href="/issues/3796">Bug #3796</a>: OsmoBTS doesn't send proper cause values in NACK</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=153092019-07-18T06:08:36Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=196692020-09-18T09:12:45Zpespin
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/4755">Bug #4755</a>: Premature OML Radio Carrier(00,00,ff) Opstart</i> added</li></ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=197442020-09-30T12:04:30Zlaforge
<ul><li><strong>Assignee</strong> set to <i>pespin</i></li></ul><p>assigning to pespin as he's working on related patches at the moment. Doesn't mean I expect him to complete this entire task, particularly not at the moment.</p> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=197452020-09-30T12:05:17Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul><ul>
<li><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/20284">https://gerrit.osmocom.org/c/osmo-bts/+/20284</a></li>
<li><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/20311">https://gerrit.osmocom.org/c/osmo-bts/+/20311</a></li>
</ul> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=199612020-10-16T13:57:09Zpespin
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>High</i></li><li><strong>% Done</strong> changed from <i>10</i> to <i>90</i></li></ul><p>Initial set of patches adding initial OMl FSMs in osmo-bts can be found here:<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/20407">https://gerrit.osmocom.org/c/osmo-bts/+/20407</a> Change NM Channel availability Dependency->Offline when RadioCarrier becomes ...<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/20408">https://gerrit.osmocom.org/c/osmo-bts/+/20408</a> Introduce NM BTS Site Manager FSM<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/20409">https://gerrit.osmocom.org/c/osmo-bts/+/20409</a> Introduce NM BTS FSM<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/20284">https://gerrit.osmocom.org/c/osmo-bts/+/20284</a> Introduce NM Radio Carrier and Baseband Transceiver FSMs<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/20311">https://gerrit.osmocom.org/c/osmo-bts/+/20311</a> Introduce NM Channel FSM</p>
<p>PS: I changed the priority of the ticket since current status (before FSM) actually affects sysmobts not working properly after some osmo-bsc OML fixes (for in turn osmo-bts-trx OML issues) a few days ago.</p>
<p>Once those patches above are merged, we can close the ticket and keep going with the multiple smaller tickets pointing at specific issues.</p> OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmhttps://osmocom.org/issues/2469?journal_id=200622020-10-21T14:13:13Zpespin
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p>Patches merged.<br />I just submitted a small fix making TS not enabled under some situations (RSL link up quite late):<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/20824">https://gerrit.osmocom.org/c/osmo-bts/+/20824</a> bts_trx.c: Dispatch missing NM_EV_RSL_UP/DOWN to the bb_transc object</p>