Project

General

Profile

Actions

Bug #5744

open

sysmobts: when a BTS is rf_locked and doesn't support BTS_FEAT_MULTI_TSC the OML connection is dropped

Added by lynxis over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
11/07/2022
Due date:
% Done:

0%

Spec Reference:

Description

I need to validate and reproduce this issue.

  • Use a osmo-bsc with a sysmobts 1020.
  • Configure the bts on the bsc as `rf_locked 1`
  • Configure a BSIC != 0
  • Start/Power up the BTS 1020.
  • The OML connection will be dropped by the BSC after the BTS answered invalid configuration.

The problem is the BSIC configuration. The sysmobts 1020 doesn't support BTS_FEAT_MULTI_TSC. The BSIC isn't set on the BTS MO (because of the rf_locked 1), but the TSC is set on the channel.

A fix would be always configuring the BSIC on BTS MO or delay the TRX channel configuration.

Actions #1

Updated by laforge over 1 year ago

Sorry, I think the subject of this issue is incomplete. "and only supports" what? :)

Actions #2

Updated by laforge over 1 year ago

the only constraint I'm aware is BSIC vs TSC. If they agree, it should be fine.

Actions #3

Updated by lynxis over 1 year ago

  • Subject changed from sysmobts: when a sysmobts is rf_locked and only supports to sysmobts: when a BTS is rf_locked and doesn't support BTS_FEAT_MULTI_TSC the OML connection is dropped
  • Description updated (diff)
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)