Project

General

Profile

Bug #2295

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

Added by laforge 8 months ago.

Status:
New
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.

Also available in: Atom PDF