//TODO add check of PICS_SCCAS_REJECTION_OF_MALICIOUS_REFER in TP_ISC_SCCAS_GEN_REF_01
//A3/2.3 handling of SDP media description conflicts? 5.3, 6A.5 m
//A3/2.4 SCC AS server procedure for indicating traffic leg? 5.3, 6A.6.1 o
//A3/3 procedures for call origination for service continuity? 7.3 m
...
...
@@ -68,15 +78,44 @@ PICS used for test case selection
//A3/4.1 removal of the g.3gpp.mid-call media feature tag from the SIP 2xx response towards the remote UE? 8.3.2 c.11
//A3/5 procedures for PS-CS access transfer? 9.3.2, 9.3.3, 9.3.6 c.12
//A3/5.1 procedures for PS to CS access transfer with MSC server assisted mid-call feature? 9.3.2A, 9.3.4 c.13
//A3/5.2 procedures for PS to CS dual radio access transfer of calls in an early dialog or alerting phase? 9.3.5.1, 9.3.5.2, 9.3.5.4, 9.3.5.5 c.14
/** @desc Does IUT supports procedures for PS to CS dual radio access transfer of calls in an early dialog or alerting phase? 9.3.5.1, 9.3.5.2, 9.3.5.4, 9.3.5.5 c.14
/** @desc Does IUT supports procedures for PS-CS access transfer, Single Radio (PS to CS SRVCC)? 12.3.0, 12.3.0A, 12.3.0B, 12.3.1, 12.3.3.1, 12.3.3.2, 12.3.3.4, 12.3.5, 12.3.6, 12.3.7, 12.3.8, 12.3.9, 12.3.11 c.20
* @see ETSI TS 103 833-1 A.3/8
*/
moduleparbooleanPICS_SCCAS_PS2CS_SRVCC:=false;
//
//A3/8.1 inclusion of the g.3gpp.srvcc-alerting feature-capability indicator in the Feature-Caps header field in SIP 200 (OK) responses to SIP INVITE requests due to STN-SR on the target access leg? 12.3.1, 3rd numbered list item 2) c.21
//A3/8.2 procedures for PS to CS SRVCC access transfer with MSC server assisted mid-call feature? 12.3.2 c.22