Tests for M3UA SSNM behavior. This is just being introduced in
osmo-stp, so all tests will fail on 'latest', and some will still fail
until SSNM processing inside osmo-stp is becoming more complete.
Change-Id: I5074dccde9940956439235e8d02e6a722b8da5f5
Related: OS#2623
The tests were written without considering the arrival of such messages;
however, it is well within the M3UA spec that such messages appear at
any time indicating remote point code availability etc.
In libosmo-sccp.git Id92be4691b0fd77598a6edb642c028bbd8c5b623 we start
generating those messages in osmo-stp.
Let's ignore them in the tests to avoid unexpected failures.
Later on, we likely will introduce / adapt tests to actually expect
those messages whenever appropriate.
Change-Id: I85ce8fd4f26db184833cf348293f0255bb5eaac3
Related: OS#2623
Fixes warning:
Osmocom_Gb_Types.ttcn:1377.13-32: warning: Inadequate restriction on the
referenced function `f_oct_or_wc(bmax, 2)', this may cause a dynamic test
case error at runtime
Change-Id: Icb8698c7f2ca697a3638d5a4e4e38f20e14fd34c
Fixes:
warning: Inadequate restriction on the referenced template parameter
`tfi', this may cause a dynamic test case error at runtime
Same for other parameters.
Change-Id: If2cadbc7087ac0f99537b9916ef0c23363c9242c
Fixes:
warning: Inadequate restriction on the referenced template parameter
`chreq_desc', this may cause a dynamic test case error at runtime
Change-Id: I10b170c13aedc8abaaaf3b67d563ade8c3586c5b
Fixes warning: Keyword 'now' is treated as an identifier. Activate
compiler option '-I' to use real-time testing features
Change-Id: I2b350bc93b33f36f72d35cb48d01f6c37ac1630f
There was a missing comma in the configuration as well the
indention was misaligned.
Related: OS#4953
Fixes: be7afce974 ("NS_Emulation: Respect data_weight==0 or signalling_weight==0")
Change-Id: I7f146ff71c107983e5787982970d0f6cd313cde9
We initialize those verbose structures over and over in different tests,
and we usually don't care about detials, only whether they enable EGPRS
or not.
So let's define them once and reuse them in tests whenever possible.
Some tests requiring specific values (eg to test allocation of 8 PDCH on
a single TBF) are left intact.
Change-Id: Id047929ad71dc7e330b09fd6cbfab2da43320fde
This is only a step towards a major set of changes.
This specific commit changes internal implementation of functions to stay
compatible with existing tests.
Later on, changes will be modified to use the new altsteps directly.
Related: OS#4927
Change-Id: Iecc33565fdc673e3499db12a0d4e0587290cfd45
This way tests can match directly on specific RLCMAC blocks, giving the
opportunity to handle different types using altsteps.
Before this, a user of the port could only receive a pcu_msg DATA_REQ
with a octetstring containing the rlcmac block, then decode it in a
second step when already in the alt step.
Related: OS#4927
Change-Id: Id8628e327d16c3a57e680e5a1ba0a2a8874f3a23
Our definitions contain the minimum for 'CalledPartyBCD_Number',
optional extensions are not supported. Thus do not indicate their
presence, use '1'B (inverted logic) in both templates.
Change-Id: I448a1f7b71ed7d63d397da2b7d04942b501deaa5
Related: SYS#5340
It seems only docker config files were updated, while the local ones
have been forgotten in recent changes. We have to find a proper
solution for this :/
Change-Id: I26e900617bb87983912d8440376a7449f318e737
Sometimes we run into situations where the g_unblocked_nsvcs_* is
exceeding the number of NSVCs we have in g_nsvcs. This can only happen
as we blindly append integers to the ro_integer fields, rather than
checking if they are already contained.
Let's factor out the add_unique and del functions (in Osmocom_Types)
and use them from NS_Emulation.
Change-Id: Ib3273d6ce9b80f700c964d578fdb0f268eac6a14
We don't need several re-definitions of a "record of integer" type,
plus associated helper functions. Let's move that to the shared
Osmocom_Types.ttcn
Change-Id: I6a68ab8180a40b93c540db9cb80941c39c2fb549
There is quite a number of them, as we start 100 UE components
plus associated structure underneath. Let's avoid spamming the console.
Change-Id: I6621ac6094de310e974ce0438d01fca868719eb1
This allows us to test with a variety of packet sizes up to [close to]
the MTU of the underlying transport (configurable by modulepar)
Change-Id: I8e38ecf6b270c81bd73ee43b1fa0b259a999c14b
This test case tests NS-UL-UNITDATA transmit and expectes the exact same
LLC PDU to be sent back as NS-DL-UNITDATA.
This way we can verify that both uplink and downlink paths are working,
and that no messages are lost. It works stable here on my laptop,
showing that if we test the TTCN3 NS + BSSGP code over a E1 line
against another instance (fr against fr-net) works reliable.
Change-Id: Ic115af02207c9b9f4c84fa75890048acb6856c79
Rather than running in an endless loop (useful for manual tets),
terminate each UE_CT after sending 50 packets. Also adjust the ramping
and timeouts in a way that it manages to terminate ahead of the guard
timeout.
Change-Id: I7f40f5c59d399d528072986d067b5014fbd085c4
This happens e.g. if FrameRelay detects a "service affecting condition",
i.e. the link is considered dead.
Change-Id: I7409079f5e2b77cc08ccc93d1b0baa72720cefb8
... as this contains a fix to FrameRelay_Emulation to disable T392 if a
service affecting condition is detected.
Change-Id: I8b266577f738b7c12514eb8671e11d7a75be6034
Pau Espin Pedrol
Harald Welte
Pau Espin
Vadim Yanitskiy