Actions
Bug #1945
closedosmo-bts fails to send SI5ter even though it was received from the BSC
Start date:
02/08/2017
Due date:
% Done:
100%
Spec Reference:
Description
When setting an SI5ter in the BSC config, it gets transmitted to and stored in the BTS,
but is never passed on to the MS in the SACCH filling.
Updated by neels about 7 years ago
When configuring an SI5ter in the nitb config like this:
network bts 0 neighbor-list mode manual-si5 si5 neighbor-list add arfcn 0 si5 neighbor-list add arfcn 1 si5 neighbor-list add arfcn 2 si5 neighbor-list add arfcn 3 si5 neighbor-list add arfcn 4 si5 neighbor-list add arfcn 5 si5 neighbor-list add arfcn 580 si5 neighbor-list add arfcn 1023
the SI5ter is passed to the BTS:
nitb log:
20170207153242986 DRR <0003> ../../../src/libbsc/bsc_init.c:105 SI5: 49 06 1d 8f 22 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b 20170207153242986 DRR <0003> ../../../src/libbsc/bsc_init.c:105 SI5ter: 49 06 06 8f ff fe 00 00 00 00 00 00 00 00 00 00 00 00 00 2b 2b 2b 2b
bts log:
20170207143243080 DRSL <0000> ../../../src/common/rsl.c:470 Rx RSL SACCH FILLING (SI5ter)
but using GSMTAP shows that the SI5ter is never sent to the MS.
Updated by neels about 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 100
fixed by https://gerrit.osmocom.org/1778
(still waiting for merge)
Updated by neels about 7 years ago
- Status changed from In Progress to Resolved
Actions
