Actions
Bug #3030
closedsysinfo.c:157 PH-RTS-IND: Unable to determine actual BS_AG_BLKS_RES value as SI3 is not available yet, fallback to 1
Start date:
03/02/2018
Due date:
% Done:
0%
Spec Reference:
Description
When starting OsmoBTS, I am getting the following
continuously repeating messages:
... sysinfo.c:157 PH-RTS-IND: Unable to determine actual BS_AG_BLKS_RES value as SI3 is not available yet, fallback to 1 sysinfo.c:157 PH-RTS-IND: Unable to determine actual BS_AG_BLKS_RES value as SI3 is not available yet, fallback to 1 sysinfo.c:157 PH-RTS-IND: Unable to determine actual BS_AG_BLKS_RES value as SI3 is not available yet, fallback to 1 ...
BTS isn't visible by MS.
Related issues
Updated by fixeria about 6 years ago
The problem appears after recent commits, and only with OsmoBSC, but not with OsmoNiTB.
Updated by fixeria about 6 years ago
- Is duplicate of Bug #2719: OsmoBSC doesn't send BCCH filling after RSL connection unless BTS sends unsolicited message added
Updated by laforge about 6 years ago
- Status changed from New to Feedback
- Assignee set to fixeria
You should get a few of those messages, but only until SI3 has been sent via RSL. Basically in the short timeframe between OML enabling the BCCH, but RSL link not yet established or BSC/NITB not yet having sent the BCCH INFO with SI3 content.
Updated by fixeria about 6 years ago
- Priority changed from Normal to Low
I don't experience this problem with recent versions anymore.
Updated by stsp about 6 years ago
- Status changed from Feedback to Resolved
Above fix has been merged.
Actions