Project

General

Profile

Bug #2295

OML: Send proper NACK and ALARM messages in case of OML errors

Added by laforge over 1 year ago. Updated 6 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
05/27/2017
Due date:
% Done:

0%

Spec Reference:

Description

There are cases in which we print a local error message but don't send an OML FOM NACK to the BSC, like when receiving an ARFCN list for frequency hopping in oml_rx_set_radio_attr(). Code needs to be audted fo those and proper error messages sent back to BSC, possibly even together with OML ALERT.

History

#1 Updated by laforge 7 months ago

  • Assignee set to stsp

#2 Updated by stsp 6 months ago

  • Status changed from New to In Progress

#3 Updated by stsp 6 months ago

I cannot find any additional cases in common/oml.c where we're missing an ACK or NACK.

Is there other relevant code I should look at?
If there is not, then in my opinion this ticket can be closed once above patches are merged.

#4 Updated by stsp 6 months ago

  • Status changed from In Progress to Resolved

Closing this. Please re-open or create a new issue if similar problems are found elsewhere in the code.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)