Actions
Bug #3795
closedOsmoBTS doesn't ignore unsupported OML "placement"
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
Updated by laforge about 5 years ago
- Related to Feature #2469: Proper OML MO (managed object) using osmo_fsm added
Updated by laforge about 5 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
Updated by laforge about 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
patch merged
Actions
