Project

General

Profile

Actions

Bug #3004

closed

Unreasonable default for RACH LOAD IND threshold

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

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

100%

Spec Reference:

Description

The RACH LOAD repoting as per TS 48.058 Section 9.3.18 has a configurable "RACH Busy Threshold" parameter configured according to 52.012 Section 9.4.44

OsmoBTS and other BTSs implement this, but OsmoBSC currently has a compiled-in default of "10" which means -10dBm. Any RACH requests below this level (which is virtuall all, as -10dBm is a way too strong receive level) will not count as busy.

Let's make sure we have a reasonable default level, probably somewhere between -90 and -100 dBm on what counts as "busy" in those reports.


Related issues

Related to OsmoBTS - Bug #3003: OsmoBTS fails to send RSL RACH LOAD INDICATIONSResolvedlaforge02/26/2018

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)