tree 08c41820bd9a8a4eb6f4ec0e5ffd979f27518f39
parent dd0027540cc2ce252b74cd5ed7e0d1f31bbfa588
author Neels Hofmeyr <nhofmeyr@sysmocom.de> 1676899591 +0100
committer laforge <laforge@osmocom.org> 1678039606 +0000

hnbgw: f_iuh2iu_disconnect: allow more time

Increase timeout for expecting an SCCP RLSD from osmo-hnbgw.

Affects tests
HNBGW_Tests.TC_ranap_cs_mo_disconnect
HNBGW_Tests.TC_ranap_ps_mo_disconnect

Rationale:

For the case

 RUA --id-Disconnect--> HNBGW  ----release-SCCP---- CN

the tests expect behavior not exactly specified.
3GPP TS 48.006 9.2 Connection release:

 The MSC sends a SCCP released message. This message shall not contain
 any user data field.

So what we should expect is this:

                           HNBGW                    MSC
 RUA --id-Disconnect-------> | ---Data-Form-1(!)---> |  Iu-ReleaseComplete
                             | <--Released---------- |  (no data)

Instead, we expect the HNBGW to immediately send a RLSD to the MSC:

                           HNBGW                    MSC
 RUA --id-Disconnect-------> | ---Released---------> |  Iu-ReleaseComplete

osmo-hnbgw is being fixed in that respect: it will soon give time for
the CN to send an SCCP RLSD, and only if that times out will osmo-hnbgw
send an SCCP RLSD to the CN.

So HNBGW_Tests.ttcn should still ensure that osmo-hnbgw will eventually
send an SCCP RLSD if the CN fails to do so, but it should allow more
time to accomodate the release timeout.

Related: osmo-hnbgw I6ff7e36532ff57c6f2d3e7e419dd22ef27dafd19
Related: SYS#6297
Change-Id: Ibf6eaeb1b82d43e4f208f64a71f2f6e889883a11