Changes

stp: Define IUT default T(beat) in mp_t_beat_sec_default

Several tests expect to know this value from the IUT in order to test
related features. Since it will be used in more places in follow-up
patches, move it so the information only needs to be configured once.

Change-Id: Ic518e0d35f377fef85344177b630eb8599ec22d0

stp: Validate timer xua beat 0 disables BEAT procedure

Check in all sort of configurations that the BEAT procedure on xUA/IPA
can be disabled just fine per ASP using the VTY.

Related: SYS#8156
Change-Id: Id47bf862638a099bb5f6721fcfba873001aed616

eim/testenv: put mnesia database into volatile location

When running the TTCN3 testsuite in testenv, we create the database
files in a non-volatile location. This means that with every
consecutive test run, the database from the first test run is
re-used. This may lead to unexpected behaviour.

With this patch we change the location of the database to a volatile
location, so that each testrun uses a fresh database.

Related: SYS#8100
Change-Id: I178e4fcd29880668467b6deaa44f44d142b8c29c

stp: tcap: Avoid need of N_NOTICE.req

Commits
7970ceaead78ff224390a25f416b22bcd8e4e37e..32618160bdb154ca756c783b67b131533226f7ae
added a fork of titan.Protocol.Emulations.SCCP with a new N-NOTICE.req
primitive which was needed in STP_Tests_TCAP to trigger transmission of
a UDTS message.
That primitive doesn't exist in the specs, since no user of SCCP is
expected to be requesting a transmision of UDTS.
Hence, this commit rewrites the test to avoid the need for such a
primitive, by hooking directly into the lower layer MTP3 User SAP (M3UA
or IPA) and crafting and transmitting the SCCP UDTS over there directly.
Follow up commits will revert the commits adding such a N-NOTICE req to
the SCCP and TCAP layers.

Related: SYS#8090
Change-Id: Ia1b7f487124584ab1720cb89bca5999cbb12392d

Revert "stp: Add TCAP_N_NOTICE_req to send a UDTS with TCAP payload"

This reverts commit 11bf6593481d413f35c48db9b614e39fe4a05de1.

Change-Id: I4e96d9f0ceaafb2b5883b0e1f2d8d9f6065fd415

Revert "stp: add ASP_SCCP_N_NOTICE_req support and f_asp_tx_notice()"

This reverts commit 89637ff81dd0662c7d816b9dac5405fed2942e31.

Change-Id: Iecce8999b72b363a7aa3f583beeb937e79fe215f

Revert "deps: use a fork of titan.ProtocolEmulations.SCCP"

This reverts commit 7970ceaead78ff224390a25f416b22bcd8e4e37e.

Change-Id: I4eb81e0ffc6500340199c4a23a7aabfee925c33b

stp: expected-results.xml: Add two missing tests

Change-Id: I756ee108ad8a657679b2d098175e01b859af4bc8

eIM: Make tests work with testenv

The eIM can now be tested using testenv.py.

Related: SYS#8100
Change-Id: I38364e4bd5625b301c32fd58b50e35667c64b1be

hlr: pyhss: add ussd configuration

Configure the same strings for returning MSISDN and IMSI as in OsmoHLR,
because this is what the tests expect.

Related: https://github.com/nickvsnetworking/pyhss/pull/302
Change-Id: I7d2f62e6c034e3fd3c5dce048ccb297f4dea7825

deps: Update nas.git to rebased branch on top of v1.2.1

We have a forked repo of ETSI's nas.git on our osmocom gitea, which
contains an extra fix for upstream (currently waiting to be merged [1])
and one patch implementing C++ helpers to fit our own environment, which
needs to be kept downstream.

There has been quite a lot of development in upstream lately (TTF_T059),
with eg. old NGAP.git code being put inside nas.git (we are still using
our own copy of NGAP inside osmo-ttcn3-hacks/library/, but that may
change in the future).

A new branch rebased on top of upstream's master (v1.2.1) has been
pushed to our forked repo, so use it here to already align better with
upstream, easing further work and contributions in the future.

[1] https://forge.etsi.org/rep/int/5g-core/nas/-/merge_requests/18

Related: SYS#7073
Change-Id: I731c37324de93fe2bf35dac7e64304fc5057ee5f

ruff: ignore new failing default rules

With the new ruff 0.16 version, a lot of new default rules have been
added. Ignore the ones that are failing for now to make the linter pass
again.

Related: https://astral.sh/blog/ruff-v0.16.0#better-default-rule-set
Change-Id: If95dc72c1826b4b96961453b2c2ed1d2c81ba149

testenv: fix B006

Fix "B006 Do not use mutable data structures for argument defaults". I
ran into bugs caused by this a couple of times actually, it is good to
check for that.

Related: https://docs.astral.sh/ruff/rules/mutable-argument-default/
Change-Id: Id860c1cba20c0218aa1d1bb17378a0f5a521cfe0

testenv: Dockerfile: rebar3 version via apt-cache

When building for Debian Unstable, we need a higher rebar3 version so it
is compatible with the Erlang OTP version in the distribution. Get the
version of rebar3 from the distribution via apt-cache and download it
instead of hardcoding a version number.

