Project

General

Profile

Bug #3795

OsmoBTS doesn't ignore unsupported OML "placement"

Added by laforge 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Abis
Target version:
-
Start date:
02/09/2019
Due date:
% Done:

100%

Spec Reference:

Description

TS 12.21 describes segmenting of OML messages using placement fist/middle/last and the "sequence' number of the OML header. We don't implment this and hence must ignore or reject any related messages. However, we simply treat such segments as if they were a complete OML message.


Related issues

Related to OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmNew08/29/2017

History

#1 Updated by laforge 10 months ago

  • Related to Feature #2469: Proper OML MO (managed object) using osmo_fsm added

#2 Updated by laforge 10 months ago

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

#3 Updated by laforge 10 months ago

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

patch merged

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)