NGAP: Add UESecurityCapabilities IE to PathSwitchRequestAcknowledge
This IE is now used by Open5GS, so add it to the receive template.
This fixes C5G_Tests.TC_handover_inter_ngran_xn.
Note that there is also a pull request to fix the location of this IE in Open5GS. (https://github.com/open5gs/open5gs/pull/4589) Without this fix the test case will fail.
C5G: Release UE Context before sending Service request
A recent fix in Open5GS rejects RAN_UE_NGAP_ID in InitialUEMessage. This causes all tests to fail that send a subsequent InitialUEMessage with the same RAN_UE_NGAP_ID.
Release the UE Context before re-using the RAN_UE_NGAP_ID, because the connection handler can only handle one context at a time.
Note that the AMF_UE_NGAP_ID is incremented by Open5GS for every context.
This fixes: TC_ue_service_request_cm_idle_inact_sess TC_ue_service_request_cm_idle_ul_data TC_ue_service_request_cm_idle_unknown_sess_active
RemsimServer Tests: give the remsim server some time to update the slotmap
The check of the slotmap can race if it is requests straight away, because the slotmap might be still in the slotmap list as long the bankd hasn't responded yet.
* Use a TCAP id outside of the TCAP routing range for the M3UA TCAP id. * Test both directions IPA -> M3UA and M3UA -> IPA. * Test TCAP routing with a different called address answering
msc: CC SETUP MT speech: verify bearer capabilities
Verify that the MSC sends the bearer capability IE from 3GPP TS 24.008 § D.1.2 for speech in the network to MS direction, instead of allowing e.g. what osmo-msc master and latest release currently do:
- Filling out radio channel requirement the same way as the MS to Network direction, which is wrong for the Network to MS direction: "Bits 6 and 7 are spare bits. The sending side (i.e. the network) shall set bit 7 to value 0 and bit 6 to value 1." (3GPP TS 24.008 Table 10.5.102)
- Sending a speech list in the Network to MS direction, which seems to be allowed in theory and MS are supposed to ignore it (end of Table 10.5.103) but causes bugs in some MS in practice. Therefore it is better to ensure that osmo-msc does not send it (OS#6656).
Implement this in f_mt_call_complete(), which gets used e.g. by TC_lu_and_mt_call.
