Datasets:

OrganizedProgrammers
/

ETSISpecContent

Dataset card Data Studio Files Files and versions Community

Split (1)

train · 194k rows

hash stringlengths 32 32	doc_id stringlengths 7 13	section stringlengths 3 121	content stringlengths 0 3.82M
9c9040046fb0b6b58964d63a2286c73c	101 594-2	5.2.2 Actions at the Transferor AS	TSS Netw/TransferorAS TP ECT_N01_001 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose Communication transfer: Assured transfer. Transferor was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. After the communication between the Transferee and the Transfer Target is confirmed, the communication between Transferor and Transferee is terminated. The Transferor was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE 1 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Communication ISC#2 with ISC#3 Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 13 TSS Netw/TransferorAS TP ECT_N01_002 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose Communication transfer: Assured transfer. Transferee was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. After the communication between the Transferee and the Transfer Target is confirmed, the communication between Transferor and Transferee is terminated. The Transferee was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Communication ISC#2 with ISC#3 Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 14 TSS Netw/TransferorAS TP ECT_N01_003 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose Communication transfer: Blind transfer. Transferor was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. After the REFER request to the Transferee is sent, the communication between Transferor and Transferee is terminated. The Transferor was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE 1 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Communication ISC#2 with ISC#3 Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 15 TSS Netw/TransferorAS TP ECT_N01_004 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose Communication transfer: Blind transfer. Transferee was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. After the REFER request to the Transferee is sent, the communication between Transferor and Transferee is terminated. The Transferee was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Communication ISC#2 with ISC#3 Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 16 TSS Netw/TransferorAS TP ECT_N01_005 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose Communication transfer: Consultative transfer. Transferor was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. The Transferor has a session with Transferee and the Transfer target set on hold. The Transferor refers the Transferee to establish a session to the Transfer target. After the successful session between Transferee and Transfer target, the sessions of the Transferor are released by the Transferor. The Transferor was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite?Replaces=call-id1%3Bto-tag%3DS1%3B from-tag%3DS1&Require=replaces Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI;method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI Referred-By contains ISC#1 URI INVITE 4: Request URI = ISC#3 URI; Replaces: call-id1;to-tag=S1;from-tag=S1 Require: replaces Referred-By contains ISC#1 URI NOTIFY(100): Event contains refer; Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer; message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE 1 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 17 TSS Netw/TransferorAS TP ECT_N01_005 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) Communication ISC#2 with ISC#3 Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 18 TSS Netw/TransferorAS TP ECT_N01_006 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose Communication transfer: Consultative transfer. Transferee was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. The Transferor has a session with Transferee and the Transfer target. The Transferor refers the Transferee to establish a session to the Transfer target. After the successful session between Transferee and Transfer target set on hold, the sessions of the Transferor are released by the Transferor. The Transferee was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite?Replaces=call-id1%3B to-tag%3DS1%3Bfrom-tag%3DS1&Require=replaces Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI Referred-By contains ISC#1 URI INVITE 4: Request URI = ISC#3 URI Replaces=call-id1;to-tag=S1; from-tag=S1 Require: replaces Referred-By contains ISC#1 URI NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 19 TSS Netw/TransferorAS TP ECT_N01_006 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) Communication ISC#2 with ISC#3 Apply post test routine TSS Netw/TransferorAS TP ECT_N01_007 Reference 4.5.2.4.1.2.2 Selection expression PICS 4.5.1/2 Test purpose The method in the Refer-To header is not the 'INVITE' method. Ensure that the REFER request is rejected if the Method in the Refer-To header used in this dialogue is not the INVITE method e.g. BYE. SIP header values: REFER: Refer-To contains ISC#3 URI; method=BYE Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER REFER 4xx or 5xx or 6xx Response 4xx or 5xx or 6xx Response Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 20 TSS TP ECT_N01_008 Reference 4.5.2.4.1.2.2 Selection expression PICS 4.5.1/2 Test purpose The request-URI is not targeted at the same UE instance that is involved in the dialog. Ensure that the ECT simulation service does not apply if the Request URI is not the Transferee URI. The REFER request is rejected. SIP header values: REFER: Request URI contained the other URI (PIXIT) Refer-To contains the URI of ISC#3, method=invite Referred-By contains SIP or tel URI of ISC#1 Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER REFER 4xx or 5xx or 6xx Response 4xx or 5xx or 6xx Response Apply post test routine TSS Netw/TransferorAS TP ECT_N01_009 Reference 4.5.2.4.1.2.2 Selection expression PICS 4.5.1/2 Test purpose There is no method parameter contained in the Refer-To header. Ensure that the REFER request is rejected if there is no Method parameter contained in the Refer-To header. SIP header values: REFER: Refer-To To contains ISC#3 URI (no method parameter) Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER REFER 4xx or 5xx or 6xx Response 4xx or 5xx or 6xx Response Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 21 TSS Netw/TransferorAS TP ECT_N01_010 Reference 4.5.2.4.2.3 Selection expression PICS 4.5.1/2 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose In the REFER request, the Referred-By header does not contain the valid identity of the served user. A Referred-By header is available in the REFER request, the AS verifies if the provided Referred-By header contains a valid identity of the served user. If not it will replace the Referred-By header with a valid value matching the REFER request's P-Asserted-Identity. SIP header values: REFER 1: Request URI: ISC#2 Referred-By contains ISC#x URI (PIXIT any value) P-Asserted-Identity=ISC#1 REFER 1: Request URI: ISC#2 Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 22 TSS Netw/TransferorAS TP ECT_N01_011 Reference 4.5.2.4.2.3 Selection expression PICS 4.5.1/2 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose The REFER request does not contain a Referred-By header. If no Referred-By header is available in the REFER request a Referred-By header is added that matches the REFER method's P-Asserted-Identity. SIP header values: REFER 1: Request URI: ISC#2 Referred-By not present P-Asserted-Identity=ISC#1 REFER 1: Request URI: ISC#2 Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 23 TSS Netw/TransferorAS TP ECT_N01_012 Reference 4.5.2.4.2.1 Selection expression PICS 4.5.1/2 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose The Referred-By header in the received INVITE does not contain the valid identity of the served user. If a Referred-By header is available in the INVITE request, the AS verifies if the provided Referred-By header contains a valid identity of the served user. If not it will replace the Referred-By header with a valid value matching the REFER request's P-Asserted-Identity. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite P-Asserted-Identity=ISC#1 INVITE 3: Request URI = ECT Session Identifier URI Referred-By contains ISC#x URI (PIXIT any value) INVITE 4: Request URI = ISC#3 URI Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 24 TSS Netw/TransferorAS TP ECT_N01_013 Reference 4.5.2.4.2.1 Selection expression PICS 4.5.1/2 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose The received INVITE does not contain a Referred-By header. If no Referred-By header is available in the INVITE request a Referred-By header is added that matches the REFER request's P-Asserted-Identity. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite P-Asserted-Identity=ISC#1 INVITE 3: Request URI = ECT Session Identifier URI Referred-By not present INVITE 4: Request URI = ISC#3 URI Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 25 TSS Netw/TransferorAS TP ECT_N01_014 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND PICS 4.7.1/4 Test purpose Assured transfer. The Transferor AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferor AS when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 100 Trying' if the REFER request is accepted. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 200 OK' if the refered communication is established. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 26 TSS Netw/TransferorAS TP ECT_N01_015 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 4.7.1/4 Test purpose Blind transfer. The Transferor AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferor AS when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 100 Trying' if the REFER request is accepted. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 200 OK' if the refered communication is established. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 27 TSS Netw/TransferorAS TP ECT_N01_016 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND PICS 4.7.1/4 Test purpose Consultative transfer. The Transferor AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferor AS when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 100 Trying' if the REFER request is accepted • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 200 OK' if the refered communication is established. SIP header values: REFER 1: Refer-To contains ISC#3 URI;method=invite?Replaces=call-id1%3Bto-tag%3DS1%3B from-tag%3DS1&Require=replaces Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE(S1) BYE 200 OK (BYE) 200 OK (BYE) BYE BYE(S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 28 TSS Netw/TransferorAS TP ECT_N01_017 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND PICS 4.7.1/4 Test purpose Assured transfer. The Transferor AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferor AS when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 29 TSS Netw/TransferorAS TP ECT_N01_018 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 4.7.1/4 Test purpose Blind transfer. The Transferor AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferor AS when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 30 TSS Netw/TransferorAS TP ECT_N01_019 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND PICS 4.7.1/4 Test purpose Consultative transfer. The Transferor AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferor AS when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI;method=invite?Replaces=call-id1%3Bto-tag%3DS1%3B from-tag%3DS1&Require=replaces Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE(S1) BYE 200 OK (BYE) 200 OK (BYE) BYE BYE(S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 31 TSS Netw/TransferorAS TP ECT_N01_020 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND PICS 4.7.1/5 Test purpose Assured transfer. The Transferor AS initiate the special REFER handling procedures directly. Ensure that three party call control applies directly at the Transferor AS when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 100 Trying' after the REFER request is accepted. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 200 OK' after the referred communication is confirmed. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 32 TSS Netw/TransferorAS TP ECT_N01_021 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 4.7.1/5 Test purpose Blind transfer. The Transferor AS initiate the special REFER handling procedures directly. Ensure that three party call control applies directly at the Transferor AS when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 100 Trying' after the REFER request is accepted. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 200 OK' after the referred communication is confirmed. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK NOTIFY(100) 200 OK NOTIFY ACK ACK INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 33 TSS Netw/TransferorAS TP ECT_N01_022 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND PICS 4.7.1/5 Test purpose Consultative transfer. The Transferor AS initiate the special REFER handling procedures directly. Ensure that three party call control applies directly at the Transferor AS when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 100 Trying' after the REFER request is accepted. • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 200 OK' after the referred communication is confirmed. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Subscription-State: terminated;reason=noresource Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 REFER 1 REFER 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 34
9c9040046fb0b6b58964d63a2286c73c	101 594-2	5.2.3 Actions at the Transferee UE	TSS User/Transferee TP ECT_U02_001 Reference 4.5.2.5 Selection expression PICS 4.5.1/1 AND (PICS 4.6.1/1 OR PICS 4.6.1/2) AND PICS 4.6.1/5 Test purpose The User Equipment receives the request to establish a communication to the transfer target (Transferee Blind/assured transfer) Ensure that the UE establishes a session with a 'transfer target' if a REFER request was received containing a Refer-To header and a Referred-By header. The Request Line of INVITE request sent by the UE is set to the URI received in the Refer-To header. The received Referred-By header is sent in the INVITE request.Ensure that a NOTIFY request is sent containing a message/sipfrag body set to 'SIP/2.0 100 Trying' after the REFER request is accepted.Ensure that a NOTIFY request is sent containing a message/sipfrag body set to 'SIP/2.0 200 OK' after the referred communication is confirmed. SIP header values: REFER: Request URI: Gm#1 Refer-To: contains Gm#3 URI;method=invite Referred-By: contains Gm#2 URI NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK INVITE: Request URI: Gm#3 Referred-By contains Gm#2 URI ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 35 Comments: UE ( Gm#1) Test equipment ( Gm#2) Establishment of session #1 Session #1 on hold REFER REFER CASE A 202 Accepted (Session #1) 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE(inactive/sendonly) (Session #1) INVITE 200 OK INVITE 200 OK INVITE(inactive/recvonly) ACK ACK INVITE (Session #2) INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY CASE B NOTIFY(100) (Session #1) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY 202 Accepted (Session #1) 202 Accepted INVITE(inactive/sendonly) (Session #1) INVITE 200 OK INVITE 200 OK INVITE(inactive/recvonly) ACK ACK INVITE (Session #2) INVITE 180 Ringing 180 Ringing 200 OK INVITE (Session #2) 200 OK INVITE ACK ACK NOTIFY(200) (Session #1) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 36 TSS User/Transferee TP ECT_U02_002 Reference 4.5.2.5 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/3 AND PICS 4.6.1/5 Test purpose The User Equipment receives the request to establish a communication to the transfer target (Transferee consultative transfer) Ensure that the UE establishes a session with a 'transfer target' if a REFER request was received containing a Refer-To header and a Referred-By header. The Request Line of INVITE request sent by the UE is set to the URI received in the Refer-To header. The received Referred-By header is sent in the INVITE request. The Replaces header escaped in the received REFER request is sent in the INVITE request. Ensure that a NOTIFY request is sent containing a message/sipfrag body set to 'SIP/2.0 100 Trying' after the REFER request is accepted. Ensure that a NOTIFY request is sent containing a message/sipfrag body set to 'SIP/2.0 200 OK' after the referred communication is confirmed. SIP header values: REFER: Request URI: Gm#1 Refer-To: contains Gm#3 URI; method=invite?Replaces=<any value>%3Bto-tag%3D<any To tag value>%3Bfrom-tag%3D<any From tag value>&Require=replaces Referred-By: contains Gm#2 URI NOTIFY(100): Event contains refer Subscription-State: active;expires=(any value) message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK INVITE: Request URI: Gm#3 Referred-By contains Gm#2 URI Replaces: <any value>;to-tag=<any To tag value>=from-tag=<any From tag value> Require: contains replaces Comments: UE ( Gm#1) Test equipment ( Gm#2) Establishment of session #1 Session #1 on hold REFER REFER CASE A 202 Accepted (Session #1) 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE(inactive/sendonly) (Session #1) INVITE 200 OK INVITE 200 OK INVITE(inactive/recvonly) ACK ACK INVITE (Session #2) INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY CASE B NOTIFY(100) (Session #1) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY 202 Accepted (Session #1) 202 Accepted INVITE(inactive/sendonly) (Session #1) INVITE 200 OK INVITE 200 OK INVITE(inactive/recvonly) ACK ACK INVITE (Session #2) INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY(200) (Session #1) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 37 TSS User/Transferee TP ECT_U02_003 Reference 4.5.2.5 [1] Selection expression PICS 4.5.1/1 AND NOT PICS 4.6.1/5 Test purpose UE has not the capability to handle the REFER request. Ensure that the UE is able to send a 403 Forbidden or 501 Not implemented unsuccessful final response if the REFER handling is not implemented. SIP header values: REFER: Request URI=Gm#1, Refer-To other URI (PIXIT); method=invite Referred-By contains Gm#2 URI Comments: UE ( Gm#1) Test equipment (Gm#2) Establishment of session #1 Session #1 on hold REFER REFER CASE A 403 Forbidden 403 Forbidden CASE A 501 Not implemented 501 Not implemented Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 38
9c9040046fb0b6b58964d63a2286c73c	101 594-2	5.2.4 Action at the Transferee AS	TSS Netw/TransfereeAS TP ECT_N02_001 Reference 4.5.2.7 Selection expression PICS 4.5.1/2 Test purpose Communication transfer: Assured transfer applicable at the Transferee AS. Ensure that the Transferee AS can act as a proxy when receives the REFER request, the INVITE request and the BYE request for the call that is transferred as an assured transfer. SIP header values: REFER 1: Refer-To ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 (S2) INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 39 TSS Netw/TransfereeAS TP ECT_N02_002 Reference 4.5.2.7 Selection expression PICS 4.5.1/2 Test purpose Communication transfer: Blind transfer applicable at the Transferee AS. Ensure that the Transferee AS can act as a proxy when receives the REFER request, the INVITE request and the BYE request for the call that is transferred as a blind transfer. SIP header values: REFER 1: Refer-To ISC#3 URI;method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To ISC#3 URI;method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3 URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 40 TSS Netw/TransfereeAS TP ECT_N02_003 Reference 4.5.2.7 Selection expression PICS 4.5.1/2 Test purpose Communication transfer: Consultative transfer applicable at the Transferee AS. Ensure that the Transferee AS can act as a proxy when receives the REFER request, the INVITE request and the BYE request for the call that is transferred as a Consultative transfer. SIP header values: REFER 1: Refer-To ISC#3 URI;method=invite?Replaces=call-id1%3Bto-tag%3DS1%3B from-tag%3DS1&Require=replaces Referred-By contains ISC#1 URI REFER 2: Refer-To contains ISC#3/Transferee AS URI;method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3/Transferee AS URI Referred-By contains ISC#1 URI INVITE 4: Request URI = ISC#3 URI Replaces: call-id1;to-tag=S1;from-tag=S1 Referred-By contains ISC#1 URI Require: replaces NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (S2 inactive) INVITE (inactive) 200 OK (inactive) 200 OK (S2 inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 41 TSS Netw/TransfereeAS TP ECT_N02_004 Reference 4.5.2.7.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/7 Test purpose The Referred-By header in the received INVITE does not contain the valid identity of the served user. Value is replaced. If a Referred-By header is available in the INVITE request sent to the Transfer Target, the AS verifies the provided Referred-By header contains the value stored in the received REFER request. If no match is found, the value of the Referred-By header is replaced by the value of the Referred-By header received in the REFER request. SIP header values: REFER 2: Refer-To URI; method=invite … Referred-By ISC#1 INVITE 3: Referred-By other URI (PIXIT) INVITE 4: Referred-By ISC#1 Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 42 TSS Netw/TransfereeAS TP ECT_N02_005 Reference 4.5.2.7.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 Test purpose The Referred-By header in the received INVITE does not contain the valid identity of the served user. The request is rejected. If a Referred-By header is available in the INVITE request sent to the Transfer Target, the AS verifies if the provided Referred-By header contains the value stored in the received REFER request. If no match is found, the INVITE request is rejected. SIP header values: REFER 2: Refer-To URI; method=invite … Referred-By ISC#1 INVITE 3: Referred-By other URI (PIXIT) Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE 4xx 4xx ACK ACK Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 43 TSS Netw/TransfereeAS TP ECT_N02_006 Reference 4.5.2.7.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/8 Test purpose The received INVITE does not contain a Referred-By header. If no Referred-By header is available in the INVITE request sent to the Transfer Target, the AS inserts a Referred- By header and the value is equal to the value stored in the received REFER request. SIP header values: REFER 2: Refer-To URI; method=invite … Referred-By ISC#1 INVITE 3: (no Referred-By header) INVITE 4: Referred-By ISC#1 Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 44 TSS Netw/TransfereeAS TP ECT_N02_007 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND PICS 4.7.1/4 Test purpose Assured transfer. The Transferee AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferee AS when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 100 Trying' if the REFER request is accepted. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 200 OK' if the refered communication is established. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 45 TSS Netw/TransfereeAS TP ECT_N02_008 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 4.7.1/4 Test purpose Blind transfer. The Transferee AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferee AS when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 100 Trying' if the REFER request is accepted. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 200 OK' if the refered communication is established. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 46 TSS Netw/TransfereeAS TP ECT_N02_009 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND PICS 4.7.1/4 Test purpose Consultative transfer. The Transferee AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferee AS when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 100 Trying' if the REFER request is accepted. • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY containing a message/sipfrag body set to 'SIP/2.0 200 OK' if the refered communication is established. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE(S1) BYE 200 OK (BYE) 200 OK (BYE) BYE BYE(S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 47 TSS Netw/TransfereeAS TP ECT_N02_010 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND PICS 4.7.1/4 Test purpose Assured transfer. The Transferee AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferee AS when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 48 TSS Netw/TransfereeAS TP ECT_N02_011 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 4.7.1/4 Test purpose Blind transfer. The Transferee AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferee AS when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 49 TSS Netw/TransfereeAS TP ECT_N02_012 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND PICS 4.7.1/4 Test purpose Consultative transfer. The Transferee AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies at the Transferee AS when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 Session #2 on hold REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE(S1) BYE 200 OK (BYE) 200 OK (BYE) BYE BYE(S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 50 TSS Netw/TransfereeAS TP ECT_N02_013 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND PICS 4.7.1/5 Test purpose Assured transfer. The Transferee AS initiate the special REFER handling procedures directly. Ensure that three party call control applies at the Transferee AS directly when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 100 Trying' after the REFER request is accepted. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 200 OK' after the referred communication is confirmed. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 51 TSS Netw/TransfereeAS TP ECT_N02_014 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 4.7.1/5 Test purpose Blind transfer. The Transferee AS initiate the special REFER handling procedures directly. Ensure that three party call control applies at the Transferee AS directly when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 100 Trying' after the REFER request is accepted. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 200 OK' after the referred communication is confirmed. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK NOTIFY(100) 200 OK NOTIFY ACK ACK INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 52 TSS Netw/TransfereeAS TP ECT_N02_015 Reference 4.5.2.4.1.2.3, 4.7.2.9.7/ [3] Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 AND PICS 4.7.1/5 Test purpose Consultative transfer. The Transferee AS initiate the special REFER handling procedures directly. Ensure that three party call control applies directly at the Transferee AS when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 100 Trying' after the REFER request is accepted. • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. • A NOTIFY request is sent to the Transferor containing a message/sipfrag body set to 'SIP/2.0 200 OK' after the referred communication is confirmed. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 REFER 1 REFER 202 Accepted 202 Accepted 3 party call control applies INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE(S1) BYE 200 OK (BYE) 200 OK (BYE) BYE BYE(S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 53
9c9040046fb0b6b58964d63a2286c73c	101 594-2	5.2.5 Actions at the transfer target's UE	TSS User/TransferTarget TP ECT_U03_001 Reference 4.5.2.17 Selection expression PICS 4.5.1/1 AND Test purpose The User Equipment receives the request to terminate a communication to the transferor. Ensure that a User Equipment in a confirmed session receives an INVITE request to establish a new session that and a Replaces header is present (consultative transfer): • The User Equipment accepts the request • The User Equipment terminates the session indicated in the Replaces header SIP header values: INVITE: Request URI: Gm#1 Referred-By contains any URI Replaces: <CallID Session #1>;to-tag=<Session #1;from-tag=<Session #1> Comments: UE ( Gm#1) Test equipment ( Gm#2) Establishment of session #1 INVITE INVITE (Session #2) 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK BYE (Session #1) BYE 200 OK BYE 200 OK BYE Apply post test routine TSS User/TransferTarget TP ECT_U03_002 Reference 4.5.2.17 Selection expression PICS 4.5.1/1 AND Test purpose The User Equipment receives a Referred-By header. • Ensure that a User Equipment receives a Referred-By header in an INVITE request accepts the request. SIP header values: INVITE: Request URI: Gm#1 Referred-By contains any URI Comments: UE ( Gm#1) Test equipment ( Gm#2) Establishment of session #1 INVITE INVITE (Session #2) 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK BYE (Session #1) BYE 200 OK BYE 200 OK BYE Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 54
9c9040046fb0b6b58964d63a2286c73c	101 594-2	5.2.6 Interaction with other services
9c9040046fb0b6b58964d63a2286c73c	101 594-2	5.2.6.1 Originating identification restriction (OIR)	TSS Interaction/OIR TP ECT_N03_001 Reference 4.6.5 Selection expression PICS 4.5.1/2 AND PICS 7.7.2/1 Test purpose Referred-By header Privacy regarding the requested privacy for the P-Asserted-Identity. Ensure that a Privacy header is present and the value 'user' is included in addition if the Privacy header was received with the value 'id'. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI P-Asserted-Identity ISC#1 URI Privacy: id REFER 2: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI P-Asserted-Identity ISC#1 URI Privacy: id, user Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 55 TSS Interaction/OIR TP ECT_N03_002 Reference 4.6.5 Selection expression PICS 4.5.1/2 AND PICS 7.7.2/1 Test purpose Privacy header in the INVITE of the Transferee is set according previous received privacy indication. Ensure that the INVITE request sent to the transfer target has the same privacy requirements as previous received in initial call between the transferee and the transferor. • Transferee sends a Privacy header value 'id' in the 200 OK INVITE of the initial call. The SUT inserts a Privacy header set to 'id' if the INVITE request sent to the Transfer target does not contain a Privacy header. SIP header values: 200 OK INVITE 1: Privacy: id INVITE 3: (no Privacy header) INVITE 4: Privacy: id Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE 1 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) 1 ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER REFER REFER REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 56 TSS Interaction/OIR TP ECT_N03_003 Reference 4.6.5 Selection expression PICS 4.5.1/2 AND PICS 7.7.2/1 Test purpose Privacy header in the INVITE of the Transferee is set according previous received privacy indication. Ensure that the INVITE request sent to the transfer target has the same privacy requirements as previous received in initial call between the transferee and the transferor. • Transferee sends a Privacy header value 'id' in the INVITE of the initial call. The SUT inserts a Privacy header set to 'id' if the INVITE request sent to the Transfer target does not contain a Privacy header. SIP header values: INVITE 1: Privacy: id INVITE 3: (no Privacy header) INVITE 4: Privacy: id Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) 1 ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER REFER REFER REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 57 5.2.6.2 Anonymous Communication Rejection and Communication Barring (ACR/CB) TSSInteraction/ACR-CB TP ECT_N04_001 Reference 4.6.9 Selection expression PICS 4.5.1/2 AND PICS 7.7.2/2 Test purpose transfer requests with a Transfer Target that is barred by the served users Outgoing Communication Barring (OCB) rules. Ensure that the As does not accept a transfer requests with a transfer Target that is barred by the Transferor's Outgoing Communication Barring (OCB) rules. Precondition: The Transfer Target is barred by the Transferor's Outgoing Communication Barring rules. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER 403 Forbidden 403 Forbidden Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 58
9c9040046fb0b6b58964d63a2286c73c	101 594-2	5.2.6.3 CONFerence Calling (CONF)	TSS Interaction/CONF TP ECT_N05_001 Reference 4.6.6 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 7.7.2/3 Test purpose ECT does not apply if the Refer-To header of the REFER request dialogue contains the URI targeted a conference invited by REFER. Ensure that ECT does not apply if the "Isfocue" parameter was received in the Contact header of a 1xx or 200 OK response in a dialogue to join a conference after received a REFER request to refer to the conference. The REFER request is rejected with a 4xx or 5xx or 6xx unsuccessful final response. SIP header values: INVITE: Request URI=conference factory URI 200 OK (INVITE) 1: Contact: conference URI; isfocus REFER 1: Request URI=ISC#2 Refer-To conference URI;method=invite Referred-By ISC#1 URI Comments: ISC#ISC#1 AS Transferor AS CONF A conference is already established REFER REFER 202 Accepted 202 Accepted INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER REFER 4xx or 5xx or 6xx Response 4xx or 5xx or 6xx Response Apply post test routine TSS Interaction/CONF TP ECT_N05_002 Reference 4.6.6 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 7.7.2/3 Test purpose ECT does not apply if the Refer-To header of the REFER request dialogue contains the URI targeted a conference invited by INVITE. Ensure that ECT does not apply if the "Isfocue" parameter was received in the Contact header of a 1xx or 200 OK response in a dialogue to join a conference after received a INVITE request. The REFER request is rejected with a 4xx or 5xx or 6xx unsuccessful final response. SIP header values: INVITE: ISC#1 URI Contact: conference URI; isfocus Comments: ISC#ISC#1 AS Transferor AS CONF A conference is already established INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER REFER 4xx or 5xx or 6xx Response 4xx or 5xx or 6xx Response Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 59 TSS Interaction/CONF TP ECT_N05_003 Reference 4.6.6 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 7.7.2/3 Test purpose ECT does not apply if the a conference controller invokes ECT. Ensure that ECT does not apply if the conference controller invokes ECT. The REFER request is rejected with a 4xx or 5xx or 6xx unsuccessful final response. SIP header values: INVITE 1: conference factory URI Comments: ISC#ISC#1 AS Transferor AS CONF INVITE 1 INVITE 200 OK (INVITE) 200 OK (INVITE) Invite an other user to the conference REFER REFER 4xx or 5xx or 6xx Response 4xx or 5xx or 6xx Response Apply post test routine
9c9040046fb0b6b58964d63a2286c73c	101 594-2	5.2.6.4 Explicit Communication Transfer (ECT)	TSS Interaction/ECT TP ECT_N06_001 Reference 4.6.10.2, 4.6.10.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose Interaction with ECT: Blind transfer. A session between ISC#1 and ISC#2 exists and was transferred before. Ensure that if the INVITE dialog on which the REFER is received is a previously transferred communication indicated by the presence of a Referred-By header in the INVITE request the: • REFER is forwarded and the value of the Refer-To header is replaced by the ECT session Identifier. • The Request URI of the INVITE request received to forward to the Transfer Target is replaced with the value of the Transfer Target. SIP header values: REFER 1: Refer-To ISC#3 URI; method=invite Referred-By ISC#1 URI REFER 2: Refer-To ECT Session Identifier URI; method=invite Referred-By ISC#1 URI INVITE 2: Request URI = ECT Session Identifier URI Referred-By ISC#1 URI INVITE 3: Request URI = ISC#3 URI Referred-By ISC#1 URI Comments: ISC#ISC#1 AS Transferor ISC#ISC#2 ISC#ISC#3 A transferred communication already exists Session #1 on hold REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) INVITE INVITE 2 (S2) INVITE 3 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 60 TSS Interaction/ECT TP ECT_N06_002 Reference 4.6.10.2, 4.6.10.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose Interaction with ECT: Assured transfer. A session between ISC#1 and ISC#2 exists and was transferred before. Ensure that if the INVITE dialog on which the REFER is received is a previously transferred communication indicated by the presence of a Referred-By header in the INVITE request the: • REFER is forwarded and the value of the Refer-To header is replaced by the ECT session Identifier. • The Request URI of the INVITE request received to forward to the Transfer Target is replaced with the value of the Transfer Target. SIP header values: REFER 1: Refer-To ISC#3 URI; method=invite Referred-By ISC#1 URI REFER 2: Refer-To ECT Session Identifier URI; method=invite Referred-By ISC#ISC#1 URI INVITE 2: Request URI = ECT Session Identifier URI Referred-By ISC#1 URI INVITE 3: Request URI = ISC#3 URI Referred-By ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 A transferred communication already exists Session #1 on hold REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted INVITE INVITE 2 (S2) INVITE 3 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 61 TSS Interaction/ECT TP ECT_N06_003 Reference 4.6.10.2, 4.6.10.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose Interaction with ECT: Consultative transfer. A session between ISC#1 and ISC#2 exists and was transferred before. Ensure that if the INVITE dialog on which the REFER is received is a previously transferred communication indicated by the presence of a Referred-By header in the INVITE request the: • REFER is forwarded and the value of the Refer-To header is replaced by the ECT session Identifier. • The Request URI of the INVITE request received to forward to the Transfer Target is replaced with the value of the Transfer Target. SIP header values: INVITE 1: Request URI = ISC#3 REFER 1: Refer-To ISC#3 URI; method=invite?Replaces=call-id-S2%3B to-tag=S2%3B from-tag=S2&Require=replaces Referred-By ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#1 URI INVITE 2: Request URI = ECT Session Identifier URI Referred-By ISC#1 URI INVITE 3: Request URI = ISC#3 URI Replaces=call-id-S2; to-tag=S2; from-tag=S2 Referred-By ISC#1 URI Require: replaces Comments: ISC#1 AS Transferor ISC#2 ISC#3 A transferred communication already exists INVITE 1 (S1) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 2 (S3) INVITE 3 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S2) 200 OK (BYE) 200 OK (BYE) BYE (S1) BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 62 Annex A (informative): Bibliography ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 10)". ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 63 History Document history V5.1.1 October 2012 Publication
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	1 Scope	The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the protocol specification as defined in ETSI TS 124 629 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [2].
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	2.1 Normative references	The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 629: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.629 Release 10)". [2] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [3] ISO/IEC 9646-1: "Information technology -- Open systems interconnection -- Conformance testing methodology and framework -- Part 1: General concepts". [4] ISO/IEC 9646-7: "Information technology -- Open systems interconnection -- Conformance testing methodology and framework -- Part 7: Implementation Conformance Statements". [5] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 10)". [6] ETSI TS 124 628: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.628 Release 10)".
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	2.2 Informative references	The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 124 607: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.607 Release 10)". ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 6 [i.2] ETSI TS 124 611: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.611 Release 10)". [i.3] ETSI TS 124 605: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 Release 10)".
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	3 Definitions, symbols and abbreviations
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	3.1 Definitions	For the purposes of the present document, the terms and definitions given in TS 124 629 [1], ETS 300 406 [2], ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply: Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented NOTE: The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, API ICS etc. ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	3.2 Symbols	For the purposes of the present document, the symbols given in [1] apply.
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	3.3 Abbreviations	For the purposes of the present document, the abbreviations given in [1] and the following apply: ICS Implementation Conformance Statement IUT Implementation Under Test PICS Protocol ICS SUT System Under Test UE User Equipment URI Uniform Resource Identifier
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4 PICS proforma for TS 124 629	Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS proforma in this clause so that it can be used for its intended purposes and may further publish the completed PICS.
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.1 Guidance for completing the PICS proforma
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.1.1 Purposes and structure	The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in TS 124 629 [1] may provide information about the implementation in a standardized manner. ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 7 The PICS proforma is subdivided into clauses for the following categories of information: • guidance for completing the PICS proforma; • identification of the implementation; • identification of the TS 124 629 [1]; • global statement of conformance; • roles; • user equipment role; - major capabilities; • network role; - major capabilities.
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.1.2 Abbreviations and conventions	The PICS proforma contained in this clause is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [4]. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". Status column The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column: m mandatory - the capability is required to be supported. o optional - the capability may be supported or not. n/a not applicable - in the given context, it is impossible to use the capability. o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies an unique group of related optional items and the logic of their selection which is defined immediately following the table. ci conditional - the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying an unique conditional status expression which is defined immediately following the table. Reference column The reference column makes reference to TS 124 629 [1], except where explicitly stated otherwise. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [4], are used for the support column: Y or y supported by the implementation. N or n not supported by the implementation. N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status). ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 8 References to items For each possible item answer (answer in the support column) within the PICS proforma a unique reference exists, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/", followed by the item number in the table. If there is more than one support column in a table, the columns are discriminated by letters (a, b, etc.), respectively. EXAMPLE 1: 4.5.1/4 is the reference to the answer of item 4 in table 4.5.1 of clause 4. EXAMPLE 2: 4.6.1/3b is the reference to the second answer (i.e. in the second support column) of item 3 in table 4.6.1 of clause 4. Prerequisite line A prerequisite line takes the form: Prerequisite: <predicate>. A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be completed if the predicate is FALSE.
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.1.3 Instructions for completing the PICS proforma	The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in clause 4.1.2. However, the tables containing in "user role" clause shall only be completed for user implementations, and the tables containing in "network role" clause shall only be completed for network implementations. If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately. More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.2 Identification of the implementation	Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.2.1 Date of the statement	.........................................................................................................................................................................................
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.2.2 Implementation Under Test (IUT) identification	IUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... IUT version: ......................................................................................................................................................................................... ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 9
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.2.3 System Under Test (SUT) identification	SUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Operating system: .........................................................................................................................................................................................
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.2.4 Product supplier	Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... .........................................................................................................................................................................................
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.2.5 Client (if different from product supplier)	Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 10 Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... .........................................................................................................................................................................................
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.2.6 PICS contact person	(A person to contact if there are any queries concerning the content of the ICS) Name: ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... .........................................................................................................................................................................................
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.3 Identification of the TS 124 629	This PICS proforma applies to the following standard: ETSI TS 124 629 (2011-05): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.629 Release 10)".
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.4 Global statement of conformance	Are all mandatory capabilities implemented? (Yes/No) ..................... NOTE: Answering "No" to this question indicates non-conformance to the <reference specification type> specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma. ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 11
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.5 Roles	Table 4.5.1: Roles Item Role Reference Status Support 1 User Equipment 4.4 o.1 2 Network (Application Server) 4.5 o.1 o..1: It is mandatory to support exactly one of these items. Comments:
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.6 User Equipment role	This clause contains the PICS proforma tables related to the User Equipment role. They need to be completed only for user implementations: Prerequisite: 4.5.1/1 -- user role
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.6.1 Major capabilities	Table 4.6.1: Major capabilities Item Item description Reference Status Support 1 Is the blind transfer supported? 5.11.6 [5] o.11 2 Is the assured transfer supported? 5.11.6 [5] o.11 3 Is the consultative transfer supported? 5.11.6 [5] o.11 4 [Transferor] Is the UE able to Issue a REFER request in the original communications dialog to invoke the transfer of the session? 4.5.2.1 c11 5 [Transferee] Is the UE able to handle a received REFER to transfer the current session? 4.5.2.5 [5] o o.11: It is mandatory to support at least one of these items. c11: IF 4.6.1/1 OR 4.6.1/2 OR 4.6.1/3 THEN m ELSE n/a. Comments: ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 12
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.7 Network role	This clause contains the PICS proforma tables related to the Application Server role. They need to be completed only for network implementations: Prerequisite: 4.5.1/2 -- network role
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.7.1 Major capabilities	Table 4.7.1: Major capabilities Item Item description Reference Status Support 1 Is the blind transfer supported? 5.11.6 [5] o.21 2 Is the assured transfer supported? 5.11.6 [5] o.21 3 Is the consultative transfer supported? 5.11.6 [5] o.21 4 The AS initiate the special REFER handling procedures when a 403 Forbidden or 501 Not implemented is received after the REFER request is forwarded to the Transferee? 4.5.2.4.1.2.3, 4.7.2.9.7 [6] o 5 The AS of the initiator of the REFER request that has prior knowledge that the remote party is not allowed to receive or does not support the REFER method, initiates the special REFER handling procedures directly? 4.5.2.4.1.2.3, 4.7.2.9.7 [6] o 6 Does the Transferee AS reject the INVITE request sent to the Transfer Target if the Referred-By header does not match the stored Referred-By header of the received REFER? 4.5.2.7.3 c21 7 Does the Transferee AS replaces the URI of the Referred-By header in the INVITE sent to the Transfer Target with the URI stored from the received REFER request, if there is no match? 4.5.2.7.3 c22 8 Does the Transferee AS inserts a Referred-By header in the INVITE request sent to the Transfer Target if the Referred-By header is absent and the value is equal to the stored value received in the REFER request. 4.5.2.7.3 o o.21: It is mandatory to support at least one of these items. c21: IF NOT 4.7.1/7 THEN o ELSE n/a. c22: IF NOT 4.7.1/6 THEN o ELSE n/a. Comments:
d7be5559bd20fb33f9aa3cf72a47f0b9	101 594-1	4.7.2 Supplementary service capabilities	Table 4.7.2: Supplementary service capabilities Item Item description Reference Status Support 1 Does the network supports the Originating Identification Restriction (OIR) supplementary services? [i.1] o 2 Does the Network supports the Anonymous Communication Rejection (ACR) and Communication Barring (CB) supplementary services? [i.2] o 3 Does the network supports the Conference (CONF) supplementary services? [i.3] o Comments: ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 13 History Document history V5.1.1 October 2012 Publication
e871d60fd728df1e61851585ff9b650b	101 588-2	1 Scope	The present document specifies the test suite structure and test purposes of the Completion of Communications to Busy Subscriber (CCBS) service and the Completion of Communication on no Reply (CCNR) service, based on stage three of the IMS simulation services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP-Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
e871d60fd728df1e61851585ff9b650b	101 588-2	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
e871d60fd728df1e61851585ff9b650b	101 588-2	2.1 Normative references	The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 642: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.642 Release 10)". [2] ETSI TS 101 588-1: "Technical Committee for IMS Network Testing (INT); Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem 3GPP Release 10; Part 1: Protocol Implementation Conformance Statement (PICS)".
e871d60fd728df1e61851585ff9b650b	101 588-2	2.2 Informative references	The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.
e871d60fd728df1e61851585ff9b650b	101 588-2	3 Definitions, symbols and abbreviations
e871d60fd728df1e61851585ff9b650b	101 588-2	3.1 Definitions	For the purposes of the present document, the terms and definitions given in TS 124 642 [1] apply. ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 6
e871d60fd728df1e61851585ff9b650b	101 588-2	3.2 Symbols	For the purposes of the present document, the symbols given in TS 124 642 [1] apply.
e871d60fd728df1e61851585ff9b650b	101 588-2	3.3 Abbreviations	For the purposes of the present document, the abbreviations given in TS 124 642 [1] apply.
e871d60fd728df1e61851585ff9b650b	101 588-2	4 Test Suite Structure (TSS)	Table 4-1: Test Suite Structure CC originating_AS Invocation CC_N01_xxx Revocation CC_N02_xxx Operation CC_N03_xxx terminating_AS possibleIndication CC_N04_xxx Invocation CC_N05_xxx Revocation CC_N06_xxx CCOperation CC_N07_xxx Interaction TIR CC_N08_xxx CDIV CC_N09_xxx
e871d60fd728df1e61851585ff9b650b	101 588-2	4.1 Configuration	The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as described in [1]. The stage 3 description respects the requirements to several network entities and also to requirements regarding to end devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities. Therefore to test the appropriate entities the configurations below are applicable: Testing of the Application Server: This entity is responsible to perform the service. Hence the ISC interface is the appropriate access point. Figure 4-1 points to this. Figure 4-1: Applicable interface to test AS functionalities If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (consider figure 4-2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded. ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 7 Figure 4-2: Applicable interfaces to test using the (generic) NNI interface Testing of User Equipment: There are several requirements regarding to the end devices. Therefore a special configuration appears. User Equipment Implementation under Test Test System Gm Figure 4-3: Applicable configuration to test the User Equipment
e871d60fd728df1e61851585ff9b650b	101 588-2	5 Test Purposes (TP)
e871d60fd728df1e61851585ff9b650b	101 588-2	5.1 Introduction	For each test requirement a TP is defined.
e871d60fd728df1e61851585ff9b650b	101 588-2	5.1.1 TP naming convention	TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 5-1). Table 5-1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "CC" <iut> = type of IUT: U User - equipment N Network <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001 to 999) ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 8
e871d60fd728df1e61851585ff9b650b	101 588-2	5.1.2 Test strategy	As the base standard TS 124 642 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 101 588-1 [2]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered.
e871d60fd728df1e61851585ff9b650b	101 588-2	5.2 Actions at the originating AS
e871d60fd728df1e61851585ff9b650b	101 588-2	5.2.1 CC Invocation	TSS CC/originating_AS/Invocation TP CC_N01_001 Reference 4.5.4.2.1.1.1, 4.5.4.2.1.1.3 Selection expression PICS 4.3.2-1/9 Test purpose Detecting CCNL is possible. Ensure that when an originating user establishes a session to a terminating user not logged in, a 183 (Session Progress) response is forwarded to the originating user if a 480 (Temporarily Unavailable) response has been received. The Application Server provides an announcement. Preconditions: SIP header values: 480 Temporarily Unavailable Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 480 (Temporarily Unavailable) 183 Session Progress ACK Announcement that CC is possible Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_002 Reference 4.5.4.2.1.1.1, 4.5.4.2.1.1.3 Selection expression Test purpose Detecting CCBS is possible. Ensure that when an originating user establishes a session to a terminating user is busy, a 183 (Session Progress) response is forwarded to the originating user if a 486 (Busy Here) response has been received. The Application Server provides an announcement. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=BS Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 486 (Busy Here) 183 Session Progress ACK Announcement that CC is possible Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 9 TSS CC/originating_AS/Invocation TP CC_N01_003 Reference 4.5.4.2.1.1.1, 4.5.4.2.1.1.3 Selection expression Test purpose Detecting CCNR is possible. Ensure that when an originating user establishes a session to a terminating user is busy, a 183 (Session Progress) response is forwarded to the originating user if a 180 (Ringing) response has been received. The Application Server provides an announcement. The Call-Info header is removed from the 180 (Ringing) sent to the originating user. Preconditions: SIP header values: 180 Ringing 1 Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 180 (Ringing) 1 180 (Ringing) Start CCNR-T5 Timeout CCNR-T5 Announcement that CC is possible Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_004 Reference 4.5.4.2.1.1.3 Selection expression PICS 4.3.2-1/9 Test purpose CCNL is possible hence not confirmed. Ensure that when the originating user does not confirm the CCNL indication to invoke the service a 486 (Busy Here) is forwarded to the originating user when Retention timer CC-T1 is expired. Preconditions: SIP header values: 480 Temporarily Unavailable 1 Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 480 (Temporarily Unavailable) 1 183 Session Progress Start CC-T1 ACK Announcement that CC is possible 480 (Temporarily Unavailable) Timeout CC-T1 ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 10 TSS CC/originating_AS/Invocation TP CC_N01_005 Reference 4.5.4.2.1.1.3 Selection expression Test purpose CCBS is possible hence not confirmed. Ensure that when the originating user does not confirm the CCBS indication to invoke the service a 486 (Busy Here) is forwarded to the originating user when Retention timer CC-T1 is expired. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=BS Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 486 (Busy Here) 183 Session Progress Start CC-T1 ACK Announcement that CC is possible 486 (Busy Here) Timeout CC-T1 ACK Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_006 Reference 4.5.4.2.1.1.3 Selection expression Test purpose CCNR is possible hence not confirmed. Ensure that when the originating user does not confirm the CCBS indication to invoke the service a 199 (Early Dialog Terminated) is forwarded to the originating user when Retention timer CC-T1 is expired. Preconditions: SIP header values: 180 Ringing 1 Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 180 (Ringing) 1 180 (Ringing) Start CCNR-T5, CC-T1 Timeout CCNR-T5 Announcement that CC is possible Timeout CC-T1 199 (Early Dialog Terminated) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 11 TSS CC/originating_AS/Invocation TP CC_N01_007 Reference 4.5.4.2.1.1.5, 4.5.4.2.1.1.6 Selection expression NOT PICS 4.3.2.1/10 AND NOT PICS 4.3.2.1/11 Test purpose Successful CCBS request. A 486 (Busy Here) is received from the terminating AS containing a Call-Info header field a purpose parameter set to call-completion and the m parameter is set to BS. Ensure that the AS withholds the 486 and sends a 183 Session Progress and starts to play an announcement to inform the originating user that Call Completion is possible. The originating user activates via inband interaction the CCBS call completion service. Ensure that the AS sends a SUBSCRIBE to the terminating AS. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. The Application Server confirms the successful invocation to the originating user by sending of a 486 (Busy Here) final response. Preconditions: SIP header values: 486 Busy Here 1: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=BS SUBSRIBE sip: T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion NOTIFY Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 486 (Busy Here) 1 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful 486 (Busy Here) 2 ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 12 TSS CC/originating_AS/Invocation TP CC_N01_008 Reference 4.5.4.2.1.1.5, 4.5.4.2.1.1.6 Selection expression PICS 4.3.2.1/10 AND PICS 4.3.2.1/11 Test purpose Successful CCBS request. A 486 (Busy Here) is received from the terminating AS containing a Call-Info header field a purpose parameter set to call-completion and the m parameter is set to BS. Ensure that the AS withholds the 486 and sends a 183 Session Progress and starts to play an announcement to inform the originating user that Call Completion is possible. The originating user activates via inband interaction the CCBS call completion service. Ensure that the AS sends a SUBSCRIBE to the terminating AS. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. The Application Server confirms the successful invocation to the originating user by sending of a 486 (Busy Here) final response. Ensure that a Date header and a Content-Type header containing a message/external- body value are present in the 486 sent to the originating user. Preconditions: SIP header values: 486 Busy Here 1: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=BS SUBSRIBE sip: T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion NOTIFY Event:call-completion Content-Type: application/call-completion cc-state: queued 486 Busy Here 2: Date: <current date and time> Content-Type: message/external-body; access-type=”URL”; URL= < any url > Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 486 (Busy Here) 1 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful 486 (Busy Here) 2 ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 13 TSS CC/originating_AS/Invocation TP CC_N01_009 Reference 4.5.4.2.1.1.1 Selection expression Test purpose CCBS not possible, A CC queue limit has been exceeded. Ensure that the AS does not offer the activation of the call completion service if the user A CCBS queue limit has been exceeded. The 486 is passed through. Preconditions: CCBS queue limit exceeded SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Set the A queue to limit INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK TSS CC/originating_AS/Invocation TP CC_N01_010 Reference 4.5.4.2.1.1.1 Selection expression NOT PICS 4.3.2-1/3 Test purpose CCBS invocation not possible, further identical request (communication parameters). Ensure that the AS does not offer the activation of the CCBS call completion service if a request was activated for an identical communication, determined by the stored basic communication information. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (Gm) SUT SIP 2 (ISC) A successful CCBS request is already invoked INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 14 TSS CC/originating_AS/Invocation TP CC_N01_011 Reference 4.5.4.2.1.2 Selection expression Test purpose Unsuccessful CCBS request. Ensure when the originating user invokes the CCBS service and the Application Server receives a 480 (Temporarily Unavailable) to indicate short term denial or a 403 (Forbidden) to indicate long term denial the originating user receives a confirmation that the CCBS request was not successful. Preconditions: SIP header values: 486 Busy Here 1: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=BS SUBSRIBE sip: T-AS; m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 486 (Busy Here) 1 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE CASE A 480 (Temporarily Unavailable) CASE B 403 (Forbidden) Confirm to the caller that the invocation was not successful 486 (Busy Here) 2 ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 15 TSS CC/originating_AS/Invocation TP CC_N01_012 Reference 4.5.4.2.1.1.5 4.8.1 Selection expression Test purpose CCBS request. Timeout CC-T2. Ensure that the CC request operation timer CC-T2 is started after CCBS request is received from caller. When the timer CC-T2 is expired because no NOTIFY is received from the terminating user as a confirmation that the CCBS request was successful at the terminating AS the CCBS request is rejected. The caller is informed. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted Start Timer CC-T2 ↓ Timeout Timer CC-T2 Confirm to the caller that the invocation was not successful 486 (Busy Here) ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 16 TSS CC/originating_AS/Invocation TP CC_N01_013 Reference 4.5.4.2.1.1.5, 4.5.4.2.1.1.6 Selection expression Test purpose CCNR successful request. A 180 (Ringing) is received from the terminating AS containing a Call-Info header field a purpose parameter set to call-completion and the m parameter is set to BS. Ensure that the Application Server forwards a 180 (Ringing) without the Call-Info header to the originating user and starts to play an announcement to inform the originating user that Call Completion is possible. The originating user activates via inband interaction the CCNR call completion service. Ensure that the AS sends a SUBSCRIBE to the terminating AS. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. The Application Server confirms the successful invocation to the originating user by sending of a 480 (Temporarily Unavailable) final response. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NR SUBSRIBE sip: T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: UE-A; purpose=call-completion;m=NR P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion NOTIFY Event:call-completion Content-Type: application/call-completion cc-state: queued 480 Temporarily Unavailable Date: <current date and time> Content-Type: message/external-body; access-type=”URL”; URL= < any url > Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCNR is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful CANCEL 200 OK CANCEL 480 (Temporarily Unavailable) 487 Request Terminated ACK ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 17 TSS CC/originating_AS/Invocation TP CC_N01_014 Reference 4.5.4.2.1 Selection expression Test purpose CCNR not possible, A CC queue limit has been exceeded. Ensure that the originating AS does not offered the call completion service if a 180 (Ringing) is received and a Call-Info header with a purpose parameter set to call-completion and a m parameter set to NR is received and the CCBS queue limit is exceeded. Preconditions: CCBS queue limit exceeded SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Set the A queue to limit INVITE INVITE 100 Trying 100 Trying 180 Ringing 2 180 Ringing 1 CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK TSS CC/originating_AS/Invocation TP CC_N01_015 Reference 4.5.4.2.1 Selection expression NOT PICS 4.3.2-1/3 Test purpose CCNR invocation not possible, further identical request (communication parameters). Ensure that the AS does not offer the activation of the CCNR call completion service if a request was activated for an identical communication, determined by the stored basic communication information. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) A successful CCNR request is already invoked INVITE INVITE 100 Trying 100 Trying 180 Ringing 2 180 Ringing 1 No offer to invoke CCNR CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 18 TSS CC/originating_AS/Invocation TP CC_N01_016 Reference 4.5.4.2.1.1.4 Selection expression PICS 4.3.2-1/12 Test purpose Communication to user B is cancelled when CCNR is invoked by the originating user. Ensure when the confirmation of the CCNR invocation is received from user A before timeout CC-T1 the Application Server terminated the session with user B by sending a CANCEL request to user B. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCNR is possible Inband-interaction procedures for the CC activation CANCEL 200 OK CANCEL 487 Request Terminated ACK Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_017 Reference 4.5.4.2.1.2 Selection expression Test purpose Unsuccessful CCNR request. Ensure when the originating user invokes the CCNR service and the Application Server receives a 480 (Temporarily Unavailable) to indicate short term denial or a 403 (Forbidden) to indicate long term denial the originating user receives a confirmation that the CCBS requesr was not successful. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NR SUBSRIBE sip: T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=NR P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 180 Ringing 1 180 Ringing 2 Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE CASE A 480 (Temporarily Unavailable) CASE B 403 (Forbidden) Confirm to the caller that the invocation was not successful Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 19 TSS CC/originating_AS/Invocation TP CC_N01_018 Reference 4.5.4.2.1.1.5 4.8.1 Selection expression Test purpose CCNR request. Timeout CC-T2. Ensure that the CC request operation timer CC-T2 is started after CCNR request is received from caller. When the timer CC-T2 is expired because no NOTIFY is received from the terminating user as a confirmation that the CCBS request was successful at the terminating AS the CCNR request is rejected. The caller is informed. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=NR P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted Start Timer CC-T2 ↓ Timeout Timer CC-T2 Confirm to the caller that the invocation was not successful CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 20 TSS CC/originating_AS/Invocation TP CC_N01_019 Reference 4.5.4.2.1.1.5, 4.5.4.2.1.1.6 Selection expression PICS 4.3.2-1/9 Test purpose CCNL successful request. A 480 (Temporarily Unavailable) is received from the terminating AS containing a Call-Info header field a purpose parameter set to call-completion and the m parameter is set to NL. Ensure that the Application Server sends a 183 (Session Progress) to the originating user and starts to play an announcement to inform the originating user that Call Completion is possible. The originating user activates via inband interaction the CCNL call completion service. Ensure that the AS sends a SUBSCRIBE to the terminating AS. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. The Application Server confirms the successful invocation to the originating user by sending of a 480 (Temporarily Unavailable) final response. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NL SUBSRIBE sip: T-AS;m=NL From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: UE-A; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion NOTIFY Event:call-completion Content-Type: application/call-completion cc-state: queued 480 Temporarily Unavailable 2 Date: <current date and time> Content-Type: message/external-body; access-type=”URL”; URL= < any url > Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 480 (Temporarily Unavailable) 1 ACK 183 (Session Progress) Announcement that CCNR is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful 480 (Temporarily Unavailable) 2 ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 21 TSS CC/originating_AS/Invocation TP CC_N01_020 Reference 4.5.4.2.1.1.1 Selection expression PICS 4.3.2-1/9 Test purpose CCNL not possible, A CC queue limit has been exceeded. Ensure that the AS does not offer the activation of the call completion service if the user A CCNL queue limit has been exceeded. The 480 (Temporarily Unavailable) is passed through. Preconditions: CCBS queue limit exceeded SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Set the A queue to limit INVITE INVITE 100 Trying 100 Trying 480 (Temporarily Unavailable) 480 (Temporarily Unavailable) 1 ACK ACK TSS CC/originating_AS/Invocation TP CC_N01_021 Reference 4.5.4.2.1.1.1 Selection expression PICS 4.3.2-1/9 AND NOT PICS 4.3.2-1/3 Test purpose CCNL invocation not possible, further identical request (communication parameters). Ensure that the AS does not offer the activation of the CCNL call completion service if a request was activated for an identical communication, determined by the stored basic communication information. The 480 (Temporarily Unavailable) is passed through. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) A successful CCNL request is already invoked INVITE INVITE 100 Trying 100 Trying 480 (Temporarily Unavailable) 480 (Temporarily Unavailable) 1 ACK ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 22 TSS CC/originating_AS/Invocation TP CC_N01_022 Reference 4.5.4.2.1.2 Selection expression PICS 4.3.2-1/9 Test purpose Unsuccessful CCNL request. Ensure when the originating user invokes the CCNL service and the Application Server receives a 480 (Temporarily Unavailable) to indicate short term denial or a 403 (Forbidden) to indicate long term denial the originating user receives a confirmation that the CCNL requesr was not successful. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE-B or T-AS>;purpose=call-completion;m=NL SUBSRIBE sip: T-AS;m=NL From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 480 (Temporarily Unavailable) 1 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE CASE A 480 (Temporarily Unavailable) CASE B 403 (Forbidden) Confirm to the caller that the invocation was not successful 480 (Temporarily Unavailable) 2 ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 23 TSS CC/originating_AS/Invocation TP CC_N01_023 Reference 4.5.4.2.1.1.5 4.8.1 Selection expression PICS 4.3.2-1/9 Test purpose CCNL request. Timeout CC-T2. Ensure that the CC request operation timer CC-T2 is started after CCNL request is received from caller. When the timer CC-T2 is expired because no NOTIFY is received from the terminating user as a confirmation that the CCNL request was successful at the terminating AS the CCNL request is rejected. The caller is informed. Preconditions: SIP header values: 480 Temporarily Unavailable: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL SUBSRIBE sip:T-AS;m=NL From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Comments: SIP 1 (Gm) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 480 (Temporarily Unavailable) 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted Start Timer CC-T2 ↓ Timeout Timer CC-T2 Confirm to the caller that the invocation was not successful 480 (Temporarily Unavailable) ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 24
e871d60fd728df1e61851585ff9b650b	101 588-2	5.2.2 CC Revocation	TSS CC/originating_AS/Revocation TP CC_N02_001 Reference 4.5.4.2.2.1.2 Selection expression PICS 4.3.2-1/8 Test purpose CCBS revocation request received from the user. Ensure that the originating AS sends a SUBCRIBE request and the Expires header is set to zero when the originating user revokes the outstanding CCBS request. The revocation is performed by an INVITE request and the userpart of the Request URI is set to the service code command to cancel a CCBS request. Preconditions: SIP header values: INVITE: Request URI= Service Code Command (revoke CCBS request) SUBSRIBE sip:T-AS;m=BS Call.Info: UE-A (Public user identity); purpose=call-completion;m=BS P-Assertd-Identity: UE-A (Public user identity) Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCBS request Revocation request from the user INVITE 200 OK INVITE ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the revocation was successful BYE 200 OK BYE ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 25 TSS CC/originating_AS/Revocation TP CC_N02_002 Reference 4.5.4.2.2.1.2 Selection expression PICS 4.3.2-1/8 Test purpose CCNR revocation request received from the user. Ensure that the originating AS sends a SUBCRIBE request and the Expires header is set to zero when the originating user revokes the outstanding CCNR request. The revocation is performed by an INVITE request and the userpart of the Request URI is set to the service code command to cancel a CCNR request. Preconditions: SIP header values: INVITE: Request URI= Service Code Command (revoke CCNR request) SUBSRIBE sip:T-AS;m=NR Call.Info: UE-A (Public user identity); purpose=call-completion;m=NR P-Assertd-Identity: UE-A (Public user identity) Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCNR request Revocation request from the user INVITE 200 OK INVITE ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the revocation was successful BYE 200 OK BYE ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 26 TSS CC/originating_AS/Revocation TP CC_N02_003 Reference 4.5.4.2.2.1.2 Selection expression PICS 4.3.2-1/8 AND PICS 4.3.2-1/9 Test purpose CCNL revocation request received from the user. Ensure that the originating AS sends a SUBCRIBE request and the Expires header is set to zero when the originating user revokes the outstanding CCNL request. The revocation is performed by an INVITE request and the userpart of the Request URI is set to the service code command to cancel a CCNL request. Preconditions: SIP header values: INVITE: Request URI= Service Code Command (revoke CCNL request) SUBSRIBE sip:T-AS; m=NL Call.Info: UE-A (Public user identity); purpose=call-completion;m=NL P-Assertd-Identity: UE-A (Public user identity) Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCNL request Revocation request from the user INVITE 200 OK INVITE ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the revocation was successful BYE 200 OK BYE ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 27 TSS CC/originating_AS/Revocation TP CC_N02_004 Reference 4.5.4.2.2.1.3 Selection expression Test purpose CCBS revocation caused by timer expiry CC-T3. Ensure that the originating AS revokes the outstanding CCBS request if the CC service duration timer CC-T3 expires. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=BS Event:call-completion Call.Info: UE-A (Public user identity); purpose=call-completion;m=NL P-Assertd-Identity: UE-A (Public user identity) Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCBS request Start CC-T3 Timeout CC-T3 SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY TSS CC/originating_AS/Revocation TP CC_N02_005 Reference 4.5.4.2.2.1.3 Selection expression Test purpose CCNR revocation caused by timer expiry CC-T3. Ensure that the originating AS revokes the outstanding CCNR request if the CC service duration timer CC-T3 expires. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NR Call.Info: UE-A (Public user identity); purpose=call-completion;m=NR P-Assertd-Identity: UE-A (Public user identity) Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCBS request Start CC-T3 Timeout CC-T3 SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 28 TSS CC/originating_AS/Revocation TP CC_N02_006 Reference 4.5.4.2.2.1.3 Selection expression PICS 4.3.2-1/9 Test purpose CCNL revocation caused by timer expiry CC-T3. Ensure that the originating AS revokes the outstanding CCNL request if the CC service duration timer CC-T3 expires. Preconditions: SIP header values: SUBSRIBE sip:T-AS Call.Info: UE-A (Public user identity); purpose=call-completion;m=NL P-Assertd-Identity: UE-A (Public user identity) Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCNL request Start CC-T3 Timeout CC-T3 SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY TSS CC/originating_AS/Revocation TP CC_N02_007 Reference 4.5.4.2.2.2 Selection expression Test purpose CCBS revocation caused by terminating AS. Ensure that the originating AS revokes the outstanding CCBS request if the AS receives a NOTIFY request from the terminating user and the the Subscription-State header field set to "terminated"; and the "reason" Subscription-State header field parameter set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCBS request NOTIFY 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 29 TSS CC/originating_AS/Revocation TP CC_N02_008 Reference 4.5.4.2.2.2 Selection expression Test purpose CCNR revocation caused by terminating AS. Ensure that the originating AS revokes the outstanding CCNR request if the AS receives a NOTIFY request from the terminating user and the the Subscription-State header field set to "terminated"; and the "reason" Subscription-State header field parameter set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCNR request NOTIFY 200 OK NOTIFY TSS CC/originating_AS/Revocation TP CC_N02_009 Reference 4.5.4.2.2.2 Selection expression PICS 4.3.2-1/9 Test purpose CCNL revocation caused by terminating AS. Ensure that the originating AS revokes the outstanding CCNL request if the AS receives a NOTIFY request from the terminating user and the the Subscription-State header field set to "terminated"; and the "reason" Subscription-State header field parameter set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCNL request NOTIFY 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 30
e871d60fd728df1e61851585ff9b650b	101 588-2	5.2.3 CC Operation	TSS CC/originating_AS/Operation TP CC_N03_001 Reference 4.5.4.2.3.1 Selection expression NOT PICS 4.3.2-1/4 Test purpose CCBS Recall successful by sending a REFER request to the originating user. Ensure that the originating AS starts the CCBS recall procedure when the indication that the callee is available to recall indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". A REFER request is sent to the caller. The m parameter of the Request line is set to BS in the INVITE request sent to the callee as the result of the received INVITE request from the caller. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=BS Refer-To; UE B; method=INVITE INVITE 1: sip: UE B; m=BS From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY (200) NOTIFY (200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 31 TSS CC/originating_AS/Operation TP CC_N03_002 Reference 4.5.4.2.3.1 Selection expression NOT PICS 4.3.2-1/4 Test purpose CCNR Recall successful by sending a REFER request to the originating user. Ensure that the originating AS starts the CCNR recall procedure when the indication that the callee is available to recall indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". A REFER request is sent to the caller. The m parameter of the Request line is set to NR in the INVITE request sent to the callee as the result of the received INVITE request from the caller. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NR Refer-To; UE B; method=INVITE INVITE 1: sip: UE B; m=NR From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=NR NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE INVITE 1 180 Ringing 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY (200) NOTIFY (200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 32 TSS CC/originating_AS/Operation TP CC_N03_003 Reference 4.5.4.2.3.1 Selection expression NOT PICS 4.3.2-1/4 AND PICS 4.3.2-1/9 Test purpose CCNL Recall successful by sending a REFER request to the originating user. Ensure that the originating AS starts the CCNL recall procedure when the indication that the callee is available to recall indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". A REFER request is sent to the caller. The m parameter of the Request line is set to NL in the INVITE request sent to the callee as the result of the received INVITE request from the caller. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NL Refer-To; UE B; method=INVITE INVITE 1: sip: UE B; m=NL From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=NL NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCNL request CCNL request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE INVITE 1 180 Ringing 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY (200) NOTIFY (200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 33 TSS CC/originating_AS/Operation TP CC_N03_004 Reference 4.5.4.2.3.1 Selection expression PICS 4.3.2-1/4 Test purpose CCBS Recall successful by using the special REFER interworking. Sending an INVITE request to the originating user. Ensure that the originating AS starts the CCBS recall procedure when the indication that the callee is available to recall indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". An INVITE request is sent to the caller. When the session with the caller is answered, an INVITE request is sent to the callee and the m parameter in the Request line is set to BS. When the callee answers the session, caller and callee are connected. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 2: sip: UE B; m=BS From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 1 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK INVITE 2 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 34 TSS CC/originating_AS/Operation TP CC_N03_005 Reference 4.5.4.2.3.1 Selection expression PICS 4.3.2-1/4 Test purpose CCNR Recall successful by using the special REFER interworking. Sending an INVITE request to the originating user. Ensure that the originating AS starts the CCNR recall procedure when the indication that the callee is available to recall indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". An INVITE request is sent to the caller. When the session with the caller is answered, an INVITE request is sent to the callee and the m parameter in the Request line is set to NR. When the callee answers the session, caller and callee are connected. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 2: sip: UE B; m=NR From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=NR NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 1 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE INVITE 2 ACK ACK 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 35 TSS CC/originating_AS/Operation TP CC_N03_006 Reference 4.5.4.2.3.1 Selection expression PICS 4.3.2-1/4 AND PICS 4.3.2-1/9 Test purpose CCNL Recall successful by using the special REFER interworking. Sending an INVITE request to the originating user. Ensure that the originating AS starts the CCNL recall procedure when the indication that the callee is available to recall indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". An INVITE request is sent to the caller. When the session with the caller is answered, an INVITE request is sent to the callee and the m parameter in the Request line is set to NL. When the callee answers the session, caller and callee are connected. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 2: sip: UE B; m=NL From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=NL NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCNL request CCNL request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 1 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE INVITE 2 ACK ACK 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 36 TSS CC/originating_AS/Operation TP CC_N03_007 Reference 4.5.4.2.3.2.1 Selection expression Test purpose CCBS Recall not accepted by originating user. CC-T4 expires. Ensure that the originating AS revokes the outstanding CCBS request after having received the notification that the CCBS recall to the callee is possible and the caller does not accept the recall offer. A SUBCRIBE is sent to the terminating AS and the Expires header is set to zero. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=BS Refer-To; UE B method=INVITE INVITE: sip: UE A; m=BS Call.Info: UE-A (from the From header of original communication); purpose=call-completion;m=BS From: UE B SUBSRIBE sip:T-AS Call.Info: UE-A (Public user identity); purpose=call-completion;m=NL P-Assertd-Identity: UE-A (Public user identity) Event:call-completion Expires=0 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted Start Timer CC-T4 CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Start Timer CC-T4 ↓ Timeout Timer CC-T4 SUBSCRIBE SUBSCRIBE 202 Accepted 202 Accepted NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 37 TSS CC/originating_AS/Operation TP CC_N03_008 Reference 4.5.4.2.3.2.1 Selection expression Test purpose CCNR Recall not accepted by originating user. Ensure that the originating AS revokes the outstanding CCNR request after having received the notification that the CCNR recall to the callee is possible and the caller does not accept the recall offer. A SUBCRIBE is sent to the terminating AS and the Expires header is set to zero. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NR Refer-To; UE B; method=INVITE INVITE: sip: UE A; m=NR Call.Info: UE-A (from the From header of original communication); purpose=call-completion;m=NR From: UE B SUBSRIBE sip:T-AS Call.Info: UE-A (Public user identity); purpose=call-completion;m=NL P-Assertd-Identity: UE-A (Public user identity) Event:call-completion Expires=0 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted Start Timer CC-T4 CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Start Timer CC-T4 ↓ Timeout Timer CC-T4 SUBSCRIBE SUBSCRIBE 202 Accepted 202 Accepted NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 38 TSS CC/originating_AS/Operation TP CC_N03_009 Reference 4.5.4.2.3.2.1 Selection expression PICS 4.3.2-1/9 Test purpose CCNL Recall not accepted by originating user. Ensure that the originating AS revokes the outstanding CCNL request after having received the notification that the CCNL recall to the callee is possible and the caller does not accept the recall offer. A SUBCRIBE is sent to the terminating AS and the Expires header is set to zero. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NL Refer-To; UE B; method=INVITE INVITE: sip: UE A; m=NL Call.Info: UE-A (from the From header of original communication); purpose=call-completion;m=NL From: UE B SUBSRIBE sip:T-AS Call.Info: UE-A (Public user identity); purpose=call-completion;m=NL P-Assertd-Identity: UE-A (Public user identity) Event:call-completion Expires=0 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted Start Timer CC-T4 CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Start Timer CC-T4 ↓ Timeout Timer CC-T4 SUBSCRIBE SUBSCRIBE 202 Accepted 202 Accepted NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 39 TSS CC/originating_AS/Operation TP CC_N03_010 Reference 4.5.4.2.3.2.2 Selection expression NOT PICS 4.3.2-1/4 Test purpose CCBS Caller is found to be busy, when a CC recall notification has been received. Ensure that when the caller is found to be busy, when a CCBS CC recall notification has been received, then the originating AS shall suspend the CC request until the caller becomes not busy. The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "closed". The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "open" when the caller is no longer busy. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=BS Refer-To; UE B; method=INVITE INVITE: sip: UE A; m=BS Call.Info: UE-A (from the From header of original communication); purpose=call-completion;m=BS From: UE B PUBLISH 1: sip T-AS Call.Info: UE-A (Public user identity); purpose=call-completion;m=BS P-Assertd-Identity: UE A (Public user identity) Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>closed</basic> NOTIFY 2 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: queued PUBLISH 2: sip T-AS To: UE B Call.Info: UE-A (Public user identity); purpose=call-completion;m=BS P-Assertd-Identity: UE A (Public user identity) Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>open</basic> ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 40 Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall Establish a session to SIP 2 (make UE A busy) NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 486 (Busy Here) 486 (Busy Here) PUBLISH 1 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY CASE B INVITE INVITE 486 (Busy Here) 486 (Busy Here) PUBLISH 1 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Disconnect session to SIP 2 (make UE A available) PUBLISH 2 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 41 TSS CC/originating_AS/Operation TP CC_N03_011 Reference 4.5.4.2.3.2.2 Selection expression NOT PICS 4.3.2-1/4 Test purpose CCNR Caller is found to be busy, when a CC recall notification has been received. Ensure that when the caller is found to be busy, when a CCNR CC recall notification has been received, then the originating AS shall suspend the CC request until the caller becomes not busy. The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "closed". The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "open" when the caller is no longer busy. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NR Refer-To; UE B; method=INVITE INVITE: sip: UE A; m=NR Call.Info: UE-A (from the From header of original communication); purpose=call-completion;m=NR From: UE B PUBLISH 1: sip T-AS Call.Info: UE-A (Public user identity); purpose=call-completion;m=NR P-Assertd-Identity: UE A (Public user identity) Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>closed</basic> NOTIFY 2 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: queued PUBLISH 2: sip T-AS To: UE B Call.Info: UE-A (Public user identity); purpose=call-completion;m=NR P-Assertd-Identity: UE A (Public user identity) Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>open</basic> ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 42 Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS Terminating user available for recall Establish a session to SIP 2 (make UE A busy) NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 486 (Busy Here) 486 (Busy Here) PUBLISH 1 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY CASE B INVITE INVITE 486 (Busy Here) 486 (Busy Here) PUBLISH 1 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Disconnect session to SIP 2 (make UE A available) PUBLISH 2 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 43 TSS CC/originating_AS/Operation TP CC_N03_012 Reference 4.5.4.2.3.2.2 Selection expression NOT PICS 4.3.2-1/4PICS 4.3.2-1/9 Test purpose CCNL Caller is found to be busy, when a CC recall notification has been received. Ensure that when the caller is found to be busy, when a CCNL CC recall notification has been received, then the originating AS shall suspend the CC request until the caller becomes not busy. The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "closed". The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "open" when the caller is no longer busy. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NL Refer-To; UE B; method=INVITE INVITE: sip: UE A; m=NL Call.Info: UE-A (from the From header of original communication); purpose=call-completion;m=NL From: UE B PUBLISH 1: sip T-AS Call.Info: UE-A (Public user identity); purpose=call-completion;m=NL P-Assertd-Identity: UE A (Public user identity) Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>closed</basic> NOTIFY 2 sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: queued PUBLISH 2: sip T-AS To: UE B Call.Info: UE-A (Public user identity); purpose=call-completion;m=NL P-Assertd-Identity: UE A (Public user identity) Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>open</basic> ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 44 Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCNL request CCNL request confirmed by AS Terminating user available for recall Establish a session to SIP 2 (make UE A busy) NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 486 (Busy Here) 486 (Busy Here) PUBLISH 1 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY CASE B INVITE INVITE 486 (Busy Here) 486 (Busy Here) PUBLISH 1 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Disconnect session to SIP 2 (make UE A available) PUBLISH 2 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/originating_AS/Operation TP CC_N03_013 Reference 4.5.4.2.3.2.3 Selection expression NOT PICS 4.3.2-1/3 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCBS again. The two communications are identical. The AS discards the current request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCBS) again then the originating AS retains the original request and discards the current request and informs the caller that the request has not been accepted because a CC request had already been stored against the requested callee. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) 183 Session Progress 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation Announcement that CCBS is not invoked Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 45 TSS CC/originating_AS/Operation TP CC_N03_014 Reference 4.5.4.2.3.2.3 Selection expression NOT PICS 4.3.2-1/3 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCNR again. The two communications are identical. The AS discards the current request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCNR) again then the originating AS retains the original request and discards the current request and informs the caller that the request has not been accepted because a CC request had already been stored against the requested callee. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCNR is possible Inband-interaction procedures for the CC activation Announcement that CCBS is not invoked CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK Apply post test routine TSS CC/originating_AS/Operation TP CC_N03_015 Reference 4.5.4.2.3.2.3 Selection expression PICS 4.3.2-1/9 AND NOT PICS 4.3.2-1/3 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCNL again. The two communications are identical. The AS discards the current request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCNL) again then the originating AS retains the original request and discards the current request and informs the caller that the request has not been accepted because a CC request had already been stored against the requested callee. Preconditions: SIP header values: 480 Temporarily Unavailable: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS INVITE INVITE 100 Trying 100 Trying 480 (Temporarily Unavailable) 480 (Temporarily Unavailable) 183 Session Progress 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation Announcement that CCBS is not invoked Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 46 TSS CC/originating_AS/Operation TP CC_N03_016 Reference 4.5.4.2.3.2.3 Selection expression PICS 4.3.2-1/3 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCBS again. The two communications are identical. The AS treat this as a new CC request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCBS) again, the originating AS shall treat this as a new CC request, A SUBSRIBE request is sent to the terminating AS indicating a CCBS request - a m parameter set to "BS" is attached at the Request line. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) 183 Session Progress 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 47 TSS CC/originating_AS/Operation TP CC_N03_017 Reference 4.5.4.2.3.2.3 Selection expression PICS 4.3.2-1/4 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCNR again. The two communications are identical. The AS treat this as a new CC request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCNR) again, the originating AS shall treat this as a new CC request, A SUBSRIBE request is sent to the terminating AS indicating a CCBS request - a m parameter set to "NR" is attached at the Request line. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=NR P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCNR is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 48 TSS CC/originating_AS/Operation TP CC_N03_018 Reference 4.5.4.2.3.2.3 Selection expression PICS 4.3.2-1/3 AND PICS 4.3.2-1/9 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCNL again. The two communications are identical. The AS treats this as a new CC request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCNL) again, the originating AS shall treat this as a new CC request, A SUBSRIBE request is sent to the terminating AS indicating a CCNL request - a m parameter set to "NL" is attached at the Request line. Preconditions: SIP header values: 480 Temporarily Unavailable: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL SUBSRIBE sip:T-AS;m=NL From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS INVITE INVITE 100 Trying 100 Trying 480 (Temporarily Unavailable) 480 (Temporarily Unavailable) 183 Session Progress 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 49
e871d60fd728df1e61851585ff9b650b	101 588-2	5.3 Actions at the terminating AS
e871d60fd728df1e61851585ff9b650b	101 588-2	5.3.1 CC possible indication	TSS CC/terminating_AS/possibleIndication TP CC_N04_001 Reference 4.5.4.3.1.1 Selection expression Test purpose The terminating AS inserts a Call-Info header in the 486 final response received from the terminating user. Ensure that the terminating AS inserts a Call-Info header and the purpose parameter is set to call-completion and the m parameter is set to BS in the 486 (Busy Here) received from the callee and forwards to the originating AS. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_002 Reference 4.5.4.3.1.1 Selection expression Test purpose The terminating AS inserts a Call-Info header in the 486 final response in case of NDUB. Ensure that the terminating AS in case of NDUB sends a 486 (Busy Here) containing a Call-Info header and the purpose parameter is set to call-completion and the m parameter is set to BS to the originating AS. Preconditions: Callee is network determined user busy SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE 100 Trying 486 (Busy Here) 1 ACK Apply post test routine TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_003 Reference 4.5.4.3.1.1 Selection expression Test purpose The terminating AS inserts a Call-Info header in the 180 provisional response. Ensure that the terminating AS inserts a Call-Info header in the 180 (Ringing) and the purpose parameter is set to call-completion and the m parameter is set to NR received from the callee and forwards to the originating AS. Preconditions: SIP header values: 180 (Ringing) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 50 TSS CC/terminating_AS/possibleIndication TP CC_N04_004 Reference 4.5.4.3.1.1 Selection expression PICS 4.3.2-1/9 Test purpose The terminating AS inserts a Call-Info header in the 480 final response if the terminating user is not logged-in. Ensure that the terminating AS inserts a Call-Info header and the purpose parameter is set to call-completion and the m parameter is set to NL in the 480 (Temporarily Unavailable) if the terminating user is not logged-in and forwards to the originating AS. Preconditions: SIP header values: 480 Temporarily Unavailable: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE 100 Trying 480 (Temporarily Unavailable) ACK Apply post test routine TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_005 Reference 4.5.4.3.1.1 Selection expression Test purpose Terminating user does not subscribe to the CCBS service. No Call-Info header field included. Ensure that no Call-Info header is included in the 486 (Busy Here) If the terminating AS knows that the CC is not possible on destination B (callee). Preconditions: Terminating user does not subscribe to the CC service SIP header values: 486 (Busy Here) 1: Call-Info not included Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_006 Reference 4.5.4.3.1.1 Selection expression Test purpose Terminating user does not subscribe to the CCNR service. No Call-Info header field included. Ensure that no Call-Info header is included in the 180 (Ringing) If the terminating AS knows that the CC is not possible on destination B (callee). Preconditions: Terminating user does not subscribe to the CC service SIP header values: 180 (Ringing) 1: Call-Info not included Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 51 TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_007 Reference 4.5.4.3.1.1 Selection expression PICS 4.3.2-1/9 Test purpose Terminating user does not subscribe to the CCNL service. No Call-Info header field included. Ensure that no Call-Info header is included in the 480 (Temporarily Unavailable) If the terminating AS knows that the CC is not possible on destination B (callee) and the terminating user is not logged-in. Preconditions: Terminating user does not subscribe to the CC service SIP header values: 480 Temporarily Unavailable: Call-Info not included Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE 100 Trying 480 (Temporarily Unavailable) ACK Apply post test routine
e871d60fd728df1e61851585ff9b650b	101 588-2	5.3.2 CC Invocation	TSS CC/terminating_AS/Invocation TP CC_N05_001 Reference 4.5.4.3.2.1 Selection expression Test purpose CCBS service invocation successful at the terminating AS. Ensure that the terminating AS is able to queue the CCBS request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion 202 Accepted Expires: ≤ value received in SUBSRIBE NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 52 TSS CC/terminating_AS/Invocation TP CC_N05_002 Reference 4.5.4.3.2.1 Selection expression Test purpose CCNR service invocation successful at the terminating AS. Ensure that the terminating AS is able to queue the CCNR request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=NR P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion 202 Accepted Expires: ≤ value received in SUBSRIBE NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 53 TSS CC/terminating_AS/Invocation TP CC_N05_003 Reference 4.5.4.3.2.1 Selection expression PICS 4.3.2-1/9 Test purpose CCNL service invocation successful at the terminating AS. Ensure that the terminating AS is able to queue the CCNL request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued. Preconditions: SIP header values: 480 (Temporarily Unavailable) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL SUBSRIBE sip:T-AS;m=NL From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion 202 Accepted Expires: ≤ value received in SUBSRIBE NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 480 (Temporarily Unavailable) 1 480 (Temporarily Unavailable) ACK ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 54 TSS CC/terminating_AS/Invocation TP CC_N05_004 Reference 4.5.4.3.2.2 Selection expression Test purpose CCBS service invocation unsuccessful at the terminating AS. Maximum number of queue entries is reached. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCBS invoke received from the originating AS with a 480 (Temporarily Unavailable) if the callee's B queue limit is reached. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Set the B queue to limit INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK SUBSCRIBE 480 Temporarily Unavailable Apply post test routine TSS CC/terminating_AS/Invocation TP CC_N05_005 Reference 4.5.4.3.2.2 Selection expression Test purpose CCBS service invocation unsuccessful at the terminating AS. No CC queue for the terminatin user available. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCBS invoke received from the originating AS with a 403 Forbidden if no CC queue is available for the requested CC service at the terminating AS for the terminating user. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE B> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK SUBSCRIBE 403 Forbidden Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 55 TSS CC/terminating_AS/Invocation TP CC_N05_006 Reference 4.5.4.3.2.2 Selection expression Test purpose CCNR service invocation unsuccessful at the terminating AS. Maximum number of queue entries is reached. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCNR invoke received from the originating AS with a 480 (Temporarily Unavailable) if the callee's B queue limit is reached. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Set the B queue to limit INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing SUBSCRIBE 480 Temporarily Unavailable Apply post test routine TSS CC/terminating_AS/Invocation TP CC_N05_007 Reference 4.5.4.3.2.2 Selection expression Test purpose CCNR service invocation unsuccessful at the terminating AS. No CC queue for the terminatin user available. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCNR invoke received from the originating AS with a 403 Forbidden if no CC queue is available for the requested CC service at the terminating AS. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE B> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 180 (Ringing) SUBSCRIBE 403 Forbidden Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 56 TSS CC/terminating_AS/Invocation TP CC_N05_008 Reference 4.5.4.3.2.2 Selection expression PICS 4.3.2-1/9 Test purpose CCNL service invocation unsuccessful at the terminating AS. Maximum number of queue entries is reached. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCNL invoke received from the originating AS with a 480 (Temporarily Unavailable) if the callee's B queue limit is reached. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NL From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Set the B queue to limit INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK SUBSCRIBE 480 Temporarily Unavailable Apply post test routine TSS CC/terminating_AS/Invocation TP CC_N05_009 Reference 4.5.4.3.2.2 Selection expression PICS 4.3.2-1/9 Test purpose CCNL service invocation unsuccessful at the terminating AS. No CC queue for the terminatin user available. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCNL invoke received from the originating AS with a 403 Forbidden if no CC queue is available for the requested CC service at the terminating AS for the terminating user. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE B> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK SUBSCRIBE 403 Forbidden Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 57 TSS CC/terminating_AS/Invocation TP CC_N05_010 Reference 4.5.4.3.2.1 Selection expression PICS 4.3.2-1/2 Test purpose CCBS service invocation successful at the terminating AS. Retain option supported. Ensure that the terminating AS is able to queue the CCBS request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued and the service-retention header is present and set to 'true'. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued cc-service-retention: true Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 58 TSS CC/terminating_AS/Invocation TP CC_N05_0011 Reference 4.5.4.3.2.1 Selection expression NOT PICS 4.3.2-1/2 Test purpose CCNR service invocation successful at the terminating AS. Retain option not supported. Ensure that the terminating AS is able to queue the CCBS request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued and the service-retention header is not present. Preconditions: SIP header values: 486 Busy Here 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 59 TSS CC/terminating_AS/Invocation TP CC_N05_012 Reference 4.5.4.3.2.1 Selection expression PICS 4.3.2-1/2 Test purpose CCNR service invocation successful at the terminating AS. Retain option supported. Ensure that the terminating AS is able to queue the CCNR request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued and the service-retention header is present and set to 'true'. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=NR P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued cc-service-retention: true Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 60 TSS CC/terminating_AS/Invocation TP CC_N05_0013 Reference 4.5.4.3.2.1 Selection expression NOT PICS 4.3.2-1/2 Test purpose CCNR service invocation successful at the terminating AS. Retain option not supported. Ensure that the terminating AS is able to queue the CCNR request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued and the service-retention header is not present. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=NR P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 61 TSS CC/terminating_AS/Invocation TP CC_N05_014 Reference 4.5.4.3.2.1 Selection expression PICS 4.3.2-1/2 AND PICS 4.3.2-1/9 Test purpose CCNL service invocation successful at the terminating AS. Retain option supported. Ensure that the terminating AS is able to queue the CCNL request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued and the service-retention header is present and set to 'true'. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL SUBSRIBE sip:T-AS;m=NL From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued cc-service-retention: true Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 480 (Temporarily Unavailable) 1 480 (Temporarily Unavailable) ACK ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 62 TSS CC/terminating_AS/Invocation TP CC_N05_0015 Reference 4.5.4.3.2.1 Selection expression NOT PICS 4.3.2-1/2 AND PICS 4.3.2-1/9 Test purpose CCNL service invocation successful at the terminating AS. Retain option not supported. Ensure that the terminating AS is able to queue the CCNL request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued and the service-retention header is not present. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NL SUBSRIBE sip:T-AS;m=NL From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: active;expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) INVITE INVITE 100 Trying 100 Trying 480 (Temporarily Unavailable) 1 480 (Temporarily Unavailable) ACK ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 63
e871d60fd728df1e61851585ff9b650b	101 588-2	5.3.3 CC Revocation	TSS CC/terminating_AS/Revocation TP CC_N06_001 Reference 4.5.4.3.3.1 Selection expression Test purpose CCBS service revocation successful at the terminating AS. Ensure that the terminating AS is able to respond a NOTIFY request and the Subscription-State header is set to terminated and the reason parameter is set to timeout for a CCBS queue entry if a SUBSCRIBE request is received and the Expires header is set to '0'. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Call.Info: <UE-A>; purpose=call-completion;m=BS P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Expires=0 NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 64 TSS CC/terminating_AS/Revocation TP CC_N06_002 Reference 4.5.4.3.3.1 Selection expression Test purpose CCNR service revocation successful at the terminating AS. Ensure that the terminating AS is able to respond a NOTIFY request and the Subscription-State header is set to terminated and the reason parameter is set to timeout for a CCNR queue entry if a SUBSCRIBE request is received and the Expires header is set to '0'. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=NR P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/terminating_AS/Revocation TP CC_N06_003 Reference 4.5.4.3.3.1 Selection expression PICS 4.3.2-1/9 Test purpose CCNL service revocation successful at the terminating AS. Ensure that the terminating AS is able to respond a NOTIFY request and the Subscription-State header is set to terminated and the reason parameter is set to timeout for a CCNL queue entry if a SUBSCRIBE request is received and the Expires header is set to '0'. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NL From:<UE-A> To:<UE-B> Call.Info: <UE-A>; purpose=call-completion;m=NL P-Assertd-Identity: UE-A Expires: CC-T3 Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=timeout Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 65 TSS CC/terminating_AS/Revocation TP CC_N06_004 Reference 4.5.4.3.3.2 Selection expression Test purpose CCBS service revocation at the terminating AS. CC-T7 expires. Ensure that the terminating AS is able to revoke a CCBS queue entry if the CC service duration timer CC-T7 expires. A NOTIFY request is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason header is set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Start CC-T7 ↓ CC-T7 expires NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/terminating_AS/Revocation TP CC_N06_005 Reference 4.5.4.3.3.2 Selection expression Test purpose CCNR service revocation at the terminating AS. CC-T7 expires. Ensure that the terminating AS is able to revoke a CCNR queue entry if the CC service duration timer CC-T7 expires. A NOTIFY request is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason header is set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Start CC-T7 ↓ CC-T7 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 66 TSS CC/terminating_AS/Revocation TP CC_N06_006 Reference 4.5.4.3.3.2 Selection expression PICS 4.3.2-1/9 Test purpose CCNL service revocation at the terminating AS. CC-T7 expires. Ensure that the terminating AS is able to revoke a CCNL queue entry if the CC service duration timer CC-T7 expires. A NOTIFY request is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason header is set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Start CC-T7 ↓ CC-T7 expires NOTIFY 200 OK NOTIFY Apply post test routine
e871d60fd728df1e61851585ff9b650b	101 588-2	5.3.4 CC Operation	TSS CC/terminating_AS/CCOperation TP CC_N07_001 Reference 4.5.4.3.4.1.1, 4.5.4.3.4.1.2 Selection expression Test purpose Callee becomes not busy, CCBS recall procedure performed. Ensure that the terminating AS starts the call completion recall procedure if the callee becomes not busy. The terminating AS starts the Destination B idle guard timer CC-T8. When the timer CC-T8 expires, a NOTIFY request is sent to the originating AS. The state header in the call-completion MIME body is set to "ready". Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: active; expires=< any value > Content-Type: application/call-completion cc-state: ready Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 67 TSS CC/terminating_AS/CCOperation TP CC_N07_002 Reference 4.5.4.3.4.1.1, 4.5.4.3.4.1.2 Selection expression Test purpose Callee becomes not busy after having initiated an activity, CCNR recall procedure performed. Ensure that the terminating AS starts the call completion recall procedure if the callee is having initiated an activity. The terminating AS starts the Destination B idle guard timer CC-T8. When the timer CC-T8 expires, a NOTIFY request is sent to the originating AS. The state header in the call-completion MIME body is set to "ready". Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: active; expires=< any value > Content-Type: application/call-completion cc-state: ready Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/terminating_AS/CCOperation TP CC_N07_003 Reference 4.5.4.3.4.1.1, 4.5.4.3.4.1.2 Selection expression PICS 4.3.2-1/9 Test purpose Callee becomes not busy after is logged-in, CCNL recall procedure performed. Ensure that the terminating AS starts the call completion recall procedure if the callee is having initiated an activity. The terminating AS starts the Destination B idle guard timer CC-T8. When the timer CC-T8 expires, a NOTIFY request is sent to the originating AS. The state header in the call-completion MIME body is set to "ready". Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: active; expires=< any value > Content-Type: application/call-completion cc-state: ready Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNL request Callee is logged-in Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 68 TSS CC/terminating_AS/CCOperation TP CC_N07_004 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression Test purpose CCBS: An INVITE request received while a CC recall is processed. CC call indicator present in the Request line. Ensure that when an INVITE request is received from the originating AS while CC-T9 is running and in the Request line the m parameter is present set to "BS" and a Call-Info header is present the m parameter is set to 'BS', this INVITE is processed to the callee. An INVITE is sent to the callee and the m parameter is not present in the Request line. When a 180 (Ringing) is received from the callee a NOTIFY request is sent to the originating AS and Subscription-State header is set to "terminated" and the reason header is set to "noresource". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=BS Call-Info: <sip:UE-A>;purpose=call-completion;m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 69 TSS CC/terminating_AS/CCOperation TP CC_N07_005 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression Test purpose CCNR: An INVITE request received while a CC recall is processed. CC call indicator present in the Request line. Ensure that when an INVITE request is received from the originating AS while CC-T9 is running and in the Request line the m parameter is present set to "NR" and a Call-Info header is present the m parameter is set to 'NR', this INVITE is processed to the callee. An INVITE is sent to the callee and the m parameter is not present in the Request line. When a 180 (Ringing) is received from the callee a NOTIFY request is sent to the originating AS and Subscription-State header is set to "terminated" and the reason header is set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=NR Call-Info: <sip:UE-A>;purpose=call-completion;m=NR NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 70 TSS CC/terminating_AS/CCOperation TP CC_N07_006 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression PICS 4.3.2-1/9 Test purpose CCNL: An INVITE request received while a CC recall is processed. CC call indicator present in the Request line. Ensure that when an INVITE request is received from the originating AS while CC-T9 is running and in the Request line the m parameter is present set to "NL" and a Call-Info header is present the m parameter is set to 'NL', this INVITE is processed to the callee. An INVITE is sent to the callee and the m parameter is not present in the Request line. When a 180 (Ringing) is received from the callee a NOTIFY request is sent to the originating AS and Subscription-State header is set to "terminated" and the reason header is set to "noresource". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=NL Call-Info: <sip:UE-A>;purpose=call-completion;m=NL NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNL request Callee is logged-in NOTIFY 1 200 OK NOTIFY INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 71 TSS CC/terminating_AS/CCOperation TP CC_N07_007 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression Test purpose CCBS: An INVITE request received while a CC recall is processed. CC call indicator not present in the Request line. Service requirements and destination selection information are not identical to the stored values. The call is rejected. Ensure that the terminating AS has sent a NOTIFY request to a CCBS entry and the state parameter in the call-completion MIME body was set to "ready" after the terminating AS receives an INVITE request and there is no 'm' parameter in the Request line and no Call-Info header is present the m parameter set to 'NL', the terminating AS rejects the call. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE: sip: UE B destination selection information and Service requirements not identical as used in the dialogue as CCBS was requested 486 Busy Here Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE 486 (Busy Here) ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 72 TSS CC/terminating_AS/CCOperation TP CC_N07_008 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression Test purpose CCNR: An INVITE request received while a CC recall is processed. CC call indicator not present in the Request line. Service requirements and destination selection information are not identical to the stored values. The call is rejected. Ensure that the terminating AS has sent a NOTIFY request to a CCNR entry and the state parameter in the call-completion MIME body was set to "ready" after the terminating AS receives an INVITE request and there is no 'm' parameter in the Request line the terminating AS rejects the call. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE: sip: UE B destination selection information and Service requirements not identical as used in the dialogue as CCNR was requested 486 Busy Here Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE 486 (Busy Here) ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 73 TSS CC/terminating_AS/CCOperation TP CC_N07_009 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression PICS 4.3.2-1/9 Test purpose CCNL: An INVITE request received while a CC recall is processed. CC call indicator not present in the Request line. Service requirements and destination selection information are not identical to the stored values. The call is rejected. Ensure that the terminating AS has sent a NOTIFY request to a CCNL entry and the state parameter in the call-completion MIME body was set to "ready" after the terminating AS receives an INVITE request and there is no 'm' parameter in the Request line the terminating AS rejects the call. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE: sip: UE B destination selection information and Service requirements not identical as used in the dialogue as CCNL was requested 486 Busy Here Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is logged-in NOTIFY 1 200 OK NOTIFY INVITE 486 (Busy Here) ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 74 TSS CC/terminating_AS/CCOperation TP CC_N07_010 Reference 4.5.4.3.4.2 a) Selection expression Test purpose CCBS: Terminating user becomes busy while CC-T8 is running. If in case of CCBS, upon expiry of the destination B idle guard timer CC-T8, the callee is busy (e.g. the callee has initiated an outgoing communication), then the terminating AS shall defer servicing of the destination B CC queue until the callee becomes not busy again. After the callee is not busy, the terminating AS starts the recall procedure again. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A (S2) Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ INVITE (S1) INVITE 200 OK INVITE 200 OK INVITE ACK ACK CC-T8 expires BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 75 TSS CC/terminating_AS/CCOperation TP CC_N07_011 Reference 4.5.4.3.4.2 a) Selection expression Test purpose CCNR: Terminating user becomes busy while CC-T8 is running. If in case of CCNR, upon expiry of the destination B idle guard timer CC-T8, the callee is busy (e.g. the callee has initiated an outgoing communication), then the terminating AS shall defer servicing of the destination B CC queue until the callee becomes not busy again. After the callee is not busy, the terminating AS starts the recall procedure again. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A (S2) Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK Start CC-T8 ↓ INVITE (S1) INVITE 200 OK INVITE 200 OK INVITE ACK ACK CC-T8 expires BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 76 TSS CC/terminating_AS/CCOperation TP CC_N07_012 Reference 4.5.4.3.4.2 a) Selection expression PICS 4.3.2-1/9 Test purpose CCNL: Terminating user becomes busy while CC-T8 is running. If in case of CCNL, upon expiry of the destination B idle guard timer CC-T8, the callee is busy (e.g. the callee has initiated an outgoing communication), then the terminating AS shall defer servicing of the destination B CC queue until the callee becomes not busy again. After the callee is not busy, the terminating AS starts the recall procedure again. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A (S2) Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNL request Callee is logged-in Start CC-T8 ↓ INVITE (S1) INVITE 200 OK INVITE 200 OK INVITE ACK ACK CC-T8 expires BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 77 TSS CC/terminating_AS/CCOperation TP CC_N07_013 Reference 4.5.4.3.4.2 c) Selection expression NOT PICS 4.3.2-1/2 Test purpose CCBS: The callee is busy upon arrival of the CC call. Retain option not supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is not supported at the terminating AS, the terminating AS shall cancel the corresponding CCBS request; the terminating AS shall send a 486 (Busy Here) response with a Call-Info header field with a "purpose" header field parameter set to "call-completion" and a m parameter set to "BS" to the originating AS. The CC request is cancelled. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=BS Call-Info: <sip:UE-A>;purpose=call-completion;m=BS 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) INVITE 486 (Busy Here) 486 (Busy Here) ACK ACK NOTIFY 2 200 OK NOTIFY BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 78 TSS CC/terminating_AS/CCOperation TP CC_N07_014 Reference 4.5.4.3.4.2 c) Selection expression NOT PICS 4.3.2-1/2 Test purpose CCNR: The callee is busy upon arrival of the CC call. Retain option not supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is not supported at the terminating AS, the terminating AS shall cancel the corresponding CCNR request; the terminating AS shall send a 486 (Busy Here) response with a Call-Info header field with a "purpose" header field parameter set to "call-completion" and a m parameter set to "BS" to the originating AS. The CC request is cancelled. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=NR Call-Info: <sip:UE-A>;purpose=call-completion;m=NR 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) INVITE 486 (Busy Here) 486 (Busy Here) ACK ACK NOTIFY 2 200 OK NOTIFY BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 79 TSS CC/terminating_AS/CCOperation TP CC_N07_015 Reference 4.5.4.3.4.2 c) Selection expression NOT PICS 4.3.2-1/2 AND PICS 4.3.2-1/9 Test purpose CCNL: The callee is busy upon arrival of the CC call. Retain option not supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is not supported at the terminating AS, the terminating AS shall cancel the corresponding CCNR request; the terminating AS shall send a 486 (Busy Here) response with a Call-Info header field with a "purpose" header field parameter set to "call-completion" and a m parameter set to "BS" to the originating AS. The CC request is cancelled. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=NL Call-Info: <sip:UE-A>;purpose=call-completion;m=NL 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNL request Callee is logged-in NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) INVITE 486 (Busy Here) 486 (Busy Here) ACK ACK NOTIFY 2 200 OK NOTIFY BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 80 TSS CC/terminating_AS/CCOperation TP CC_N07_016 Reference 4.5.4.3.4.2 c) Selection expression PICS 4.3.2-1/2 Test purpose CCBS: The callee is busy upon arrival of the CC call. Retain option supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is supported at the terminating AS, the terminating AS shall retain the original CCBS request in the queue; in this case the terminating AS shall continue to monitor destination B, shall not restart the timer CCBS-T7, shall stop timer CC-T9 and shall send a 486 (Busy Here) response with a Call-Info header field with a "purpose" header field parameter set to "call-completion" and the m parameter set to "BS" to the originating AS. After the callee becomes not busy, the recall procedure is started again. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=BS Call-Info: <sip:UE-A>;purpose=call-completion;m=BS 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) INVITE 486 (Busy Here) 486 (Busy Here) ACK ACK BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 81 TSS CC/terminating_AS/CCOperation TP CC_N07_017 Reference 4.5.4.3.4.2 c) Selection expression PICS 4.3.2-1/2 Test purpose CCNR: The callee is busy upon arrival of the CC call. Retain option supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is supported at the terminating AS, the terminating AS shall retain the original CCNR request in the queue; in this case the terminating AS shall continue to monitor destination B, shall not restart the timer CCBS-T7, shall stop timer CC-T9 and shall send a 486 (Busy Here) response with a Call-Info header field with a "purpose" header field parameter set to "call-completion" and the m parameter set to "BS" to the originating AS. After the callee becomes not busy, the recall procedure is started again. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=NR Call-Info: <sip:UE-A>;purpose=call-completion;m=NR 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) INVITE 486 (Busy Here) 486 (Busy Here) ACK ACK BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 82 TSS CC/terminating_AS/CCOperation TP CC_N07_018 Reference 4.5.4.3.4.2 c) Selection expression PICS 4.3.2-1/2 AND PICS 4.3.2-1/9 Test purpose CCNL: The callee is busy upon arrival of the CC call. Retain option supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is supported at the terminating AS, the terminating AS shall retain the original CCNL request in the queue; in this case the terminating AS shall continue to monitor destination B, shall not restart the timer CCBS-T7, shall stop timer CC-T9 and shall send a 486 (Busy Here) response with a Call-Info header field with a "purpose" header field parameter set to "call-completion" and the m parameter set to "BS" to the originating AS. After the callee becomes not busy, the recall procedure is started again. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=NL Call-Info: <sip:UE-A>;purpose=call-completion;m=NL 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) INVITE 486 (Busy Here) 486 (Busy Here) ACK ACK BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 83 TSS CC/terminating_AS/CCOperation TP CC_N07_019 Reference 4.5.4.3.4.2 d) Selection expression Test purpose CCBS: Recall does not apply, CC-T9 expires. Ensure that the terminating As revokes the CCBS request after the Recall timer. CC-T9 is expired. The terminating AS sends a NOTIFY request to the originating AS and the Subscription-State header is set to "terminated" and the reason header is set to "rejected". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready NOTIFY 2 sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Start CC-T9 ↓ CC-T9 expires NOTIFY 2 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 84 TSS CC/terminating_AS/CCOperation TP CC_N07_020 Reference 4.5.4.3.4.2 d) Selection expression Test purpose CCNR: Recall does not apply, CC-T9 expires. Ensure that the terminating As revokes the CCNR request after the Recall timer. CC-T9 is expired. The terminating AS sends a NOTIFY request to the originating AS and the Subscription-State header is set to "terminated" and the reason parameter is set to "rejected". Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready NOTIFY 2 sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Start CC-T9 ↓ CC-T9 expires NOTIFY 2 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 85 TSS CC/terminating_AS/CCOperation TP CC_N07_021 Reference 4.5.4.3.4.2 d) Selection expression PICS 4.3.2-1/9 Test purpose CCNL: Recall does not apply, CC-T9 expires. Ensure that the terminating As revokes the CCNL request after the Recall timer. CC-T9 is expired. The terminating AS sends a NOTIFY request to the originating AS and the Subscription-State header is set to "terminated" and the reason parameter is set to "rejected". Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready NOTIFY 2 sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Start CC-T9 ↓ CC-T9 expires NOTIFY 2 200 OK NOTIFY TSS CC/terminating_AS/CCOperation TP CC_N07_022 Reference 4.5.4.3.3.2 Selection expression Test purpose CCBS: Service duration timer, CC-T7 expires. Ensure that the terminating AS revokes the CCBS request after the CC service duration timer CC-T7 expires. A NOTIFY is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason parameter is set to "noresource". Preconditions: SIP header values: NOTIFY 2 sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Start CC-T7 Callee is busy ↓ CC-T7 expires NOTIFY 2 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 86 TSS CC/terminating_AS/CCOperation TP CC_N07_023 Reference 4.5.4.3.3.2 Selection expression Test purpose CCNR: Service duration timer, CC-T7 expires. Ensure that the terminating AS revokes the CCNR request after the CC service duration timer CC-T7 expires. A NOTIFY is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason parameter is set to "noresource". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Start CC-T7 Callee is idle ↓ CC-T7 expires NOTIFY 1 200 OK NOTIFY TSS CC/terminating_AS/CCOperation TP CC_N07_024 Reference 4.5.4.3.3.2 Selection expression PICS 4.3.2-1/9 Test purpose CCNL: Service duration timer, CC-T7 expires. Ensure that the terminating AS revokes the CCNL request after the CC service duration timer CC-T7 expires. A NOTIFY is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason parameter is set to "noresource". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNL request Start CC-T7 Callee is idle ↓ CC-T7 expires NOTIFY 1 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 87 TSS CC/terminating_AS/CCOperation TP CC_N07_025 Reference 4.5.4.3.4.1.5 Selection expression Test purpose CCBS: Caller becomes busy while CC recall procedure. Ensure that the terminating AS after the originating AS has suspended the CC recall procedure sends a NOTIFY request and the MIME body contains the state parameter set to 'queued'. When the originating AS resumes the CC call procedure after expiry of the B idle guard timer CC-T8 sends again the remote user free indication after the caller indicates no longer busy. A NOTIFY is sent an den MIME body contains the state parameter set to "queued". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready PUBLISH 1 sip:T-AS Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>closed</basic> PUBLISH 2 sip:T-AS Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>open</basic> NOTIFY 2 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 2 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 2 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Start CC-T8 ↓ CC-T8 expires NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 88 TSS CC/terminating_AS/CCOperation TP CC_N07_026 Reference 4.5.4.3.4.1.5 Selection expression Test purpose CCNR: Caller becomes busy while CC recall procedure. Ensure that the terminating AS after the originating AS has suspended the CC recall procedure sends a NOTIFY request and the MIME body contains the state parameter set to 'queued'. When the originating AS resumes the CC call procedure after expiry of the B idle guard timer CC-T8 sends again the remote user free indication after the caller indicates no longer busy. A NOTIFY is sent an den MIME body contains the state parameter set to "queued". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready PUBLISH 1 sip:T-AS Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>closed</basic> PUBLISH 2 sip:T-AS Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>open</basic> NOTIFY 2 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNR request Callee is available for CC recall NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 2 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 2 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Start CC-T8 ↓ CC-T8 expires NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 89 TSS CC/terminating_AS/CCOperation TP CC_N07_027 Reference 4.5.4.3.4.1.5 Selection expression PICS 4.3.2-1/9 Test purpose CCNL: Caller becomes busy while CC recall procedure. Ensure that the terminating AS after the originating AS has suspended the CC recall procedure sends a NOTIFY request and the MIME body contains the state parameter set to 'queued'. When the originating AS resumes the CC call procedure after expiry of the B idle guard timer CC-T8 sends again the remote user free indication after the caller indicates no longer busy. A NOTIFY is sent an den MIME body contains the state parameter set to "queued". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: ready PUBLISH 1 sip:T-AS Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>closed</basic> PUBLISH 2 sip:T-AS Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>open</basic> NOTIFY 2 sip:O-AS From: UE B To: UE A Subscription-State: active; expires=< any value > Event:call-completion Content-Type: application/call-completion cc-state: queued Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCNL request Callee is available for CC recall NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 2 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 2 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Start CC-T8 ↓ CC-T8 expires NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 90
e871d60fd728df1e61851585ff9b650b	101 588-2	5.4 Interaction of Call-Completion with other services
e871d60fd728df1e61851585ff9b650b	101 588-2	5.4.1 Terminating Identification Restriction (TIR)	TSS CC/ Interaction/TIR TP CC_N08_001 Reference 4.6.4 Selection expression PICS 4.3.2-1/4 Test purpose CCBS, CCNR, CCNL Recall successful by using the special REFER interworking. TIR settings considered in the CC recall. Ensure that the originating AS starts the CCBS recall procedure and in the 200 OK INVITE from the originating user is privacy indicated, the P-Asserted-Identity in the INVITE request set to the terminating user is also restricted. Preconditions: SIP header values: 200 OK 1 Privacy: id INVITE 2: sip: UE B; m=BS/NR/NL From: UE A To: UE B P-Asserted-Identity: UE-A Privacy: id Call-Info: <sip:UE-A>;purpose=call-completion;m=BS/NR/NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 1 180 Ringing 180 Ringing 200 OK INVITE 1 200 OK INVITE ACK ACK INVITE 2 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
e871d60fd728df1e61851585ff9b650b	101 588-2	5.4.2 Communication diversion services (CDIV)	TSS CC/Interaction/CDIV TP CC_N09_001 Reference 4.6.8.2 Selection expression Test purpose Detecting CCBS is possible. Ensure that when an originating user establishes a session to User B and the user B has activated communication diversion unconditional to user C, the terminating user C is busy, a 486 (Busy Here) response is sent to the originating AS and the Call-Info header contains the URI of user C or the terminating AS. Preconditions: SIP header values: 486 Busy Here 1: Call-Info: <sip:UE-C or T-AS>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE C INVITE INVITE 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 91 TSS CC/Interaction/CDIV TP CC_N09_002 Reference 4.6.8.2 Selection expression Test purpose Detecting CCNR is possible. Ensure that when an originating user establishes a session to User B and the user B has activated communication diversion unconditional to user C, a 180 (Ringing) response is sent to the originating AS and the Call-Info header contains the URI of user C or the terminating AS. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-C or T-AS>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE C INVITE INVITE 180 (Ringing) 1 180 (Ringing) Apply post test routine TSS CC/Interaction/CDIV TP CC_N09_003 Reference 4.6.8.2 Selection expression PICS 4.3.2-1/9 Test purpose Detecting CCNL is possible. Ensure that when an originating user establishes a session to User B and the user B has activated communication diversion unconditional to user C, the terminating user C is not logged-in, a 480 (Temporarily Unavailable) response is sent to the originating AS and the Call-Info header contains the URI of user C or the terminating AS. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE-C or T-AS>;purpose=call-completion;m=NL Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE C INVITE INVITE 480 (Temporarily Unavailable) 1 480 (Temporarily Unavailable) ACK ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 92 TSS CC/Interaction/CDIV TP CC_N09_004 Reference 4.6.8.2 Selection expression Test purpose CCBS Recall is given to the CC served user after CFU was activated. User A invokes a CCBS request to user B. subsequently user A activates CFU to user C. Ensure that the CCBS recall is sent to user A instead of forwarded to user C. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: active; expires=< any value > Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=BS Refer-To; UE B method=INVITE INVITE: sip: UE A; m=BS Call.Info: UE-A; purpose=call-completion;m=BS Comments: SIP 1 (Gm) UE A SUT SIP 2 (ISC) Establish a successful CCBS request Activate CFU to user C Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 93 TSS CC/Interaction/CDIV TP CC_N09_005 Reference 4.6.8.2 Selection expression Test purpose CCNR Recall is given to the CC served user after CFU was activated. User A invokes a CCNR request to user B. subsequently user A activates CFU to user C. Ensure that the CCNR recall is sent to user A instead of forwarded to user C. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: active; expires=< any value > Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NR Refer-To; UE B method=INVITE INVITE: sip: UE A; m=NR Call.Info: UE-A; purpose=call-completion;m=NR Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCNR request Activate CFU to user C Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 94 TSS CC/Interaction/CDIV TP CC_N09_006 Reference 4.6.8.2 Selection expression PICS 4.3.2-1/9 Test purpose CCNL Recall is given to the CC served user after CFU was activated. User A invokes a CCNL request to user B. subsequently user A activates CFU to user C. Ensure that the CCBS recall is sent to user A instead of forwarded to user C. Preconditions: SIP header values: NOTIFY sip:O-AS From: UE B To: UE A Event:call-completion Subscription-State: active; expires=< any value > Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NL Refer-To; UE B method=INVITE INVITE: sip: UE A; m=NL Call.Info: UE-A; purpose=call-completion;m=NL Comments: SIP 1 (Gm) SUT SIP 2 (ISC) Establish a successful CCNL request Activate CFU to user C Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Apply post test routine TSS CC/Interaction/CDIV TP CC_N09_007 Reference 4.6.8.2 Selection expression Test purpose CCBS revocation after terminating user has activated . Ensure that the terminating AS revokes the outstanding CCBS request if the terminating user activates CFU to user C after the originating user has established CCBS on the terminating user B. The terminating AS sends a NOTIFY request to the originating AS and the Subscription-State header field set to "terminated"; and the "reason" Subscription- State header field parameter set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) User B Establish a successful CCBS request Activate CFU to user C NOTIFY 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 95 TSS CC/Interaction/CDIV TP CC_N09_008 Reference 4.6.8.2 Selection expression Test purpose CCNR revocation after terminating user has activated . Ensure that the terminating AS revokes the outstanding CCNR request if the terminating user activates CFU to user C after the originating user has established CCNR on the terminating user B. The terminating AS sends a NOTIFY request to the originating AS and the Subscription-State header field set to "terminated"; and the "reason" Subscription- State header field parameter set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) User B Establish a successful CCNR request Activate CFU to user C NOTIFY 200 OK NOTIFY TSS CC/Interaction/CDIV TP CC_N09_009 Reference 4.6.8.2 Selection expression PICS 4.3.2-1/9 Test purpose CCNL revocation after terminating user has activated . Ensure that the terminating AS revokes the outstanding CCNL request if the terminating user activates CFU to user C after the originating user has established CCNL on the terminating user B. The terminating AS sends a NOTIFY request to the originating AS and the Subscription-State header field set to "terminated"; and the "reason" Subscription- State header field parameter set to "noresource". Preconditions: SIP header values: NOTIFY sip:O-AS From:<UE-B> To:<UE-A> Event:call-completion Subscription-State: terminated; reason= noresource Comments: SIP 1 (ISC) SUT SIP 2 (Gm) User B Establish a successful CCNL request Activate CFU to user C NOTIFY 200 OK NOTIFY ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 96 TSS CC/Interaction/CDIV TP CC_N09_010 Reference 4.6.8.3 Selection expression Test purpose CCBS indication is sent if the original call is diverted on Busy. The terminating user has activated the CFB service. In case of a callee is busy the communication is forwarded to User C and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCBS is possible at the diverted-to user UE C if busy or at the callee UE B. Preconditions: Communication Forwarding Busy is activated SIP header values: 486 Busy Here 1: Call-Info: <sip:UE C>;purpose=call-completion;m=BS 486 Busy Here 2: Call-Info: <sip: UE B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 486 (Busy Here) ACK CFB applies CASE A INVITE 486 (Busy Here) 1 486 (Busy Here) ACK ACK CASE B INVITE 486 (Busy Here) 2 486 (Busy Here) ACK ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N09_0011 Reference 4.6.8.3 Selection expression Test purpose CCNR indication is sent if the original call was diverted on Busy. The terminating user has activated the CFNR service. In case of a callee is busy the communication is forwarded to User C and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCNR is possible at the diverted-to user UE C if not answer the communication or at the callee UE B. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-C>;purpose=call-completion;m=NR 486 Busy Here 1 Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 486 (Busy Here) ACK CFB applies CASE A INVITE 180 (Ringing) 1 180 (Ringing) CASE B INVITE 486 (Busy Here) 1 180 (Ringing) ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 97 TSS CC/Interaction/CDIV TP CC_N09_0012 Reference 4.6.8.3 Selection expression PICS 4.3.2-1/9 Test purpose CCNL indication is sent if the original call was diverted on Busy. The terminating user has activated the CFNL service. In case of a callee is busy the communication is forwarded to User C and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCNL is possible at the diverted-to user UE C if not logged-in or at the callee UE B. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE-C>;purpose=call-completion;m=NL 486 (Busy Here) 1 Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 486 (Busy Here) ACK CFB applies CASE A UE C is not logged-in 480 (Temporarily Unavailable) 1 ACK CASE B 486 (Busy Here) 1 ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 98 TSS CC/Interaction/CDIV TP CC_N09_013 Reference 4.6.8.3 Selection expression Test purpose CCBS recall after the callee activates CFB. Recall is considered as being busy. Ensure that User B activates CFB after User A has activated CCBS on User B. The CC recall from user A encounters a busy condition at user B: • the terminating AS considers a CC recall to a busy callee and the AS indicates CCBS is possible to the originating AS or • the AS forwards the communication to User C. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready 486 Busy Here 1 Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 2 (Gm) UE C Invoke CCBS request Terminating user activates CFB User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 200 OK INVITE 200 OK INVITE ACK ACK INVITE CASE A INVITE 486 (Busy Here) 1 486 (Busy Here) ACK ACK CASE B INVITE 180 (Ringing) 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 99 TSS CC/Interaction/CDIV TP CC_N09_014 Reference 4.6.8.3 Selection expression Test purpose CCNR recall after the callee activates CFB. Recall is considered as being busy. Ensure that User B activates CFB after User A has activated CCNR on User B. The CC recall from user A encounters a busy condition at user B: • the terminating AS considers a CC recall to a busy callee and the AS indicates CCBS is possible to the originating AS or • the AS forwards the communication to User C. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready 486 Busy Here 1 Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 2 (Gm) UE C Invoke CCNR request Terminating user activates CFB User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 200 OK INVITE 200 OK INVITE ACK ACK INVITE CASE A INVITE 486 (Busy Here) 1 486 (Busy Here) ACK ACK CASE B INVITE 180 (Ringing) 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 100 TSS CC/Interaction/CDIV TP CC_N09_015 Reference 4.6.8.3 Selection expression PICS 4.3.2-1/9 Test purpose CCNL recall after the callee activates CFB. Recall is considered as being busy. Ensure that User B activates CFB after User A has activated CCNL on User B. The CC recall from user A encounters a busy condition at user B: • the terminating AS considers a CC recall to a busy callee and the AS indicates CCBS is possible to the originating AS or • the AS forwards the communication to User C. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready 486 Busy Here 1 Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 2 (Gm) UE C Invoke CCNL request Terminating user activates CFB User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 200 OK INVITE 200 OK INVITE ACK ACK INVITE CASE A INVITE 486 (Busy Here) 1 486 (Busy Here) ACK ACK CASE B INVITE 180 (Ringing) 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 101 TSS CC/Interaction/CDIV TP CC_N09_016 Reference 4.6.8.4 Selection expression Test purpose CCBS: indication is sent if the original call was diverted on no Reply. In case of a diverted-to user after CFNR was performed is busy and the callee has subscribed the call completion service, ensure that the terminating AS informs the caller: • that CCBS is possible at User C or • that CCNR is possible at User B. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE C>;purpose=call-completion;m=BS 180 (Ringing) 1 Call-Info: <sip:UE B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 180 (Ringing) 1 180 (Ringing) CFNR applies CASE A INVITE 486 (Busy Here) 1 486 (Busy Here) ACK ACK CASE B INVITE 486 (Busy Here) ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N09_017 Reference 4.6.8.4 Selection expression Test purpose CCNR: indication is sent if the original call was diverted on no Reply. In case of a diverted-to user after CFNR was performed does not answer the communication request and the callee has subscribed the call completion service, ensure that the terminating AS informs the caller: • that CCNR is possible at User C or • that CCNR is possible at User B Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE B>;purpose=call-completion;m=NR 180 Ringing 2 Call-Info: <sip:UE C>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 180 (Ringing) 1 180 (Ringing) CFNR applies CASE A INVITE 180 (Ringing) 2 180 (Ringing) CASE B INVITE 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 102 TSS CC/Interaction/CDIV TP CC_N09_018 Reference 4.6.8.4 Selection expression PICS 4.3.2-1/9 Test purpose CCNL: indication is sent if the original call was diverted on no Reply. In case of a diverted-to user after CFNR was performed is not logged-in and the callee has subscribed the call completion service, ensure that the terminating AS informs the caller: • that CCNL is possible at User C or • that CCNR is possible at User B. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE C>;purpose=call-completion;m=NL 180 (Ringing 1 Call-Info: <sip: UE B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 180 (Ringing) 1 180 (Ringing) CFNR applies CASE A UE C is not logged-in 480 (Temporarily Unavailable) 1 ACK CASE B Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 103 TSS CC/Interaction/CDIV TP CC_N09_019 Reference 4.6.8.4 Selection expression Test purpose CCBS: Recall after CFNR was activated. The terminating user activates CFNR after the originating user has requested the CCBS service at the terminating user. Ensure that the CC recall is: • applied as a CC recall or • forwarded as a normal call. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE-B; m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C Invoke CCBS request User B becomes available NOTIFY 1 200 OK NOTIFY Callee activates CCNR INVITE 1 CASE A INVITE 180 Ringing 180 Ringing CASE B INVITE 180 Ringing 180 Ringing CFNR is performed INVITE 180 Ringing 180 Ringing Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 104 TSS CC/Interaction/CDIV TP CC_N09_020 Reference 4.6.8.4 Selection expression Test purpose CCNR: Recall after CFNR was activated. The terminating user activates CFNR after the originating user has requested the CCNR service at the terminating user. Ensure that the CC recall is: • applied as a CC recall or • forwarded as a normal call. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE-B; m=NR Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C Invoke CCNR request User B becomes available NOTIFY 1 200 OK NOTIFY Callee activates CCNR INVITE 1 CASE A INVITE 180 Ringing 180 Ringing CASE B INVITE 180 Ringing 180 Ringing CFNR is performed INVITE 180 Ringing 180 Ringing Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 105 TSS CC/Interaction/CDIV TP CC_N09_021 Reference 4.6.8.4 Selection expression PICS 4.3.2-1/9 Test purpose CCNL: Recall after CFNR was activated. The terminating user activates CFNR after the originating user has requested the CCNL service at the terminating user. Ensure that the CC recall is: • applied as a CC recall or • forwarded as a normal call. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE-B; m=NL Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C Invoke CCNL request User B becomes available NOTIFY 1 200 OK NOTIFY Callee activates CCNR INVITE 1 CASE A INVITE 180 Ringing 180 Ringing CASE B INVITE 180 Ringing 180 Ringing CFNR is performed INVITE 180 Ringing 180 Ringing Apply post test routine TSS CC/Interaction/CDIV TP CC_N09_022 Reference 4.6.8.5 Selection expression Test purpose CCBS: indication is sent if the original call was diverted on not logged-in. In case of a diverted-to user after CFNL was performed is busy and the diverted-to user (User C) has subscribed the call completion service, ensure that the terminating AS inform the caller: • that CCBS is possible at User C or • that CCNL is possible at User B. Preconditions: SIP header values: 486 Busy Here 1: Call-Info: <sip:UE C>;purpose=call-completion;m=BS 480 Temporarily Unavailable 1 Call-Info: <sip: UE B>;purpose=call-completion;m=NL Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE CFNL applies CASE A INVITE 486 (Busy Here) 1 486 (Busy Here) ACK ACK CASE B INVITE 480 (Temporarily Unavailable) 1 486 (Busy Here) ACK ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 106 TSS CC/Interaction/CDIV TP CC_N09_023 Reference 4.6.8.5 Selection expression Test purpose CCNR: indication is sent if the original call was diverted on not logged-in. In case of a diverted-to user after CFNL was performed does not answer the communication request and the diverted- to user (User C) has subscribed the call completion service, ensure that the terminating AS inform the caller: • that CCNR is possible at User C or • that CCNL is possible at User B. Preconditions: SIP header values: 180 Ringing1: Call-Info: <sip:UE C>;purpose=call-completion;m=NR 480 Temporarily Unavailable 1 Call-Info: <sip: UE B>;purpose=call-completion;m=NL Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE CFNL applies CASE A INVITE 180 (Ringing) 1 180 (Ringing) CASE B INVITE 480 (Temporarily Unavailable) 1 180 (Ringing) ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N09_024 Reference 4.6.8.5 Selection expression PICS 4.3.2-1/9 Test purpose CCNL: indication is sent if the original call was diverted on not logged-in. In case of a diverted-to user after CFNL was performed is not logged-in and the diverted-to user (User C) has subscribed the call completion service, ensure that the terminating AS inform the caller: • that CCNL is possible at User C or • that CCNL is possible at User B. Preconditions: SIP header values: 480 (Temporarily Unavailable) 1: Call-Info: <sip:UE C>;purpose=call-completion;m=NL 480 Temporarily Unavailable 2 Call-Info: <sip: UE B>;purpose=call-completion;m=NL Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE CFNL applies UE C is not logged-in CASE A 480 (Temporarily Unavailable) 1 ACK CASE B 480 (Temporarily Unavailable) 2 ACK Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 107 TSS CC/Interaction/CDIV TP CC_N09_025 Reference 4.6.8.6 Selection expression Test purpose CCBS: indication is sent if the original call was deflected. In case of a diverted-to user after CD (alerting) was performed is busy and the diverted-to user has subscribed the call completion service, ensure that the terminating AS informs the caller that CCBS is possible at User C. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE C>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 180 (Ringing) 180 (Ringing) 302 (Moved Temporarily) ACK CD applies INVITE 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N09_026 Reference 4.6.8.6 Selection expression Test purpose CCNR: indication is sent if the original call was deflected. In case of a diverted-to user after CD (alerting) was performed does not answer the communication request and the diverted-to user has subscribed the call completion service, ensure that the terminating AS informs the caller that CCNR is possible at User C. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE C>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 180 (Ringing) 180 (Ringing) 302 (Moved Temporarily) ACK CD applies INVITE 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 108 TSS CC/Interaction/CDIV TP CC_N09_027 Reference 4.6.8.6 Selection expression PICS 4.3.2-1/9 Test purpose CCNL: indication is sent if the original call was deflected. In case of a diverted-to user after CD (alerting) was performed is not logged-in and the diverted-to user has subscribed the call completion service, ensure that the terminating AS informs the caller that CCNL is possible at User C. Preconditions: SIP header values: 480 Temporarily Unavailable 1: Call-Info: <sip:UE C>;purpose=call-completion;m=NL Comments: SIP 1 (ISC) SUT SIP 2 (Gm) UE B SIP 3 (Gm) UE C INVITE INVITE 180 (Ringing) 180 (Ringing) 302 (Moved Temporarily) ACK CD applies UE C is not logged-in 480 (Temporarily Unavailable) 1 ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N09_028 Reference 4.6.8.6 Selection expression Test purpose CCBS recall is not deflected. Ensure that a CCBS recall is not deflected at the terminating Application Server. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=BS From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE 1 INVITE 180 (Ringing) 180 (Ringing) 4xx 302 (Moved Temporarily) ACK ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 109 TSS CC/Interaction/CDIV TP CC_N09_029 Reference 4.6.8.6 Selection expression Test purpose CCNR recall is not deflected. Ensure that a CCNR recall is not deflected at the terminating Application Server. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=NR From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE 1 INVITE 180 (Ringing) 180 (Ringing) 4xx 302 (Moved Temporarily) ACK ACK TSS CC/Interaction/CDIV TP CC_N09_030 Reference 4.6.8.6 Selection expression PICS 4.3.2-1/9 Test purpose CCNL recall is not deflected. Ensure that a CCNL recall is not deflected at the terminating Application Server. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready INVITE 1: sip: UE B; m=NL From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=NL Comments: SIP 1 (ISC) SUT SIP 2 (Gm) Invoke CCBS request User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE 1 INVITE 180 (Ringing) 180 (Ringing) 4xx 302 (Moved Temporarily) ACK ACK ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 110 TSS CC/Interaction/CDIV TP CC_N09_031 Reference 4.6.8.1 Selection expression Test purpose CCBS recall is not forwarded. The originating user activates CCBS. Before the terminating user becomes available the originating user activates CFU: Ensure that the CCBS recall is not forwarded if the originating user has activated CFU. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=BS Refer-To; UE B; method=INVITE INVITE 1: sip: UE B; m=BS From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=BS Comments: SIP 1 (Gm) UE A SUT SIP 2 (ISC) Invoke CCBS request Activate CFU to user C User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 111 TSS CC/Interaction/CDIV TP CC_N09_032 Reference 4.6.8.1 Selection expression Test purpose CCNR recall is not forwarded. The originating user activates CCNR. Before the terminating user becomes available the originating user activates CFU. Ensure that the CCNR recall is not forwarded if the originating user has activated CFU. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NR Refer-To; UE B; method=INVITE INVITE 1: sip: UE B; m=NR From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=NR Comments: SIP 1 (Gm) UE A SUT SIP 2 (ISC) Invoke CCBS request Activate CFU to user C User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 112 TSS CC/Interaction/CDIV TP CC_N09_033 Reference 4.6.8.1 Selection expression PICS 4.3.2-1/9 Test purpose CCNL recall is not forwarded. The originating user activates CCNL. Before the terminating user becomes available the originating user activates CFU. Ensure that the CCNL recall is not forwarded if the originating user has activated CFU. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready REFER: sip: UE A; m=NL Refer-To; UE B; method=INVITE INVITE 1: sip: UE B; m=NL From: UE A To: UE B Call-Info: <sip:UE-A>;purpose=call-completion;m=NL Comments: SIP 1 (Gm) UE A SUT SIP 2 (ISC) Invoke CCBS request Activate CFU to user C User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY CASE A REFER REFER 202 Accepted 202 Accepted CASE B INVITE INVITE 180 (Ringing) 180 (Ringing) Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 113 TSS CC/Interaction/CDIV TP CC_N09_034 Reference 4.6.8.1 Selection expression Test purpose CCBS recall is not forwarded. Originating user is not logged-in. The originating user activates CCBS. Before the terminating user becomes available the originating user activates CFU. Ensure that the CCBS recall is suspended if the originating user has activated CFU and is not logged-in. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready PUBLISH: sip T-AS Call.Info: UE-A; purpose=call-completion;m=BS P-Assertd-Identity: UE A Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>closed</basic> Comments: SIP 1 (Gm) UE A SUT SIP 2 (ISC) Invoke CCBS request Activate CFU to user C User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 114 TSS CC/Interaction/CDIV TP CC_N09_035 Reference 4.6.8.1 Selection expression Test purpose CCNR recall is not forwarded. Originating user is not logged-in. The originating user activates CCNR. Before the terminating user becomes available the originating user activates CFU. Ensure that the CCNR recall is suspended if the originating user has activated CFU and is not logged-in. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready PUBLISH: sip T-AS Call.Info: UE-A; purpose=call-completion;m=NR P-Assertd-Identity: UE A Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>closed</basic> Comments: SIP 1 (Gm) UE A SUT SIP 2 (ISC) Invoke CCBS request Activate CFU to user C User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 115 TSS CC/Interaction/CDIV TP CC_N09_036 Reference 4.6.8.1 Selection expression PICS 4.3.2-1/9 Test purpose CCNL recall is not forwarded. Originating user is not logged-in. The originating user activates CCNL. Before the terminating user becomes available the originating user activates CFU. Ensure that the CCNL recall is suspended if the originating user has activated CFU and is not logged-in. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: UE-B To: UE-A Event:call-completion Content-Type: application/call-completion cc-state: ready PUBLISH: sip T-AS Call.Info: UE-A; purpose=call-completion;m=NL P-Assertd-Identity: UE A Expires=(> 0) Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <tuple id=" any uri "> <status> <basic>closed</basic> Comments: SIP 1 (Gm) UE A SUT SIP 2 (ISC) Invoke CCBS request Activate CFU to user C User B becomes available NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH Apply post test routine ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 116 History Document history V5.1.1 October 2012 Publication
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	1 Scope	The present document specifies the protocol implementation conformance statement of the Completion of Communications to Busy Subscriber (CCBS) service and the Completion of Communication on no Reply (CCNR) service, based on stage three of the IMS simulation services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	2.1 Normative references	The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 642: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.642 Release 10)". [2] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [3] ISO/IEC 9646-1: "Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 1: General concepts". [4] ISO/IEC 9646-7: "Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements".
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	2.2 Informative references	The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 6
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	3 Definitions, symbols and abbreviations
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	3.1 Definitions	For the purposes of the present document, the terms and definitions given in TS 124 642 [1], ETS 300 406 [2], ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply: Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented NOTE: The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, API ICS, etc. ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	3.2 Symbols	For the purposes of the present document, the symbols given in TS 124 642 [1] apply.
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	3.3 Abbreviations	For the purposes of the present document, the abbreviations given in TS 124 642 [1] and the following apply: ICS Implementation Conformance Statement IUT Implementation Under Test SCS System Conformance Statement SUT System Under Test PICS Protocol ICS 4 Protocol Implementation Conformance Statement proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS proforma in this clause so that it can be used for its intended purposes and may further publish the completed PICS.
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.1 Instructions for completing the PICS proforma	4.1.1 More detailed instructions are given at the beginning of the different clauses of the PICS proforma The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5.
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.1.1.1 Purposes and structure	The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in reference specification [1] may provide information about the implementation in a standardized manner. ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 7 The PICS proforma is subdivided into clauses for the following categories of information: • instructions for completing the PICS proforma; • identification of the implementation; • identification of the reference protocol specification; • PICS proforma tables (containing the global statement of conformance).
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.1.2 Abbreviations and conventions	The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [4]: Item column It contains a number that identifies the item in the table. Item description column It describes each respective item (e.g. parameters, timers, etc.). Reference column It gives reference to the CCBS/CCNR specification [1], except where explicitly stated otherwise. Status column The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column: m mandatory - the capability is required to be supported. n/a not applicable - in the given context, it is impossible to use the capability. No answer in the support column is required. o optional - the capability may be supported or not. o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. ci conditional - the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression that is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." shall be used to avoid ambiguities. If an ELSE clause is omitted, "ELSE n/a" shall be implied. NOTE: Support of a capability means that the capability is implemented in conformance to the specification [1]. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [4], are used for the support column: Y or y supported by the implementation; N or n not supported by the implementation; N/A or n/a- no answer required (allowed only if the status is N/A, directly or after evaluation of a conditional status). ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 8
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.2 Identification of the implementation	Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.2.1 Date of the statement	Date of the statement:
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.2.2 Implementation Under Test (IUT) identification	IUT name: IUT version:
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.2.3 System Under Test (SUT) identification	SUT name: Hardware configuration: Operating system:
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.2.4 Product supplier	Name: Address: Telephone number: Facsimile number: Additional information:
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.2.5 Client	Name: Address: Telephone number: Facsimile number: Additional information: ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 9
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.2.6 PICS contact person	Name: Telephone number: Facsimile number: Additional information:
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.3 PICS proforma tables
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.3.1 Global statement of conformance	Table 4.3.1-1: Global statement of conformance (Yes/No) Are all mandatory capabilities implemented?
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	4.3.2 Network capabilities	Table 4.3.2-1: Network capabilities Item Item description Reference Status Support 1 Is the CCBS/CCNR request retention option supported? 4.5.4.2.3.2.4/ [1] o 2 Is the retain option supported? 4.5.4.3.4.2/ [1] o 3 Is it possible to activate a further CCBS or CCNR request for an identical communication, determined by the stored basic communication information? 4.5.4.2.1.1.1/ [1] o 4 Has the originating AS knowledge that UE-A does not support the REFER method extension, the originating AS starts the 3rd party call control procedure? 4.5.4.2.3/ [1] o 5 Does the originating CC-AS reduce the number of request entries for the caller? 4.5.4.2.1.1.3/ [1] o 6 Does the terminating CC-AS reduce the number of request entries for the callee? 4.5.4.3.2/ [1] o 7 Does the terminating CC-AS sends an indication to the originating CC-AS that CCBS or CCNR is possible if the terminating user has activated CFU while the recall is in progress? 4.6.8.2/ [1] o 8 It is possible that an outstanding CC request can be revoked by the user using service code commands? 4.5.4.2.2.1.2/ [1] o 9 Does the Application Server suppoerts "Completion of Communications on Not Logged in"? 4.5.4.2.1.1.1/ [1] 4.5.4.3.1.1/ [1] o 10 Does the originating CC-AS include a Date header in the 486 (Busy Here) or 480 (Temporarily unavailable) sent to the originating user if the CC-Invocation was successful? 4.5.4.2.1.1.6/ [1] o 11 Does the originating CC-AS include a "an message/external-body MIME type" in the 486 (Busy Here) or 480 (Temporarily unavailable) sent to the originating user if the CC-Invocation was successful? 4.5.4.2.1.1.6/ [1] o 12 Does the originating AS in case of receipt of a CCNR invocation confirmation, terminate the original communication by sending a CANCEL request to UE-B? 4.5.4.2.1.1.4/ [1] o ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 10 Table 4.3.2-2: Timer Item Timer number Reference Status Support Values in seconds Allowed Supported CC-T1 4.8.1/ [1] m 15 CC-T2 4.8.1/ [1] m > 10 CC-T3 4.8.1/ [1] m ≤ 10 800 CC-T4 4.8.1/ [1] m ≤ 20 CCNR-T5 4.8.1/ [1] m ≤ 20 CC-T7 4.8.1/ [1] m ≤ 11 400 CC-T8 4.8.1/ [1] m ≤ 10 CC-T9 4.8.1/ [1] m ≤ 30
49ab0451e991beb8c5c85fc26ebffe7a	101 588-1	5 Additional informations for PICS	If necessary, the supplier may provide additional comments in this clause. ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 11 History Document history V5.1.1 October 2012 Publication
7f110eeff44cca5c59b5fc967e08482a	101 585	1 Scope	The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for IMS interconnection tests at the Ic Interface to verify the overall compatibility of SIP, ISDN and non-ISDN (PSTN) over the national or international networks when using End Devices. The TSS&TP specification covers the procedures described in TS 124 229 [2] and TS 129 165 [1] respectively.
7f110eeff44cca5c59b5fc967e08482a	101 585	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
7f110eeff44cca5c59b5fc967e08482a	101 585	2.1 Normative references	The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Inter-IMS Network to Network Interface (NNI) (3GPP TS 29.165 Release 10)". [2] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 Release 10)". [3] IETF RFC 4566 (2006): "SDP: Session Description Protocol". [4] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [5] IETF RFC 3264 (2002): "An Offer/Answer Model with the Session Description Protocol (SDP)". [6] IETF RFC 3312 (2002): "Integration of Resource Management and Session Initiation Protocol (SIP)". [7] ETSI TS 124 607: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.607 Release 10)". [8] ETSI TS 124 608: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 Release 10)". [9] ETSI TS 124 604: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 version 10.3.0 Release 10)". [10] ETSI TS 124 605: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 Release 10)". ETSI ETSI TS 101 585 V1.2.1 (2014-04) 7 [11] ETSI TS 124 629: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.629 Release 10)". [12] ETSI TS 124 611: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.611 Release 10)". [13] ETSI TS 124 654: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification (3GPP TS 24.654 Release 10)". [14] ETSI TS 124 642: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.642 Release 10)". [15] ETSI TS 124 615: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.615 Release 10)". [16] ETSI TS 124 606: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.606 Release 10)". [17] ETSI TS 124 610: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610 Release 10)". [18] ETSI TS 124 616: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.616 Release 10)". [19] ETSI TS 129 658: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; TISPAN; SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification (3GPP TS 29.658 Release 10)". [20] ETSI TS 124 628: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.628 Release 10)". [21] IETF RFC 5009 (September 2007): "Private header (P-Header) extension to the Session Initiation Protocol (SIP) for authorization of Early Media". [22] Recommendation ITU-T V.152 (November 2004): "Procedures for supporting Voice-Band Data over IP Networks". [23] Recommendation ITU-T T.38 (September 2010, prepublished): "Procedures for real-time Group 3 facsimile communication over IP networks". [24] Recommendation ITU-T Q.1912.5: "SERIES Q: SWITCHING AND SIGNALLING Specifications of signalling related to Bearer Independent Call Control (BICC) Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part". [25] ETSI TS 183 036: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification". [26] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals". ETSI ETSI TS 101 585 V1.2.1 (2014-04) 8 [27] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)".
7f110eeff44cca5c59b5fc967e08482a	101 585	2.2 Informative references	The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]". [i.2] ISO/IEC 9646 (1994): "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework". [i.3] ETSI TR 102 775 (V1.5.1): "Speech and multimedia Transmission Quality (STQ); Guidance on objectives for Quality related Parameters at VoIP Segment-Connection Points; A support to NGN transmission planners". [i.4] Recommendation ITU-T Q.1902.2 (07/2001): "Bearer Independent Call Control protocol (Capability Set 2) and Signalling System No.7 ISDN User Part: General functions of messages and parameters".
7f110eeff44cca5c59b5fc967e08482a	101 585	3 Definitions and abbreviations
7f110eeff44cca5c59b5fc967e08482a	101 585	3.1 Definitions	For the purposes of the present document, the following terms and definitions apply: BICC or ISUP specific terminology, references to Recommendation ITU-T Q.1902.2 [i.4]. For SIP and SDP specific terminology, references to RFC 3261 [4] and RFC 4566 [3] respectively. Definitions for additional terminology used in this interworking Recommendation are as follows: Adjacent SIP Node (ASN): SIP node (e.g. SIP Proxy or Back-to-Back User Agent or the SIP side of an IWU) that has established a direct trust relation (association) with Incoming or Outgoing IWU entities NOTE: The SIP Proxy and Back-to-Back User Agent are defined in accordance with RFC 3261 [4]. Basic Call Control (BCC): signalling protocol associated with the DSS1 - ISDN Basic Call control procedures of ITU-T recommendation Q.931 [15] (EN 300 403-1 [i.1]) Incoming Interworking Unit (I-IWU): physical entity, (which can be combined with a BICC ISN or ISUP exchange) that terminates incoming calls using SIP and originates outgoing calls using the BICC or ISUP protocols incoming or outgoing: direction of a call (not signalling information) with respect to a reference point incoming SIP or BICC/ISUP (network): network, from which the incoming calls are received, that uses the SIP or BICC/ISUP protocol (without the term "network", it simply refers to the protocol) inopportune: specifies a test purpose covering a signalling procedure where an inopportune message (type of message not expected in the IUT current state) is sent to the IUT Outgoing Interworking Unit (O-IWU): physical entity, (which can be combined with a BICC ISN or ISUP exchange) that terminates incoming calls using BICC or ISUP protocols and originates outgoing calls using the SIP outgoing SIP or BICC/ISUP (network): network, to which the outgoing calls are sent, that uses the SIP or BICC/ISDN protocol NOTE: Without the term "network", it simply refers to the protocol. ETSI ETSI TS 101 585 V1.2.1 (2014-04) 9 SIP precondition: indicates the support of the SIP "precondition procedure" NOTE: as defined in RFC 3312 [6]. syntactically invalid: specifies a test purpose covering a signalling procedure where a valid (expected in the current status of the IUT) but not correctly encoded (unknown or incorrect parameter values) message is sent to the IUT, which reacts correctly and eventually reject the message test purpose: non-formal test description, mainly using text NOTE: TSIs test description can be used as the basis for a formal test specification (e.g. Abstract Test Suite in TTCN). See ISO/IEC 9646 [i.2]. valid: specifies a test purpose covering a signalling procedure where all the messages sent to or received from the IUT are valid (expected in the current status of the IUT) and correctly encoded
7f110eeff44cca5c59b5fc967e08482a	101 585	3.1.1 Conventions for representation of SIP/SDP information	1) All letters of SIP method names are in capital. EXAMPLE 1: INVITE, INFO. 2) SIP header fields are identified by the unabbreviated header field name as defined in the relevant RFC, including capitalization and enclosed hyphens but excluding the following colon. EXAMPLE 2: To, From, Call-ID. 3) Where it is necessary to refer with finer granularity to components of a SIP message, the component concerned is identified by the ABNF rule name used to designate it in the defining RFC (generally 25/RFC 3261 [4]), in plain text without surrounding angle brackets. EXAMPLE 3: Request-URI, the user info portion of a sip: URI. 4) URI types are represented by the lower-case type identifier followed by a colon and the abbreviation "URI" EXAMPLE 4: sip: URI, tel: URI. 5) SIP provisional responses and final responses other than 2XX are represented by the status code followed by the normal reason phrase for that status code, with initial letters capitalized. EXAMPLE 5: 100 Trying, 484 Address Incomplete. 6) Because of potential ambiguity within a call flow about which request a 200 OK final response answers, 200 OK is always followed by the method name of the request. EXAMPLE 6: 200 OK INVITE, 200 OK PRACK. 7) A particular line of an SDP session description is identified by the two initial characters of the line -- that is, the line type character followed by "=" EXAMPLE 7: m=line, a=line. 8) Where it is necessary to refer with finer granularity to components of a session description, the component concerned is identified by its rule name in the ABNF description of the SDP line concerned, delimited with angle brackets. EXAMPLE 8: the <media> and <fmt> components of the m= line. ETSI ETSI TS 101 585 V1.2.1 (2014-04) 10
7f110eeff44cca5c59b5fc967e08482a	101 585	3.2 Abbreviations	For the purposes of the present document, the following abbreviations apply: ACR Anonymous Communication Rejection CB Communication Barring CFB Communication Forwarding Busy CCBS Completion of Communications to Busy Subscriber CCNR Completion of Communications by No Reply CD Communication Deflection CDIV Communication DIVersion CDP Charging Determinating Point CDR Communication Data Record CFNL Communication Forwarding Not Logged in CFNR Communication Forwarding No Reply CFU Communication Forwarding Unconditional CONF Conference CUG Closed User Group CW Communication Waiting ECT Explicit Communication Transfer FFS For Further Study GW GateWay HOLD Communication Hold ISDN Integrated Services Digital Network IUT Implementation Under Test MCID Malicious Communication Identification MWI Message Waiting Indication NDUB Network Determined User Busy OIP Originating Identification Presentation OIR Originating Identification presentation Restriction PASP Public Answering Safety Point PICS Protocol Implementation Conformance Statement PSTN Public Switched Telephone Network QoS Quality of service SIP Session Initiation Protocol TIP Terminating Identification Presentation TIR Terminating Identification Restriction TP Test Purpose TSS Test Suite Structure UDUB User Determined User Busy ETSI ETSI TS 101 585 V1.2.1 (2014-04) 11
7f110eeff44cca5c59b5fc967e08482a	101 585	4 Test Suite Structure (TSS)	BCALL successful SS_bcall_xxx Codec_Negotiation SS_codec_xxx Resource_Reservation SS_resource_xxx unsuccessful SS_unsucc_xxx SIP-SIP Service OIP SS_oip_xxx OIR SS_oir_xxx TIP SS_tip_xxx TIR SS_tir_xxx HOLD SS_hold_xxx CFU SS_cfu_xxx CFB SS_cfb_xxx CFNR SS_cfnr_xxx CFNL SS_cfnl_xxx CD SS_cd_xxx CONF SS_conf_xxx ACR-CB SS_acr-cb_xxx CUG SS_cug_xxx CW SS_cw_xxx ECT SS_ect_xxx MCID SS_mcid_xxx MWI SS_mwi_xxx CC SS_cc_xxx SIP-I UUS SS_uus_xxx SUB SS_sub_xxx TP SS_tp_xxx NubP SS_NP_xxx ACCOUNTING SS_acc _xxx CS SS_csel_xxx EmC SS_ecall_xxx SIP_charging SS_sipc_xxx SIP-SIP/QoS SS_qos_xxx
7f110eeff44cca5c59b5fc967e08482a	101 585	5 Declarations
7f110eeff44cca5c59b5fc967e08482a	101 585	5.1 Numbering Scheme	FFS.
7f110eeff44cca5c59b5fc967e08482a	101 585	5.2 Reference configuration	This reference configuration depicted in figure 5.2-1 shall be used to perform an interconnection test between two network operators. Here is depicted the reference point to observe the message flow at the 'Ic' interface between the two networks (in the Test purposes mentioned 'Interconnection Interface') one for a single operator and the possible set of end devices used to perform the Test Purposes. ETSI ETSI TS 101 585 V1.2.1 (2014-04) 12 Figure 5.2-1: Reference configuration for the interconnection test
7f110eeff44cca5c59b5fc967e08482a	101 585	5.3 Selection of End Devices	With the specified Test Purposes in the present document, the compatibility between the interconnected networks and the used end devices shall be assured. Each Test Purpose shall be performed by using a physical end device to assure the end-to-end compatibility between the two interconnected networks. This is highly recommended due to the fact that the impact from an end device to another end device is important and will be marginal compensated by the network. Which Test Purposes are possible to perform depends on the types of end devices used in the network. The table 5.3-1 gives an overview of end devices. The green highlighted element in the table represents the mandatory type of end devices used in the test. The yellow highlighted elements in the table represents the optional type of end devices used in the test. Table 5.3-1: Overview of end devices Type of End devices Network B Network A SIP POTS ISDN GSM VoLTE PSTN SIP POTS ISDN GSM VoLTE PSTN ETSI ETSI TS 101 585 V1.2.1 (2014-04) 13
7f110eeff44cca5c59b5fc967e08482a	101 585	6 Selection Expressions	Table 6-1 is used to select the optional Test Purposes for the compatibly test between network operator A and network operator B. • Network operator 1 is in the role of Network A, Network operator 2 is in the role of Network B. In case of Repeat this test in reverse direction. mentioned in the Comment line in the Test Purpose. • Network operator 2 is in the role of Network A, Network operator 1 is in the role of Network B. In each Test Purpose is determined in the field SELECTION EXPRESSION whether the selection expression applies and the Test Purpose shall be performed. It has to be decided for which role the Test purpose is applicable (Support Network A, Support Network B). Before the start of the test, the table shall be filled out (yes/no) so the operators reply to the questions in table 6-1. This table can be used as a PICS form as used in a conformance test. Table 6-1: Selection expression applicable in the Test Purposes SELECTION EXPRESSION: Support Support Network A Network B Network capabilities SE 1: The originating network (Network A) sends the P-Charging-Vector header? SE 2: The originating network (Network A) sends a subset of parameters in the P-Charging-Vector header? SE 3: The P-Early-Media header is supported? SE 4: Overlap procedure using multiple INVITE method is supported? SE 5: Overlap sending using in-dialog method is supported? SE 6: Network A supports the PSTN XML schema? SE 7: The resource reservation procedure is supported? SE 8: Void SE 9: The network is untrusted? SE 10: Originating network does not have a number portability data base, the number portability look up is done in the interconnected network? SE 11: The network supports the REFER method? SE 12: The Network supports the 3 party call control procedure (REFER interworking)? SE 13: The Number Portability is supported? SE 14: Carrier Selection is performed? SE 15: The Network is a Long distance carrier? SE 16: SIP Support of Charging is supported? SE 17: The interworking ISUP - SIP I is performed in the network? Supplementary services SE 18: The network supports the Originating Identification Presentation (OIP)? SE 19: The network supports the "Special arrangement" procedure for the originating user? SE 20: The network supports the Originating Identification Restriction (OIR)? SE 21: The Network supports the Terminating Identification Presentation (TIP)? SE 22: The network supports the "Special arrangement" procedure for the terminating user? SE 23: The Network supports the Terminating Identification Restriction (TIR)? SE 24: The Network supports the session HOLD procedure? SE 25: The network supports Communication Forwarding Unconditional (CFU)? SE 26: The network supports Communication Forwarding Busy (CFB)? SE 27: The network supports Communication Forwarding No Reply (CFNR)? SE 28: The Network supports Communication Forwarding Not Logged in (CFNL)? SE 29: The Network supports Communication Deflection? SE 30: The Network supports the CDIV Notification procedure? ETSI ETSI TS 101 585 V1.2.1 (2014-04) 14 SELECTION EXPRESSION: Support Support Network A Network B SE 31: The Network supports conference (CONF)? SE 32: The Network supports the Communication Barring procedure (CB) - (Black list for incoming calls)? SE 33: The Network supports the Anonymous Communication Rejection (ACR)? SE 34: The Network supports the Closed User Group (CUG)? SE 35: The Network supports the Communication Waiting (CW) service? SE 36: The Network supports the TAS-CW timer? SE 37: The Network supports Explicit Communication Transfer (ECT)? SE 38: The network supports Malicious Communication Identification (MCID)? SE 39: The Network supports Message Waiting Indication (MWI)? SE 40: The Network supports Completion of Communications to Busy Subscriber (CCBS)? SE 41: The Network supports Completion of Communications by No Reply (CCNR)? Terminal capabilities SE 42: Void SE 43: The End device supports Fax transmission via G.711 codec? SE 44: The End device supports Fax transmission via V.152 codec? SE 45: The End device supports Fax transmission via m-line T.38 codec? SE 46: A SIP end device is used supporting an ISDN user equipment and the PSTN XML Schema is used? SE 47: End device is located in the PSTN or PLMN? SE 48: The terminating UE supports the from-change tag procedure and sends a second user identity in an UPDATE request after the dialogue is confirmed? SE 49: The end device performs ECT using the 'Blind/assured transfer'? SE 50: The end device performs ECT using the 'Consultative transfer'? SE 51: The end device supports the Resource reservation procedure? PSTN/PLMN Supplementary services SE 52: CLIP/CLIR is supported in the PSTN/PLMN part of the network? SE 53: COLP/COLR is supported in the PSTN/PLMN part of the network? SE 54: HOLD is supported in the PSTN/PLMN part of the network? SE 55: CDIV is supported in the PSTN/PLMN part of the network? SE 56: CONF/3PTY is supported in the PSTN/PLMN part of the network? SE 57: ACR is supported in the PSTN/PLMN part of the network? SE 58: CUG is supported in the PSTN/PLMN part of the network? SE 59: CW is supported in the PSTN/PLMN part of the network? SE 60: ECT is supported in the PSTN/PLMN part of the network? SE 61: MCID is supported in the PSTN/PLMN part of the network? SE 62: SUB is supported in the PSTN/PLMN part of the network? SE 63: UUS is supported in the PSTN/PLMN part of the network? SE 64: TP is supported in the PSTN/PLMN part of the network?
7f110eeff44cca5c59b5fc967e08482a	101 585	7 Test purposes	The application usage procedures in the ATS shall be compliant with TS 129 165 [1], TS 124 229 [2] and RFC 3261 [4]. The validation of the registration procedure is out of scope of the present document. ETSI ETSI TS 101 585 V1.2.1 (2014-04) 15
7f110eeff44cca5c59b5fc967e08482a	101 585	7.1 Testing of SIP protocol requirements

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.