Actions
Bug #2300
closedproblems processing measurement reports
Start date:
05/28/2017
Due date:
% Done:
100%
Spec Reference:
Description
scenario:
- Using current 201310-nightly builds on a sysmobts-v2 (1002) hardware
- OsmoBTS 0.4.0.446-e0fb is the osmo-bts version according to 'show version'
- NITB (non onboard) configured to use tch-h only traffic channels
- MO-to-MT call between two phones
- no measurement reports seen on Abis towards BSC!
- osmo-bts floods following messages to the console:
<0004> measurement.c:155 (bts=0,trx=0,ts=1,ss=0) no space for uplink measurement <0004> measurement.c:155 (bts=0,trx=0,ts=1,ss=1) no space for uplink measurement <0004> measurement.c:155 (bts=0,trx=0,ts=1,ss=0) no space for uplink measurement <0004> measurement.c:155 (bts=0,trx=0,ts=1,ss=1) no space for uplink measurement <0004> measurement.c:155 (bts=0,trx=0,ts=1,ss=0) no space for uplink measurement <0004> measurement.c:155 (bts=0,trx=0,ts=1,ss=1) no space for uplink measurement
I suspect that something was broken with the recent patches changing the exact time when the measurements would be processed. The "no space" strongly indicates that the computation/processing never happens, and thus there's no more space for raw uplink rxlev/rxqual samples.
Actions