Project

General

Profile

Bug #2357

Make SI2q compatible with dynamically updated SI via RSL

Added by msuraev 2 months ago. Updated 15 days ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
07/11/2017
Due date:
% Done:

10%

Resolution:
Spec Reference:

Description

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.

History

#1 Updated by msuraev 2 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

#2 Updated by msuraev 2 months ago

  • Assignee set to msuraev

Shall it be marked as CLX?

#3 Updated by msuraev 2 months ago

  • Status changed from In Progress to Stalled

#4 Updated by msuraev 26 days ago

  • 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.

#5 Updated by msuraev 22 days ago

  • Status changed from In Progress to Stalled

#6 Updated by msuraev 15 days ago

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.

Also available in: Atom PDF