path: root/msc
AgeCommit message (Collapse)AuthorFilesLines
33 hoursMSC_Tests.ttcn: introduce TC_proc_ss_abortVadim Yanitskiy1-0/+86
This test case is aimed to verify HLR-/EUSE-initiated abort of an active SS/USSD session according to the following scenario: 1. (HLR/EUSE -> MSC) GSUP_PROC_SS_REQ with random facility; 2. Network-originated connection establishment: 2.a. (MSC -> BSC -> MS) Paging Request; 2.b. ... 2.c. (MS -> BSC -> MSC) Paging Response; 3. (MSC -> MS) GSM 04.80 REGISTER with random facility; 4. (HLR/EUSE -> MSC) GSUP_PROC_SS_ERR (abort); 5. (MSC -> MS) GSM 04.80 RELEASE COMPLETE; 6. Connection release. As can be seen, HLR/EUSE initiates the session abort right after the GSM 04.80 REGISTER message is delivered to the MS, and just before the MS sends anything back in response. Change-Id: I5586a88136c936441a842f49248824680603672e Related: OS#2931
46 hoursMSC_Tests.ttcn: introduce TC_proc_ss_paging_failVadim Yanitskiy1-4/+64
The idea of this test case is to check that OsmoMSC does inform HLR/EUSE that a subscriber did not respond to Paging Request in case of network-originated SS/USSD. Both f_expect_gsup_msg() and f_expect_dtap_msg() were extended with optional timeout value, as we need to wait longer than 2.0 seconds (default). Let's stick to 10.0 seconds. Change-Id: I1f53c56d569c8ac4071835685bbe3bc9e0ebd7f0 Related: OS#2931
2 daysMSC_Tests.ttcn: introduce TC_proc_ss_for_unknown_sessionVadim Yanitskiy1-0/+43
The idea of this test case is to check that OsmoMSC properly rejects GSUP PROC_SS messages for unknown sessions. As it turned out, OsmoMSC doesn't send GSUP PROC_SS ERROR as expected. The fix has been submitted. Change-Id: Ie267ee174c5061cd3fc102a2824abe03d73f3aac Related: OS#2931
2 daysMSC_Tests.ttcn: use f_expect_gsup_msg() in f_tc_mt_ussd_for_unknown_subscr()Vadim Yanitskiy1-12/+1
Change-Id: Id067cee3b7d06613d8387e0fa9d8a5c1dbcc49cf
3 daysMSC_Tests.ttcn: add timers to SS/USSD test casesVadim Yanitskiy1-0/+16
Change-Id: I1883bae34a9fe0435a6138cb7594461dee3bb232
3 daysMSC_Tests.ttcn: introduce TC_mt_ussd_for_unknown_subscrVadim Yanitskiy1-0/+51
The idea of this test case is to check that OsmoMSC properly rejects SS/USSD requests for unknown subscribers. Running this test case against the current OsmoMSC helped to discover several problems: - OsmoMSC doesn't print anything in such cases; - IMSI in the response error message is empty; - both session state and ID IEs are omited; which are going to be fixed soon. Change-Id: Id35cd3ec15d1bab15260312d7bbb41e2d10349fe Related: OS#2931
4 dayslib/IPA_Emulation: Build IPA_CTRL conditionally based on definePau Espin Pedrol1-1/+1
Change-Id: I4d1eca6b0008a395b7f7449e6ea3f9b6d41133c7
11 daysAdd and set transport field for RanOps structurePau Espin Pedrol1-0/+1
This will allow RAN_Emulation to have better knowledge on the protocol stack in use, and behave differently based on that information. For intance, forthcoming commit will append OsmuxSupport IE only if transport is BSSAP AoIP. Change-Id: Ife62e328af2d3f2475ff93249f2138820c7ddabb
2019-06-03msc: Fix Iu tests timing out due to explicit CM ServiceAccept not recvdPau Espin Pedrol1-1/+1
Even if ciphering it not enabled, osmo-msc still sends a SecurityModeCommand to use IntegrityProtection, and as a result osmo-msc assumes implicit ACCEPT in all UTRAN CM service requests. Fixes: OS#3991 Change-Id: Ida91f907dd6dfae68cbc63752ddc6f2948792689
2019-05-31msc: Add module param to disable osmux (fix msc-latest jenkins job)Pau Espin Pedrol1-6/+14
ttcn3-bsc-test-latest currently fails on most tests because it tries to use "osmux off" VTY param and only current osmo-msc master supports it. Change-Id: I53d58b2d905905ebf1df322d0389b3715a48212f
2019-05-31msc: Enable/disable osmux always based on testPau Espin Pedrol1-1/+5
Initially it was thought safe to only enable it since the osmux test was at the end, but actually IU tests run after it, and those don't expect osmux to be enabled. This way we also always match osmo-msc osmux state with whatever the test expects (and sets through f_init()). Change-Id: I8fb48af7d37f1a2391a39c19f5ec5064cd5869d2
2019-05-27cosmetic: Update copyright statement, license notice and SPDXHarald Welte3-0/+34
Some of our files didn't have a copyright notice at all, let's add it. Also, update the notices in other files and ensure a SPDX identifier is present in all but the most trivial files. Change-Id: If7fa19ce484b415bc645e39b3d0d666b44b5f0fd
2019-05-27msc: Introduce Osmux infra and one test for osmo-mscPau Espin Pedrol2-24/+125
Change-Id: Ibcb82d1a2d570c6c0ad0c3b6504bffe2244eccd9
2019-05-27bsc: Introduce Osmux infra and one test for osmo-bscPau Espin Pedrol1-0/+1
Test verifies once osmux is enabled in osmo-bsc, BSSMAP RESET (ACK) contains Osmux Support IE and that it correctly handles BSSMAP ASsign Req with Osmux CID. Related: OS#2551 Depends: osmo-bsc 6de754cdde5319af3059d8fc6abf85037ec7eacc Depends: titan.ProtocolModules.BSSMAP Iaf1e137269c0da20b2c96fd104b57edf336693af Change-Id: If69c716dc06d61d810c32d1720a237c7535baca8
2019-05-23MSC_Tests: Remove duplicated structures from BSSMAP_TemplatesPau Espin Pedrol1-138/+0
Change-Id: Ia82b65fe7e53cc0ab73df94b844b9b85aba9468b
2019-05-21Depend on our own fork of titan.ProtocolModules.BSSMAPPau Espin Pedrol1-1/+1
Since we use some BSSMAP extensions to signal Osmux, we need to maintain our own fork of BSSMAP_Types in order to supports those IEs in BSSMAP RESET and BSSMAP Assin Req/Compl. Hence, switch all build componenets to fetch and use our fork. Depends: titan.ProtocolModules.BSSMAP Iaf1e137269c0da20b2c96fd104b57edf336693af Change-Id: Ic8debe5f3ffe8e1d4258fa6b4632a3871b99af40
2019-05-11add three tests for CIPHER MODE COMPLETE without algoStefan Sperling3-3/+107
Add three tests which exercise MSC behaviour when a CIPHER MODE COMPLETE command lacks the optional chosenEncryptionAlgorithm IE. Check for behaviour with A5/1, A5/3, and A5/1 + A5/3 configured in the network, and expect the location update to succeed. These tests pass on master, but they should somehow verify the cipher the MSC ends up using. I am not quite sure how to do that. Would inspecting the MSC's VTY be a reasonable approach? How could his be done by code which runs on BSC_ConnectionHandler? Change-Id: I1a2a126795c544613a7a87e238e1fc8c4e943885 Related: OS#2872
2019-05-11msc: Add a test for LU with invalid MCC/MNC in BSSAP/RANAPHarald Welte2-0/+43
Verify that the MSC rejects a location update from a Cell/BSC that contains a PLMN which does not match the core network's PLMN. Related: OS#3162 Change-Id: I676894358259b9cc0f973769ce552ba58a2a58a1
2019-05-11msc: Separate as_GSUP_SAI from f_mm_authHarald Welte1-19/+24
In some cases we might want to match on (and perform) the GSUP SEND AUTH INFO without also expecting/performing a MM authentication on the Iu/A interface. Hence it makes sense to split those two. Change-Id: I7b298d589930bab976b478ac84553a6352f25c93
2019-05-09msc: Permit optional authentication before reject/timeoutHarald Welte1-0/+3
Tests like TC_lu_imsi_reject, TC_lu_imsi_timeout_gsup and TC_cmserv_imsi_unknown all expected a reject straight in response to the LU REQ / CM SERV REQ. However, the MSC may very well decide to perform authentication beforehand. It's an implementation detail when a MSC/VLR performs authentication, so the tests should be tolerant to this. This primarily shows up in 3G/Iu/RANAP related tests, as authentication is mandatory there. Change-Id: Icdd3f34eca08092703ab2ba9a8e755e2d609a59b
2019-05-09msc: Don't require protocolExtensions in RANAP PagingHarald Welte2-4/+4
We were using '?' for the protocolExtensions in RANAP messages, which required that such extensions existed. In reality, we want to use '*' which accepts paging messages whether or not there are any protocolExtensions present. As this is the default in all our RANAP receive template, callers don't even need to specify it. This should fix all Iu paging related test failures in MSC_Tests*.ttcn Change-Id: If22e16ecb301c86b9073ffde0af9e03bc85fbcc7
2019-05-09msc: add inter-BSC and inter-MSC Handover testsNeels Hofmeyr2-29/+488
Change-Id: I7d76c982ad4e198534fa488609c41e8892b268ab
2019-05-07msc: mo and mt voice call tests: add lots of missing partsNeels Hofmeyr2-84/+196
Both f_mo_call_establish() and f_mt_call_establish() were testing barely half a voice call setup. For example, f_mo_call_establish() used to be satisfied with just two CRCX, but no actual RTP connections being made. Add numerous MNCC and MGCP messages more closely resembling an actual call. The main reason is to achieve a state that passes both current osmo-msc master as well as the upcoming inter-MSC Handover refactoring. Add log markers to f_*_call_*(): often when a test halts, it is not at all clear why. With these log markers it is saner to figure out what has happened and what hasn't. Change-Id: I162985045bb5e129977a3a797b656e30220990df
2019-05-02move as_iu_release_compl_disc from BSC_ConnHdlr to RAN_EmulationHarald Welte1-21/+0
... this way other tests beyond MSC_Tests.ttcn can use it. Change-Id: If6d4bbbd09c6261bd665aa66e0d4d027aeaa4d16
2019-05-02move imsi_hex2oct to Osmocom_Types.ttcnHarald Welte1-19/+0
This function is required not only for the MSC_Tests, but also for the upcoming Iu related SGSN tests Change-Id: Ic23669671ce79151046f2330726bb68542faeb0e
2019-04-30msc: Add Iu related tests for most existing 2G testsHarald Welte3-58/+590
This might look a bit like copy+paste programming for our testcases. However, we actually want the Iu related tests show up as separate 'testscase' in the TTCN-3 sense, so there's no way that's more elegant than this :/ Change-Id: I3b56e17487c9df839e67ed390a1ff89979683e8e
2019-04-30msc: Introduce f_cl3_or_initial_ue as replacement for f_bssap_compl_l3()Harald Welte2-27/+33
The new function will check the RAN type and dispath to f_bssap_compl_l3() in case of 2G/GERAN and to f_ranap_initial_ue() on case of 3G/UTRAN. Change-Id: Ia27afa265d441d1a0cbb40cc2d938aff46fa25f9
2019-04-30msc: Add RANAP to msc testsHarald Welte5-76/+317
Integrate RANAP to MSC_Tests.ttcn Related: OS#2856 Change-Id: Idfa54b7607ad6e7016ed9411b0cc5330c901ea34
2019-04-25RAN_Adapter: Rename functions from f_bssap_* to f_ran_adapter_*Harald Welte1-4/+4
Change-Id: I73818247f1dfc71c8ece11660e6c18f5f153d186
2019-04-25RAN_Emulation: Modularize protocol supportHarald Welte3-2/+3
The RAN_Emulation currently unconditionally provides BSSAP and MGCP support. Let's re-structure the code so that support for those protocols is now possible to enable/disable at compile time. This patch is in preparation of introducing RANAP support in RAN_Emulation. Change-Id: Id53ba3ff05f9946230e0e4a759245de14a0f9fbd Related: OS#2856
2019-04-25msc: Add testcase for UMTS AKA over GERAN TC_lu_imsi_auth3g_tmsi()Harald Welte1-0/+15
Change-Id: I10cc7ed214e83b4624587c60f332034d3f19b22d
2019-04-25msc: f_mm_auth(): Add support for UMTS AKAHarald Welte2-9/+30
Change-Id: Id57adcebd63a06cfa555824e493561fe08f13d6d
2019-04-21MSC_Tests: Allow test cases to specify RAN indexHarald Welte2-9/+12
This allows to start ConnHdlr on specific RAN connections, i.e. on different emulated BSCs (and soon RNCs). Change-Id: I3d7ec567a7b69d8c6f79d26971bf1c94e077d5f5
2019-04-21f_perform_lu(): Use f_expect_clear(), reduce code duplicationHarald Welte1-3/+1
Change-Id: I64b183ad6615f2b0b9565a711de87fe4249625a1
2019-04-21Add f_expect_paging() rather than using tr_BSSMAP_Paging directlyHarald Welte2-7/+14
this will ease the introduction of RANAP support Change-Id: I213303337373c349676be4f8ac4175acdc701e47
2019-04-21Rename BSSMAP_Emulation -> RAN_EmulationHarald Welte3-46/+46
So far, BSSMAP_Emulation supported only a transport over BSSMAP. However, we soon intend to merge support for RANAP in order to simulate RANAP/Iu connections as well as BSSMAP. Let's start by renaming some of the existing types/functions/ports/modules without introducing any functional changes just yet. Related: OS#2857, OS#2856 Change-Id: Iecbcb0c6c136baad9460eca40606bb4010d8882d
2019-04-21BSC_ConnectionHandler: Define SDP template for CN-side CRCXHarald Welte1-14/+11
Change-Id: I90546249c41de8f99ce4a558e76cb46597413518
2019-04-12msc: expect only one Paging on failed MT SMSNeels Hofmeyr1-31/+4
An MSC might decide to repeatedly retry Paging if it failed the first time, but osmo-msc currently has no such mechanism. Instead, it so far had a bug that retriggered a failed Paging from a start in a situation where there are SMS pending for only one subscriber, and sending the SMS fails. osmo-msc patch I24bf9f1c1167efe1080ae4cf47ed2ef0bd981e49 changes this behavior to accept a Paging failure and not launch the same SMS again numerous times. Adjust the tests to this new behavior. Depends: I24bf9f1c1167efe1080ae4cf47ed2ef0bd981e49 (osmo-msc) Change-Id: I7dce12942a65eaaf97f78ca69401c7f93faacb9e
2019-04-12msc: clear the failed SMS when a test is doneNeels Hofmeyr1-6/+13
If an MT SMS is triggered and not handled in the test, it is so far left behind when the test ends. That causes Paging to retrigger for that SMS at any later point during subsequent test runs, causing stray bogus test failures. Actually remove the SMS from the SMS database and the queue with a new VTY command: The vty command to clear failed SMS from the db is added in osmo-msc I637cbd7adc075a192f49752b38779391472ff06d Depends: I637cbd7adc075a192f49752b38779391472ff06d (osmo-msc) Change-Id: I4ff05187131e93f5bc58dc7ea44546f770e5b4c1
2019-04-09MSC_Tests: Add testcase to simulate VLR/HLR failure (SGsAP)Philipp Maier2-0/+39
Currently we do not simulate a situation where the HLR is unreachable to the MSC. Lets add a test wehere the HLR is disconnected and an LU via SGsAP is tried. The SGs interface should then carry out a reset procedure. Change-Id: I830d0b936cbe9d73d1e0b1f4792c2be3d0b08cb9 Related: OS#3859
2019-04-09MSC_Tests: allow disabeling GSUPPhilipp Maier2-8/+21
The GSUP link between testsuit and osmo-msc is currently on by default and can not be disabled. However, there may be situations where a missing GSUP connection must be simulated. Lets add add a parameter to disable GSUP if necessary. Change-Id: I7c86aa0a906a0d7e8be765f9109a65b4b4387bc6 Related: OS#3859
2019-04-02MSC_Tests: fix TC_sgsap_expl_imsi_det_nonepsPhilipp Maier1-2/+4
When a subscriber is detached from non eps services, it gets fully detached from 2G, which means that the VLR is supposed to remove the subscriber. Lets check if the subscriber is in deed no longer known by the VLR. Change-Id: I2ec3f548dfcf5a9b99f10214a8bfd0c6978e253b Related: OS#3614
2019-04-02MSC_Tests: add testcase TC_sgsap_impl_imsi_det_epsPhilipp Maier2-0/+26
We have a testcase that sends an explicit (UE-Initiated) imsi detach from EPS services. Lets also cover the case for an implicit (Network-initated) detach. Change-Id: I63ebc32ae457dd74214d4abee4f511cde28de4a7 Related: OS#3614
2019-04-02MSC_Tests: add testcase TC_sgsap_impl_imsi_det_nonepsPhilipp Maier2-0/+29
We have a testcase that sends an explicit (UE-Initiated) imsi detach from non EPS services. Lets also cover the case for an implicit (Network-initated) detach. Change-Id: I76049e6717680c54c18f97b7cd51944901a81ae7 Related: OS#3614
2019-04-02MSC_Tests: add function to check if a subscriber is in VLRPhilipp Maier1-0/+17
The control interface of osmo-msc is able to return a list with all active subscribers from the VLR. Lets add a function, so that we can check from TTCN3 if a specified subscriber is known by the VLR or not. Change-Id: I7661ae55afe34795c3701d59795331b32d64c988 Related: OS#3614
2019-03-19msc: f_tc_sgsap_mt_sms_and_nothing: also do f_sgsap_bssmap_screeningNeels Hofmeyr1-0/+2
The only reason to omit f_sgsap_bssmap_screening() in this was the still pending SMS in the database. Since SMS are now removed, f_sgsap_bssmap_screening() will succeed. Change-Id: Ibea1e1fb33e0dde7e8bf51ff226d5e57c5a5d763
2019-03-19msc: TC_lu_disconnect: add final delay to fix spurious failureNeels Hofmeyr1-0/+1
I hit a "Broken pipe" error, hoping that the bit of delay makes the teardown more stable. Change-Id: I765a75f91a748239f6cc82f4a61f02d59166f00b
2019-03-17msc: for mo and mt call, interleave MGCP and AssignmentNeels Hofmeyr1-13/+21
Upcoming osmo-msc changes move away from the current ordering of MGCP and Assignment messages. Allow these async dialogs to appear in any order. Change-Id: Ia06af1e347601949f4ddb19f963daa400766d9e7
2019-03-14msc: TC_gsup_cancel: end with f_expect_clear() to avoid broken pipeNeels Hofmeyr1-0/+2
Change-Id: I3b3ae0b9c3f02f523dfb60c9efb732db3ade2785
2019-03-14msc: add codec to all Assignment Complete messagesNeels Hofmeyr1-2/+6
So far we omit a Speech Codec (Chosen) from Assignment Complete messages, which is actually a mandatory parameter. osmo-msc seems to carry on nevertheless, but it actually shouldn't be able to. Always send a Speech Codec (Chosen). Change-Id: Ib35f019383db8ace05a9dc349648e2da7ba58bfa