Project

General

Profile

Bug #3843

clean up sending of OML failure event reports

Added by dexter 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/15/2019
Due date:
% Done:

100%

Spec Reference:

Description

When osmo-bts sends a failure event report to the BSC either a signal to SS_FAIL is dispatched or the function oml_fail_rep() is called. There should be only one way to send failure event reports. Dispatching a signal seems to complicated for the task.

History

#1 Updated by dexter 2 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90

I have now removed all references to the old methods of triggering oml failure events. Now oml_tx_failure_event_rep() is the only valid way to send a failure event report.

https://gerrit.osmocom.org/#/c/osmo-bts/+/13264 oml: make oml_tx_failure_event_rep() public
https://gerrit.osmocom.org/#/c/osmo-bts/+/13268 oml: use oml_tx_failure_event_rep() instead of oml_fail_rep()
https://gerrit.osmocom.org/#/c/osmo-bts/+/13269 oml: use oml_tx_failure_event_rep() instead of signals to SS_FAIL

#2 Updated by dexter about 1 month ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)