Project

General

Profile

Actions

Bug #5243

closed

Both BTS_Tests.TC_meas_res_sign_sdcch4 and BTS_Tests.TC_meas_res_sign_sdcch8 started to fail

Added by fixeria over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Abis
Target version:
-
Start date:
09/30/2021
Due date:
% Done:

100%

Spec Reference:

Description

TITAN shows this verdict:

Stacktrace

"BTS_Tests.ttcn:2153 : Received unexpected MEAS RES { msg_disc := { msg_group := RSL_MDISC_DCHAN (4), transparent := false }, msg_type := RSL_MT_MEAS_RES (40), ies := { { iei := RSL_IE_CHAN_NR (1), body := { chan_nr := { u := { sdcch4 := { tag := '001'B, sub_chan := 0 } }, tn := 0 } } }, { iei := RSL_IE_MEAS_RES_NR (27), body := { meas_res_nr := 1 } }, { iei := RSL_IE_UPLINK_MEAS (25), body := { uplink_meas := { len := 3, rfu := '0'B, dtx_d := false, rxlev_f_u := 5, reserved1 := '00'B, rxlev_s_u := 5, reserved2 := '00'B, rxq_f_u := 7, rxq_s_u := 7, supp_meas_info := omit } } }, { iei := RSL_IE_BS_POWER (4), body := { bs_power := { reserved := 0, epc := false, fpc := false, power_level := 0 } } }, { iei := RSL_IE_L1_INFO (10), body := { l1_info := { ms_power_lvl := 7, fpc := false, reserved := 0, actual_ta := 0 } } }, { iei := RSL_IE_L3_INFO (11), body := { l3_info := { len := 6, payload := '06150A0A0000'O } } }, { iei := RSL_IE_MS_TIMING_OFFSET (37), body := { ms_timing_offset := 65 } } } }" 
      BTS_Tests.ttcn:7821 BTS_Tests control part
      BTS_Tests.ttcn:3278 TC_meas_res_sign_sdcch4 testcase

which is not really informative.

I manually compared PCAP files of a successful and failed runs, and found out that for some reason the first RSL Measurement Report comes with Measurement result number IE equal 1. The test suite expects it to be 0, and thus fails. We need to investigate why osmo-bts counts from 1.

Actions #1

Updated by fixeria over 2 years ago

  • Assignee changed from fixeria to pespin
  • % Done changed from 0 to 80

This is caused by one of the recently merged changes:

commit 3871c1ff0ca3b125ce0436b42d6a6e20c1cd10c6
Author: Pau Espin Pedrol <pespin@sysmocom.de>
Date:   Mon Sep 27 17:55:31 2021 +0200

    Decouple handling of Measurement Report from lapdm

Here is a patch that should theoretically fix the problem (not tested):

https://gerrit.osmocom.org/c/osmo-bts/+/25651 fix handle_ms_meas_report(): properly count measurement reports [NEW]

pespin can you please give it a try? Thanks!

Actions #2

Updated by pespin over 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 80 to 100

Fixes the problem. I just merged it, thanks.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)