aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2023-05-23WIP: ASCI related BTS testslaforge/asciHarald Welte2-0/+84
Change-Id: I3a93fa486a48957367d2c727cc0a8eea33d3bf11
2023-05-23WIP: bsc: ASCI Assignment test (VBS/VGCS)Harald Welte2-1/+150
Change-Id: I9b824a08d3948dc01e4748d4a4d61b889d31e5ff
2023-05-23BSSMAP_Templates: Add VBS/VGCS related templatesHarald Welte1-3/+709
As we want to test VBS/VGCS related aspects of BSC and/or MSC soon, we will need related templates to construct and match related messages and IEs. This requires titan.ProtocolModules.BSSMAP updated for modern-day VGCS/VBS related message definitions as I submitted in https://gitlab.eclipse.org/eclipse/titan/titan.ProtocolModules.BSSMAP_v11.2.0/-/merge_requests/3 Change-Id: I949f731de794b22292b01d0ddf9a75a9e7e7e71d
2023-05-23GSM_RR_Types: Add support for VBS/VGCS related L3 RR messagesHarald Welte1-4/+111
This adds support for the VBS/VGCS related L3 RR messages to GsmRrL3Union / GsmRrL3Message. Only those with proper L3 header and classic "tabular" syntax are supported so far, no CSN.1 messages with short L2 header for SACCH. Change-Id: I79ca7ee2b94bb370cd7162cfd9db436049998041
2023-05-05deps/Makefile: Change remote gerrit->gitea for titan.ProtocolModules.BSSMAPPau Espin Pedrol1-3/+3
It was decided that the preferred way to maintain our eclipse titan forked repos is through gitea, not through gerrit. Hence, update the remote to point to the gitea repo. The gerrit one will probably be removed at some point. Related: OS#6011 Change-Id: I69f8e207a28b8ea424d8fa4f23bdcaa3ba2e1345
2023-05-05PCUIF_Types: rename PCU_IF_SAPI_AGCH_DT to PCU_IF_SAPI_PCH_DTPhilipp Maier1-1/+1
The SAPI PCU_IF_SAPI_AGCH_DT has been renamed to PCU_IF_SAP_PCH_DT in the recent pcuif_proto.h version since the IMMEDIATE ASSIGNMENT what it is used for is sent on the PCH not on the AGCH. The SAPI constant is currently not used in the TTCN3 testsuite, but it will soon be used when we introduce support for the recent PCUIF which will then use the direct TLLI (DT) method. Related: OS#5927 Change-Id: Ifc09067bcb0f9f422ca429313fa09fea081dc316
2023-05-04Makefile: workaround Eclipse Gitlab rate limitingPau Espin Pedrol1-1/+3
Got this while pulling in the entire set of deps: """ remote: You have reached the limit of requests you can make to Eclipse GitLab. This could be caused by too many open tabs, which query the GitLab server in the background. Please close unused tabs, or put them to sleep so they don't issue requests needlessly. """ Change-Id: I5866154a6af88875a446e092f0926cdc4a1a9fc4
2023-05-04deps/Makefile: Update titan.ProtocolModules.BSSMAP to new rebased master ↵Pau Espin Pedrol1-1/+1
reference The master branch in osmocom's gerrit repository has been rebased on top of current upstream master, hence the commit hash changed. Update it. Related: OS#6011 Change-Id: Ife9dba3fc98d287d71b2334453dd9ce71471ddcb
2023-05-04MGCP_Test: move template RtpFlowData upPhilipp Maier1-23/+23
The template RtpFlowData is defined in the middle of the code, lets move it up below the related record definition Change-Id: If854f708e4da8b3a7b02d1ace2eb7caa3e2f2bfb
2023-05-04MGCP_Test: add fmtp to template t_RtpFlowPhilipp Maier1-13/+9
When creating a flow with fmtp parameters we must always add them in a second step. Lets update t_RtpFlow, so that it supports fmtp as an optional parameter. Change-Id: I04b17c0d233c1db4b9ba1306a4e0555914519bf8
2023-05-04MGCP_Test: support multiple codecsPhilipp Maier4-98/+191
At the moment The RTP emulation and MGCP_Test only allow to specify one codec and one set of RX/TX fixed payload octet strings to verify against. This is quite limiting since it might be necessary to test against different types and formats of payloads simultaneously in order to see if osmo-mgw converts or forwards them correctly. Let's extend this to support multiple codecs on MGCP/SDP level plus support for multiple RTP payloads on RTP emulation level. Related: OS#5461 Change-Id: I8422313fccad1bfcee52c933f643068bebdaf2d5
2023-05-03sccp: set titan.SCCP commit: use fix for localRef == 0Neels Hofmeyr1-1/+1
Use this fix in our tests: https://github.com/osmocom/titan.ProtocolEmulations.SCCP/commit/17a894fc6620a0df11d0d98c897fb66168276b16 This allows osmo-hnbgw to start out with SCCP local reference == 0 without that causing test failure. 'Related' patch below happens to have that effect, and it was *really* hard to find out why th the tests failed. It seemed like I had messed up osmo-hnbgw, but then I found out it wasn't my fault at all. Related: Iea1824f1c586723d989c80a909bae16bd2866e08 osmo-hnbgw Change-Id: Idb3f2398c934a1d785e8ee7913c12c0f289c1f18
2023-05-01hnbgw: add TC_sccp_cr_limit: test CR data length cutoffNeels Hofmeyr2-28/+133
Depends: If35697234796af8943691b2de62218e7dc93a08c libosmo-sccp Change-Id: Ia68dad973ef18513b52f5accb5264c557c7295ea
2023-04-30RSL_Types: Add (most) VGCS/VBS related IEs + MessagesHarald Welte2-2/+132
This will help us to start tests for VGCS/VBS. Change-Id: I4c4a9ac1bbd5114cb2237ea282d7bace13a52abe
2023-04-26MGCP_Test: fix typoPhilipp Maier1-1/+1
Change-Id: I1c860acb60267a9b4d8049bf231c49f9c915923b
2023-04-25hnbgw: wait longer for PFCP AssocNeels Hofmeyr1-3/+3
Since I introduced stricter timeouts on PFCP messages in hnbgw: add f_pfcp_expect() commit 6bbfe057afe6f23e2f325789a3dcac81065ab952 Change-Id I2117475b695d486b1204d61e5bb21120a6187354 the HNBGW tests with PFCP support fail often: The Assoc Setup resending timeout (X26) is configured to 5 seconds, and the timeout to wait for this is also 5 seconds. Every once in a while they happen to miss, causing a test failure. Increase the initial Assoc Setup Req timeout to 15 seconds to avoid sporadic failures. Change-Id: I4b9af224e2346a4735f3d4e01b234acf56c5f3ff
2023-04-24bsc: TC_assignment_csd: test non-transp data ratesOliver Smith1-3/+13
Related: OS#4393 Change-Id: I2dce9486f3528a79bdea09bdbc1f02833e6bedc0
2023-04-24bsc: TC_assignment_csd: test more transp data ratesOliver Smith1-4/+19
Related: OS#4393 Change-Id: I9a5f0e630fefcafb1b26eabba73de7e76d9e7e5d
2023-04-21bsc: AssignmentState: voice_call -> rtp_streamOliver Smith2-17/+17
Now that CSD is supported, rename the variable. It is true for both voice calls and for CSD. Related: OS#4393 Change-Id: Idfd9a102ad172d3aeaa4222a21357cdcd51680df
2023-04-20bsc: improve TC_assignment_csdOliver Smith4-1/+53
Verify that CSD ipaccess CRCX/MDCX has the CSD RTP payload type, and that the RSL_IE_IPAC_RTP_CSD_FMT IE is set with RSL_IPA_RTP_CSD_TRAU_BTS. Related: OS#4393 Change-Id: Id0e0c5631d7a36635e1ef49cf5bf554f0336556b
2023-04-20stp: Add tests for setups with multiple "routing context 0" ASPsHarald Welte2-1/+90
These two test cases verify that * libosmo-sigtran doesn't include a routing context IE even in ASP role when using a ASP with a single routing context 0 configured * osmo-stp can route between a single SG-role ASP with routing context to two ASP-role ASPs which both have routing context 0 (i.e. no routing context IE in use) The tests do not pass with current libosmo-sigtran until OS#6003 is fixed, presumably by Change-Id I5ce89b393a3b950ab7fd1eace9038718c9efcc51 Change-Id: I81052ece7d1cc8b43da6155356ed1c4d9620acdc Related: OS#6003
2023-04-20stp: Discard any ASP-UP retransmissionsHarald Welte1-0/+19
In some cases, there's some time between accepting the SCTP connection and the execution of f_M3UA_CLNT_asp_up(). This may cause the client sending re-transmitted ASP-UP messages. Let's simply flush and ignore those, rather than failing the test case. Change-Id: Iea39e9543535977a3004b150e222ce8c7f4d821a
2023-04-20{RAN,BSSAP_LE}_Adapter: Support M3UA without routing contextHarald Welte2-3/+16
The 3rd-party M3UA_Emulation supports operation both with and without a routing context. Let's make sure the layers we build on top don't lose that capability by forcing routing context usage. Change-Id: Iff849953d923770c93029a6a5c5b86daa8c38f1e
2023-04-18ggsn: Speed up tests by lowering retransmission T3,N3 timersPau Espin Pedrol2-0/+7
The params are set in GGSN_Tests.cfg and not in GGSN_Tests.default, because those lower values are not really good default ones as per spec. For instance when running against open5gs-smfd, these values should be left to the default in code of 5 and 3 seconds, because open5gs-smfd doesn't support changing the values through cfg file yet. Related: OS#5485 Change-Id: I3798fba89c2c357afeaa83a73759442c6c433cea
2023-04-15cosmetic: gbproxy: fix missing closing parenthesis in log lineHarald Welte1-1/+1
Change-Id: I4f2b5ef048ccd03d5ac2f448ef14691ece3200d2
2023-04-14L3_Templates, bsc: set ts_PAG_RESP() arg to template (value)Neels Hofmeyr2-13/+13
Change-Id: Ib77fc2377c1cf86abca9cf3082b74926d3c2c431
2023-04-14bsc: add TC_mscpool_sccp_n_pcstate_attaches_mscNeels Hofmeyr1-16/+74
Related: I3a0869598b8395601a16d78dbc46eec400c0ea84 (osmo-bsc) Change-Id: Ib4a5330df30a73e744c316898817b2fa3271d75e
2023-04-14bsc: add TC_mscpool_sccp_n_pcstate_detaches_mscNeels Hofmeyr1-0/+46
Related: SYS#6319 OS#5917 Related: I3a0869598b8395601a16d78dbc46eec400c0ea84 (osmo-bsc) Change-Id: Ia1aea4e33230d6a685b72ea5ba20dd9c7d265d44
2023-04-13pcu: Fix some tests missing proper tear downPau Espin Pedrol1-0/+28
As a result, they sometimes end up in error during test tear down, and they show up as failed. Change-Id: I89047a57a508df5c18e0d7bd2366cf15cda055be
2023-04-13ggsn: Add osmo-ggsn.cfgPau Espin Pedrol1-0/+80
Taken from docker-playground/ttcn3-ggsn-test/osmo-ggsn.cfg Change-Id: Ifbd50b6c1ebfd0371bd384c4ae0c4dc763478f49
2023-04-12bts/oml: Repurpose test TC_ipa_rsl_connect_nackPau Espin Pedrol2-8/+15
The old test was not really correct, since it is fine for the BTS to ACK the RSL CONNECT despite later on failing to connect the RSL link. RSL_CONNECT is really just setting the attributes (it could even be replaced by SETATTR in the future), and connect happens later on. This can still be found out by the BSC because the BBTRANSC will never transition to a Enabled state until the RSL link becomes up. This patch repurposes the existent test to do some more meaningful check in a case the RSL CONNECT can be answered with a NACK. This scenario was actually failing to be properly checked in osmo-bts until recently, so it is expected that it will fail (and even crash) older versions of osmo-bts. Depends: osmo-bts.git Change-Id If27639ae1727fc5232e1a964a1b29f50c8805d80 Related: OS#5964 Change-Id: I10df611f0086d34a5482f7c8a79703938313ab3d
2023-04-11bts/oml: Ignore SW Activated ReportsPau Espin Pedrol1-0/+1
Some components directly report being activated. Let's allow it. This fixes TC_initial_state_reports. Change-Id: I054dc74f60edee027923f03f8e73e56b1dc11a83
2023-04-11bts: Proper tear downPau Espin Pedrol1-1/+25
This way we stop vc_IPA_OML before stopping the main component. If we don't do this, the vc_IPA_OML is potentially receiving tons of OML messages during BTS bringup which it tries to forward to the main component. If the main component has stopped at that point, port IPA_OML_PORT is no longer active and hence vc_IPA_OML fails with a dynamic test error. Change-Id: I761ae94aa698a74bb30b8a6b1860358545f222b5
2023-04-03bts: oml: Start OML IPA_Emulation component as alive-typePau Espin Pedrol1-1/+1
This will hopefully help fix sporadic errors while tearing down the test after successful run: mtc BTS_Tests_OML.ttcn:625 Removing unterminated connection between port IPA_OSMO_PCU and TC_ts_opstart-OML-IPA(15):IPA_OSMO_PCU_PORT. IPA_Emulation.ttcnpp:774 setverdict(error): none -> error Related: OS#5965 Change-Id: I53c065016e88a5b253eff496560fa6e371fe491b
2023-04-03bsc: Add missing tests in expected-results.xmlPau Espin Pedrol1-0/+13
Change-Id: I09d503f6d61d4f4d09d83357dd1b79315803584c
2023-03-31bts: Add missing tests in expected-results.xmlPau Espin Pedrol1-0/+8
Change-Id: Ie751804c0557846224f6159fb1a02eb3444f84a4
2023-03-28hnbgw: add f_bssap_expect()Neels Hofmeyr1-41/+29
End the guessing when seeing "timeout of T_guard": set a precise failure verdict when an expected RANAP/SCCP ("BSSAP") message did not arrive as expected. Change-Id: I51c60ed8fcef83c98e6c62c9f62a8c3c665de860
2023-03-28hnbgw: add f_pfcp_expect()Neels Hofmeyr1-6/+26
End the guessing when seeing "timeout of T_guard": set a precise failure verdict when an expected PFCP message did not arrive as expected. Change-Id: I2117475b695d486b1204d61e5bb21120a6187354
2023-03-28hnbgw: add f_rua_expect()Neels Hofmeyr1-23/+21
End the guessing when seeing "timeout of T_guard": set a precise failure verdict when an expected RUA message did not arrive as expected. Change-Id: I29e6b7659ba53efee9f676197b502f79780ead7e
2023-03-27BTS_Tests.cfg: set mp_l1_supports_gprs to trueVadim Yanitskiy1-0/+1
This parameter enables running additional TC_pcu_* tests. Both trxcon and virtphy do support GPRS (l1gprs) now. Change-Id: I68351bf45fa3470a3a25eae2110056abae39af47
2023-03-27BTS_Tests: keep pchan configuration unchanged in TC_pcu_*Vadim Yanitskiy1-17/+7
Change [1] fixes support of dynamic timeslots in osmo-bts-virtual, so we don't need to change the pchan configuration anymore. Change-Id: I98397ac0fc17ece8f0e41b1ef1c158b47c9de026 Related: [1] osmo-bts.git I5db5b7dd6a8e84cf9a0d84f04a650c2ed8a4e368
2023-03-27BTS_Tests: do L1CTL.clear in f_pcu_to_l1()Vadim Yanitskiy1-0/+1
When calling f_pcu_to_l1(), the L1CTL port still contains many BCCH related L1CTL DATA.ind messages in the queue. It's not a really a problem since they all get discarded, but still they're producing lots of useless TTCN_MATCHING log messages. Change-Id: I57b745bcfc48dc621359658cd43d2ee622fde49b
2023-03-27bts: fix TC_ipa_osmo_pcu_anr_fwd: send/expect proper payloadsVadim Yanitskiy1-8/+51
The testcase expectations are wrong, because when matching the PCU_IF_MSG_NEIGH_ADDR_REQ on the PCU port, TITAN's RAW codec reasonably chooses the 'neigh_addr_req' field in the PCUIF_ContainerMsgUnion, not the 'other' field as expected. The 'other' field would be choosen if the 'msg_type' is not PCU_IF_MSG_NEIGH_ADDR_{REQ,CNF}. A quick and dirty fix would be changing the PCU_IF_MSG_NEIGH_ADDR_REQ to something else, e.g. PCU_IF_MSG_CONTAINER. This would make both encoder and decoder agree on the union field to be used and would work in theory (because for some reason we reuse PCUIF_MsgType as the container payload type, and osmo-bts does not really care about the payload), but I don't really like this approach. I believe we should be sending realistic payloads instead. Change-Id: Id4a6ecf5b271a16645a42c8bea22f47869f7c81f Closes: OS#5963
2023-03-22SI: add missing Message TypeMax1-0/+17
Add Message types for Radio Resource management messages using the RR short protocol discriminator from Table 10.4.2 3GPP TS 44.018 Related: OS#5783 Change-Id: Id3b59638a3cf75c7105b1992094a4cc20855161d
2023-03-19library: L1CTL: rework GPRS related message definitionsVadim Yanitskiy4-250/+254
The old GPRS related messages are no longer valid. Use the new message definitions supported by both trxcon and virtphy since recently. Comment out lines referencing the old definitions in LAPDm_RAW_PT.ttcn. This module contains an implementation of the RLC/MAC abstraction layer, which is currently not used anywhere. Change-Id: Ib8f4459480bbe12584a6fa71882f745f03c5055d Related: osmocom-bb.git I9567d64f9d00262e36147e8d7e541e5e246bda5f Related: OS#5500
2023-03-19library: L1CTL: merge L1ctl{Ul,Dl}Message into L1ctlMessageVadim Yanitskiy5-162/+179
Currently we have two variants of the L1CTL PDU: * L1ctlUlMessage: L23 -> L1 requests (*_REQ), * L1ctlDlMessage: L1 -> L23 responses (*_IND, *_CONF). The L1CTL_PT port is defined in a way that one can: * Tx L1ctl{Ul,Dl}Message PDUs, * Rx L1ctlDlMessage PDUs. This means that the testsuite can act as the L23 talking to the L1 (e.g. trxcon or virtphy), but not vice-versa. Adding an additional Rx `UD_send_data -> L1ctlUlMessage` mapping is not an option, because such a mapping would be ambiguous and would cause errors. By merging the two L1CTL PDU variants into the one, we can achieve the testsuite acting as the L1. This will be useful for testing the L23 applications in osmocom-bb.git, like the modem app. Take a chance to reorder fields to match the order in L1ctlMsgType. Change-Id: I1313068c5f02b65d3dbb05a1341a9d7286225f0c Related: OS#5500
2023-03-16Limit maximum number of open file descriptors to overcome titan bugPau Espin Pedrol1-0/+4
Without this, titan tries to allocate too much memory and triggers OOM under some systems (happening here with 16GB of RAM). Related: https://gitlab.eclipse.org/eclipse/titan/titan.core/-/issues/690 Change-Id: Iafa8cfa769386e63e1d879d8cce6e24b244d9a6f
2023-03-14osmo-hnbgw-with-pfcp.cfg: improve loggingNeels Hofmeyr1-2/+11
Change-Id: Iaf4e8993f9d3b41f74145291940ca59947f9d171
2023-03-14msc: detect RTP to CN failure in call testsNeels Hofmeyr2-4/+33
When CN RTP is missing, the X2 timer will fire after all other call signalling looks successful. So far we establish an MT call, wait three seconds and directly disconnect, long before X2 or X2427 can fire. Make X2 shorter. (By means of f_vty_config() from ttcn, so that we don't need to edit various osmo-msc.cfg in various repositories. The short timer is always critical for the test to be accurate.) Add proper function to detect premature disconnect. Otherwise we just get a cryptic message like "Couldn't find MnccExpect for incoming call" because of MNCC messaging after the unexpected release event. Change-Id: I3ccf541360cc8440e664f0e29494b9ce7b6f8943
2023-03-14msc: TC_mt_t310: avoid sporadic failure from X2 timeoutNeels Hofmeyr1-0/+4
Change-Id: Ic23cbca5775031dcb0ea1744454e20cda090701c
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-24 18:07:17 +0000