Related: OS#7025#note-10
Change-Id: Ie3c8812c41648dd5ca655114dec00ae7d48eaba8

testenv: support Debian Unstable

Related: SYS#7025#note-10
Change-Id: Ib8f04ee1e8b33f6e724ea2a74b1a96f26746e878

testenv: init: check distro argument early

Check the --distro argument and print a proper error, instead of failing
later on with a stack trace if it is unsupported.

Change-Id: I9d51c2b236f10f4c10e991873df47b4f3297e6e1

CCID: Check if reader times out while expecting procedure byte

A case 2 APDU (according to ISO 7816) is sent toward the reader. The
reader expects a procedure byte or a status word. If none of these are
sent by the SIM the reader must timeout and send an error message back
to the host.

Change-Id: Iacd6aacaf8220e69b9b7038e354d54c788d1eb05

CCID: Check if reader handles Abort correctly

The tests aborts an ongoing case 2 APDU (according to ISO 7816). The
SIM responds with a NULL procedure byte so that the reader does not
time out.

The abort messages are sent on both, the control pipe and the bulk
pipe with the same sequence number.

This test fails with osmo-ccid-firmware, because the abort
message/handling is not yet implemented.

Change-Id: Iebe97e73497b8468ebf08faf2c4db700fc76997f

deps: use a fork of titan.ProtocolEmulations.SCCP

The fork adds support for sending UDTS via
ASP_SCCP_N_NOTICE_req.

Change-Id: I8c0de4dab088930d5d7a9febcbebcb5e1f9411e8

stp: add ASP_SCCP_N_NOTICE_req support and f_asp_tx_notice()

Wire ASP_SCCP_N_NOTICE_req as a simple passthrough in TCAP_CODEC_PT,
so test components can send UDTS via the existing SCCP_TCAP port.
Add f_asp_tx_notice() to STP_Tests_TCAP as a convenience wrapper.

Change-Id: I74c05405f1c99d43b4bf863f959275ee51301f2e

stp: Add TCAP_N_NOTICE_req to send a UDTS with TCAP payload

Change-Id: Ie13cecc2f2fc8a20d9646f0fb010b91c2ecf7766

stp: Test that UDTS containing tcap is routed correctly

Related: SYS#8090
Depends: libosmo-sigtran.git I2051aa9e84e553feb17daabb93ba3ce82358e0e4
Change-Id: I264ab424fbc3652249535bbe4f30029defa64c09

CCID: Check if reader times out after first status word

A case 1 APDU is sent towards the reader. The reader expects two status
words. If only the first word is sent by the SIM, the reader must
timeout and send an error message back to the host.

Change-Id: Ic5b892e356c13808555d75746c48c6d8c96ec462

CCID: Send a wrong procedure byte towards the reader

A case 2 request (according to ISO 7816) is sent and a response with
data is expected, but the first byte replied by the SIM is not a
procedure byte, nor a valid status byte.

This text expects the reader to return an error that states an incorrect
received procedure byte.

Change-Id: Iaa0bd8845b3408fba309874fe41c855d8e7efccc

eIM, IPAd: migrate from SGP.32 V.1.0.1 to SGP.32 V.1.2

SGP.32 V.1.2 is not backward compatible to SGP.32 V.1.0.1. This patch updates
the ASN.1 specification and the TTCN3 templates and types accordingly.

It also applies the bare minimum of changes required to compile the eIM and IPAd
testcases.

Related: SYS#8100
Related: SYS#8101
Change-Id: Id9e112669d9ed8caaec0893c55189eb566fe59be
Co-authored-by: Andreas Eversberg <aeversberg@sysmocom.de>

STP_Tests_TCAP: Fix ipa_to_ipa testcase

tcap routing doesn't work the way the test thinks. E.g. a Begin can't be
routed to a special destination because it does't contain a dtid which
is needed to route to the correct ASP.

Change-Id: Ie274232b706348b5ab6d0ac248883d86c53ebb4e

STP_Tests_TCAP: Test routing of fragments in TC_tcap_loadshare_ipa_tcap_range_success_pc

A TCAP Begin will cause the stp to create a cache entry and route
according to that. Send only a TCAP Continue so we check the tcap range
routing logic.

Change-Id: I1cb47174b8f0e69970e75109b9d15b2012e150c3

library: add f_gsm_fn_{sum,sub,diff}()

Change-Id: Ie91ccef5d3f170f4a341a6cf9d3323a896b299e6

bts: TC_pcu_interf_ind: check reporting interval instead of absolute FN

Recent osmo-bts commit 53f0ec29 broke TC_pcu_interf_ind:

  Verdict: fail reason: Odd TDMA frame number := 935

There's no requirement that periodic interference reports must land
on a TDMA frame number satisfying 'fn mod 104 == 0' - only that they
keep arriving every configured averaging period.  Instead, verify
that the interval between consecutive reports equals 104 TDMA frames
(1 SACCH period), using the new f_gsm_fn_sub() helper.

Change-Id: Ia96f2926400bae8c0a6fb8f81eb56b48ca5f2de9
Related: 53f0ec29 ("l1sap: fix duplicate RF RESOURCE INDICATION on clock bootstrap")