Make SI2q compatible with dynamically updated SI via RSL
After SI2q configuration is changed via vty, the SI messages can be regenerated using
bts 0 resend-system-information command. That should lead to proper update of SI2q index and count (if number of messages has changed) and should be propagated to RSL accordingly.
Right now only last message (7/7 for example) got properly updated count, others still use old value.
Note: this is for BSC-side fix, the BTS side should be fixed by gerrit 3180.
- Status changed from Stalled to In Progress
Note to self: look at https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-nitb-sysinfo/8/testReport/(root)/Test/ and figure out why si2quater test is not failing.
Currently TTCN tests do not perform any checks after issuing
bts 0 resend-system-information command. Also, there's no decoding of rest octets ATM. It should be possible to detect failure by comparing rest octets as hex strings for example but it would require much deeper understanding of TTCN than I have right now.
#7 Updated by msuraev about 2 months ago
- % Done changed from 10 to 20
Gerrit 4110 & 4160 were sent for review.
Note: those are for OsmoBSC - not sure if this should be backported to OpenBSC too.
The 4160 were tested with 16 UARFCN-SC combinations which correctly result in 2 SI2q. Those SI2q were properly sent to BTS which properly rotated between them when scheduling SI transmissions. However, upon reception of 2nd SI2q, the 1st one was overwritten as well which means only last SI2q is always scheduled. The investigation is still on-going.
Once it's fixed, we can proceed with resend-system-information tests.