Skip to content
Unstable

Changes

Summary

  1. hnbgw: TC_rab_release: Fix race condition stats checked too early (details)
  2. bsc: Fix missing teardown in TC_ho_in_fail_msc_clears_after_ho_detect (details)
  3. msc: fix a race condition in f_mt_call_establish() (details)
Commit 8b7572b990f6d28de55ab15ac9650443cb27b8d5 by laforge
hnbgw: TC_rab_release: Fix race condition stats checked too early

It could happen sometimes that the stats report was requested before the
hnbgw received the message increasing the counter.

Change-Id: Ica53d956ee8aed760854d3148af170144234e6b2
The file was modifiedhnbgw/HNBGW_Tests.ttcn
Commit 2e9216b3e85d494c973deec3a6cd33477ded0a5f by laforge
bsc: Fix missing teardown in TC_ho_in_fail_msc_clears_after_ho_detect

Missing handling of teardown messages made the test fail sporadically
due to ttcn3 side already closing the SCCP connection when it was still
expected to receive messages.

Change-Id: I492607aca0e42a823836f4a714ea818c5a897855
The file was modifiedbsc/BSC_Tests.ttcn
Commit 3aa177267d775b37fae0bff68ced6d52d9f42f30 by laforge
msc: fix a race condition in f_mt_call_establish()

It can happen that the MSC sends a paging request quicker than
function f_ran_register_imsi() returns (e.g. when a node executing
the testsuite is under significant load).  In this case the
BSSMAP PAGING message is dropped by the RAN_Emulation CT:

  CommonBssmapUnitdataCallback: IMSI/TMSI not found in table

This can be avoided by calling f_ran_register_imsi() *before*
sending the MNCC SETUP.req, which is triggering paging.

This patch fixes sporadic failures of:

* TC_lu_and_mt_call
* TC_lu_and_mt_call_ipv6
* TC_lu_and_mt_call_no_dlcx_resp

Change-Id: Ie8b69c3b59ea61e01adb24c71c1376335a5ddde6
The file was modifiedmsc/BSC_ConnectionHandler.ttcn