Actions
Bug #3004
closedUnreasonable default for RACH LOAD IND threshold
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
Updated by laforge about 6 years ago
- Related to Bug #3003: OsmoBTS fails to send RSL RACH LOAD INDICATIONS added
Updated by laforge about 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 60
Updated by laforge about 6 years ago
- % Done changed from 0 to 80
See https://gerrit.osmocom.org/6960 for a change to -90 dBm
Updated by laforge about 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
patch merged
Actions
