Project

General

Profile

Actions

Bug #5961

closed

BTS accepts OPSTART without prior SET ATTRIBUTES

Added by laforge about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Abis
Target version:
-
Start date:
03/26/2023
Due date:
% Done:

100%

Spec Reference:
Tags:

Description

For several different Abis MO, osmo-bts appears to accept OPSTART despite no attributes having been set before.

This makes our BTS_Tests_OML fail, likely ever since those tests were written:

  • BTS_Tests_OML.TC_bts_opstart_noattr
    • RADIO CARRIER: Test OPSTART without SET BTS ATTRIBUTES; expect NACK
    • error: Unexpected OPSTART ACK for NM_OC_BTS (1) { bts_nr := 0, trx_nr := 255, ts_nr := 255 }
  • BTS_Tests_OML.TC_radio_carrier_opstart_noattr
    • RADIO CARRIER: Test OPSTART without SET BTS ATTRIBUTES; expect NACK
    • error: Unexpected OPSTART ACK for NM_OC_RADIO_CARRIER (2) { bts_nr := 0, trx_nr := 0, ts_nr := 255 }
  • BTS_Tests_OML.TC_ts_opstart_noattr
    • BTS: Test OPSTART without SET BTS ATTRIBUTES; expect NACK
    • error: Unexpected OPSTART ACK for NM_OC_CHANNEL (3) { bts_nr := 0, trx_nr := 0, ts_nr := 1 }

Related issues

Related to OsmoBTS - Bug #5992: osmo-bts: Handle Opstart result from within nm_*_fsmResolvedpespin04/03/2023

Actions
Is duplicate of OsmoBTS - Bug #3789: BTS permits OPSTART of MO without attributesResolvedpespin02/07/2019

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)