Project

General

Profile

Actions

Bug #3003

closed

OsmoBTS fails to send RSL RACH LOAD INDICATIONS

Added by laforge about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
osmo-bts-trx
Target version:
-
Start date:
02/26/2018
Due date:
% Done:

100%

Spec Reference:

Description

Even when putting the BTS under 100% RACH load (>= 90 RACH/s on a Combined CCCH), I still don't see "RSL CCCH LOAD INDICATION (RACH)" on the RSL side. All CCCH LOAD IND observed in wireshark are for PCH.


Related issues

Related to OsmoBSC - Bug #3004: Unreasonable default for RACH LOAD IND thresholdResolvedlaforge02/26/2018

Actions
Actions #1

Updated by laforge about 6 years ago

  • Category changed from Abis to osmo-bts-trx
  • Status changed from New to In Progress
  • % Done changed from 0 to 20

it seems like this is an osmo-bts-trx specific issue, as the current API is structured in a way that the number of rach_busy slots must be incremeneted below the L1SAP, whereas the processing/reporting happens above.

I'm currently re-working the code to move rach busy slot counting to above L1SAP, avoiding any related bts-specific issues.

Actions #2

Updated by laforge about 6 years ago

  • Related to Bug #3004: Unreasonable default for RACH LOAD IND threshold added
Actions #4

Updated by laforge about 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 60 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)