Datasets:
OrganizedProgrammers
/
ETSISpecContent

Dataset card Data Studio Files Community
1
hash
stringlengths
32
32
doc_id
stringlengths
7
13
section
stringlengths
3
121
content
stringlengths
0
3.82M
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.2.2.7 Receipt of the Release message (REL)
TP307001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8 TSS reference: ISUP-SIP/Basic call/ Receipt of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: REL received before INVITE was sent Ensure that the SUT after receiving the IAM but before an INVITE has been sent. On receipt of a REL message: • no action is required on the SIP side other than to terminate local procedures if any are in progress. SIP Parameter values: ISUP Parameter values: REL: cause value: CV_ISUP (PIXIT) location: LOC_ISUP (PIXIT) Comments: ISUP/BICC SUT SIP IAM REL RLC  TP307002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8 TSS reference: ISUP-SIP/Basic call/ Receipt of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: REL received, BYE is sent after ACK for 200 OK was sent before early dialogue Ensure that the SUT after receiving the IAM with the complete called party number, sending an INVITE message on receipt REL message before a 200 OK response (any) message has been received which establishes a confirmed dialogue: • The SUT shall hold the REL message until a SIP 200 OK INVITE response has been received. • The SUT shall send a BYE request. The cause Value Indicator parameter defined as CV_ISUP shall be mapped to the Reason header field defined as CV_SIP. SIP Parameter values: cause value: CV_SIP (PIXIT) ISUP Parameter values: REL: cause value: CV_ISUP (PIXIT) location: LOC_ISUP (PIXIT) Comments: ISUP/BICC SUT SIP IAM INVITE REL RLC   200 OK INVITE ACK BYE  200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 181 TP307003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8 TSS reference: ISUP-SIP/Basic call/ Receipt of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: 200 OK INVITE received before 200 OK CANCEL was received. A BYE is sent Ensure that the SUT after receiving the IAM with the complete called party number, sending an INVITE message. On receipt of a REL message before a 200 OK response message has been received: • The SUT shall hold the REL message. A CANCEL is sent when any SIP response was been received. • On subsequently receiving 200 OK INVITE messages, the SUT shall send an ACK for the 200 OK INVITE and subsequently send a BYE request after the ACK has been sent. The cause Value Indicator parameter defined as CV_ISUP shall be mapped to the Reason header field defined as CV_SIP. SIP Parameter values: BYE: cause value: CV_SIP (PIXIT) ISUP Parameter values: REL: cause value: CV_ISUP (PIXIT) location: LOC_ISUP (PIXIT) Comments: ISUP/BICC SUT SIP IAM INVITE  100 Trying REL RLC  CANCEL  200 OK INVITE  200 OK CANCEL ACK BYE  200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 182 TP307004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8 TSS reference: ISUP-SIP/Basic call/ Receipt of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: REL received before early dialogue is established. Ensure that the SUT after receiving the IAM with the complete called party number, sending an INVITE message. On receipt of a REL message before an early dialogue with the message defined as SIP_MESSAGE has been established: • The SUT shall hold the REL message until a SIP_MESSAGE_VA response has been received. • The SUT shall send a CANCEL request. The cause Value Indicator parameter defined as CV_ISUP shall be mapped to the Reason header field defined as CV_SIP. SIP Parameter values: CANCEL: cause value: CV_SIP (PIXIT) ISUP Parameter values: REL: cause value: CV_ISUP (PIXIT) location: LOC_ISUP (PIXIT) Comments: ISUP/BICC SUT SIP IAM INVITE REL RLC   SIP_MESSAGE_VA CANCEL  200 OK CANCEL  487 Request terminated ACK TP307005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8 TSS reference: ISUP-SIP/Basic call/ Receipt of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: REL received, BYE is sent after ACK for 200 OK was sent in early dialogue Ensure that the SUT after receiving the IAM with the complete called party number, sending an INVITE message. On receipt of a REL message after a 200 OK response message has been received: • The SUT shall send a BYE request after the ACK has been sent. The cause Value Indicator parameter defined as CV_ISUP shall be mapped to the Reason header field defined as CV_SIP. SIP Parameter values: BYE: cause value: CV_SIP (PIXIT) ISUP Parameter values: REL: cause value: CV_ISUP (PIXIT) location: LOC_ISUP (PIXIT) Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE REL RLC  ACK BYE  200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 183 TP307006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8 TSS reference: ISUP-SIP/Basic call/ Receipt of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: REL received, BYE is sent after ACK for 200 OK was sent in early dialogue established by several messages Ensure that the SUT after receiving the IAM with the complete called party number, sending an INVITE message. On receipt of a REL message after an early dialogue with the SIP message defined with the SIP_MESSAGE_VA has been established: • The SUT shall send a CANCEL request. The cause Value Indicator parameter defined as CV_ISUP shall be mapped to the Reason header field defined as CV_SIP. SIP Parameter values: CANCEL: cause value: CV_SIP (PIXIT) ISUP Parameter values: REL: cause value: CV_ISUP (PIXIT) location: LOC_ISUP (PIXIT) Comments: ISUP/BICC SUT SIP IAM INVITE  SIP_MESSAGE_VA REL RLC  CANCEL  200 OK CANCEL  487 Request terminated ACK Table 11 Values for test purpose TP307004; TP307006 VA SIP MESSAGE_VA VA_1 180 Ringing VA_2 181 Call Is Being Forwarded VA_3 182 Queued VA_4 183 Session Progress Table 12 Values for test purposes 307004 - 307006 ←SIP Message Reason header field CV_SIP ← REL Cause Indicators parameter CV_ISUP VA_1 Normal call clearing # 16 Normal call clearing # 16 VA_2 Normal, unspecified # 31 Normal, unspecified # 31 VA_3 Temporary failure # 41 Temporary failure # 41 VA_4 Invalid message, unspecified # 95 Invalid message, unspecified # 95 VA_5 Recovery on timer expiry # 102 Recovery on timer expiry # 102 VA_6 Protocol error, unspecified # 111 Protocol error, unspecified # 111 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 184 Table 13: Mapping of Cause Indicators parameter into SIP Reason header fields Cause indications parameter field Value of parameter field component of SIP Reason header field Component value - - Protocol "ITU-T Recommendation Q.850 [5]" Cause Value "XX" (see note 1) Protocol-cause "cause= XX" (see note 1) - - Reason-text Should be filled with the definition text as stated in ITU-T Recommendation Q.850 [5] (see note 2) NOTE 1: "XX" is the Cause Value as defined in ITU-T Recommendation Q.850 [5]. NOTE 2: Due to the fact that the Cause Indications parameter does not include the definition text as defined in table1/ITU-T Recommendation Q.850 [5] this is based on provisioning in the O-IWU.
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.2.2.8 Sending of a REL message / receipt of a backward BYE
TP308001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.7 TSS reference: ISUP-SIP /Basic call/ Sending of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: BYE received, REL cause #16 is sent Ensure that the SUT after receiving the IAM sends out an INVITE message and on receipt of a BYE message where a Reason header field with ITU-T Recommendation Q.850 [5] Cause Value is not included: • sends a REL message with the Cause value Value No. 16 ("normal clearing"). SIP Parameter values: ISUP Parameter values: REL; Cause value "Normal call clearing" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL   BYE RLC 200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 185 TP308002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.7 TSS reference: ISUP-SIP /Basic call/ Sending of the Release message (REL)/ SIP selection criteria: PICS 4/11 ISUP selection criteria: Test purpose: BYE Reason header #x received, REL cause #x is sent Ensure that the SUT after receiving the IAM sends out a INVITE message and on receipt of a BYE message where a Reason header field with ITU-T Recommendation Q.850 [5] Cause Value is included: • sends a REL message. The Cause Value is in the Reason header filed mapped to the ISUP Cause Value field in the ISUP REL. SIP Parameter values: BYE cause value: CV_SIP (PIXIT) ISUP Parameter values: REL; cause value: CV_ISUP (PIXIT) Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL   BYE RLC 200 OK BYE Table 14: Mapping of SIP Reason header fields into Cause Indicators parameter component of SIP Reason header field Component value BICC/ISUP Parameter / field value Protocol "ITU-T Rec. Q.850 [5]" Cause Indication parameter - protocol-cause "cause = XX" (see note) Cause Value "XX" (see note) - - Location "network beyond interworking point" NOTE: "XX" is the Cause Value as defined in ITU-T Recommendation Q.850 [5]. TP308003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.7 TSS reference: ISUP-SIP /Basic call/ Sending of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: Final response without Reason header received, mapping in REL Ensure that the SUT after receiving the IAM sends out an INVITE message. On receipt of a Failure message (4xx, 5xx, 6xx) where a Reason header field with ITU-T Recommendation Q.850 [5] Cause Value is not included defined as SIP_Failure_VA: • sends a REL message with the Cause value set to CV_ISUP. SIP Parameter values: ISUP Parameter values: REL; cause value: CV_ISUP Comments: ISUP/BICC SUT SIP IAM INVITE REL   SIP_Failure_VA RLC ACK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 186 Table 15 Values for test purpose TP308003 VA ←REL (Cause Value) CV_ ISUP ←4XX/5XX/6XX SIP message SIP_Failure_VA VA_01 127 Interworking 400 Bad Request VA_02 127 Interworking 401 Unauthorised VA_03 127 Interworking 402 Payment Required VA_04 127 Interworking 403 Forbidden VA_05 127 Interworking 405 Method Not Allowed VA_06 127 Interworking 406 Not Acceptable VA_07 127 Interworking 407 Proxy authentication required VA_08 127 Interworking 408 Request Timeout VA_09 22 Number changed (without diagnostic) 410 Gone VA_10 127 Interworking 413 Request Entity too long VA_11 127 Interworking 414 Request-uri too long VA_12 127 Interworking 415 Unsupported Media type VA_13 127 Interworking 416 Unsupported URI scheme VA_14 127 Interworking 420 Bad Extension VA_15 127 Interworking 421 Extension required VA_16 127 Interworking 423 Interval Too Brief VA_17 20 Subscriber absent 480 Temporarily Unavailable VA_18 127 Interworking 481 Call/Transaction does not exist VA_19 127 Interworking 482 Loop Detected VA_20 127 Interworking 483 Too many hops VA_21 127 Interworking 485 Ambiguous VA_22 17 User busy 486 Busy Here VA_23 127 Interworking 488 Not acceptable here VA_24 127 Interworking 493 Undecipherable VA_25 127 Interworking 500 Server Internal error VA_26 127 Interworking 501 Not implemented VA_27 127 Interworking 502 Bad Gateway VA_28 127 Interworking 503 Service Unavailable VA_29 127 Interworking 504 Server timeout VA_30 127 Interworking 505 Version not supported VA_31 127 Interworking 513 Message too large VA_32 127 Interworking 580 Precondition failure VA_33 17 User busy 600 Busy Everywhere VA_34 21 Call rejected 603 Decline VA_35 1 Unallocated number 604 Does not exist anywhere VA_36 127 Interworking 606 Not acceptable TP308004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.7 TSS reference: ISUP-SIP /Basic call/ Sending of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: Final response with Reason header received, mapping in REL Ensure that the SUT after receiving the IAM sends out an INVITE message. On receipt of a Failure message (4xx, 5xx, 6xx) where a Reason header field with ITU-T Recommendation Q.850 [5] Cause Value CV_ISUP is included defined as SIP_Failure_VA: • sends a REL message with the Cause value set to CV_ISUP. SIP Parameter values: ISUP Parameter values: REL; cause value: CV_ISUP Comments: ISUP/BICC SUT SIP IAM INVITE REL(#xx)   SIP_Failure_VA RLC ACK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 187 Table 16 Values for test purpose TP308004, TP308005 VA ←REL (Cause Value PIXIT) ←4XX/5XX/6XX SIP message SIP_Failure_VA VA_01 CV_ ISUP 400 Bad Request VA_02 CV_ ISUP 401 Unauthorised VA_03 CV_ ISUP 402 Payment Required VA_04 CV_ ISUP 403 Forbidden VA_05 CV_ ISUP 405 Method Not Allowed VA_06 CV_ ISUP 406 Not Acceptable VA_07 CV_ ISUP 407 Proxy authentication required VA_08 CV_ ISUP 408 Request Timeout VA_09 CV_ ISUP 410 Gone VA_10 CV_ ISUP 413 Request Entity too long VA_11 CV_ ISUP 414 Request-uri too long VA_12 CV_ ISUP 415 Unsupported Media type VA_13 CV_ ISUP 416 Unsupported URI scheme VA_14 CV_ ISUP 420 Bad Extension VA_15 CV_ ISUP 421 Extension required VA_16 CV_ ISUP 423 Interval Too Brief VA_17 CV_ ISUP 480 Temporarily Unavailable VA_18 CV_ ISUP 481 Call/Transaction does not exist VA_19 CV_ ISUP 482 Loop Detected VA_20 CV_ ISUP 483 Too many hops VA_21 CV_ ISUP 485 Ambiguous VA_22 CV_ ISUP 486 Busy Here VA_23 CV_ ISUP 488 Not acceptable here VA_24 CV_ ISUP 493 Undecipherable VA_25 CV_ ISUP 500 Server Internal error VA_26 CV_ ISUP 501 Not implemented VA_27 CV_ ISUP 502 Bad Gateway VA_28 CV_ ISUP 503 Service Unavailable VA_29 CV_ ISUP 504 Server timeout VA_30 CV_ ISUP 505 Version not supported VA_31 CV_ ISUP 513 Message too large VA_32 CV_ ISUP 580 Precondition failure VA_33 CV_ ISUP 600 Busy Everywhere VA_34 CV_ ISUP 603 Decline VA_35 CV_ ISUP 604 Does not exist anywhere VA_36 CV_ ISUP 606 Not acceptable ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 188 TP308005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.7 TSS reference: ISUP-SIP /Basic call/ Sending of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: Final response contains a Reason header in early dialogue received Ensure that the SUT after receiving the IAM sends out an INVITE message, a SIP message defined as SIP_MESSAGE_VA has been received on receipt of a Failure message (4xx, 5xx, 6xx) defined as SIP_Failure_VA where a Reason header field with ITU-T Recommendation Q.850 [5] Cause Value is included: • sends a REL message. The Cause Value in the header field set to CV_SIP is mapped to the ISUP Cause Value field in the ISUP REL message with the Cause value set to CV_ ISUP. SIP Parameter values: CV_SIP (PIXIT) ISUP Parameter values: CV_ ISUP (PIXIT) Comments: ISUP/BICC SUT SIP IAM INVITE  SIP MESSAGE_VA REL   SIP_Failure_VA RLC ACK Table 17 Values for test purpose TP308005 VA SIP MESSAGE_VA VA_1 180 Ringing VA_2 181 Call Is Being Forwarded VA_3 182 Queued VA_4 183 Session Progress TP308006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.7 TSS reference: ISUP-SIP /Basic call/ Sending of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: Final response without Reason header received, mapping in REL Ensure that the SUT after receiving the IAM sends out an INVITE message. On receipt of a response message (3xx) defined as SIP_Response_VA, the SUT: • sends a REL message with the Cause value 127 Interworking. SIP Parameter values: ISUP Parameter values: REL; cause value: 127 Comments: ISUP/BICC SUT SIP IAM INVITE REL(#127)   SIP_Response_VA RLC ACK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 189 Table 18 Values for test purposes TP308006 VA ←REL (Cause Value) CV_ ISUP ←3XX SIP message SIP_Response_VA VA_01 127 Interworking 300 Multiple Choices VA_02 127 Interworking 301 Moved Permanently VA_03 127 Interworking 302 Move Temporarily VA_04 127 Interworking 305 Use Proxy VA_05 127 Interworking 380 Alternative Service
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.2.2.9 Autonomous release at O-MGCF
TP309001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.12.1 TSS reference: ISUP-SIP/Basic call/Autonomous release/ SIP selection criteria: PICS 3/2 ISUP selection criteria: Test purpose: Overlap supported, REL is sent when 404/484 received and Ti/w3 is expired Ensure that the SUT on receipt of a 484 Address Incomplete or 404 Not Found response for the current INVITE (i.e. there are no other pending INVITE transactions for this call), if the SUT is configured to propagate overlap signalling into the SIP network, the SUT: • Shall not send a REL message immediately and shall instead start timer TOIW3. The REL message shall only be sent if TI/W3 expires. • The REL message contains the Cause Value 28. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE CASE A  484 Address Incomplete ACK Start timer TI/W3 Timeout TI/W3 REL #28  RLC CASE B  404 Not Found ACK Start timer TI/W3 Timeout TI/W3 REL #28  RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 190 TP309002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.12.1 TSS reference: ISUP-SIP/Basic call/Autonomous release/ SIP selection criteria: NOT PICS 3/2 ISUP selection criteria: Test purpose: Overlap not supported, REL is sent when 404/484 received Ensure that the SUT on receipt of a 484 Address Incomplete response for the current INVITE (i.e. there are no other pending INVITE transactions for this call), if the O-MGCF is not configured to propagate overlap signalling into the SIP network then the timer shall not be started and the: • REL shall be sent immediately to the BICC/ISUP network. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE REL #28   484 Address Incomplete RLC ACK TP309003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.18 TSS reference: ISUP-SIP/Basic call/Autonomous release/ SIP selection criteria: PICS 4/5 AND PICS 4/11 ISUP selection criteria: PICS 4/2 Test purpose: Preconditions supported, call setup released when COT(failed) received Ensure that the SUT on receipt of a COT "failed" and preconditions used, the SUT: • sends a CANCEL to the SIP network. SIP Parameter values: ISUP Parameter values: IAM: Nature of connection indicators "continuity check required on this circuit" Comments: ISUP/BICC SUT SIP IAM INVITE COT(failed) CANCEL  200 OK CANCEL  487 Request terminated ACK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 191 TP309004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.7.3 TSS reference: ISUP-SIP/Basic call/Autonomous release/ SIP selection criteria: PICS 4/5 AND PICS 4/11 ISUP selection criteria: PICS 4/2 Test purpose: Preconditions supported, call setup released when T8 expired Ensure that the SUT when the ISUP/BICC timer T8 is expired and preconditions used, the SUT: • sends a CANCEL or BYE to the SIP network. SIP Parameter values: ISUP Parameter values: IAM: Nature of connection indicators "continuity check required on this circuit" Comments: ISUP/BICC SUT SIP IAM INVITE T8 expirees CANCEL  200 OK CANCEL  487 Request terminated ACK TP309005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.16 TSS reference: ISUP-SIP/Basic call/Autonomous release/ SIP selection criteria: PICS 4/7 AND PICS 4/15 ISUP selection criteria: PICS 4/2 Test purpose: Preconditions supported, 580 mapped in REL #47 Ensure that the SUT when the resource reservation is unsuccessful and preconditions used, the SUT responds to an INVITE: • send a REL with cause value # 47 SIP Parameter values: ISUP Parameter values: IAM: Nature of connection indicators "continuity check required on this circuit" Comments: ISUP/BICC SUT SIP IAM INVITE REL   580 Precondition Failure RLC ACK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 192 TP309006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.17.2 TSS reference: ISUP-SIP/Basic call/Autonomous release/ SIP selection criteria: PICS 4/7 AND PICS 4/15 ISUP selection criteria: PICS 4/2 Test purpose: Preconditions supported, 580 mapped in REL #47 Ensure that the SUT when the resource reservation is unsuccessful and preconditions used, the SUT responds to an UPDATE: • send a REL with cause value # 47 SIP Parameter values: ISUP Parameter values: IAM: Nature of connection indicators "continuity check required on this circuit" Comments: ISUP/BICC SUT SIP IAM INVITE  183 Session Progress PRACK  200 OK PRACK REL   580 Precondition Failure RLC ACK 6.2.2.10 Receipt of Reset circuit message (RSC), Circuit group reset message (GRS) or Circuit group blocking message (CGB) with the indication hardware failure oriented
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.2.2.10.1 Receipt of Reset Circuit message (RSC)
TP310001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Reset circuit message (RSC) SIP selection criteria: ISUP selection criteria: Test purpose: RSC received while an INVITE was not sent Ensure that the SUT after receiving the IAM but before an INVITE has been sent on receipt of a RSC message: • no action is required on the SIP side other than to terminate local procedures if any are in progress. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM RSC RLC  ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 193 TP310002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Reset circuit message (RSC) SIP selection criteria: ISUP selection criteria: Test purpose: RSC received while no response for an INVITE is received Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt RSC message before a SIP MESSAGE_VA response message has been received: • The SUT shall hold the RSC message until a SIP response has been received. • The SUT shall send a CANCEL request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE RSC RLC   SIP MESSAGE_VA CANCEL  200 OK CANCEL  487 Request terminated ACK Table 19 Values for test purpose TP310002 VA SIP MESSAGE_VA VA_1 100 Trying VA_2 180 Ringing VA_3 181 Call Is Being Forwarded VA_4 182 Queued VA_5 183 Session Progress ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 194 TP310003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Reset circuit message (RSC) SIP selection criteria: ISUP selection criteria: Test purpose: RSC received. While CANCEL is sent, a 200 OK INVITE is received Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt RSC message before a 200 OK response message has been received: • On subsequently receiving 200 OK INVITE messages, the SUT shall send an ACK for the 200 OK INVITE and subsequently send a BYE request after the ACK has been sent. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE  100 Trying RSC CANCEL RLC   200 OK INVITE ACK  200 OK CANCEL BYE  200 OK BYE TP310004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Reset circuit message (RSC) SIP selection criteria: ISUP selection criteria: Test purpose: RSC received after the ACK for a 200 OK INVITE was sent. A BYE is sent Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message with the complete called party number, sending a BYE message on receipt RSC message after a 200 OK response message has been received: • The SUT shall send a BYE request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK RSC BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 195 TP310005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Reset circuit message (RSC) SIP selection criteria: ISUP selection criteria: Test purpose: RSC in early dialogue received. A CANCEL is sent Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt RSC message after an early dialogue with the SIP message defined with the SIP_MESSAGE_VA has been established: • The SUT shall send a CANCEL or BYE request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE  SIP MESSAGE_VA RSC RLC  CANCEL  200 OK CANCEL  487 Request terminated ACK Table 20 Values for test purpose; TP310005 VA SIP MESSAGE_VA VA_1 180 Ringing VA_2 181 Call Is Being Forwarded VA_3 182 Queued VA_4 183 Session Progress
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.2.2.10.2 Receipt of Circuit group reset message (GRS)
TP311001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group reset message (GRS) SIP selection criteria: ISUP selection criteria: Test purpose: GRS received while an INVITE was not sent Ensure that the SUT after receiving the IAM but before an INVITE has been sent on receipt of GRS message: • no action is required on the SIP side other than to terminate local procedures if any are in progress. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM GRS GRA  ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 196 TP311002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group reset message (GRS) SIP selection criteria: ISUP selection criteria: Test purpose: GRS received while no response for an INVITE is received Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt GRS message before SIP MESSAGE_VA response message has been received: • The SUT shall hold the GRS message until a SIP response has been received. • The SUT shall send a CANCEL request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O- MGCF. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE GRS GRA   SIP MESSAGE_VA CANCEL  200 OK CANCEL  487 Request terminated ACK Table 21 Values for test purpose TP311002 VA SIP MESSAGE_VA VA_1 100 Trying VA_2 180 Ringing VA_3 181 Call Is Being Forwarded VA_4 182 Queued VA_5 183 Session Progress ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 197 TP311003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group reset message (GRS) SIP selection criteria: ISUP selection criteria: Test purpose: GRS received. While CANCEL is sent, a 200 OK INVITE is received Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt GRS message before a 200 OK response message has been received: • The SUT shall hold the GRS message until a response has been received. A CANCEL is sent. • On subsequently receiving 200 OK INVITE messages, the SUT shall send an ACK for the 200 OK INVITE and subsequently send a BYE request after the ACK has been sent. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE  100 Trying GRS CANCEL GRA   200 OK INVITE ACK  200 OK CANCEL BYE  200 OK BYE TP311004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group reset message (GRS) SIP selection criteria: ISUP selection criteria: Test purpose: GRS received after the ACK for a 200 OK INVITE was sent. A BYE is sent Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message with the complete called party number, sending a BYE message on receipt GRS message after a 200 OK response message has been received: • The SUT shall send a BYE request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK GRS BYE GRA   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 198 TP311005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group reset message (GRS) SIP selection criteria: ISUP selection criteria: Test purpose: GRS in early dialogue received. A CANCEL is sent Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt GRS message after an early dialogue with the SIP message defined with the SIP_MESSAGE_VA has been established: • The SUT shall send a CANCEL request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE  SIP MESSAGE_VA GRS GRA  CANCEL  200 OK CANCEL  487 Request terminated ACK Table 22 Values for test purpose TP311005 VA SIP MESSAGE_VA VA_1 180 Ringing VA_2 181 Call Is Being Forwarded VA_3 182 Queued VA_4 183 Session Progress ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 199 TP311006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group reset message (GRS) SIP selection criteria: ISUP selection criteria: Test purpose: GRS for more than one CIC received. Send a BYE for each circuit Ensure that the SUT after receiving more than one IAM's sending an INVITE message for each call association on receipt of a GRS message were the Range Parameter value is bigger than "1": • the SUT shall send a BYE requests for each call association. SIP Parameter values: ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM(1) INVITE(1) ACM   180 Ringing ANM   200 OK INVITE ACK IAM(2) INVITE(2) ACM   180 Ringing ANM   200 OK INVITE ACK GRS(1) BYE(1) GRA   200 OK BYE BYE(2)  200 OK BYE NOTE: BYE(1) and BYTE(2) possible received in reverse order.
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.2.2.10.3 Receipt of Circuit group blocking message (CGB)
TP312001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group blocking message (CGB) with the indication hardware failure oriented SIP selection criteria: ISUP selection criteria: Test purpose: CGB received while an INVITE was not sent Ensure that the SUT after receiving the IAM but before an INVITE has been sent on receipt of CGB message Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented": • no action is required on the SIP side other than to terminate local procedures if any are in progress. SIP Parameter values: ISUP Parameter values: CGB/CGBA: Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" Comments: ISUP/BICC SUT SIP IAM CBG CGBA  ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 200 TP312002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group blocking message (CGB) with the indication hardware failure oriented SIP selection criteria: ISUP selection criteria: Test purpose: CGB received while no response for an INVITE is received Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt CGB message Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" before a SIP MESSAGE_VA response message has been received: • The SUT shall hold the CGB message until a SIP 200 OK response has been received. • The SUT shall send a CANCEL request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: CGB/CGBA: Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" Comments: ISUP/BICC SUT SIP IAM INVITE CGB CGBA   SIP MESSAGE_VA CANCEL  200 OK CANCEL  487 Request terminated ACK Table 23 Values for test purpose TP312002 VA SIP MESSAGE_VA VA_1 100 Trying VA_2 180 Ringing VA_3 181 Call Is Being Forwarded VA_4 182 Queued VA_5 183 Session Progress ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 201 TP312003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group blocking message (CGB) with the indication hardware failure oriented SIP selection criteria: ISUP selection criteria: Test purpose: CGB received. While CANCEL is sent, a 200 OK INVITE is received Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt CGB message Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" before a 200 OK response message has been received: • On subsequently receiving 200 OK INVITE messages, the SUT shall send an ACK for the 200 OK INVITE and subsequently send a BYE request after the ACK has been sent. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: CGB/CGBA: Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" Comments: ISUP/BICC SUT SIP IAM INVITE  100 Trying CGB CANCEL CGBA   200 OK INVITE ACK  200 OK CANCEL BYE  200 OK BYE TP312004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group blocking message (CGB) with the indication hardware failure oriented SIP selection criteria: ISUP selection criteria: Test purpose: CGB received after the ACK for a 200 OK INVITE was sent. A BYE is sent Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message with the complete called party number, sending a BYE message on receipt CGB message Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" after a 200 OK response message has been received: • The SUT shall send a BYE request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: CGB/CGBA: Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK CGB BYE CGBA   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 202 TP312005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group blocking message (CGB) with the indication hardware failure oriented SIP selection criteria: ISUP selection criteria: Test purpose: CGB in early dialogue received. A CANCEL is sent Ensure that the SUT after receiving the IAM with the complete called party number, sending a INVITE message on receipt CGB message Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" after an early dialogue with the SIP message defined with the SIP_MESSAGE_VA has been established: • The SUT shall send a CANCEL request. • A Reason header field containing the (ITU-T Recommendation Q.850 [5]) Cause Value # 31 is added to the SIP message to be sent by the SIP side of the O-MGCF. SIP Parameter values: ISUP Parameter values: CGB/CGBA: Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" Comments: ISUP/BICC SUT SIP IAM INVITE  SIP MESSAGE_VA CGB CGBA  CANCEL  200 OK CANCEL  487 Request terminated ACK Table 24 Values for test purpose ; TP312005 VA SIP MESSAGE_VA VA_1 180 Ringing VA_2 181 Call Is Being Forwarded VA_3 182 Queued VA_4 183 Session Progress ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 203 TP312006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group blocking message (CGB) with the indication hardware failure oriented SIP selection criteria: ISUP selection criteria: Test purpose: CGB for more than one CIC received. Send a BYE for each circuit Ensure that the SUT after receiving more than one IAM's sending an INVITE message for each call association on receipt of a CGB message Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" where the Range and Status Parameter value is bigger than "1": • the SUT shall send a BYE requests for each call association. SIP Parameter values: ISUP Parameter values: CGB/CGBA: Circuit Group Supervision Message Type Indicator coded as "hardware failure oriented" Comments: ISUP/BICC SUT SIP IAM(1) INVITE(1) ACM   180 Ringing ANM   200 OK INVITE ACK IAM(2) INVITE(2) ACM   180 Ringing ANM   200 OK INVITE ACK CGB(1) BYE(1) CGBA   200 OK BYE BYE(2)  200 OK BYE NOTE: BYE(1) and BYTE(2) possible received in reverse order. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 204
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3 Interworking of supplemetary services
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1 Interworking from SIP to ISUP (Incoming Call)
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.1 Calling Line Identification (CLI)
TP501001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity not in E.164 format and From header not in the E.164 Format, no Privacy header. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field has not been received. sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 25: Values for test purposes TP501001 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 205 TP501002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity not in E.164 format and From header not in the E.164 Format, Privacy value none. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field was received and the priv-value component is set to "none". sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 206 TP501003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity not in E.164 format and From header not in the E.164 Format, Privacy value header. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field was received and the priv-value component is set to "header". sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 207 TP501004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity not in E.164 format and From header not in the E.164 Format, Privacy value user. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field was received and the priv-value component is set to "user". sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 208 TP501005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity not in E.164 format and From header not in the E.164 Format, Privacy value id. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field was received and the priv-value component is set to "id". sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 209 TP501006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity not in E.164 format and From header in the E.164 Format, no Privacy header received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field has not been received. sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 with the Generic number parameter coded: Address signals = derived from the From header Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 26: Values for test purposes TP501006 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 210 TP501007 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity not in E.164 format and From header in the E.164 Format, Privacy value none received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field was received and the priv-value component is set to "none". sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 with the Generic number parameter coded: Address signals = number provided by the user Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 27: Values for test purposes TP501007 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 211 TP501008 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity not in E.164 format and From header in the E.164 Format, Privacy value header received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field was received and the priv-value component is set to "header". sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 with the Generic number parameter coded: Address signals = number provided by the user Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 28: Values for test purposes TP501008 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 212 TP501009 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity not in E.164 format and From header in the E.164 Format, Privacy value user received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field was received and the priv-value component is set to "user". sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 with the Generic number parameter coded: Address signals = number provided by the user Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 29: Values for test purposes TP501009 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 213 TP501010 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity not in E.164 format and From header in the E.164 Format, Privacy value id received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field was received and the priv-value component is set to "id". sends an IAM message with the Calling party number parameter coded: Address signals = absent Screening indicator = network provided Number Incomplete Indicator = incomplete Numbering plan indicator = 000 Address Presentation Restricted Indicator = PIXIT Nature of address indicator = 0000000 with the Generic number parameter coded: Address signals = number provided by the user Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 30: Values for test purposes TP501010 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 214 TP501011 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity in E.164 format and From header not in the E.164 Format, no Privacy header received. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field has not been received. sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 31: Values for test purposes TP501011 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 215 TP501012 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity in E.164 format and From header not in the E.164 Format, Privacy value none received. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field was received and the priv-value component is set to "none". sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 32: Values for test purposes TP501012 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 216 TP501013 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity in E.164 format and From header not in the E.164 Format, Privacy value header received. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field was received and the priv-value component is set to "header". sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 217 TP501014 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity in E.164 format and From header not in the E.164 Format, Privacy value user received. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field was received and the priv-value component is set to "user". sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 218 TP501015 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity in E.164 format and From header not in the E.164 Format, Privacy value id received. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field was received and the priv-value component is set to "id". sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 219 TP501016 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity in E.164 format and From header in the E.164 Format, no Privacy header received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field has not been received. sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE with the Generic number parameter coded: Address signals = number derived from the From header Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 33: Values for test purposes TP501016 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 220 TP501017 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity in E.164 format and From header in the E.164 Format, Privacy value none received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field was received and the priv-value component is set to "none". sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE with the Generic number parameter coded: Address signals = number derived from the From header Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 34: Values for test purposes TP501017 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 221 TP501018 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity in E.164 format and From header in the E.164 Format, Privacy value header received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field was received and the priv-value component is set to "header". sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE with the Generic number parameter coded: Address signals = number derived from the From header Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 35: Values for test purposes TP501018 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 222 TP501019 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity in E.164 format and From header in the E.164 Format, Privacy value user received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field was received and the priv-value component is set to "user". sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE with the Generic number parameter coded: Address signals = number derived from the From header Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 36: Values for test purposes TP501019 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 223 TP501020 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/3 Test purpose: P-Asserted-Identity in E.164 format and From header in the E.164 Format, Privacy value id received. Send Calling party number and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field was received and the priv-value component is set to "id". sends an IAM message with the Calling party number parameter coded: Address signals = number derived from SIP P-Asserted-Identity Screening indicator = network provided Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE with the Generic number parameter coded: Address signals = number derived from the From header Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation restricted NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 224 TP501021 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/1 Test purpose: P-Asserted-Identity not in E.164 format and From header not in the E.164 Format, no Privacy header. Send Calling party number network provided Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field has not been received. sends an IAM message with the Calling party number parameter coded: Address signals = network provided (PIXIT) Screening indicator = network provided Nature of address indicator = NoA_VALUE Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = PIXIT SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 225 TP501022 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity sip URI, without user=phone and P-Asserted-Identity tel URI, no Privacy header. Send Calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a SIP URI with an identity 1 in the format "+" CC+ NDC+ SN has been received without user = phone; • the SIP P-Asserted-Identity containing a Tel URI with an identity 2 in the format "+" CC+ NDC+ SN has been received; • a Privacy header field has not been received. sends an IAM message with the Calling party number parameter coded: Address signals = identity 2 Screening indicator = network provided Number Incomplete Indicator = PIXIT Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 226 TP501023 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/1 AND PICS 6/12 Test purpose: P-Asserted-Identity not in E.164 format, no Privacy header. Send Calling party number network provided Address not available Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • a Privacy header field has not been received. sends an IAM message with the Calling party number parameter coded: Address signals = not present Screening indicator = network provided Number Incomplete Indicator = incomplete Address Presentation Restricted Indicator = Address not available NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 227 TP501024 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: PICS 6/1 AND PICS 6/3 AND PICS 6/12 Test purpose: P-Asserted-Identity not in E.164 format and From header in the E.164 Format, no Privacy header received. Send Calling party number network provided and Additional calling party number Ensure that the SUT in the Idle state, on receipt of a INVITE message where: • the SIP P-Asserted-Identity containing a URI with an identity in the format "+" CC+ NDC+ SN has not been received; • the SIP From header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received; • a Privacy header field has not been received. sends an IAM message with the Calling party number parameter coded: Address signals = not present Screening indicator = network provided Number Incomplete Indicator = incomplete Address Presentation Restricted Indicator = Address not available with the Generic number parameter coded: Address signals = number derived from the From header Screening indicator = user provided, not verified Number Incomplete Indicator = complete Numbering plan indicator = ISDN numbering plan Address Presentation Restricted Indicator = Presentation allowed NoAS: NoA_VALUE SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC Table 37: Values for test purposes TP501022, TP501023, TP501024 VA The next BICC/ISUP node is located NoA_VALUE Number parameter address format VA_01 in the same country 'National (Significant) number" NDC+SN VA_02 a different country "International number" CC+NDC+SN ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 228
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.2 Call Hold (HOLD)
TP502001 SIP reference: RFC 3261 [6] ISUP reference: clause 7.4.10/ [14] TSS reference: SIP-ISUP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: Each party can hold and retrieve the remote party in the confirmed state Ensure that a party can put the other party on hold at any time after the call is answered and before call clearing has begun. Ensure that a party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The calling party should be able to retrieve the other party The called party should be able to put the other party on hold The called party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM INVITE(sendonly) CPG(hold) 200 OK INVITE(recvonly)  INVITE(sendrecv) CPG(retrieve) 200 OK INVITE(sendrecv)  INVITE(sendonly)   CPG(hold) 200 OK INVITE(recvonly) INVITE(sendrecv)   CPG(retrieve) 200 OK INVITE(sendrecv) ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 229 TP502002 SIP reference: RFC 3261 [6] ISUP reference: clause 7.4.10/ [14] TSS reference: SIP-ISUP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 PICS 8/1 Test purpose: The calling party can hold and retrieve the remote party in the early dialogue Ensure that a party can put the other party on hold in the alerting state. Ensure that the party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The calling party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM UPDATE(sendonly) CPG(hold) 200 OK UPDATE(recvonly)  UPDATE(sendrecv) CPG(retrieve) 200 OK UPDATE(sendrecv)  TP502003 SIP reference: RFC 3261 [6] ISUP reference: clause 7.4.10/[14] TSS reference: SIP-ISUP/SS/HOLD/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/22 Test purpose: The calling party can hold and retrieve the remote party after the calling party has provided all information to process the call Ensure that a party can put the other party on hold after the calling user has provided all of the information necessary for processing the call. Ensure that the party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The calling party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version> incremented ISUP Parameter values: ACM: called party status: no indication CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval Event indicator PROGRESS (retrieve the call) Comments: SIP MGCF ISUP INVITE IAM UPDATE(sendonly) 200 OK UPDATE(recvonly)  UPDATE(sendrecv) 200 OK UPDATE(sendrecv)  ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 230 TP502004 SIP reference: RFC 3261 [6] ISUP reference: 7.4.10/[14] TSS reference: SIP-ISUP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: A party can hold and retrieve the remote party in the confirmed state using the UPDATE method (receiving) Ensure that a party can put the other party on hold at any time after the call is answered and before call clearing has begun. Ensure that a party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The calling party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM UPDATE(sendonly) CPG(hold) 200 OK INVITE(recvonly)  UPDATE(sendrecv) CPG(retrieve) 200 OK UPDATE(recvonly)  TP502005 SIP reference: RFC 3261 [6] ISUP reference: 7.4.10/[14] TSS reference: SIP-ISUP/SS/HOLD/ SIP selection criteria: PICS 8/4 PICS 8/3 ISUP selection criteria: PICS 5/22 Test purpose: A party can hold and retrieve the remote party in the confirmed state using the UPDATE method (sending) Ensure that a party can put the other party on hold at any time after the call is answered and before call clearing has begun. Ensure that a party can retrieve the call previously put on hold. The called party should be able to put the other party on hold The called party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM UPDATE(sendonly)   CPG(hold) 200 OK INVITE(recvonly) UPDATE(sendrecv)   CPG(retrieve) 200 OK UPDATE(recvonly) ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 231 TP502006 SIP reference: RFC 3261 [6] ISUP reference: 7.4.10/[14] TSS reference: SIP-ISUP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: Both parties can hold and retrieve the remote party in the confirmed state. First hold party retrieves first Ensure that a party can put the other party on hold at any time after the call is answered and before call clearing has begun. Ensure that a party in held state can put the remote party put on hold. Ensure that a party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The called party should be able to put the other party on hold The calling party should be able to retrieve the other party The called party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly or a=inactive (put on hold) a=sendrecv or a=recvonly or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: SIP MGCF ISUP INVITE 180 Ringing   200 OK INVITE   INVITE(sendonly) CPG(hold) 200 OK INVITE(recvonly)  INVITE(inactive)   CPG(hold) 200 OK INVITE(inactive) INVITE(recvonly) CPG(retrieve) 200 OK INVITE(sendonly)  INVITE(sendrecv)   CPG(retrieve) 200 OK INVITE(sendrecv) ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 232 TP502007 SIP reference: RFC 3261 [6] ISUP reference: 7.4.10/[14] TSS reference: SIP-ISUP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: Both parties can hold and retrieve the remote party in the confirmed state. Second hold party retrieves first Ensure that a party can put the other party on hold at any time after the call is answered and before call clearing has begun. Ensure that a party in held state can put the remote party put on hold. Ensure that a party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The called party should be able to put the other party on hold The called party should be able to retrieve the other party The calling party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly or a=inactive (put on hold) a=sendrecv or a=recvonly or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: SIP MGCF ISUP INVITE 180 Ringing   200 OK INVITE   INVITE(sendonly) CPG(hold) 200 OK INVITE(recvonly)  INVITE(inactive)   CPG(hold) 200 OK INVITE(inactive) INVITE(recvonly)   CPG(retrieve) 200 OK INVITE(sendonly) INVITE(sendrecv) CPG(retrieve) 200 OK INVITE(sendrecv) 
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.3 Terminal portability (TP)
Void. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 233
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.4 Conference calling (CONF)
TP504001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.14 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/10 Test purpose: Generic notification Conference established and Conference disconnected and SIP procedure Ensure that the SUT does not stop the temporarily sending one or more unicast media streams if a CPG message Generic notification indicator was received due to the CONF supplementary service. SIP Parameter values: ISUP Parameter values: CPG: Generic notification = Conference established CPG: Generic notification = Conference disconnected Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation  CPG(Conference established) Conversation  CPG(Conference disconnected) BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 234 TP504002 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.14 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/10 Test purpose: Generic notification Isolated and Reattached and SIP procedure Ensure that the SUT stop the temporarily sending one or more unicast media streams if a CPG message Generic notification indicator with the value GEN_NOT_VALUE was received due to the CONF supplementary service. If the media stream is either in state "sendonly" or "inactive" then: INVITE with the attribute line a=sendonly/sendrecv or omitted attribute line, else: no mapping. SIP Parameter values: SDP: a=sendonly/sentrecv or a line is omitted ISUP Parameter values: CPG: Generic notification = Conference established CPG: Generic notification = Isolated CPG: Generic notification = Reattached CPG: Generic notification = Conference disconnected Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation  CPG(Conference established) INVITE(sendonly)   CPG(Isolated) 200 OK INVITE(recvonly) ACK  INVITE(sendrecv)   CPG(Reattached) 200 OK INVITE(sendrecv) ACK  Conversation  CPG(Conference disconnected) BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 235 TP504003 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.14 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: NOT PICS 5/10 ISUP selection criteria: Test purpose: No mapping of isolated and reattached Ensure that the SUT on receipt of a CPG message due to the CONF supplementary service, the Generic notification indicator with the value. No mapping, no disrupting the SIP procedure. SIP Parameter values: No mapping ISUP Parameter values: CPG: Generic notification = Conference established CPG: Generic notification = isolated CPG: Generic notification = reattached CPG: Generic notification = Conference disconnected Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation  CPG(Conference established)  CPG(Isolated)  CPG(Reattached) Conversation  CPG(Conference disconnected) BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 236 TP504004 SIP reference: RFC 3261 [6] NGN reference: 7.4.14/[14] TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS [16] 8/2 ISUP selection criteria: PICS [16] 5/10 Test purpose: No mapping of generic notifications no change the session state Ensure that the MGCF can receive in a CPG the Generic notifications is "other party added" or "other party isolated" or "other party reattached" or "other party split" or " conference floating" or " other party disconnected" and there is no mapping on the SIP side and the call is not disrupted. SIP Parameter values: ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK  CPG(Conference established)  CPG(other party added)  CPG(other party isolated)  CPG(other party reattached)  CPG(other party split)  CPG(other party disconnected)  CPG(Conference floating)  CPG(Conference disconnected) BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 237 TP504005 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "conference established" Upon the receipt of a conference information document with the <conference-state-type> element active is set to "true", the MGCF shall send a CPG message to the CS side with a notification "conference established". SIP Parameter values: NOTIFY 1: Event contains conference; Subscription-State contains active; expires=xxxx application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 238 TP504006 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "other party added" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "connected" and it was not set to "on-hold" before and the Contact URI in the element entity is not the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "other other party added". SIP Parameter values: NOTIFY 1: see test case 504005 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) 200 OK NOTIFY  NOTIFY 2 CPG(other party added) 200 OK NOTIFY  BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 239 TP504007 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "isolated" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "on-hold" and it was set to "connected" before and the Contact URI in the element entity is the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "isolated". SIP Parameter values: NOTIFY 1: see test case 504005 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>on-hold</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) 200 OK NOTIFY  NOTIFY 2 CPG(isolated) 200 OK NOTIFY  BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 240 TP504008 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "other party isolated" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "on-hold" and it was set to "connected" before and the Contact URI in the element entity is not the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "other party isolated". SIP Parameter values: NOTIFY 1: See test case 504005 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>on-hold</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) 200 OK NOTIFY  NOTIFY 2 CPG(other party isolated) 200 OK NOTIFY  BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 241 TP504009 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "reattached" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "connected" and it was set to "on-hold" before and the Contact URI in the element entity is the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "reattached". SIP Parameter values: NOTIFY 1: See test case 504005 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>on-hold</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> NOTIFY 3: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) 200 OK NOTIFY  NOTIFY 2 CPG(isolated) 200 OK NOTIFY  NOTIFY 3 CPG(reattached) 200 OK NOTIFY  BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 242 TP504010 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "other party reattached" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "connected" and it was set to "on-hold" before and the Contact URI in the element entity is not the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "other party reattached". SIP Parameter values: NOTIFY 1: see test case 504005 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>on-hold</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> NOTIFY 3: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) 200 OK NOTIFY  NOTIFY 2 CPG(other party isolated) 200 OK NOTIFY  NOTIFY 3 CPG(other party reattached) 200 OK NOTIFY  BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 243 TP504011 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "other party disconnected" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "disconnected" and the element joining- method of joining-type is not set to "focus-owner, the MGCF shall send a CPG message to the CS side with a notification "other party disconnected". SIP Parameter values: NOTIFY 1: see test case 504005 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> NOTIFY 3: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>disconnected</status> <joining-method>dialed-out</ joining-method> <disconnection-method>departed<disconnection- method/> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) 200 OK NOTIFY  NOTIFY 2 CPG(other party added) 200 OK NOTIFY  NOTIFY 3 CPG(other party disconnected) 200 OK NOTIFY  BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 244 TP504012 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: NOT PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "other party added" Upon the receipt of a conference information document the conference notification information is not mapped to the PSTN side. No NOTIFY is sent to the ISDN user. SIP Parameter values: NOTIFY 1: see test case 504005 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>3</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) 200 OK NOTIFY  NOTIFY 2 CPG(other party added) 200 OK NOTIFY  BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 245 TP504013 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: ISUP selection criteria: Test purpose: The referring of MGCF is not possible call is established Ensure that a REFER request received by the MGCF is not successful. The request is rejected with 403 Forbidden. The CS -site is not affected. SIP Parameter values: REFER: Request URI contained the conference URI Refer-To contains the URI of ISUPx, method=invite Referred-By contains SIP or tel URI of SIPx ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK REFER 403 Forbidden  TP504014 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.5.6 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: ISUP selection criteria: Test purpose: The referring of MGCF is not possible call is not established Ensure that a REFER request received by the MGCF is not successful. The request is rejected with 403 Forbidden. The CS -site is not affected. SIP Parameter values: REFER: Request URI contained the conference URI Refer-To contains the URI of ISUPx, method=invite Referred-By contains SIP or tel URI of SIPx ISUP Parameter values: Comments: SIP MGCF ISUP REFER 403 Forbidden  ACK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 246
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.5 Three Party service (3PTY)
TP505001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.15 TSS reference: SIP-ISUP/SS/3PTY/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/5 AND PICS 5/18 Test purpose: Notification procedure supported Ensure that the SUT stop the temporarily sending one or more unicast media streams if a CPG message Generic notification indicator with the value • Conference established • Conference disconnected was received due to the 3PTY supplementary service. The media stream is set to: • sendrecv • no change SIP Parameter values: SDP: a= sendonly SDP: a= sendrecv ISUP Parameter values: CPG: notification = remote hold CPG: Generic notification = Conference established Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation INVITE(sendonly)   CPG(hold) 200 OK INVITE(recvonly) ACK  INVITE(sendrecv)   CPG(Conference established) 200 OK INVITE(sendrecv) ACK  Conversation  CPG(Conference disconnected) Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 247 TP505002 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.15 ITU-T Recommendation Q.734.2 [35], clause 2.7 TSS reference: SIP-ISUP/SS/3PTY/ SIP selection criteria: ISUP selection criteria: NOT PICS 5/18 Test purpose: Notification procedure not supported Ensure that the SUT on receipt of a CPG message due to the 3PTY supplementary service, the Generic notification indicator with the value. No mapping, no disrupting the SIP procedure. SIP Parameter values: No mapping ISUP Parameter values: CPG: Generic notification = Conference established CPG: Generic notification = Conference disconnected Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone INVITE(sendonly)   CPG(hold) 200 OK INVITE(recvonly) ACK   CPG(Conference established) Conversation  CPG(Conference disconnected) Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 248 TP504003 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.15 TSS reference: SIP-ISUP/SS/3PTY SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "conference established" Upon the receipt of a conference information document with the <conference-state-type> element active is set to "true", the MGCF shall send a CPG message to the CS side with a notification "conference established". SIP Parameter values: NOTIFY 1: Event contains conference; Subscription-State contains active; expires=xxxx application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK INVITE(sendonly) CPG(hold) 200 OK INVITE(recvonly)  ACK INVITE(SDP focus) 200 OK INVITE  ACK NOTIFY 1 CPG(Conference established) BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 249
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.6 Connected line identification (COL)
TP506001 ISUP reference: [2], clause 7.4.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: NOT PICS 5/22 ISUP selection criteria: Test purpose: Mapping of connected number not supported Ensure that the SUT, if a connected number is received in an ANM, does not disrupt the SIP signalling procedure. The connected number is not mapped into any SIP message. SIP Parameter values: ISUP Parameter values: ANM: Connected number Parameter Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 250 TP506002 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND PICS 13/1 ISUP selection criteria: Test purpose: Connected number national, presentation allowed, no additional connected number received Ensure that the SUT, on receipt of an ANM message with a Connected number parameter coded Address presentation restricted parameter = presentation allowed Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals in the format: NDC+SN and without the Generic number parameter, sends a 200 OK INVITE to the UAC with a P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received and Add CC (of the country where the MGCF is located) to Connected PN address signals to construct E.164 number in URI global number format. SIP Parameter values: 200 OK INVITE: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: ANM; Connected number parameter Address presentation restricted parameter = '00'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = Network provided Address signals = derived from the P-Asserted-Identity Generic number parameter not present Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 251 TP506003 NGN reference: ES 283 027 [1], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND PICS 13/1 ISUP selection criteria: Test purpose: Connected number international, presentation allowed, no additional connected number received Ensure that the SUT, on receipt of an ANM message with a Connected number parameter coded Address presentation restricted parameter = presentation allowed Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals in the format: CC+NDC+SN and without the Generic number parameter, sends a 200 OK INVITE to the UAC with a P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN as received in the connected number in the ANM. SIP Parameter values: 200 OK INVITE: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: ANM; Connected number parameter Address presentation restricted parameter = '00'B Nature of address indicator = 0000100'B Numbering plan indicator = '001'B Screening indicator = Network provided Address signals = PIXIT Generic number parameter not present Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 252 TP506004 ISUP reference: [14], clauses 7.4.2.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND NOT PICS 13/1 ISUP selection criteria: Test purpose: Connected number national, presentation allowed, additional connected number received Ensure that the SUT, on receipt of an ANM message with a Connected number parameter coded Address presentation restricted parameter = presentation allowed Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals in the format: NDC+SN Generic number parameter, Number Qualifier Indicator "Additional connected number" Address presentation restricted parameter = presentation allowed Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = user provided, not verified Address signals = PIXIT NDC+SN sends a 200 OK INVITE to the UAC with a P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received and Add CC (of the country where the MGCF is located) to Connected PN address signals to construct E.164 number in URI. Prefix number with "+". The additional connected number is not interworked SIP Parameter values: 200 OK INVITE: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: ANM; Connected number parameter Address presentation restricted parameter = '00'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = Network provided Address signals = PIXIT Generic number parameter Number Qualifier Indicator "00000101"B Address presentation restricted parameter = '00'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = '00'B Address signals = PIXIT Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 253 TP506005 ISUP reference: [14], clauses 7.4.2.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND NOT PICS 13/1 ISUP selection criteria: Test purpose: Connected number international, presentation allowed, additional connected number received Ensure that the SUT, on receipt of an ANM message with a Connected number parameter coded Address presentation restricted parameter = presentation allowed Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals in the format: PIXIT CC+NDC+SN Generic number parameter, Number Qualifier Indicator "Additional connected number" Address presentation restricted parameter = presentation allowed Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = user provided, not verified Address signals = CC+NDC+SN sends a 200 OK INVITE to the UAC with a P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received in the connected number in the ANM. The additional connected number is not interworked SIP Parameter values: 200 OK INVITE: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: ANM; Connected number parameter Address presentation restricted parameter = '00'B Nature of address indicator = "0000100'B Numbering plan indicator = '001'B Screening indicator = Network provided Address signals = PIXIT Generic number parameter Number Qualifier Indicator "00000101"B Address presentation restricted parameter = '00'B Nature of address indicator = '0000100'B Numbering plan indicator = '001'B Screening indicator = '00'B Address signals = PIXIT Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 254 TP506006 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND NOT PICS 13/1 ISUP selection criteria: Test purpose: Connected number national, presentation restricted, no additional connected number received Ensure that the SUT, on receipt of an ANM message with a Connected number parameter coded Address presentation restricted parameter = presentation restricted Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals in the format: PIXIT NDC+SN and without the Generic number parameter, sends a 200 OK INVITE to the UAC with a P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received and Add CC (of the country where the MGCF is located) to Connected PN address signals to construct E.164 number in URI. Prefix number with "+". a Privacy header is inserted with the value "id" or the value "id" is added to a existence Privacy header SIP Parameter values: 200 OK INVITE: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: ANM; Connected number parameter Address presentation restricted parameter = '01'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = Network provided Address signals = PIXIT Generic number parameter not present Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 255 TP506007 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND NOT PICS 13/1 ISUP selection criteria: Test purpose: Connected number international, presentation restricted, no additional connected number received Ensure that the SUT, on receipt of an ANM message with a Connected number parameter coded Address presentation restricted parameter = presentation restricted Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals in the format: PIXIT CC+NDC+SN and without the Generic number parameter, sends a 200 OK INVITE to the UAC with a P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received in the connected number in the ANM. a Privacy header is inserted with the value "id" or the value "id" is added to a existence Privacy header SIP Parameter values: 200 OK INVITE: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: ANM; Connected number parameter Address presentation restricted parameter = '01'B Nature of address indicator = 0000100'B Numbering plan indicator = '001'B Screening indicator = Network provided Address signals = PIXIT Generic number parameter not present Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 256 TP506008 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND NOT PICS 13/1 ISUP selection criteria: Test purpose: Connected number national, presentation restricted, additional connected number received Ensure that the SUT, on receipt of an ANM message with a Connected number parameter coded Address presentation restricted parameter = presentation restricted Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals in the format: PIXIT NDC+SN Generic number parameter, Number Qualifier Indicator "Additional connected number" Address presentation restricted parameter = presentation restricted Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = user provided, not verified Address signals = NDC+SN sends a 200 OK INVITE to the UAC with a P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received and Add CC (of the country where the MGCF is located) to Connected PN address signals to construct E.164 number in URI. Prefix number with "+". a Privacy header is inserted with the value "id" or the value "id" is added to a existence Privacy header The additional connected number is not interworked SIP Parameter values: 200 OK INVITE: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: ANM; Connected number parameter Address presentation restricted parameter = '01'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = Network provided Address signals = PIXIT Generic number parameter Number Qualifier Indicator "00000101"B Address presentation restricted parameter = '01'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = '00'B Address signals = PIXIT Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 257 TP506009 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND NOT PICS 13/1 ISUP selection criteria: Test purpose: Connected number international, presentation restricted, additional connected number received Ensure that the SUT, on receipt of an ANM message with a Connected number parameter coded Address presentation restricted parameter = presentation restricted Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals in the format: PIXIT CC+NDC+SN Generic number parameter, Number Qualifier Indicator "Additional connected number" Address presentation restricted parameter = presentation restricted Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = user provided, not verified Address signals = CC+NDC+SN sends a 200 OK INVITE to the UAC with a P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received in the connected number in the ANM a Privacy header is inserted with the value "id" or the value "id" is added to a existence Privacy header The additional connected number is not interworked SIP Parameter values: 200 OK INVITE: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: ANM; Connected number parameter Address presentation restricted parameter = '01'B Nature of address indicator = "0000100'B Numbering plan indicator = '001'B Screening indicator = Network provided Address signals = PIXIT Generic number parameter Number Qualifier Indicator "00000101"B Address presentation restricted parameter = '001B Nature of address indicator = '0000100'B Numbering plan indicator = '001'B Screening indicator = '00'B Address signals = PIXIT Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 258 TP506010 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND PICS 13/1 ISUP selection criteria: Test purpose: IAM connected line request indication is sent Ensure that a optional forward call indicator value Connected line identity request indicator is set to "requested" is contained in the sent IAM if an INVITE request is received containing a Supported header equal to "from-change". SIP Parameter values: INVITE: Supported: "from-change" ISUP Parameter values: IAM: oFCi Connected line identity request indicator is set to "requested" Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 259 TP506011 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND PICS 13/1 ISUP selection criteria: Test purpose: Additional connected number national, presentation allowed in ANM is received Ensure that if a ANM is received and a Additional connected number "national number", "presentation allowed" is included then a 200 OK INVITE is sent and the Supported header contains the "from-change" tag. Ensure that the From header in the received UPDATE (after 200 OK INVITE) contains the Additional connected number in the format +”CC-NDC-SN”. The UPDATE does not contain the Privacy value ‘header’. SIP Parameter values: 200 OK INVITE: Supported: "from-change" P-Asserted-Identity derived from the Connected number UPDATE: From header contains the Generic number in the format "+"CC+NDC+SN ISUP Parameter values: IAM: oFCi Connected line identity request indicator is set to "requested" ANM: Additional connected number Number Qualifier Indicator "00000101"B Address presentation restricted parameter = presentation allowed Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = user provided, not verified Address signals = PIXIT Connected number parameter Address presentation restricted parameter = presentation allowed Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals = PIXIT Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK UPDATE  200 OK UPDATE Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 260 TP506012 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND PICS 13/1 ISUP selection criteria: Test purpose: Additional connected number international, presentation allowed in ANM is received Ensure that if a ANM is received and a Additional connected number "international number" "presentation allowed" is included then a 200 OK INVITE is sent and the Supported header contains the "from-change" tag. Ensure that the From header in the received UPDATE (after 200 OK INVITE) contains the Additional connected number in the format +”CC-NDC-SN”. The UPDATE does not contain the Privacy value ‘header’. SIP Parameter values: 200 OK INVITE: Supported: "from-change" P-Asserted-Identity derived from the Connected number UPDATE: From header contains the Generic number in the format "+"CC+NDC+SN ISUP Parameter values: IAM: oFCi Connected line identity request indicator is set to "requested" ANM: Additional connected number Number Qualifier Indicator "00000101"B Address presentation restricted parameter = presentation allowed Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = user provided, not verified Address signals = PIXIT Connected number parameter Address presentation restricted parameter = presentation allowed Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals = PIXIT Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK UPDATE  200 OK UPDATE Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 261 TP506013 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND PICS 13/1 ISUP selection criteria: Test purpose: Additional connected number national, presentation restricted in ANM is received Ensure that if a ANM is received and a Additional connected number "national number" "presentation restricted" is included then a 200 OK INVITE is sent and the Supported header contains the "from-change" tag. Ensure that the From header in the received UPDATE (after 200 OK INVITE) contains the Additional connected number in the format +”CC-NDC-SN”. The UPDATE contains the Privacy value ‘header’. SIP Parameter values: 200 OK INVITE: Supported: "from-change" P-Asserted-Identity derived from the Connected number in the format "+"CC+NDC+SN Privacy: id UPDATE: From header contains the Generic number in the format "+"CC+NDC+SN Privacy: header ISUP Parameter values: IAM: oFCi Connected line identity request indicator is set to "requested" ANM: Additional connected number Number Qualifier Indicator "00000101"B Address presentation restricted parameter = presentation restricted Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = user provided, not verified Address signals = PIXIT Connected number parameter Address presentation restricted parameter = presentation restricted Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals = PIXIT Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK UPDATE  200 OK UPDATE Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 262 TP506014 ISUP reference: [14], clauses 7.4.2 and 7.5.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: PICS 5/22 AND PICS 13/1 ISUP selection criteria: Test purpose: Additional connected number international, presentation restricted in ANM is received Ensure that if a ANM is received and a Additional connected number "international number" "presentation restricted" is included then a 200 OK INVITE is sent and the Supported header contains the "from-change" tag. Ensure that the From header in the received UPDATE (after 200 OK INVITE) contains the Additional connected number in the format +”CC-NDC-SN” . The UPDATE contains the Privacy value ‘header’. SIP Parameter values: 200 OK INVITE: Supported: "from-change" P-Asserted-Identity derived from the Connected number in the format "+"CC+NDC+SN Privacy: id UPDATE: From header contains the Generic number in the format "+"CC+NDC+SN Privacy: header ISUP Parameter values: IAM: oFCi Connected line identity request indicator is set to "requested" ANM: Additional connected number Number Qualifier Indicator "00000101"B Address presentation restricted parameter = presentation restricted Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = user provided, not verified Address signals = PIXIT Connected number parameter Address presentation restricted parameter = presentation restricted Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network provided Address signals = PIXIT Comments: SIP MGCF ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK UPDATE  200 OK UPDATE Conversation BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 263
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.7 Malicious call identification MCID
TP507001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.4 TSS reference: SIP-ISUP/SS/MCID/ SIP selection criteria: PICS 9/1 ISUP selection criteria: Test purpose: No interworking MGCF sends IRS Ensure that the SUT if an IDR is received returns an IRS message. The MCID response indicator is set to "MCID not included". The SIP signalling procedure is not disrupted. SIP Parameter values: No influence ISUP Parameter values: IDR: MCID requested IRS: MCID not included Comments: SIP SUT ISUP INVITE IAM  IDR IRS 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC TP507002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.4 TSS reference: SIP-ISUP/SS/MCID/ SIP selection criteria: NOT PICS 9/1 ISUP selection criteria: Test purpose: No interworking timeout T39 Ensure that the SUT if an IDR is received, no IDR is sent. The SIP signalling procedure is not disrupted. SIP Parameter values: No influence ISUP Parameter values: IDR: MCID requested Comments: SIP SUT ISUP INVITE IAM  IDR T39 timeout 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 264 TP507003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.9 TSS reference: SIP-ISUP/SS/MCID/ SIP selection criteria: PICS 9/1 ISUP selection criteria: Test purpose: Interworking of IDR Ensure that the SUT if an IDR is received MCID request indicator is set to 1, sends out an INFO request. It is a ‘mcid’ element included set to McidRequestIndicator=1 SIP Parameter values: INFO <?xml version="1.0" encoding="utf-8"?> <mcid > <request> <McidRequestIndicator>string</McidRequestIndicator> <tns:HoldingIndicator>string</HoldingIndicator> </request> </mcid> ISUP Parameter values: IDR: MCID requested =1 Comments: SIP SUT ISUP INVITE IAM INFO   IDR 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.8 Sub-addressing (SUB)
TP508001 SUB Reference: ES 283 027 [1], clause 7.4.5 Selection criteria: PICS 5/8 TSS reference: SIP-ISUP/SS/SUB/ Preconditions: Test purpose: The isub parameter of the P-Asserted-Identity header in an INVITE is mapped in the calling party subaddress in the IAM Ensure that the isub parameter in the P-Asserted-Identity header of the received INVITE is interworked in the Calling party subaddress contained in an ATP parameter in the sent IAM. The Type of Subbaddress is set to "0 0 0" "NSAP (ITU-T Recommendation X.213 [29] and ISO/IEC 8348 [30] Add.2)" SIP Parameter values: INVITE: P-Asserted-Identity: sip: user part; isub=<subaddress>@hostportion ISUP Parameter values: IAM: ATP(Calling party subaddress) Comments: SIP MGCF ISUP INVITE IAM 100 Trying  180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 265 TP508002 SUB Reference: ES 283 027 [1], clause 7.4.5 Selection criteria: PICS 5/8 TSS reference: SIP-ISUP/SS/SUB/ Preconditions: Test purpose: The isub parameter of the Request URI in an INVITE is mapped in the called party subaddress in the IAM Ensure that the isub parameter in the Request URI of the received INVITE is interworked is the Called party subaddress contained in an ATP parameter in the sent IAM. The Type of Subbaddress is set to "0 0 0" "NSAP (ITU-T Recommendation X.213 [29] and ISO/IEC 8348 [30] Add.2)" SIP Parameter values: INVITE: sip: user part; isub=<subaddress>@hostportion ISUP Parameter values: IAM: ATP(Called party subaddress) Comments: SIP MGCF ISUP INVITE IAM 100 Trying  180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC TP508003 SUB Reference: ES 283 027 [1], clause 7.4.5 Selection criteria: PICS 5/8 TSS reference: SIP-ISUP/SS/SUB/ Preconditions: Test purpose: The connected subaddress in the ANM is mapped in the isub parameter of the P-Asserted- Identity header in the 200 OK INVITE Ensure that the isub parameter in the P-Asserted-Identity header of the received 200 OK INVITE is interworked in the connected subaddress contained in an ATP parameter in the sent ANM. The Type of Subbaddress is set to "0 0 0" "NSAP (ITU-T Recommendation X.213 [29] and ISO/IEC 8348 [30] Add.2)" SIP Parameter values: 200 OK INVITE: P-Asserted-Identity: sip: user part; isub=<subaddress>@hostportion ISUP Parameter values: IAM: oFCi: connected line request ANM: ATP(Connected subaddress) Comments: SIP MGCF ISUP INVITE IAM 100 Trying  180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 266
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.9 Call diversion (CDIV)
TP509001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.6 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: Test purpose: OBCI "call diversion may occur" in ACM received no mapping Ensure that the SUT if an ACM is received with and call diversion may occur indicator in the optional backward call indicator is set to "call diversion may occur", the SIP signalling procedure is not disrupted (CDa, CFNR). SIP Parameter values: No mapping ISUP Parameter values: ACM optional backward call indicator call diversion may occur Comments: SIP SUT ISUP INVITE IAM  ACM 180 Ringing   CPG Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC TP509002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.6 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: NOT PICS 5/12 AND NOT PICS 5/13 AND NOT PICS 5/14 AND NOT PICS 5/15 ISUP selection criteria: Test purpose: BCI called party status "no indication" in ACM received no mapping Ensure that the SUT if a ACM is received called party status indicator "no indication" and containing a Redirection number, call diversion information, redirection number restriction and generic notification set to "Call is diverting", the SIP signalling procedure is not disrupted (CFU, CFB, Cdi). SIP Parameter values: No mapping ISUP Parameter values: ACM: Redirection number, Call diversion information, Redirection number restriction, Generic notification Comments: SIP SUT ISUP INVITE IAM  ACM 180 Ringing   CPG Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 267 TP509003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.6 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: NOT PICS 5/12 AND NOT PICS 5/13 AND NOT PICS 5/14 AND NOT PICS 5/15 ISUP selection criteria: Test purpose: CPG PROGRESS with Redirection number, Call diversion information and Generic notification received, no mapping Ensure that the SUT if a CPG is received containing a Redirection number, call diversion information, redirection number restriction and generic notification set to "Call is diverting", the SIP signalling procedure is not disrupted (CDa, CFNR, subsequent redirection). SIP Parameter values: No mapping ISUP Parameter values: ACM: Called party status "Subscriber free" CPG: Redirection number, Call diversion information, Generic notification Comments: SIP SUT ISUP INVITE IAM  ACM 180 Ringing   CPG Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC TP509004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.6 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: NOT PICS 5/12 AND NOT PICS 5/13 AND NOT PICS 5/14 AND NOT PICS 5/15 ISUP selection criteria: Test purpose: Redirection number restriction received in ANM no mapping Ensure that the SUT if an ANM is received with redirection number restriction parameter, the SIP signalling procedure is not disrupted. SIP Parameter values: No mapping ISUP Parameter values: ANM: Redirection number restriction Comments: SIP SUT ISUP INVITE IAM  ACM 180 Ringing   CPG Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 268 TP509005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 10/7 ISUP selection criteria: Test purpose: BCI called party status "no indication" in ACM received, mapping of Redirection reason. Ensure that the SUT, on receipt of an ACM message indicating a first diversion with the Backward call indicators parameter coded Called party's status indicator = no indication the Call diversion information parameter coded Notification subscription option = "010"B Redirection reason = ISUP_REASON and the Generic notification indicator parameter coded Notification indicator = call is diverting, Redirection number (PIXIT) received. A 181 Being Forwarded is sent. The Redirection number included in the ACM is mapped into the History-Info header in the 181 Being Forwarded. A Privacy header field "history" is not escaped in the URI identified the diverted to user. The redirection reason is mapped into the cause-param in of the hi-targeted-uri identifying the diverted-to user. SIP Parameter values: 181 Being Forwarded: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 181 Being Forwarded   ACM 180 Ringing   CPG(Alerting) 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509005 ISUP Parameter Derived value of parameter field SIP component Value Call diversion information History-Info header Redirection reason ISUP_REASON Cause Value in History Index; cause-param = "cause" EQUAL Status- Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 269 TP509006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: BCI called party status "subscriber free" in ACM received, mapping of Redirection reason. Ensure that the SUT on receipt of an ACM message indicating a first diversion with the Backward call indicators parameter coded Called party's status indicator = subscriber free the Call diversion information parameter coded Notification subscription option = "010"B Redirection reason = ISUP_REASON and the Generic notification indicator parameter coded Notification indicator = call is diverting, Redirection number (PIXIT) received A 180 Ringing is sent. The Redirection number included in the ACM is mapped into the History-Info header in the 180 Ringing. A Privacy header field "history" is not escaped in the URI identified the diverted to user. The redirection reason is mapped into the cause- param in of the hi-targeted-uri identifying the diverted-to user. SIP Parameter values: 180 Ringing: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509006 ISUP Parameter Derived value of parameter field SIP component Value Call diversion information History-Info header Redirection reason ISUP_REASON Cause Value in History Index; cause-param = "cause" EQUAL Status- Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 270 TP509007 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: CPG with Event indicator ALERTING received, mapping of Redirection reason. Ensure that the SUT, on receipt of a CPG message indicating a first diversion with the Event information parameter coded Event indicator = ALERTING, the Call diversion information parameter coded Notification subscription option = "010"B Redirection reason = ISUP_REASON and the Generic notification indicator parameter coded Notification indicator = call is diverting, Redirection number (PIXIT) received. A 180 Ringing is sent. The Redirection number included in the CPG is mapped into the History-Info header in the 180 Ringing. A Privacy header field "history" is not escaped in the URI identified the diverted to user. The redirection reason is mapped into the cause- param in of the hi-targeted-uri identifying the diverted-to user. SIP Parameter values: 180 Ringing: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM  ACM(no indication) 180 Ringing   CPG 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509007 ISUP Parameter Derived value of parameter field SIP component Value Call diversion information History-Info header Redirection reason ISUP_REASON Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 271 TP509008 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: CPG with Event indicator PROGRESS received, mapping of Redirection reason. Ensure that the SUT, on receipt of a CPG message indicating a first diversion with the Event information parameter coded Event indicator = PROGRESS, the Call diversion information parameter coded Notification subscription option = "010"B Redirection reason = ISUP_REASON and the Generic notification indicator parameter coded Notification indicator = call is diverting, Redirection number (PIXIT) received A 181 Being Forwarded is sent. The Redirection number included in the CPG is mapped into the History-Info header in the 181 Being Forwarded. A Privacy header field "history" is not escaped in the URI identified the diverted to user. The redirection reason is mapped into the cause-param in of the hi-targeted-uri identifying the diverted-to user. SIP Parameter values: 181 Being Forwarded: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 181 Being Forwarded   CPG 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509008 ISUP Parameter Derived value of parameter field SIP component Value Call diversion information History-Info header Redirection reason ISUP_REASON Cause Value in History Index; cause-param = "cause" EQUAL Status- Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 272 TP509009 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: BCI called party status "no indication" in ACM received, mapping of Notification subscription option. Ensure that the SUT, on receipt of an ACM message indicating a first diversion with the Backward call indicators parameter coded Called party's status indicator = no indication the Call diversion information parameter coded Notification subscription option = ISUP_NSO Redirection reason = unconditional and the Generic notification indicator parameter coded Notification indicator = call is diverting, Redirection number (PIXIT) received. A 181 Being Forwarded is sent. The Redirection number included in the ACM is mapped into the History-Info header in the 181 Being Forwarded. A Privacy header field priv-value is escaped in the URI identified the diverted to user. SIP Parameter values: 181 Being Forwarded: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=302; ?priv-value; index=1.1 ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 181 Being Forwarded   ACM 180 Ringing   CPG(Alerting) 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509009 SIP component History-Info header, priv-value component Call diversion information Notification subscription options ISUP_NSO VA_01 Privacy header field absent or "none" ISUP_NSO = presentation allowed with redirection number VA_02 Privacy "history" ISUP_NSO = presentation allowed without redirection number ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 273 TP509010 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: BCI called party status "subscriber free" in ACM received, mapping of Notification subscription option. Ensure that the SUT on receipt of an ACM message indicating a first diversion with the Backward call indicators parameter coded Called party's status indicator = subscriber free the Call diversion information parameter coded Notification subscription option = ISUP_NSO Redirection reason = unconditional and the Generic notification indicator parameter coded Notification indicator = call is diverting, Redirection number (PIXIT) received. A 180 Ringing is sent. The Redirection number included in the ACM is mapped into the History-Info header in the 180 Ringing. A Privacy header field priv-value is escaped in the URI identified the diverted to user. SIP Parameter values: 180 Ringing: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=302; ?priv-value; index=1.1 ISUP Parameter values: ANM: Redirection number restriction Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509010 SIP component History-Info header, priv-value component Call diversion information Notification subscription options ISUP_NSO VA_01 Privacy header field absent or "none" ISUP_NSO = presentation allowed with redirection number VA_02 Privacy "history" ISUP_NSO = presentation allowed without redirection number ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 274 TP509011 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: CPG with Event indicator ALERTING received, mapping of Notification subscription option. Ensure that the SUT on receipt of a CPG message indicating a first diversion with the Event information parameter coded Event indicator = ALERTING, the Call diversion information parameter coded Notification subscription option = ISUP_NSO Redirection reason = unconditional and the Generic notification indicator parameter coded Notification indicator = call is diverting, Redirection number (PIXIT) received. A 180 Ringing is sent. The Redirection number included in the CPG is mapped into the History-Info header in the 180 Ringing. A Privacy header field priv-value is escaped in the URI identified the diverted to user. SIP Parameter values: 180 Ringing: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=302; ?priv-value; index=1.1 ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM  ACM 180 Ringing   CPG 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509011 SIP component History-Info header, priv-value component Call diversion information Notification subscription options ISUP_NSO VA_01 Privacy header field absent or "none" ISUP_NSO = presentation allowed with redirection number VA_02 Privacy "history" ISUP_NSO = presentation allowed without redirection number ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 275 TP509012 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: CPG with Event indicator ALERTING received, mapping of Redirection number restriction. Ensure that the SUT on receipt of a CPG message indicating a first diversion with the Event information parameter coded Event indicator = ALERTING, Redirection number restriction parameter = ISUP_RDIR_RESTR A 180 Ringing including a History-Info header is sent. A Privacy header field priv-value is escaped in the URI identified the diverted to user. SIP Parameter values: 180 Ringing: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=302; ?priv-value; index=1.1 ISUP Parameter values: ANM: Redirection number restriction Comments: SIP SUT ISUP INVITE IAM 181 Being Forwarded   ACM 180 Ringing   CPG 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509012 Derived escaped SIP priv-value component Derived value of parameter field VA_01 Privacy header field absent or "none" ISUP_RDIR_RESTR = Presentation allowed, '00'B VA_02 Privacy header field "history" ISUP_RDIR_RESTR = presentation restricted, '01'B VA_03 Privacy header field absent or "none" ISUP_RDIR_RESTR absent ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 276 TP509013 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: ANM received, mapping of the Redirection number restriction parameter. Ensure that the SUT, on receipt of an ANM message with the Redirection number restriction parameter = ISUP_RDIR_RESTR or parameter absent, a 200 IK INVITE including a History-Info header is sent. A Privacy header field priv-value is escaped in the URI identified the diverted to user according the value of the Redirection number restriction parameter. SIP Parameter values: 200 OK INVITE: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=302; ?priv-value; index=1.1 ISUP Parameter values: ANM: Redirection number restriction Comments: SIP SUT ISUP INVITE IAM 181 Being Forwarded   ACM 180 Ringing   CPG 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509013 Derived escaped SIP component Derived value of parameter field VA_01 Privacy header field absent or "none" ISUP_RDIR_RESTR = Presentation allowed, '00'B VA_02 Privacy header field "history" ISUP_RDIR_RESTR = presentation restricted, '01'B VA_03 Privacy header field absent or "none" ISUP_RDIR_RESTR absent ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 277 TP509014 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: NOT PICS 1/5 AND PICS 10/6 Test purpose: CDIV performed, the first hi-targeted-to-uri is sent in the original called number national number Ensure that the SUT in the Idle state on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table, Privacy header field is absent and with the complete Original called number parameter contained in the URI of first Index entry of History-Info header in the format "+" CC NDC SN. The SUT sends: an IAM message with the Redirection information parameter coded Redirection counter = 1 Redirecting reason = ISUP_RR and the Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals included in the format NDC+SN. SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code ; index=1.1 ISUP Parameter values: IAM: Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals userinfo of the hi-targeted-to from index 1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509014 ISUP Parameter Derived value of parameter field SIP component Value IAM INVITE Redirection Information Redirecting reason ISUP_RR Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 278 TP509015 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 1/5 AND PICS 10/6 Test purpose: CDIV performed, the first hi-targeted-to-uri is sent in the original called number international number Ensure that the SUT in the Idle state, on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table, the Privacy header is absent and with the complete Original called number parameter contained URI of first Index entry of History-Info header in the format "+" CC NDC SN. The SUT sends an IAM message with the Redirection information parameter coded Redirection counter = 1 Redirecting reason = ISUP_RR and the Original called number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals included in the format CC+NDC+SN SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: IAM: Original called number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals userinfo of the hi-targeted-to from index 1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509015 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Redirecting reason ISUP_RR Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 279 TP509016 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 10/6 Test purpose: CDIV performed, the first hi-targeted-to-uri is sent in the original called number Privacy header is equal "history" Ensure that the SUT in the Idle state, on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table, the priv-value set to "history" and with the complete Original called number parameter contained URI of first Index entry of History-Info header in the format "+" CC NDC SN. The SUT sends an IAM message with the Redirection information parameter coded Redirection counter = 1 Redirecting reason = ISUP_RR and the Original called number parameter coded Address presentation restricted parameter = presentation restricted SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user?Privacy=history; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: IAM: Original called number parameter coded Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals userinfo of the hi-targeted-to from index 1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509016 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Redirecting reason ISUP_RR Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 280 TP509017 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: NOT PICS 1/5 AND PICS 10/6 Test purpose: CDIV performed, the first hi-targeted-to-uri is sent in the redirecting number national number Ensure that the SUT in the Idle state on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table, Privacy header field is absent and with the complete Redirecting number parameter contained in the hi-targeted-to-uri of History-Info header in the format "+" CC NDC SN. The SUT sends: an IAM message with the Redirection information parameter coded Redirection counter = 1 Redirecting reason = ISUP_RR and the Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals included in the format NDC+SN SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: IAM: Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals userinfo of the hi-targeted-to from index 1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509017 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Redirecting reason ISUP_RR Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 281 TP509018 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 1/5 AND PICS 10/6 Test purpose: CDIV performed, the first hi-targeted-to-uri is sent in the redirecting number international number Ensure that the SUT in the Idle state, on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table, Privacy header field is absent and with the complete Redirecting number parameter contained hi-targeted-to-uri of History-Info header in the format "+" CC NDC SN. The SUT sends an IAM message with the Redirection information parameter coded Redirection counter = 1 Redirecting reason = ISUP_RR and the Redirecting number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals included in the format CC+NDC+SN SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: IAM: Redirecting number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals userinfo of the hi-targeted-to from index 1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509018 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Redirecting reason ISUP_RR Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 282 TP509019 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 10/6 Test purpose: CDIV performed, the second hi-targeted-to-uri is sent in the redirecting number Privacy header is equal "history" Ensure that the SUT in the Idle state, on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table, the priv-value set to "history" and with the complete Redirecting number parameter contained hi-targeted-to-uri of History-Info header in the format "+" CC NDC SN. The SUT sends an IAM message with the Redirection information parameter coded Redirection counter = 1 Redirecting reason = ISUP_RR and the Redirecting number parameter coded Address presentation restricted parameter = presentation restricted SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user?Privacy=history; index=1, hi-targeted-ti uri diverted to user; cause=Status-Code; index=1.1 ISUP Parameter values: IAM: Redirecting number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals userinfo of the hi-targeted-to from index 1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC Values for test purposes TP509019 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Redirecting reason ISUP_RR Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 283 TP509020 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 10/6 Test purpose: CDIV performed, the second hi-targeted-to-uri Privacy header is not included is sent in the redirecting number and the first hi-targeted-to-uri Privacy header is sent in the original called number Ensure that the SUT in the Idle state, on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table and with the complete Original called number parameter contained in the URI of first Index entry of History-Info header, in the format "+" CC NDC SN the Privacy header field is absent. The Redirecting number parameter is contained in the second hi-targeted-to-uri of History-Info header in the format "+" CC NDC SN the Privacy header field is absent. Sends a IAM message with the Redirection information parameter coded Redirection counter 2 Redirecting reason = ISUP_RR, the Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals included and the Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals included SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user C; cause=302; index=1.1 hi-targeted-ti uri diverted to user D; cause=Status-Code; index=1.1.1 ISUP Parameter values: IAM: Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals userinfo of the hi-targeted-to from index 1 Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals userinfo of the hi-targeted-to from index 1.1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 284 Values for test purposes TP509020 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Redirecting reason ISUP_RR Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 285 TP509021 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 10/6 Test purpose: CDIV performed, the second hi-targeted-to-uri Privacy ="history" is sent in the redirecting number and the first hi-targeted-to-uri without Privacy "header" is sent in the original called number Ensure that the SUT in the Idle state, on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table and with the complete Original called number parameter contained the URI of first Index entry of History-Info header in the format "+" CC NDC SN, the Privacy header field is absent. The Redirecting number parameter is contained in the second hi-targeted-to-uri of History-Info header in the format "+" CC NDC SN, the Privacy value is set to "history". Sends a IAM message with the Redirection information parameter coded Redirection counter 2 Redirecting reason = ISUP_RR, the Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals included and the Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals included SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user C?Privacy=history; cause=302; index=1.1 hi-targeted-ti uri diverted to user D; cause=Status-Code; index=1.1.1 ISUP Parameter values: IAM: Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals userinfo of the hi-targeted-to from index 1 Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals userinfo of the hi-targeted-to from index 1.1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 286 Table 38: Values for test purposes TP509021 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 287 TP509022 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 10/6 Test purpose: CDIV performed, the second hi-targeted-to-uri Privacy header absent is sent in the redirecting number and the first hi-targeted-to-uri Privacy = "history" is sent in the original called number Privacy Ensure that the SUT in the Idle state, on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table and with the complete Original called number parameter contained the URI of first Index entry of History-Info header in the format "+" CC NDC SN the Privacy value set to "history". The Redirecting number parameter is contained in the second hi-targeted-to-uri of History-Info header in the format "+" CC NDC SN the Privacy header field is absent. Sends an IAM message with the Redirection information parameter coded Redirection counter 2 Redirecting reason = ISUP_RR, the Original called number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals included and the Redirecting number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals included SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user?Privacy=history; index=1, hi-targeted-ti uri diverted to user C; cause=302; index=1.1 hi-targeted-ti uri diverted to user D; cause=Status-Code; index=1.1.1 ISUP Parameter values: IAM: Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address userinfo of the hi-targeted-to from index 1 Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation allowed Address signals userinfo of the hi-targeted-to from index 1.1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 288 Values for test purposes TP509022 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 289 TP509023 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 10/6 Test purpose: CDIV performed, the second hi-targeted-to-uri Privacy="history" is sent in the redirecting number and the first hi-targeted-to-uri Privacy = "history" is sent in the original called number Privacy Ensure that the SUT in the Idle state, on receipt of an INVITE message with Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table and with the complete Original called number parameter contained the URI of first Index entry of History-Info header in the format "+" CC NDC SN the Privacy is set to "history". The Redirecting number parameter is contained in the second hi-targeted-to-uri of History-Info header in the format "+" CC NDC SN the Privacy is set to "history". Sends an IAM message with the Redirection information parameter coded Redirection counter 2 Redirecting reason = ISUP_RR, the Original called number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals included and the Redirecting number parameter coded Nature of address indicator = international number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals included SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user?Privacy=history; index=1, hi-targeted-ti uri diverted to user C?Privacy=history; cause=302; index=1.1 hi-targeted-ti uri diverted to user D; cause=Status-Code; index=1.1.1 ISUP Parameter values: IAM: Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals userinfo of the hi-targeted-to from index 1 Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = presentation restricted Address signals userinfo of the hi-targeted-to from index 1.1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 290 Values for test purposes TP509023 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 TP509024 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: CDIV performed, the third hi-targeted-to-uri is sent in the redirecting Redirection counter is mapped from the latest history entry Ensure that the SUT in the Idle state, on receipt of an INVITE message containing a History-Info header with three History entries, the hi-targeted-to-uri of first index is mapped into the Original called number parameter; the hi-targeted-to-uri of third index is mapped into the Redirecting number parameter Cause Value in History Index; cause-param = "cause" EQUAL Status-Code defined in the table. Sends a IAM message with the Redirection information parameter coded Redirection counter 3 Redirecting reason = ISUP_RR, the Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address signals included and the Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address signals included SIP Parameter values: INVITE: History-Info: hi-targeted-to uri served user; index=1, hi-targeted-ti uri diverted to user C; cause=302index=1.1 hi-targeted-ti uri diverted to user D; cause=486index=1.1.1 hi-targeted-ti uri diverted to user E; cause=Status-Code; index=1.1.1.1 ISUP Parameter values: IAM: Original called number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address signals userinfo of the hi-targeted-to from index 1 Redirecting number parameter coded Nature of address indicator = national number Numbering plan indicator = ISDN/Telephony numbering plan Address signals userinfo of the hi-targeted-to from index 1.1.1 Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 291 Values for test purposes TP509024 ISUP Parameter or IE Derived value of parameter field SIP component Value IAM INVITE Redirection Information Cause Value in History Index; cause-param = "cause" EQUAL Status-Code Cause value unknown '0000'B 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 TP509025 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: SIP-ISUP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: NOT PICS 5/12 AND NOT PICS 5/13 AND NOT PICS 5/14 AND NOT PICS 5/15 Test purpose: Interworking not supported, session successful Ensure that the SUT in the Idle state, on receipt of an INVITE message containing a History-Info header with three History entries the History-Info header entries are not mapped into any call diversion related parameters in the IAM and the session setup is not disrupted. SIP Parameter values: INVITE: History-Info: hi-targeted-to-uri served user; index=1, hi-targeted-ti uri diverted to user C; cause=Status code; index=1.1 hi-targeted-ti uri diverted to user D; cause=Status code; index=1.1.1 ISUP Parameter values: IAM: no mapping Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM 200 OK INVITE   ANM ACK Communication BYE REL 200 OK BYE   RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 292
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.10 Call waiting (CW)
TP510001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.9 TSS reference: SIP-ISUP/SS/CW/ SIP selection criteria: ISUP selection criteria: Test purpose: No mapping of Call Waiting indication in the ACM at the I-MGCF Ensure that the indication for Call Waiting contained in an ACM, Generic notification "call is a waiting call" is not interworked in a 180 Ringing Response SIP Parameter values: ISUP Parameter values: ACM: Generic notification parameter = "Call is a waiting call" Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC TP510002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.9 TSS reference: SIP-ISUP/SS/CW/ SIP selection criteria: ISUP selection criteria: Test purpose: No mapping of Call Waiting indication in the CPG at the I-MGCF Ensure that the indication for Call Waiting contained in an CPG, Generic notification "call is a waiting call", is not interworked in a 180 Ringing Response SIP Parameter values: 180 Ringing ISUP Parameter values: ACM: Called party status "no indication" CPG: Generic notification parameter = "Call is a waiting call" Comments: SIP SUT ISUP INVITE IAM  ACM 180 Ringing   CPG Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 293
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.11 User to user signalling (UUS)
TP511001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec. Q.1912.5 [32], annex B.21 ITU-T Rec. Q.737.1 [33], clause 1.3.7.2 TSS reference: SIP-ISUP/SS/UUS/ SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: Explicit request supported, a FAR user-to-user service 3 request (not essential) is rejected with FRJ Ensure that the SUT if a FAR is received with an user-to-user service 3 request (not essential) after call setup, sent a FRJ to reject the request. The SIP signalling procedure is not disrupted. SIP Parameter values: ISUP Parameter values: FRJ: User-to-user indicator = "Service 3 not provided" Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation  FAR FRJ Conversation BYE   REL 200 OK BYE RLC TP511002 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec. Q.1912.5 [32], annex B.21 ITU-T Rec. Q.737 [33], clause 1.3.5.2.5.2 TSS reference: SIP-ISUP/SS/UUS/ SIP selection criteria: ISUP selection criteria: NOT PICS 11/2 Test purpose: Explicit request not supported, no response on receipt of a FAR Ensure that the SUT if a FAR is received with an user-to-user service 3 request (not essential) after call setup, the SIP signalling procedure is not disrupted. No FRJ is sent as an implicit rejection. SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation  FAR Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 294 TP511003 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec. Q.1912.5 [32], annex B.21 ITU-T Rec. Q.737.1 [33], clause 1.3.5.2.5.2 TSS reference: SIP-ISUP/SS/UUS/ SIP selection criteria: ISUP selection criteria: Test purpose: User-to-user service 1 implicit request Ensure that the SUT if an User-to-User header is included in the INVITE a User-to-user parameter is sent in the IAM. The data field of the User-to-user information is derived from the uuidata component of the User-to-User header in the INVITE SIP Parameter values: INVITE: User-to-User uuidata ISUP Parameter values: IAM: User-to-user information Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC TP511004 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec. Q.1912.5 [32], annex B.21 ITU-T Rec. Q.737 [33], clause 1.3.5.2.5.2.1 TSS reference: SIP-ISUP/SS/UUS/ SIP selection criteria: ISUP selection criteria: Test purpose: User-to-user service 1 response Ensure that the User-to-user information parameter in an ACM, ANM or REL is mapped in uuidata of an User-to-User header sent in an Provisional response, final response or BYE SIP Parameter values: 18x: User-to-User uuidata 200: User-to-User uuidata BYE: User-to-User uuidata ISUP Parameter values: ACM: User-to-user information ANM: User-to-user information REL: User-to-user information Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 295
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.12 Explicit call transfer (ECT)
TP512001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: SIP-ISUP/SS/ECT/ SIP selection criteria: ISUP selection criteria: PICS 12/1 Test purpose: Loop prevention procedure supported, a LOP response "insufficient information" is sent Ensure that the SUT if a LOP(request) is received returns a LOP (response) with the indication "insufficient information" continue without disrupting the SIP signalling procedure. Ensure that the SUT if a FAC is received continue without disrupting the SIP signalling procedure. SIP Parameter values: ISUP Parameter values: LOP: Response "insufficient information" Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation  LOP LOP  FAC Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 296 TP512002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: SIP-ISUP/SS/ECT/ SIP selection criteria: ISUP selection criteria: NO PICS 12/1 Test purpose: Loop prevention procedure not supported Ensure that the SUT if a LOP (request) is received continue without disrupting the SIP signalling procedure. Ensure that the SUT if a FAC is received continue without disrupting the SIP signalling procedure. SIP Parameter values: ISUP Parameter values: Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation  LOP  FAC Conversation BYE   REL 200 OK BYE RLC
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.13 Completion of Call to Busy Subscriber (CCBS)
TP513001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.11 TSS reference: SIP-ISUP/SS/CCBS/ SIP selection criteria: ISUP selection criteria: Test purpose: CCBS possible in the Diagnostics field received Ensure that the SUT if a REL is received contained a Diagnostic field and the CCBS indicator is coded as CCBS possible: • continue without disrupting the SIP signalling procedure. SIP Parameter values: ISUP Parameter values: REL: Cause indicator Diagnostics CCBS possible Comments: SIP SUT ISUP INVITE IAM 486 Busy Here   REL ACK RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 297
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.14 Completion of Calls on No reply (CCNR)
TP514001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.11 TSS reference: SIP-ISUP/SS/CCNR/ SIP selection criteria: ISUP selection criteria: Test purpose: CCNR possible in the ACM received Ensure that the SUT if an ACM is received and a CCNR Possible Indicator is included: • continue without disrupting the SIP signalling procedure. SIP Parameter values: ISUP Parameter values: ACM: CCNR possible indicator CCNR possible Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.15 Anonymous Call Rejection (ACR)
TP515001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.23 TSS reference: SIP-ISUP/SS/ACR/ SIP selection criteria: ISUP selection criteria: Test purpose: Mapping of cause value #24 Ensure that the SUT, if a destination user has subscribed the ACR supplementary service: • the call attempt is rejected with a REL cause value 24 "call rejected due to ACR supplementary service". SIP Parameter values: INVITE: Privacy-header = "id" 603 Decline: Reason header field Reason: ITU-T Recommendation Q.850 [5]; cause=24 ISUP Parameter values: EL: Cause value: 24 "call rejected due to ACR supplementary service" Comments: SIP SUT ISUP INVITE IAM 603 Decline   REL ACK RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 298
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.1.16 Closed user group (CUG)
TP516001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1 TSS reference: SIP-ISUP/SS/CUG/ SIP selection criteria: ISUP selection criteria: PICS 5/7 Test purpose: Mapping of <cug> XML element in the received INVITE cugCommunicationIndicator value "00" Ensure that the <cugCommunicationIndicator> value "00" contained in the INVITE <cug> XML body is sent in a optional forward call indicator - CUG call indicator, if any other value of the optional forward call indicator have to be set equal "00". No mapping of <networkIndicator> and <cugInterlockBinaryCode> into Closed User Group interlock code. SIP Parameter values: INVITE: <cug> <networkIndicator>[PIXIT]</networkIndicator> <cugInterlockBinaryCode>[PIXIT]</cugInterlockBinaryCode> <cugCommunicationIndicator>00</cugCommunicationIndicator> </cug> ISUP Parameter values: IAM: Optional Forward Call Indicator CUG call indicator = "00" When optional forward call indicator have to be sent in case of another indicator is not set to "0" Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 299 TP516002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1 TSS reference: SIP-ISUP/SS/CUG/ SIP selection criteria: ISUP selection criteria: PICS 5/7 Test purpose: Mapping of <cug> XML element in the received INVITE cugCommunicationIndicator value "01" Ensure that the <cugCommunicationIndicator> value "01" contained in the INVITE <cug> XML body is not sent in a optional forward call indicator - CUG call indicator. If the optional forward call indicator have to be sent, the CUG call indicator is set to "00" no CUG call. No mapping of <networkIndicator> and <cugInterlockBinaryCode> into Closed User Group interlock code. SIP Parameter values: INVITE: <cug> <networkIndicator>[PIXIT]</networkIndicator> <cugInterlockBinaryCode>[PIXIT]</cugInterlockBinaryCode> <cugCommunicationIndicator>01</cugCommunicationIndicator> </cug> ISUP Parameter values: IAM: Optional Forward Call Indicator CUG call indicator = "00" When optional forward call indicator have to be sent in case of another indicator is not set to "0" Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 300 TP516003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1 TSS reference: SIP-ISUP/SS/CUG/ SIP selection criteria: ISUP selection criteria: PICS 5/7 Test purpose: Mapping of <cug> XML element in the received INVITE cugCommunicationIndicator value "10" Ensure that the <cugCommunicationIndicator> value "10" contained in the INVITE <cug> XML body is sent in a optional forward call indicator - CUG call indicator ="10". The XML <cug> <networkIndicator> is mapped into the IAM Closed User Group interlock code Network identity and the XML <cug> <cugInterlockBinaryCode> is mapped into the IAM Closed User Group interlock code Binary code. SIP Parameter values: INVITE: <cug> <networkIndicator>[PIXIT]</networkIndicator> <cugInterlockBinaryCode>[PIXIT]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> ISUP Parameter values: IAM: Optional Forward Call Indicator CUG call indicator = "10" Closed User Group interlock code Binary code derived from INVITE XML body <cugInterlockBinaryCode> Network identity derived from INVITE XML body <networkIndicator> Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 301 TP516004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1 TSS reference: SIP-ISUP/SS/CUG/ SIP selection criteria: ISUP selection criteria: PICS 5/7 Test purpose: Mapping of <cug> XML element in the received INVITE cugCommunicationIndicator value "11" Ensure that the <cugCommunicationIndicator> value "11" contained in the INVITE <cug> XML body is sent in a optional forward call indicator - CUG call indicator ="11". The XML <cug> <networkIndicator> is mapped into the IAM Closed User Group interlock code Network identity and the XML <cug> <cugInterlockBinaryCode> is mapped into the IAM Closed User Group interlock code Binary code. SIP Parameter values: INVITE: <cug> <networkIndicator>[PIXIT]</networkIndicator> <cugInterlockBinaryCode>[PIXIT]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> ISUP Parameter values: IAM: Optional Forward Call Indicator CUG call indicator = "11" Closed User Group interlock code Binary code derived from INVITE XML body <cugInterlockBinaryCode> Network identity derived from INVITE XML body <networkIndicator> Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 302 TP516005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1 TSS reference: SIP-ISUP/SS/CUG/ SIP selection criteria: ISUP selection criteria: NOT PICS 5/7 Test purpose: Mapping of <cug> XML element in the received INVITE cugCommunicationIndicator value "10". The PSTN/ISDN network does not support CUG. Ensure that the <cugCommunicationIndicator> value "10" contained in the INVITE <cug> XML body is not sent in a optional forward call indicator - CUG call indicator ="10" when the PSTN/ISDN does not support CUG. If the optional forward call indicator have to be sent, the CUG call indicator is set to "00" no CUG call. No mapping of <networkIndicator> and <cugInterlockBinaryCode> into Closed User Group interlock code. SIP Parameter values: INVITE: <cug> <networkIndicator>[PIXIT]</networkIndicator> <cugInterlockBinaryCode>[PIXIT]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> ISUP Parameter values: IAM: Optional Forward Call Indicator CUG call indicator = "00" If optional forward call indicator have to be sent in case of another indicator is not set to "0" Comments: SIP SUT ISUP INVITE IAM 180 Ringing   ACM Ringing tone 200 OK INVITE   ANM ACK Conversation BYE   REL 200 OK BYE RLC TP516006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1 TSS reference: SIP-ISUP/SS/CUG/ SIP selection criteria: ISUP selection criteria: NOT PICS 5/7 Test purpose: Mapping of <cug> XML element in the received INVITE cugCommunicationIndicator value "11". The PSTN/ISDN network does not support CUG. Ensure that the <cugCommunicationIndicator> value "11" contained in the INVITE <cug> XML body is sent in a optional forward call indicator - CUG call indicator ="11". The XML <cug> <networkIndicator> is mapped into the IAM Closed User Group interlock code Network identity and the XML <cug> <cugInterlockBinaryCode> is mapped into the IAM Closed User Group interlock code Binary code. SIP Parameter values: INVITE: <cug> <networkIndicator>[PIXIT]</networkIndicator> <cugInterlockBinaryCode>[PIXIT]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> ISUP Parameter values: Comments: SIP SUT ISUP INVITE 403 Forbidden  ACK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 303
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2 Interworking from ISUP to SIP (Outgoing Call)
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.1 Calling Line Identification (CLI)
TP601001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: No calling party number and no additional calling party number received Ensure that when the SUT has received an IAM message whereby Calling Party Number parameter and the Generic Number are not contained: • Sends an INVITE message without the "P-Asserted-Identity header field", a "From header field" set to unavailable@anonymous.invalid and without a Privacy Header field. SIP Parameter values: INVITE: From <unavailable@anonymous> ISUP Parameter values: IAM: no Calling party number no Generic Number: "Additional calling party number" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 304 TP601002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: No calling party number and additional calling party number received Ensure that when the SUT has received an IAM message whereby Calling Party Number parameter is not contained and the Generic Number is contained whereby the address presentation restriction parameter is set to "presentation allowed" and the Nature of Address Indicator is set to NoAS_VALUE: • Sends an INVITE message without the "P-Asserted-Identity header field", a "From header field" and no Privacy Header field. SIP Parameter values: P-Asserted-Identity header field: not included: From header field: Tel or SIP URI: Addr_SPEC_ID Derived from Generic Number parameter Address Signals (AcgPN) Privacy header: is not included ISUP Parameter values: IAM: Generic Number: "additional calling party number" Nature of Address Indicator: NoAS_VALUE APRI "presentation allowed" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 305 TP601003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: No calling party number and additional calling party number presentation restricted received Ensure that when the SUT has received an IAM message whereby Calling Party Number parameter is not contained and the Generic Number is contained whereby the address presentation restriction parameter is set to "presentation restricted" and the Nature of Address Indicator is set to NoAS_VALUE: • Sends an INVITE message without the P-Asserted-Identity header field, a From header field set to unavailable@anonymous.invalid and no Privacy Header field. SIP Parameter values: INVITE: From <unavailable@anonymous> P-Asserted-Identity header field: not included: Privacy header: is not included ISUP Parameter values: IAM: Generic Number: "additional calling party number", Nature of Address Indicator: NoAS_VALUE APRI "presentation restricted" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE Table 39 Values for test purpose TP601003 ISUP Parameter values: SIP Parameter values: VA_01 IAM NoAS_VALUE: "national (significant) number"(NDC+SN) INVITE FHf_Addr_SPEC_ID: CC (of the country where the MGCF is located) is added to the Generic Number Address Signals and then mapped to user portion of URI scheme VA_02 IAM NoAS_VALUE: "international number" ("+"CC+NDC+SN) INVITE FHf_Addr_SPEC_ID: the complete GenericNumber Address Signals is mapped to the user portion of URI scheme used. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 306 TP601004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: Calling party number presentation allowed and no additional calling party number received Ensure that when the SUT has received an IAM message, the Calling Party Number is contained whereby the Nature of Address Indicator is set to NoAS_VALUE the APRI is set to "presentation allowed" and the Generic Number is not contained: • Sends an INVITE message with the "P-Asserted-Identity header field" where the „Tel or SIP URI" is set to PAIh_Addr_SPEC_ID, a "From header field" where the „Tel or SIP URI" is set to FHf_Addr_SPEC_ID without "Privacy Header field" or "id" is not included. SIP Parameter values: P-Asserted-Identity header field: Tel or SIP URI: PAIh_Addr_SPEC_ID (Derived from Calling Party Number parameter Address Signals) From header field: Tel or SIP URI: Tel or SIP URI: PAIh_Addr_SPEC_ID (Derived from Calling Party Number parameter Address Signals) Privacy header: is not included or if included, "id" is not included ISUP Parameter values: IAM: Calling party number APRI "presentation allowed" no Generic Number: "Additional calling party number" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE Table 40 Values for test purpose TP601004 ISUP Parameter values: SIP Parameter values: VA_01 IAM NoAS_VALUE: "national (significant) number"(NDC+SN) INVITE PAIh_Addr_SPEC_ID = FHf_Addr_SPEC_ID: Add CC (of the country where the MGCF is located) to CgPN Signals then map to user portion of URI scheme used VA_02 IAM NoAS_VALUE: "international number" ("+"CC+NDC+SN) INVITE PAIh_Addr_SPEC_ID= FHf_Addr_SPEC_ID: the complete to CgPN Signals is mapped to the user portion of URI scheme. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 307 TP601005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: Calling party number presentation restricted and no additional calling party number received Ensure that when the SUT has received an IAM message, the Calling Party Number is contained whereby the Nature of Address Indicator is set to NoAS_VALUE the APRI is set to "presentation restricted" and the Generic Number is not contained: • Sends an INVITE message with the "P-Asserted-Identity header field" where the „Tel or SIP URI" is set to PAIh_Addr_SPEC_ID, a "From header field" set to anonymous@anonymous.invalid and with Privacy Header field value "id". SIP Parameter values: P-Asserted-Identity header field: Tel or SIP URI: PAIh_Addr_SPEC_ID (Derived from Calling Party Number parameter Address Signals) From header field: Tel or SIP URI Tel or SIP URI: anonymous@anonymous.invalid Privacy header: "id". ISUP Parameter values: IAM: Calling party number APRI "presentation restricted" no Generic Number: "Additional calling party number" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 308 TP601006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: Calling party number presentation restricted by the network and no additional calling party number received Ensure that when the SUT has received an IAM message, the Calling Party Number is contained whereby the Nature of Address Indicator is set to NoAS_VALUE the APRI is set to "presentation restricted by the network" and the Generic Number is not contained: • Sends an INVITE message with the "P-Asserted-Identity header field" where the „Tel or SIP URI" is set to PAIh_Addr_SPEC_ID, a "From header field" set to anonymous@ anonymous.invalid and with Privacy Header field value "id". SIP Parameter values: P-Asserted-Identity header field: Tel or SIP URI: PAIh_Addr_SPEC_ID (Derived from Calling Party Number parameter Address Signals) From header field: Tel or SIP URI Tel or SIP URI: anonymous@ anonymous.invalid Privacy header: "id". ISUP Parameter values: IAM: Calling party number APRI "presentation restricted by the network" no Generic Number: "Additional calling party number" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE Table 41 Values for test purpose TP601006 ISUP Parameter values: SIP Parameter values: VA_01 IAM NoAS_VALUE: "national (significant) number"(NDC+SN) INVITE PAIh_Addr_SPEC_ID = FHf_Addr_SPEC_ID: CC (of the country where the MGCF is located) is added to the CgPN Signals and then mapped to user portion of URI scheme used VA_02 IAM NoAS_VALUE: "international number" ("+"CC+NDC+SN) INVITE PAIh_Addr_SPEC_ID= FHf_Addr_SPEC_ID: the complete to CgPN Signals is mapped to the user portion of URI scheme. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 309 TP601007 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: Calling party number presentation allowed and an additional calling party number received Ensure that when the SUT has received an IAM message, the Calling Party Number is contained whereby the Nature of Address Indicator is set to NoAS_VALUE the APRI is set to "presentation allowed" and the Generic Number is contained: • Sends an INVITE message with the "P-Asserted-Identity header field", where the „Tel or SIP URI" is set to PAIh_Addr_SPEC_ID "From header field" where the „Tel or SIP URI" is set to FH_Addr_SPEC_ID and without "Privacy Header field" or "id" is not included. SIP Parameter values: P-Asserted-Identity header field: Tel or SIP URI: PAIh_Addr_SPEC_ID (Derived from Calling Party Number parameter Address Signals) From header field: Tel or SIP URI Tel or SIP URI: FH_Addr_SPEC_ID (Derived from Generic Number parameter Address Signals (AcgPN)) Privacy header: is not included or if included, "id" is not included. ISUP Parameter values: IAM: Calling party number APRI "presentation allowed" Generic Number: "additional calling party number" Nature of Address Indicator: CP_NoAS_VALUE Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 310 TP601008 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: Calling party number presentation restricted and an additional calling party number received Ensure that when the SUT has received an IAM message, the Calling Party Number is contained whereby the Nature of Address Indicator is set to NoAS_VALUE the APRI is set to presentation restricted and the Generic Number presentation allowed is included Sends an INVITE message with the "P-Asserted-Identity header field , where the "addr-spec" is set to PAIh_Addr_SPEC_ID "From header field" where the "addr-spec" is set to FH_Addr_SPEC_ID and with "Privacy Header field =id". SIP Parameter values: P-Asserted-Identity header field: Tel or SIP URI: PAIh_Addr_SPEC_ID (Derived from Calling Party Number parameter Address Signals) From header field: addr-spec Tel or SIP URI: FH_Addr_SPEC_ID (Derived from Generic Number parameter Address Signals (AcgPN)) Privacy header: "id" ISUP Parameter values: IAM: Calling party number APRI "presentation restricted" Generic Number: "additional calling party number" Nature of Address Indicator: CP_NoAS_VALUE APRI: presentation restricted Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE Table 42 Values for test purpose TP601007; TP601008 Test purposes ISUP Parameter values: SIP Parameter values: VA_01 IAM NoAS_VALUE: "national (significant) number"(NDC+SN) INVITE FHf_Addr_SPEC_ID: Add CC (of the country where the MGCF is located) to Additional calling party number Signals then map to user portion of URI scheme used INVITE PAIh_Addr_SPEC_ID: Add CC (of the country where the MGCF is located) to Calling party number Signals then map to user portion of URI scheme used VA_02 IAM NoAS_VALUE: "international number" ("+"CC+NDC+SN) INVITE FHf_Addr_SPEC_ID: the complete Additional calling party number Address Signals is mapped to the user portion of URI scheme. INVITE PAIh_Addr_SPEC_ID: the complete Calling party number Address Signals is mapped to the user portion of URI scheme used. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 311
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.2 Call Hold (HOLD)
TP602001 SIP reference: RFC 3261 [6] ISUP reference: [14], clause 7.4.10 TSS reference: ISUP-SIP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: Each party can hold and retrieve the remote party in the confirmed state Ensure that a party can put the other party on hold at any time after the call is answered and before call clearing has begun. Ensure that a party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The calling party should be able to retrieve the other party The called party should be able to put the other party on hold The called party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: ISUP/BICC MGCF SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE CPG(hold) INVITE(sendonly)  200 OK INVITE(recvonly) CPG(retrieve) INVITE(sendrecv)  200 OK INVITE(sendrecv) CPG(hold)   INVITE(sendonly) 200 OK INVITE(recvonly) CPG(retrieve)   INVITE(sendrecv) 200 OK INVITE(sendrecv) ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 312 TP602002 SIP reference: RFC 3261 [6] ISUP reference: [14], clause 7.4.10 TSS reference: ISUP-SIP/SS/HOLD/ SIP selection criteria: PICS 8/4 AND PICS 8/1 ISUP selection criteria: PICS 5/22 Test purpose: The calling party can hold and retrieve the remote party in the early dialogue Ensure that a party can put the other party on hold in the alerting state. Ensure that the party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The calling party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: ISUP/BICC MGCF SIP IAM INVITE ACM   180 Ringing CPG(hold) UPDATE(sendonly)  200 OK UPDATE(recevonly) CPG(retrieve) UPDATE(sendrecv)  200 OK UPDATE(sendrecv) TP602003 SIP reference: RFC 3261 [6] ISUP reference: [14], clause 7.4.10 TSS reference: ISUP-SIP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: HOLD indication in SDP in an UPDATE received Ensure that a party can put the other party on hold after the calling user has provided all of the information necessary for processing the call. Ensure that the party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The calling party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . <version incremented> ISUP Parameter values: ACM: called party status: no indication CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: ISUP/BICC MGCF SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE CPG(hold)   UPDATE(sendonly) 200 OK UPDATE(recevonly) CPG(retrieve)   UPDATE(sendrecv) 200 OK UPDATE(sendrecv) ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 313 TP602004 SIP reference: RFC 3261 [6] ISUP reference: [14], clause 7.4.10 TSS reference: ISUP-SIP/SS/HOLD/ SIP selection criteria: PICS 8/4 AND PICS 8/3 ISUP selection criteria: PICS 5/22 Test purpose: The SUT uses the UPDATE method to indicate HOLD in the SDP Ensure that a party can put the other party on hold by using the UPDATE method to indicate the hold and retrieve state. Ensure that the party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The calling party should be able to retrieve the other party SIP Parameter values: UPDATE SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: ISUP/BICC MGCF SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE CPG(hold) UPDATE(sendonly)  200 OK UPDATE(recevonly) CPG(retrieve) UPDATE(sendrecv)  200 OK UPDATE(sendrecv) ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 314 TP602005 SIP reference: RFC 3261 [6] ISUP reference: [14], clause 7.4.10 TSS reference: ISUP-SIP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: Each party can hold and retrieve the remote party in the confirmed state Ensure that a party can put the other party on hold at any time after the call is answered and before call clearing has begun. Ensure that a party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The called party should be able to put the other party on hold The calling party should be able to retrieve the other party The called party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: ISUP/BICC MGCF SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE CPG(hold) INVITE(sendonly)  200 OK INVITE(recvonly) CPG(hold)   INVITE(inactive) 200 OK INVITE(inactive) CPG(retrieve) INVITE(recvonly)  200 OK INVITE(sendonly) CPG(retrieve)   INVITE(sendrecv) 200 OK INVITE(sendrecv) ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 315 TP602006 SIP reference: RFC 3261 [6] ISUP reference: [14], clause 7.4.10 TSS reference: ISUP-SIP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: Each party can hold and retrieve the remote party in the confirmed state Ensure that a party can put the other party on hold at any time after the call is answered and before call clearing has begun. Ensure that a party can retrieve the call previously put on hold. The calling party should be able to put the other party on hold The called party should be able to put the other party on hold The called party should be able to retrieve the other party The calling party should be able to retrieve the other party SIP Parameter values: SDP: a=sendonly (put on hold) a=sendrecv or omitted (retrieve the call) o= . . <version incremented> ISUP Parameter values: CPG: Generic notification: remote hold Event indicator PROGRESS (put on hold) Generic notification: remote retrieval event indicator PROGRESS (retrieve the call) Comments: ISUP/BICC MGCF SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE CPG(hold) INVITE(sendonly)  200 OK INVITE(recvonly) CPG(hold)   INVITE(inactive) 200 OK INVITE(inactive) CPG(retrieve)   INVITE(recvonly) 200 OK INVITE(sendonly) CPG(retrieve) INVITE(sendrecv)  200 OK INVITE(sendrecv)
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.3 Terminal portability (TP)
Void. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 316
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.4 Conference calling (CONF)
TP604001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.14 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/10 Test purpose: Establish and disconnect a Conference Ensure that the SUT does not stop the temporarily sending one or more unicast media streams if a CPG message Generic notification indicator with the value • Conference established • Conference disconnected was received due to the CONF supplementary service. SIP Parameter values: ISUP Parameter values: CPG: Generic notification = Conference established CPG: Generic notification = Conference disconnected Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(Conference established) CPG(Conference disconnected) Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 317 TP604002 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.14 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/10 Test purpose: Isolate and reattach a Conference Ensure that the SUT stop the temporarily sending one or more unicast media streams if a CPG message Generic notification indicator with the value: • Isolated • reattached was received due to the CONF supplementary service. SIP Parameter values: SDP: a= sendonly SDP: a= sendrecv ISUP Parameter values: CPG: Generic notification = Conference established CPG: Generic notification = Isolated CPG: Generic notification = Reattached CPG: Generic notification = Conference disconnected Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(Conference established) CPG(Isolated) INVITE(sendonly)  200 OK INVITE(recvonly) ACK CPG(Reattached) INVITE(sendrecv)  200 OK INVITE(sendrecv) ACK CPG(Conference disconnected) Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 318 TP604003 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec. Q.1912.5 [32], annex B.14 ITU-T Rec. Q.734.1 [34], clause 1.7 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: ISUP selection criteria: NOT PICS 5/10 Test purpose: Mapping of isolated and reattached not supported Ensure that the MGCF can receive in a CPG the Generic notifications "isolated" and "reattached", no mapping on the SIP side and the call is not disrupted. No mapping, no disrupting the SIP procedure. SIP Parameter values: No mapping ISUP Parameter values: CPG: Generic notification = Conference established CPG: Generic notification = isolated CPG: Generic notification = reattached CPG: Generic notification = Conference disconnected Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(Conference established) CPG(Isolated) CPG(Reattached) CPG(Conference disconnected) Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 319 TP604004 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec. Q.1912.5 [32], annex B.14 ITU-T Rec. Q.734.1 [34], clause 1.7 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: ISUP selection criteria: NOT PICS 5/10 Test purpose: No mapping of generic notifications no change the session state Ensure that the MGCF can receive in a CPG the Generic notifications is "other party added" or "other party isolated" or "other party reattached" or "other party split" or " conference floating" or " other party disconnected" and there is no mapping on the SIP side and the call is not disrupted. No mapping, no disrupting the SIP procedure. SIP Parameter values: No mapping ISUP Parameter values: CPG: Generic notification = Conference established CPG: Generic notification = other party added CPG: Generic notification = other party isolated CPG: Generic notification = other party reattached CPG: Generic notification = other party split CPG: Generic notification = other party disconnected CPG: Generic notification = Conference floating CPG: Generic notification = Conference disconnected Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(Conference established) CPG(other party added) CPG(other party isolated) CPG(other party reattached) CPG(other party split) CPG(other party disconnected) CPG(Conference floating) CPG(Conference disconnected) Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 320 TP604005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1.1 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "conference established" Upon the receipt of a conference information document with the <conference-state-type> element active is set to "true", the MGCF shall send a CPG message to the CS side with a notification "conference established". SIP Parameter values: NOTIFY 1: Event contains conference; Subscription-State contains active; expires=xxxx application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: CPG(Conference established) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE CPG(Conference established)   NOTIFY 1 200 OK NOTIFY REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 321 TP604006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1.1 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "conference established" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "connected" and it was not set to "on-hold" before and the Contact URI in the element entity is not the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "other party added". SIP Parameter values: NOTIFY 1: See test case TP604006 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>y</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: CPG(other party added) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE CPG(Conference established)   NOTIFY 1 200 OK NOTIFY CPG(other party added)   NOTIFY 2 200 OK NOTIFY REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 322 TP604007 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1.1 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "isolated" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "on-hold" and it was set to "connected" before and the Contact URI in the element entity is the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "isolated". SIP Parameter values: NOTIFY 1: See test case TP604006 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>on-hold</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: CPG(isolated) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE CPG(Conference established)   NOTIFY 1 200 OK NOTIFY CPG(isolated)   NOTIFY 2 200 OK NOTIFY REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 323 TP604008 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1.1 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "other party isolated" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "on-hold" and it was set to "connected" before and the Contact URI in the element entity is not the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "other party isolated". SIP Parameter values: NOTIFY 1: See test case TP604006 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>on-hold</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: CPG(other party isolated) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE CPG(Conference established)   NOTIFY 1 200 OK NOTIFY CPG(other party isolated)   NOTIFY 2 200 OK NOTIFY REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 324 TP604009 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1.1 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "reattached" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "connected" and it was set to "on-hold" before and the Contact URI in the element entity is the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "reattached". SIP Parameter values: NOTIFY 1: see test case TP604006 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>on-hold</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> NOTIFY 3: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <users> <user entity=ISUPx URI state="full" <endpoint entity=endpoint ISUPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: CPG(reattached) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE CPG(Conference established)   NOTIFY 1 200 OK NOTIFY CPG(isolated)   NOTIFY 2 200 OK NOTIFY CPG(reattached)   NOTIFY 3 200 OK NOTIFY REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 325 TP604010 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1.1 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "reattached" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "connected" and it was set to "on-hold" before and the Contact URI in the element entity is not the address of the served PSTN/ISDN participant, the MGCF shall send a CPG message to the CS side with a notification "other party reattached". SIP Parameter values: NOTIFY 1: See test case TP604006 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>on-hold</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> NOTIFY 3: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: CPG(other party reattached) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE CPG(Conference established)   NOTIFY 1 200 OK NOTIFY CPG(other party isolated)   NOTIFY 2 200 OK NOTIFY CPG(other party reattached)   NOTIFY 3 200 OK NOTIFY REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 326 TP604011 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1.1 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is mapped into "other party disconnected" Upon the receipt of a conference information document with the <endpoint-type> and the element status of endpoint-status-type is set to "disconnected" and the element joining- method of joining-type is not set to "focus-owner, the MGCF shall send a CPG message to the CS side with a notification "other party disconnected". SIP Parameter values: NOTIFY 1: See test case TP604006 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>y</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> NOTIFY 3: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>1</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>disconnected</status> <joining-method>dialed-out</ joining-method> <disconnection-method>booted<disconnection-method/> <media id="1" <status>sendrecv</status> ISUP Parameter values: CPG(other party disconnected) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE CPG(Conference established)   NOTIFY 1 200 OK NOTIFY CPG(other party added)   NOTIFY 2 200 OK NOTIFY CPG(other party disconnected)   NOTIFY 3 200 OK NOTIFY REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 327 TP604012 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1.1 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: NOT PICS 1/1 ISUP selection criteria: Test purpose: Conference notification information is not mapped to PSTN Upon the receipt of a conference information document the conference notification information is not mapped to the PSTN side. No NOTIFY is sent to the ISDN user. SIP Parameter values: NOTIFY 1: Event contains conference; Subscription-State contains active; expires=xxxx NOTIFY 1: See test case TP604006 NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>y</user-count> if present <users> <user entity=SIPx URI state="full" <endpoint entity=endpoint SIPx URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> ISUP Parameter values: CPG(other party added) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE  NOTIFY 1 200 OK NOTIFY  NOTIFY 2 200 OK NOTIFY REL BYE RLC   200 OK BYE TP604013 SIP reference: RFC 3261 [6] ISUP reference: TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: ISUP selection criteria: Test purpose: The referring of MGCF is not possible when a call is established Ensure that a REFER request received by the MGCF is not successful. The request is rejected with . 403 Forbidden. The CS -site is not affected. SIP Parameter values: REFER: Request URI contained the conference URI Refer-To contains the URI of ISUPx, method=invite Referred-By contains SIP or tel URI of SIPx ISUP Parameter values: CPG(Conference established) Comments: ISUP MGCF SIP IAM INVITE ACM   180 Ringing ACM   200 OK INVITE  REFER 403 Forbidden ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 328
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.5 Three Party service (3PTY)
TP605001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.15 TSS reference: ISUP-SIP/SS/3PTY/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/5 AND PICS 5/18 Test purpose: The media stream is resumed if a 3PTY is established Ensure that the SUT resumes the media stream put on hold while the GPG (hold) was received and sends a re-INVITE containing an a-line in the SDP is set to "sendrecv" if a CPG (Conference established) was received SIP Parameter values: SDP: a= sendonly SDP: a= sendrecv ISUP Parameter values: CPG: Generic notification = remote hold CPG: Generic notification = Conference established CPG: Generic notification = Conference disconnected Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(hold) INVITE(sendonly)  200 OK INVITE(recvonly) ACK CPG(Conference established) INVITE(sendrecv)  200 OK INVITE(sendrecv) ACK CPG(Conference disconnected) Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 329 TP605002 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.15 TSS reference: ISUP-SIP/SS/3PTY / SIP selection criteria: PICS 8/1 ISUP selection criteria: PICS 5/5 AND PICS 5/18 Test purpose: Establish and disconnect a 3PTY session. SDP conveyed in an UPDATE request: • Ensure that the SUT resumes the media stream put on hold while the GPG (hold) was received and sends an UPDATE containing an a-line in the SDP is set to "sendrecv" if a CPG (Conference established) was received SIP Parameter values: SDP: a= sendonly SDP: a= sendrecv ISUP Parameter values: CPG: Generic notification = remote hold CPG: Generic notification = Conference established CPG: Generic notification = Conference disconnected Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(hold) UPDATE(sendonly)  200 OK UPDATE(recvonly) CPG(Conference established) UPDATE(sendrecv)  200 OK UPDATE(sendrecv) CPG(Conference disconnected) Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 330 TP605003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.13 ITU-T Rec. Q.734.2 [35], clause 2.7 TSS reference: ISUP-SIP/SS/3PTY/ SIP selection criteria: ISUP selection criteria: NOT PICS 5/18 Test purpose: Interworking of "conference established" and "Conference disconnected" not supported Ensure that the SUT on receipt of a CPG message due to the 3PTY supplementary service, the Generic notification indicator with the value. No mapping, no disrupting the SIP procedure. SIP Parameter values: No mapping ISUP Parameter values: CPG: Generic notification = remote hold CPG: Generic notification = Conference established CPG: Generic notification = Conference disconnected Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(hold) CPG(Conference established) CPG(Conference disconnected) Conversation REL BYE RLC   200 OK BYE
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.6 Connected line identification (COL)
TP606001 SIP reference: RFC 3261 [6] ES 283 027 [1], clause 7.4.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: NOT PICS 5/3 ISUP selection criteria: Test purpose: IAM with OFCI "connected line request" received, no mapping Ensure that the SUT if the IAM is received with an optional forward call indicator, connected line requested, continue without disrupting the SIP or ISUP signalling procedure. SIP Parameter values: No mapping ISUP Parameter values: IAM: Optional Forward call indicator "Connected line request" Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 331 TP606002 SIP reference: RFC 3261 [6] ES 283 027 [1], clause 7.4.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: PICS 5/3 ISUP selection criteria: Test purpose: IAM with oFCi "connected line request" received, INVITE is sent contains the "from-change" tag in the Supported header Ensure that the SUT if the IAM is received with an optional forward call indicator, connected line requested, the "from-change" tag is included in the Supported header in the sent INVITE. SIP Parameter values: INVITE: Supported: from-change ISUP Parameter values: IAM: Optional Forward call indicator "Connected line request" ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 332 TP606003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: PICS 5/3 ISUP selection criteria: NOT PICS 1/5 Test purpose: The P-Asserted-Identity is mapped into the connected number "national (significant) number" Ensure that the SUT in Idle state, on receipt of an IAM message where the COLP service has been requested by the calling party by parsing the „Optional Forward Call Indicators" field and the "Connected Line Identity Request indicator" is set to "requested", on receipt of a 1XX or 2XX message defined as SIP_MESSAGE_VA with the P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received and no Privacy header field was received or a Privacy header field was received and the priv- value is set to "none" in the ANM or CON is included the Connected number Parameter. If CC encoded in the URI is equal to the CC of the country where MGCF is located AND the next BICC/ISUP node is located in the same country then Address presentation restricted parameter = presentation allowed Nature of address indicator = National (significant) number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network Provided Address signals in the format: NDC+SN Generic number parameter not present SIP Parameter values: 1XX or 2XX response: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: IAM: Optional Forward Call Indicators, Connected Line Identity Request indicator" = "requested" ANM; Connected number parameter Address presentation restricted parameter = '00'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = '11'B Address signals = PIXIT ISUP MGCF SIP IAM INVITE  SIP_MESSAGE_VA CASE A ACM  ANM  CASE B CON  Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 333 TP606004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: PICS 5/3 ISUP selection criteria: PICS 1/5 Test purpose: The P-Asserted-Identity is mapped into the connected number "international number" Ensure that the SUT in Idle state, on receipt of an IAM message where the COLP service has been requested by the calling party by parsing the „Optional Forward Call Indicators" field and the "Connected Line Identity Request indicator" is set to "requested", on receipt of a 1XX or 2XX message defined as SIP_MESSAGE_VA with the P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN has been received and no Privacy header field was received or a Privacy header field was received and the priv- value is set to "none" in the ANM or CON is included the Connected number Parameter. If CC encoded in the URI is not equal to the CC of the country where MGCF is located AND the next BICC/ISUP node is located in the same country then Address presentation restricted parameter = Presentation allowed Nature of address indicator = International number Numbering plan indicator = ISDN/Telephony numbering plan Screening indicator = Network Provided Address signals in the format: CC+NDC+SN Generic number parameter not present SIP Parameter values: 1XX or 2XX response: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: IAM: Optional Forward Call Indicators, Connected Line Identity Request indicator" = "requested" ANM; Connected number parameter Address presentation restricted parameter = '00'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = '11'B Address signals = PIXIT ISUP MGCF SIP IAM INVITE  SIP_MESSAGE_VA CASE A ACM  ANM  CASE B CON  Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 334 TP606005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: PICS 5/3 ISUP selection criteria: PICS 1/5 Test purpose: P-Asserted-Identity not received, a connected number "address not available" is sent Ensure that the SUT in Idle state, on receipt of an IAM message where the COLP service has been requested by the calling party by parsing the „Optional Forward Call Indicators" field and the "Connected Line Identity Request indicator" is set to "requested", on receipt of a 1XX or 2XX message defined as SIP_MESSAGE_VA with no P-Asserted-Identity header field In the ANM or CON is included the Connected number Parameter. Address presentation restricted parameter = Address not available Screening indicator = Network Provided Address signals omitted Generic number parameter not present SIP Parameter values: 1XX or 2XX response: P-Asserted-Identity header field is not present ISUP Parameter values: IAM: Optional Forward Call Indicators, Connected Line Identity Request indicator" = "requested" ANM or CON Connected number parameter Address presentation restricted parameter = '10'B Nature of address indicator = '0000000'B Numbering plan indicator = '000'B Screening indicator = '11'B Address signals = not presented ISUP MGCF SIP IAM INVITE  SIP_MESSAGE_VA CASE A ACM  ANM  CASE B CON  Conversation REL BYE RLC   200 OK BYE Values for tests purposes TP606003 to TP606005 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 335 TP606006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clauses 7.4.2 and 7.5.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: PICS 5/3 ISUP selection criteria: Test purpose: Interworking of From header in the UPDATE. An additional connected number is sent in the ANM or CON Ensure that the SUT in Idle state, on receipt of an IAM message where the COLP service has been requested by the calling party by parsing the „Optional Forward Call Indicators" field and the "Connected Line Identity Request indicator" is set to "requested", on receipt of a 1XX or 2XX message with the option tag "from-change" is received a Privacy header field was received and the priv-value is set to PRIV_VALUE An UPDATE request is received containing a changed From header field containing a URI with an identity in the format "+" CC+ NDC+ SN then - map the From header field received in the UPDATE request to the Generic number in the ANM or CON In the ANM or CON is included the Connected number Parameter. Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = Presentation restricted Screening indicator = Network Provided Address signals derived from the P-Asserted-Identity in the 200 OK INVITE In the ANM or CON is included the Generic number parameter Number Qualifier = additional connected number Address presentation restricted parameter = Presentation restricted Numbering plan indicator = ISDN numbering plan Screening indicator = user provided, not verified Address signals = derived from the From header in the UPDATE SIP Parameter values: INVITE: Supported: from-change 1XX or 2XX response: P-Asserted-Identity header field URI in the format "+"CC+NDC+SN, Supported: from-change UPDATE: From header in the format "+"CC+NDC+SN ISUP Parameter values: IAM: Optional Forward Call Indicators, Connected Line Identity Request indicator" = "requested" ANM or CON Genericnumber Number Qualifier = "00000101"B Address presentation restricted parameter = '01'B Nature of address indicator = '0000011'B Numbering plan indicator = '001'B Screening indicator = '11'B Address signals = derived from the From header in the UPDATE ISUP MGCF SIP IAM INVITE CASE A ACM   180 Ringing  200 OK INVITE ACK  UPDATE ANM  200 OK UPDATE CASE B ACM   183 Session Progress  200 OK INVITE ACK  UPDATE ANM  200 OK UPDATE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 336 TP606006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clauses 7.4.2 and 7.5.2 CASE C  200 OK INVITE ACK  UPDATE CON  200 OK UPDATE Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 337 TP606007 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clauses 7.4.2 and 7.5.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: PICS 5/22 ISUP selection criteria: Test purpose: Interworking of P-Asserted-Identity and From header. The Connected number and the additional connected number is presentation allowed Ensure that the SUT in Idle state, on receipt of an IAM message where the COLP service has been requested by the calling party by parsing the „Optional Forward Call Indicators" field and the "Connected Line Identity Request indicator" is set to "requested", on receipt of a 1XX or 2XX message with the P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN and the option tag "from-change" is received a Privacy header field is not included An UPDATE request is received containing a changed From header field containing a URI with an identity in the format "+" CC+ NDC+ SN then - map the From header field received in the UPDATE request to the Generic number in the ANM In the ANM or CON is included the Connected number Parameter. Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = Presentation allowed Screening indicator = Network Provided Address signals derived from the P-Asserted-Identity in the 200 OK INVITE In the ANM or CON is included the Generic number parameter Number Qualifier = additional connected number Address presentation restricted parameter = Presentation allowed Numbering plan indicator = ISDN numbering plan Screening indicator = user provided, not verified Address signals derived from the From header in the UPDATE SIP Parameter values: INVITE: Supported: from-change 1XX or 2XX response: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN UPDATE: From header, P-Asserted-Identity ISUP Parameter values: IAM: Optional Forward Call Indicators, Connected Line Identity Request indicator" = "requested" ANM or CON Connected number parameter Address presentation restricted parameter = "00"B Numbering plan indicator = '001'B Screening indicator = '11'B Address signals = PIXIT Generic number parameter Number Qualifier = "00000101"B Address presentation restricted parameter = "00"B Numbering plan indicator = '001'B Screening indicator = '11'B Address signals = derived from the From header in the UPDATE ISUP MGCF SIP IAM INVITE CASE A ACM   180 Ringing  200 OK INVITE ACK  UPDATE ANM  200 OK UPDATE CASE B ACM   183 Session Progress ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 338 TP606007 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clauses 7.4.2 and 7.5.2  200 OK INVITE ACK  UPDATE ANM  200 OK UPDATE CASE C  200 OK INVITE ACK  UPDATE CON  200 OK UPDATE Conversation REL BYE RLC   200 OK BYE TP606008 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clauses 7.4.2 and 7.5.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: PICS 5/22 ISUP selection criteria: Test purpose: Interworking of P-Asserted-Identity to the connected number if no UPDATE was received Ensure that the SUT in Idle state, on receipt of an IAM message where the COLP service has been requested by the calling party by parsing the „Optional Forward Call Indicators" field and the "Connected Line Identity Request indicator" is set to "requested", on receipt of a 1XX or 2XX message with the P-Asserted-Identity header field containing a URI with an identity in the format "+" CC+ NDC+ SN and the option tag "from-change" is received and a Privacy header field is not included When the 200 OK was received, start timer TTIR1 An UPDATE request is not received After TTIR1 was expired the ANM or CON is sent In the ANM or CON is included the Connected number Parameter. Numbering plan indicator = ISDN/Telephony numbering plan Address presentation restricted parameter = Presentation allowed Screening indicator = Network Provided Address signals derived from the P-Asserted-Identity in the 200 OK INVITE. A Generic Number parameter is not present SIP Parameter values: INVITE: Supported: from-change 1XX or 2XX response: P-Asserted-Identity header field Tel URL containing an URI in the format "+"CC+NDC+SN ISUP Parameter values: IAM: Optional Forward Call Indicators, Connected Line Identity Request indicator" = "requested" ANM or CON Connected number parameter Address presentation restricted parameter = "00"B Numbering plan indicator = '001'B Screening indicator = '11'B Address signals = PIXIT ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 339 TP606008 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clauses 7.4.2 and 7.5.2 ISUP MGCF SIP IAM INVITE CASE A ACM   180 Ringing  200 OK INVITE ACK TTIR1 ANM  CASE B ACM   183 Session Progress  200 OK INVITE ACK TTIR1 ANM  CASE C  200 OK INVITE ACK TTIR1 CON  Conversation REL BYE RLC   200 OK BYE Values for test purpose TP606006 VA PRIV_VALUE VA_1 Id VA_2 User VA_3 Header
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.7 Sub-addressing (SUB)
TP607001 CW Reference: ES 283 027 [1], clause 4.7.4.5.2 Selection criteria: PICS 5/8 TSS reference: ISUP-SIP/SS/SUB/ Preconditions: Test purpose: The calling party subaddress is mapped in the isub parameter of the P-Asserted-Identity Ensure that the calling party subaddress in the ATP parameter of the received IAM is interworked in the isub parameter of the P-Asserted-Identity in the sent INVITE, if the Type of Subbaddress is set to "0 0 0" "NSAP. SIP Parameter values: INVITE: P-Asserted-Identity: sip: user part; isub=<subaddress>@hostportion ISUP Parameter values: IAM: ATP(Calling party subaddress) Comments: ISUP MGCF SIP IAM(ATP) INVITE  100 Trying ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 340 TP607002 CW Reference: ES 283 027 [1], clause 4.7.4.5.2 Selection criteria: PICS 5/8 TSS reference: ISUP-SIP/SS/SUB/ Preconditions: Test purpose: The called party subaddress is mapped in the isub parameter of the Request URI Ensure that the called party subaddress in the ATP parameter of the received IAM is interworked in the isub parameter of the Request URI in the sent INVITE, if the Type of Subbaddress is set to "0 0 0" "NSAP. SIP Parameter values: INVITE: Request URI: sip: user part; isub=<subaddress>@hostportion ISUP Parameter values: IAM: ATP(Called party subaddress) Comments: ISUP MGCF SIP IAM(ATP) INVITE  100 Trying ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE TP607003 CW Reference: ES 283 027 [1], clause 4.7.4.5.2 Selection criteria: PICS 5/8 TSS reference: ISUP-SIP/SS/SUB/ Preconditions: Test purpose: The isub parameter of the P-Asserted-Identity in the 200 OK INVITE is mapped in the connected subaddress in the ANM Ensure that the isub parameter in the P-Asserted-Identity of the received 200 OK INVITE is interworked in the Connected subaddress contained in an ATP parameter in the sent ANMOBCI. The Type of Subbaddress is set to "0 0 0" "NSAP (ITU-T Recommendation X.213 [29] and ISO/IEC 8348 [30] Add.2)" SIP Parameter values: INVITE: supported: from-change 200 OK INVITE: P-Asserted-IDENTITY: sip: user part; isub=<subaddress>@hostportion ISUP Parameter values: IAM: oFCi: connected line request ANM: ATP(Connected subaddress) Comments: ISUP MGCF SIP IAM INVITE  100 Trying ACM   180 Ringing  200 OK INVITE ACK ANM( ATP)   UPDATE 200 OK UPDATE Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 341 TP607004 CW Reference: ES 283 027 [1], clause 4.7.4.5.2 Selection criteria: NOT PICS 5/8 TSS reference: ISUP-SIP/SS/SUB/ Preconditions: Test purpose: The calling party subaddress is not mapped in the isub parameter of the P-Asserted- Identity Ensure that the calling party subaddress in the ATP parameter of the received IAM is not interworked in the isub parameter of the From header in the sent INVITE, if the Type of Subbaddress is not set to "0 0 0" "NSAP. SIP Parameter values: INVITE: P-Asserted-Identity: sip: user part; isub=<subaddress>@hostportion ISUP Parameter values: IAM: ATP(no Calling party subaddress) Comments: ISUP MGCF SIP IAM(ATP) INVITE  100 Trying ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE TP607005 CW Reference: ES 283 027 [1], clause 4.7.4.5.2 Selection criteria: NOT PICS 5/8 TSS reference: ISUP-SIP/SS/SUB/ Preconditions: Test purpose: The called party subaddress is not mapped in the isub parameter of the Request URI Ensure that the called party subaddress in the ATP parameter of the received IAM is not interworked in the isub parameter of the Request URI in the sent INVITE, if the Type of Subbaddress is not set to "0 0 0" "NSAP. SIP Parameter values: INVITE: Request URI: sip: user part; isub=<subaddress>@hostportion ISUP Parameter values: IAM: ATP(no Called party subaddress) Comments: ISUP MGCF SIP IAM(ATP) INVITE  100 Trying ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 342
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.8 Closed user group (CUG)
TP608001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.16 TSS reference: ISUP-SIP/SS/CUG/ SIP selection criteria: NOT PICS 5/7 ISUP selection criteria: Test purpose: SIP network does not support CUG, CUG with outgoing access allowed is interworked in a normal call Ensure that the SUT if an IAM is received with Optional forward call indicator, CUG call indicator coded as "CUG call with outgoing access" and CUG interlock code or CUG call indicator coded as "Non CUG call" or Optional forward call indicator is absent, the SIP signalling procedure is not disrupted. SIP Parameter values: No mapping ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP608002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.16 TSS reference: ISUP-SIP/SS/CUG/ SIP selection criteria: NOT PICS 5/7 ISUP selection criteria: Test purpose: SIP network does not support CUG, CUG with outgoing access not allowed is rejected. Ensure that the SUT if an IAM is received with Optional forward call indicator, CUG call indicator coded as "CUG call without outgoing access" and CUG interlock code, a REL is sent. No INVITE is sent into the SIP network. SIP Parameter values: No action ISUP Parameter values: REL: Cause #29 Comments: ISUP/BICC SUT SIP IAM REL  RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 343 TP608003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.2 TSS reference: ISUP-SIP/SS/CUG/ SIP selection criteria: PICS 5/7 ISUP selection criteria: Test purpose: SIP network supports CUG. CUG call indicator value "10" received. Ensure that Optional Forward Call Indicator Parameter CUG call indicator value ‘10’ is mapped into <cug> < cugCommunicationIndicator>, the Closed user group interlock code Parameter Network identity is mapped into <cug> <networkIndicator> and the Binary code is mapped into the <cug> <cugInterlockBinaryCode>. SIP Parameter values: INVITE: <cug> <networkIndicator>[derived from IAM Network identity]</networkIndicator> <cugInterlockBinaryCode>[derived from IAM Binary code]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> ISUP Parameter values: IAM: Optional Forward Call Indicator CUG call indicator = "10" Closed User Group interlock code Binary code derived from INVITE XML body <cugInterlockBinaryCode> Network identity derived from INVITE XML body <networkIndicator> Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 344 TP608004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.2 TSS reference: ISUP-SIP/SS/CUG/ SIP selection criteria: PICS 5/7 ISUP selection criteria: Test purpose: SIP network supports CUG. CUG call indicator value "11" received. Ensure that Optional Forward Call Indicator Parameter CUG call indicator value ‘11’ is mapped into <cug> < cugCommunicationIndicator>, the Closed user group interlock code Parameter Network identity is mapped into <cug> <networkIndicator> and the Binary code is mapped into the <cug> <cugInterlockBinaryCode>. SIP Parameter values: INVITE: <cug> <networkIndicator>[derived from IAM Network identity]</networkIndicator> <cugInterlockBinaryCode>[derived from IAM Binary code]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> ISUP Parameter values: IAM: Optional Forward Call Indicator CUG call indicator = "11" Closed User Group interlock code Binary code derived from INVITE XML body <cugInterlockBinaryCode> Network identity derived from INVITE XML body <networkIndicator> Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.9 Call diversion (CDIV)
TP609001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.6 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: NOT PICS 5/12 AND NOT PICS 5/13 AND NOT PICS 5/14 AND NOT PICS 5/15 ISUP selection criteria: Test purpose: CDIV parameter not mapped Ensure that the SUT if the IAM is received with Redirecting number, original called number and redirection information, continue without disrupting the SIP or ISUP signalling procedure. SIP Parameter values: No mapping ISUP Parameter values: IAM: Redirecting number, Original called number, Redirection information Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 345 TP609002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number and redirecting number Presentation allowed received Ensure that the SUT if the IAM is received with Redirecting number, original called number Presentation allowed and redirection information Presentation allowed, the redirection counter value is "1", an INVITE is sent containing a History-Info header. The Redirecting number is contained in the hi-targeted-to-uri in index 1, the called party number is contained in the hi-targeted-to-uri in index 1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Redirecting number; index=1, or hi-targeted-to-uri Redirecting number?Privacy=none/absent; index=1, hi-targeted-to uri diverted to user; cause=Cause_value; index=1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 1 Redirecting indicator = 3 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation allowed Redirecting number Presentation restriction: Presentation allowed Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter Source value of parameter field SIP component Derived value of header field Redirection Information Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 346 TP609003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number Presentation restricted and redirecting number Presentation allowed received Ensure that the SUT if the IAM is received with Redirecting number, original called number Presentation restricted and redirection information Presentation allowed, the redirection counter value is "1", an INVITE is sent containing a History-Info header. The Redirecting number is contained in the hi-targeted-to-uri in index 1, the called party number is contained in the hi-targeted-to-uri in index 1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Redirecting number?Privacy=history; index=1, hi-targeted-to uri diverted to user; cause=Cause_value; index=1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 1 Redirecting indicator = 3 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation restricted Redirecting number Presentation restriction: Presentation allowed Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or IE Source value of parameter field SIP component Derived value of header field Redirection Information Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 347 TP609004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number Presentation allowed and redirecting number Presentation restricted received Ensure that the SUT if the IAM is received with Redirecting number presentation restricted, original called number Presentation allowed and redirection information Presentation restricted, the redirection counter value is "1", an INVITE is sent containing a History-Info header. The Redirecting number is contained in the hi-targeted-to-uri in index 1, the called party number is contained in the hi-targeted-to-uri in index 1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Redirecting number?Privacy=history; index=1, hi-targeted-to uri diverted to user; cause=Cause_value; index=1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 1 Redirecting indicator = 4 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation allowed Redirecting number Presentation restriction: Presentation restricted Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or IE Source value of parameter field SIP component Derived value of header field Redirection Information Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 348 TP609005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number Presentation allowed and redirecting number Presentation restricted received Ensure that the SUT if the IAM is received with Redirecting number presentation restricted, original called number Presentation restricted and redirection information Presentation restricted, the redirection counter value is "1", an INVITE is sent containing a History-Info header. The Redirecting number is contained in the hi-targeted-to-uri in index 1, the called party number is contained in the hi-targeted-to-uri in index 1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Redirecting number?Privacy=history; index=1, hi-targeted-to uri diverted to user; cause=Cause_value; index=1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 1 Redirecting indicator = 4 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation restricted Redirecting number Presentation restriction: Presentation restricted Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or IE Source value of parameter field SIP component Derived value of header field Redirection Information Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 349 TP609006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number and redirecting number Presentation allowed received, Redirecting indicator indicates "all redirection information presentation restricted" Ensure that the SUT if the IAM is received with Redirecting number, original called number Presentation allowed and redirection information Presentation restricted, the redirection counter value is "1", an INVITE is sent containing a History-Info header. The Redirecting number is contained in the hi-targeted-to-uri in index 1, the called party number is contained in the hi-targeted-to-uri in index 1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Redirecting number?Privacy=history; index=1, hi-targeted-to uri diverted to user; cause=Cause_value; index=1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 1 Redirecting indicator = 4 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation allowed Redirecting number Presentation restriction: Presentation allowed Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter Source value of parameter field SIP component Derived value of header field Redirection Information Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 350 TP609007 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number and redirecting number Presentation allowed received, Redirection counter value 2 Ensure that the SUT if the IAM is received with Redirecting number Presentation allowed, original called number Presentation allowed and redirection information Presentation allowed, the redirection counter value is "2", an INVITE is sent containing a History-Info header. The Original called number is contained in the hi-tatgeted-to uri in the index 1. The Redirecting number is contained in the hi-targeted-to-uri in index 1.1, the called party number is contained in the hi-targeted-to-uri in index 1.1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Original called number; index=1, hi-targeted-to-uri Redirecting number; cause=302; index=1.1, hi-targeted-to-uri called party number; cause= Cause_value; index=1.1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 2 Redirecting indicator = 3 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation allowed Redirecting number Presentation restriction: Presentation allowed Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or Source value of parameter field SIP component Derived value of header field Redirection Information ISUP_RR Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 351 TP609008 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number Presentation restricted and redirecting number Presentation allowed received, Redirection counter value 2 Ensure that the SUT if the IAM is received with Redirecting number Presentation allowed, original called number Presentation restricted and redirection information Presentation allowed, the redirection counter value is "2", an INVITE is sent containing a History-Info header. The Original called number is contained in the hi-tatgeted-to uri in the index 1. The Redirecting number is contained in the hi-targeted-to-uri in index 1.1, the called party number is contained in the hi-targeted-to-uri in index 1.1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Original called number?Privacy=history; index=1, hi-targeted-to-uri Redirecting number; cause=302; index=1.1, hi-targeted-to-uri called party number; cause= Cause_value; index=1.1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 2 Redirecting indicator = 3 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation restricted Redirecting number Presentation restriction: Presentation allowed Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or Source value of parameter field SIP component Derived value of header field Redirection Information ISUP_RR Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 352 TP609009 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number Presentation allowed and redirecting number Presentation restricted received, Redirection counter value 2 Ensure that the SUT if the IAM is received with Redirecting number Presentation restricted, original called number Presentation allowed and redirection information Presentation restricted, the redirection counter value is "2", an INVITE is sent containing a History-Info header. The Original called number is contained in the hi-tatgeted-to uri in the index 1. The Redirecting number is contained in the hi-targeted-to-uri in index 1.1, the called party number is contained in the hi-targeted-to-uri in index 1.1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Original called number; index=1, hi-targeted-to-uri Redirecting number; ?Privacy=history;cause=302; index=1.1, hi-targeted-to-uri called party number; cause=Cause_value; index=1.1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 2 Redirecting indicator = 4 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation allowed Redirecting number Presentation restriction: Presentation restricted Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or Source value of parameter field SIP component Derived value of header field Redirection Information ISUP_RR Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 353 TP609010 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number and redirecting number Presentation restricted received, Redirection counter value 2 Ensure that the SUT if the IAM is received with Redirecting number Presentation restricted, original called number Presentation restricted and redirection information Presentation restricted, the redirection counter value is "2", an INVITE is sent containing a History-Info header. The Original called number is contained in the hi-tatgeted-to uri in the index 1. The Redirecting number is contained in the hi-targeted-to-uri in index 1.1, the called party number is contained in the hi-targeted-to-uri in index 1.1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Original called number?Privacy=history index=1, hi-targeted-to-uri Redirecting number; ?Privacy=history; cause=302; index=1.1, hi-targeted-to-uri called party number; cause= Cause_value; index=1.1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 2 Redirecting indicator = 4 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation restricted Redirecting number Presentation restriction: Presentation restricted Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or Source value of parameter field SIP component Derived value of header field Redirection Information ISUP_RR Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 354 TP609011 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number and redirecting number received, Redirection counter value 3 Ensure that the SUT if the IAM is received with Redirecting number, original called number and redirection information, the redirection counter value is "3", an INVITE is sent containing a History-Info header. The Original called number is contained in the hi- tatgeted-to uri in the index 1. The Redirecting number is contained in the hi-targeted-to-uri in index 1.1.1, the called party number is contained in the hi-targeted-to-uri in index 1.1.1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Original called number; index=1, hi-targeted-to-uri Dummy entry(PIXIT); cause=302; index=1.1, hi-targeted-to-uri Redirecting number; cause=486; index=1.1.1, hi-targeted-to-uri called party number; cause= Cause_value; index=1.1.1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 3 Redirecting reason = ISUP_RR Original called number Redirecting number Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or Source value of parameter field SIP component Derived value of header field Redirection Information ISUP_RR Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 355 TP609012 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 ISUP selection criteria: Test purpose: IAM with Original call number and redirecting number Presentation allowed received, Redirection counter value 2, Redirecting indicator indicates "all redirection information presentation restricted" Ensure that the SUT if the IAM is received with Redirecting number, original called number Presentation allowed and redirection information Presentation restricted, the redirection counter value is "2", an INVITE is sent containing a History-Info header. The Original called number is contained in the hi-tatgeted-to uri in the index 1. The Redirecting number is contained in the hi-targeted-to-uri in index 1.1, the called party number is contained in the hi-targeted-to-uri in index 1.1.1. The cause parameter value in the latest history entry is mapped from the redirection reason indicator. SIP Parameter values: INVITE: History-Info header hi-targeted-to-uri Original called number?Privacy=history; index=1, hi-targeted-to-uri Redirecting number?Privacy=history; cause=302; index=1.1, hi-targeted-to-uri called party number; cause= Cause_value; index=1.1.1 ISUP Parameter values: IAM: Redirection information: "call diversion" Redirection counter = 2 Redirecting indicator = 4 Redirecting reason = ISUP_RR Original called number Presentation restriction: Presentation allowed Redirecting number Presentation restriction: Presentation allowed Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC 200 OK BYE   IAM INVITE ISUP Parameter or Source value of parameter field SIP component Derived value of header field Redirection Information ISUP_RR Redirecting reason History-Info header Cause parameter unknown '0000'B Cause_value 404 Unconditional '0011'B 302 User Busy '0001'B 486 No reply '0010'B 408 Deflection during alerting '0100'B 487 Deflection immediate response '0101'B 480 Mobile subscriber not reachable 503 ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 356 TP609013 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 181 Received, Notification subscription option according the Privacy header in the History-Info header Ensure that the SUT (when no ACM has been sent before) on receipt of 181 (Call Is Being Forwarded) containing the History-Index, Privacy, priv-value component in the History-Info header, Privacy, priv-value component concerning the diverted-to uri Sends an ACM message indicating a first diversion with the Backward call indicators parameter coded Called party's status indicator = no indication Redirection number: Redirection number: derived from the Hi-target-to-uri of the last History-Info entry the Call diversion information parameter Notification subscription option = ISUP_NSO and the Generic notification indicator parameter = call is diverting SIP Parameter values: 181: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=priv-value; index=1.1 ISUP Parameter values: ACM BCI: No indication (00), GenNot: Call is diverting (1111011), Call diversion Info: ISUP_NSO Redirection number: derived from the Hi-target-to-uri of the last History-Info entry Comments: ISUP SUT SIP IAM INVITE ACM   181 Being Forwarded CPG   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE SIP component History-Info header, priv-value component Call diversion information Notification subscription options ISUP_NSO VA_01 Privacy header field absent ISUP_NSO = presentation allowed with redirection number VA_02 Privacy "none" ISUP_NSO = presentation allowed with redirection number VA_03 Privacy "history" ISUP_NSO = presentation allowed without redirection number ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 357 TP609014 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 181 received, ACM no indication is sent: NSO Presentation not allowed Ensure that the SUT (when no ACM has been sent before) on receipt of 181 (Call Is Being Forwarded) containing priv-value history is set to the hist-info element concerning the redirecting uri and the diverted-to-uri then Sends of an ACM message indicating a first diversion with the Backward call indicators parameter coded Called party's status indicator = no indication Redirection number: Redirection number: derived from the Hi-target-to-uri of the last History-Info entry the Call diversion information parameter Notification subscription option = presentation not allowed and the Generic notification indicator parameter = call is diverting SIP Parameter values: 181: History-Info header hi-targeted-to-uri Redirecting number?Privacy=history; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=history; index=1.1 ISUP Parameter values: ACM BCI: No indication (00), GenNot: Call is diverting (1111011), Call diversion Info: presentation not allowed Redirection number: derived from the Hi-target-to-uri of the last History-Info entry Comments: ISUP SUT SIP IAM INVITE ACM   181 Being Forwarded CPG   180 Ringing ANM   200 OK INVITE ACK REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 358 TP609015 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 181 received sending of Redirection number restriction parameter in the ACM Ensure that the SUT (when no ACM has been sent before) on receipt of 181 (Call Is Being Forwarded) containing the History-Info header, Privacy, priv-value component Sends of an ACM message indicating a first diversion with the Backward call indicators parameter coded Called party's status indicator = no indication Redirection number: Redirection number: derived from the Hi-target-to-uri of the last History-Info entry Redirection number restriction indicator Redirection number restriction option = ISUP_ReNrReIn and the Generic notification indicator parameter = call is diverting SIP Parameter values: 181: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=priv-value; index=1.1 ISUP Parameter values: ACM: BCI: No indication (00), GenNot: Call is diverting (1111011), Redirection number: derived from the Hi-target-to-uri of the last History-Info entry Redirection number restriction indicator: ISUP_ReNrReIn Comments: ISUP SUT SIP IAM INVITE ACM   181 Being Forwarded CPG   180 Ringing ANM   200 OK INVITE ACK REL BYE RLC   200 OK BYE History-Info header Privacy, priv-value component Redirection number restriction indicator ISUP_ReNrReIn VA_01 Privacy "history" Presentation restricted VA_02 Privacy header field absent Presentation allowed or absent VA_03 Privacy "none" Presentation allowed or absent ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 359 TP609016 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 181 received, coding of notification subscription option in the CPG Progress Ensure that the SUT, when an ACM has been sent before, on receipt of 181 (Call Is Being Forwarded) containing the History-Index, Privacy, priv-value component and the History- Info header, Privacy, priv-value component concerning the diverted-to uri Sends a CPG message indicating a first diversion with the Event information parameter coded Event indicator = PROGRESS, Redirection number: Redirection number: derived from the Hi-target-to-uri of the last History-Info entry the Call diversion information parameter Notification subscription option = ISUP_NSO and the Generic notification indicator parameter = call is diverting SIP Parameter values: 181: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=Priv-value; index=1.1 ISUP Parameter values: CPG: Event indicator = PROGRESS, GenNot: Call is diverting (1111011), Call diversion Info: ISUP_NSO Redirection number: derived from the Hi-target-to-uri of the last History-Info entry Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing CPG   181 Being Forwarded ANM   200 OK INVITE ACK REL BYE RLC   200 OK BYE SIP component History-Index Privacy, priv-value component Call diversion information Notification subscription options ISUP_NSO VA_01 Privacy header field absent ISUP_NSO = presentation allowed with redirection number VA_02 Privacy "none" ISUP_NSO = presentation allowed with redirection number VA_03 Privacy "history" ISUP_NSO = presentation not allowed, ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 360 TP609017 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 181 received Privacy=history concerning the redirecting and the diverted-to URI setting of NSO in the CPG Progress Ensure that the SUT, when an ACM has been sent before, on receipt of 181 (Call Is Being Forwarded) containing priv-value history is set to the hist-info element concerning the redirecting uri and the diverted-to-uri then Sends a CPG message indicating a first diversion with the Event information parameter coded Event indicator = PROGRESS, Redirection number: Redirection number: derived from the Hi-target-to-uri of the last History-Info entry the Call diversion information parameter Notification subscription option = presentation not allowed and the Generic notification indicator parameter coded Notification indicator = call is diverting, SIP Parameter values: 181: History-Info header hi-targeted-to-uri Redirecting number?Privacy=history; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=history; index=1.1 ISUP Parameter values: CPG: Event indicator = PROGRESS, GenNot: Call is diverting (1111011), Call diversion Info: presentation not allowed Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing CPG   181 Being Forwarded ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 361 TP609018 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 181 received setting of Redirection number restriction in the CPG Progress Ensure that the SUT, when an ACM has been sent before, on receipt of 181 (Call Is Being Forwarded) containing the History-Info header, Privacy, priv-value component Sends a CPG message indicating a first diversion with the Event information parameter coded Event indicator = PROGRESS, Redirection number: Redirection number: derived from the Hi-target-to-uri of the last History-Info entry Redirection number restriction indicator= ISUP_ReNrReIn and the Generic notification indicator parameter = call is diverting SIP Parameter values: 181: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=priv-value; index=1.1 ISUP Parameter values: CPG: Event indicator = PROGRESS, GenNot: Call is diverting (1111011), Redirection number: ISUP_ReNr Redirection number restriction indicator: ISUP_ReNrReIn Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing CPG   181 Being Forwarded ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE History-Info header Privacy, priv-value component Redirection number restriction indicator ISUP_ReNrReIn VA_01 Privacy "history" Presentation restricted VA_02 Privacy "none" Presentation allowed or absent VA_03 Privacy header field absent Presentation allowed or absent ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 362 TP609019 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 180 received, CPG Alerting is sent, setting of NSO. Ensure that the SUT on receipt of 180 (Ringing) (181 Call Is Being Forwarded was received before) containing the History-Info header, Privacy, priv-value component concerning diverted-to uri Sends a CPG message indicating a first diversion with the Event information parameter coded Event indicator = ALERTING, Redirection number: Redirection number: derived from the Hi-target-to-uri of the last History-Info entry the Call diversion information parameter Notification subscription option = ISUP_NSO and the Generic notification indicator parameter = call is diverting SIP Parameter values: 180: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=priv-value; index=1.1 ISUP Parameter values: CPG: Event indicator = ALERTING, GenNot: Call is diverting (1111011), Redirection number: derived from the Hi-target-to-uri of the last History-Info entry Notification subscription option: ISUP_NSO Comments: ISUP SUT SIP IAM INVITE ACM   181 Being Forwarded CPG   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE SIP component History-Info header, priv-value component Call diversion information Notification subscription options ISUP_NSO VA_01 Privacy header field absent ISUP_NSO = presentation allowed with redirection number VA_02 Privacy "none" ISUP_NSO = presentation allowed with redirection number VA_03 Privacy "history" ISUP_NSO = presentation allowed without redirection number ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 363 TP609020 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 180 received, CPG Alerting is sent, setting of NSO. Ensure that the SUT on receipt of 180 (Ringing) (181 Call Is Being Forwarded was received before) containing the History-Info header, Privacy, priv-value component concerning redirecting and diverted-to uri Sends a CPG message indicating a first diversion with the Event information parameter coded Event indicator = ALERTING, Redirection number: Number digits derived from the Hi-target-to-uri of the last History-Info entry The Call diversion information parameter Notification subscription option = presentation not allowed Redirection number: derived from the Hi-target-to-uri of the last History-Info entry and the Generic notification indicator parameter coded Notification indicator = call is diverting SIP Parameter values: 180: History-Info header hi-targeted-to-uri Redirecting number?Privacy=history; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=history; index=1.1 ISUP Parameter values: CPG: Event indicator = ALERTING, GenNot: Call is diverting (1111011), Redirection number: derived from the Hi-target-to-uri of the last History-Info entry Notification subscription option: Presentation not allowed Comments: ISUP SUT SIP IAM INVITE ACM   181 Being Forwarded CPG   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 364 TP609021 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 180 received, CPG Alerting is sent, setting of Redirection number restriction. Ensure that the SUT on receipt of 180 (Ringing) (181 Call Is Being Forwarded was received before) containing the History-Info header, Privacy, priv-value component concerning diverted-to uri Sends a CPG message indicating a first diversion with the Event information parameter coded Event indicator = ALERTING, Redirection number: Number digits derived from the Hi-target-to-uri of the last History-Info entry Redirection number restriction parameter Redirection number restriction indicator = ISUP_ReNrReIn and the Generic notification indicator coded Notification indicator = call is diverting SIP Parameter values: 180: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=priv-value; index=1.1 ISUP Parameter values: CPG: Event indicator = ALERTING, Redirection number restriction indicator: ISUP_ReNrReIn Comments: ISUP SUT SIP IAM INVITE ACM   181 Being Forwarded CPG   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE History-Info header Privacy, priv-value component Redirection number restriction indicator ISUP_ReNrReIn VA_01 Privacy "history" Presentation restricted VA_02 Privacy "none" Presentation allowed or absent VA_03 Privacy header field absent Presentation allowed or absent ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 365 TP609022 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: Redirection number restriction in ANM Ensure that the SUT on receipt of 200 (OK) containing the History-Info header, Privacy, priv-value component Sends a ANM message with Redirection number restriction indicator: ISUP_ReNrReIn SIP Parameter values: 200: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value?Privacy=priv-value; index=1.1 ISUP Parameter values: ANM: Redirection number restriction indicator: ISUP_ReNrReIn Comments: ISUP SUT SIP IAM INVITE ACM   181 Being Forwarded CPG   180 Ringing ANM   200 OK INVITE ACK REL BYE RLC   200 OK BYE History-Info header Privacy, priv-value component Redirection number restriction indicator ISUP_ReNrReIn VA_01 Privacy "history" Presentation restricted VA_02 Privacy "none" Presentation allowed or absent VA_03 Privacy header field absent Presentation allowed or absent TP609023 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: PICS 10/6 ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 181 Received, no mapping to an ACM Ensure that the SUT (when no ACM has been sent before) on receipt of 181 (Call Is Being Forwarded) containing the History-Index no ACM is sent SIP Parameter values: 181: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value; index=1.1 ISUP Parameter values: Comments: ISUP SUT SIP IAM INVITE  181 Being Forwarded ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 366 TP609024 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: PICS 10/6 ISUP selection criteria: PICS 5/12 AND PICS 5/13 AND PICS 5/14 AND PICS 5/15 Test purpose: 181 received, not mapped to a CPG Ensure that the SUT, when an ACM has been sent before, on receipt of 181 (Call Is Being Forwarded) containing the History-Index, no CPG is sent SIP Parameter values: 181: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value; index=1.1 ISUP Parameter values: Comments: ISUP SUT SIP IAM INVITE ACM   180 Ringing  181 Being Forwarded ANM   200 OK INVITE ACK REL BYE RLC   200 OK BYE TP609025 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: PICS 10/6 ISUP selection criteria: NOT PICS 5/12 AND NOT PICS 5/13 AND NOT PICS 5/14 AND NOT PICS 5/15 Test purpose: 180 received containing History-Info header, no mapping. Ensure that the SUT on receipt of 180 (Ringing) (181 Call Is Being Forwarded was received before) containing the History-Info header, the History-Info header is not mapped SIP Parameter values: 180: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value; index=1.1 ISUP Parameter values: Comments: ISUP SUT SIP IAM INVITE  181 Being Forwarded ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 367 TP609026 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.5.4 TSS reference: ISUP-SIP/SS/CDIV/ SIP selection criteria: PICS 10/6 ISUP selection criteria: NOT PICS 5/12 AND NOT PICS 5/13 AND NOT PICS 5/14 AND NOT PICS 5/15 Test purpose: No mapping of History-Info header in the 200 OK INVITE Ensure that the SUT on receipt of 200 (OK) containing the History-Info header, Privacy, priv-value component the History-Info header is not mapped SIP Parameter values: 200: History-Info header hi-targeted-to-uri Redirecting number; index=1, hi-targeted-to uri diverted to user; cause=Cause value; index=1.1 ISUP Parameter values: No mapping Comments: ISUP SUT SIP IAM INVITE  181 Being Forwarded ACM   180 Ringing ANM   200 OK INVITE ACK REL BYE RLC   200 OK BYE
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.10 User to user signalling (UUS)
TP610001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.1.7 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: Test purpose: User-to-user service 1 implicit request not supported, User-to-user information discarded by the network Ensure that the SUT if the IAM is received with User-to-user information as an implicit service 1 request returns a User-to-user indicator in the ACM "UUI discarded by the network" and continue without disrupting the SIP or ISUP signalling procedure. SIP Parameter values: No mapping ISUP Parameter values: ACM: User-to-indicator "UUI discarded by the network", Service 1 response "No indication". Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 368 TP610002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737 [33], clause 1.1.7 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: User-to-user service 1 explicit request not essential not supported, service not provided response Ensure that the SUT if the IAM is received with an explicit service 1 request "Not essential" returns a User-to-user indicator in the ACM "Service 1 not provided" and continue without disrupting the SIP or ISUP signalling procedure. SIP Parameter values: No mapping ISUP Parameter values: ACM: User-to-indicator Service 1 response "Not provided" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP610003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.1.7 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: User-to-user service 1 explicit request essential not supported, rejected by sending a REL Ensure that the SUT if the IAM is received with an explicit service 1 request "essential" returns a REL with cause #29 and an diagnostics containing the user-to-user indicator parameter name. SIP Parameter values: No action ISUP Parameter values: REL: cause #29, diagnostics value 0x2a Comments: ISUP/BICC SUT SIP IAM REL #29  RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 369 TP610004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737 [33], clause 1.2.7 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: User-to-user service 2 explicit request not essential not supported, service not provided response Ensure that the SUT if the IAM is received with an explicit service 2 request "Not essential" returns a User-to-user indicator in the ACM "Service 2 not provided" and continue without disrupting the SIP or ISUP signalling procedure. SIP Parameter values: No mapping ISUP Parameter values: ACM: User-to-indicator Service 2 response "Not provided" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP610005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.2.7 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: User-to-user service 2 explicit request essential not supported, rejected by sending a REL Ensure that the SUT if the IAM is received with an explicit service 2 request "essential" returns a REL with cause #29 and an diagnostics containing the user-to-user indicator parameter name. SIP Parameter values: No mapping ISUP Parameter values: REL: cause #29, diagnostics value 0x2a Comments: ISUP/BICC SUT SIP IAM REL #29  RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 370 TP610006 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.7.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: User-to-user service 3 explicit request not essential not supported, service not provided response Ensure that the SUT if the IAM is received with an explicit service 3 request "Not essential" returns a User-to-user indicator in the ANM "Service 3 not provided" and continue without disrupting the SIP or ISUP signalling procedure. SIP Parameter values: No mapping ISUP Parameter values: ACM: User-to-indicator, Service 3 response "Not provided" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP610007 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.7.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: User-to-user service 3 explicit request essential not supported, rejected by sending a REL Ensure that the SUT if the IAM is received with an explicit service 3 request "essential" returns a REL with cause #29 and an diagnostics containing the user-to-user indicator parameter name. SIP Parameter values: No mapping ISUP Parameter values: REL: cause #29, diagnostics value 0x2a Comments: ISUP/BICC SUT SIP IAM REL #29  RLC ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 371 TP610008 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.7.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: User-to-user service 3 explicit request not essential not supported in the confirmed state, rejected by sending a FRJ Ensure that the SUT if the FAR is received with an explicit service 3 request "Not essential" returns a FRJ with cause #29. SIP Parameter values: No action ISUP Parameter values: FRJ: User-to-user indicator = "Service 3 not provided" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation FAR FRJ  Conversation REL BYE RLC   200 OK BYE TP610009 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.1.5.2.5.2.2 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: NOT PICS 11/2 Test purpose: User-to-user service 1 explicit request not essential not supported, no response Ensure that the SUT if the IAM is received with an explicit service 1 request "Not essential" continue without disrupting the SIP or ISUP signalling procedure. No response to this request. SIP Parameter values: No mapping ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 372 TP610010 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.1.5.2.5.2.2 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: NOT PICS 11/2 Test purpose: User-to-user service 1 explicit request essential not supported, no response Ensure that the SUT if the IAM is received with an explicit service 1 request "essential" continue without disrupting the SIP or ISUP signalling procedure. No response to this request. SIP Parameter values: No action ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP610011 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.2.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: NOT PICS 11/2 Test purpose: User-to-user service 2 explicit request not essential not supported, no response Ensure that the SUT if the IAM is received with an explicit service 2 request "Not essential" continue without disrupting the SIP or ISUP signalling procedure. No response to this request. SIP Parameter values: No mapping ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 373 TP610012 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.2.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: NOT PICS 11/2 Test purpose: User-to-user service 2 explicit request essential not supported, no response Ensure that the SUT if the IAM is received with an explicit service 2 request "essential" continue without disrupting the SIP or ISUP signalling procedure. No response to this request. SIP Parameter values: No action ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP610013 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: NOT PICS 11/2 Test purpose: User-to-user service 3 explicit request not essential not supported, no response Ensure that the SUT if the IAM is received with an explicit service 3 request "Not essential" continue without disrupting the SIP or ISUP signalling procedure. No response to this request. SIP Parameter values: No mapping ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 374 TP610014 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: NOT PICS 11/2 Test purpose: User-to-user service 3 explicit request essential not supported, no response Ensure that the SUT if the IAM is received with an explicit service 3 request "essential" continue without disrupting the SIP or ISUP signalling procedure. No response to this request. SIP Parameter values: No action ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP610015 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: NOT PICS 11/1 OR NOT PICS 11/3 Test purpose: User-to-user service 3 explicit request not essential not supported in the confirmed state, no response Ensure that the SUT if the FAR is received with an explicit service 3 request "Not essential" continue without disrupting the SIP or ISUP signalling procedure. No response to this request. SIP Parameter values: No action ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation FAR REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 375 TP610016 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: Test purpose: User-to-user service 1 implicit request is mapped in the User-to-User header field in the INVITE request Ensure that the SUT if the IAM contains a User-to-user information parameter, a User-to- User header is included in the INVITE request and the uuidata component is derived from the User-to-user information. SIP Parameter values: INVITE: User-to-User: uuidata derived from the User-to-user information ISUP Parameter values: IAM: User-to-user information (PIXIT) Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP610017 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: Test purpose: User-to-user service 1 implicit response is mapped in the User-to-user information parameter in the ACM Ensure that the SUT if the 180 Ringing contains a User-to-User header, a User-to-user information parameter is included in the ACM and the User-to-user information is derived from the uuidata component. User-to-User header starts with the first octet being the protocol discriminator and followed by the user information octets SIP Parameter values: 180: User-to-User: uuidata derived from the User-to-user information (PIXIT) ISUP Parameter values: ACM: User-to-user information Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 376 TP610018 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: Test purpose: User-to-user service 1 implicit response is mapped in the User-to-user information parameter in the ANM Ensure that the SUT if the 200 OK INVITE contains a User-to-User header, a User-to-user information parameter is included in the ANM and the User-to-user information is derived from the uuidata component. User-to-User header starts with the first octet being the protocol discriminator and followed by the user information octets SIP Parameter values: 200: User-to-User: uuidata derived from the User-to-user information (PIXIT) ISUP Parameter values: ANM: User-to-user information Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL BYE RLC   200 OK BYE TP610019 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.3.5.2.5.2.1 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: Test purpose: User-to-user service 1 implicit response is mapped in the User-to-user information parameter in the REL Ensure that the SUT if the BYE contains a User-to-User header, a User-to-user information parameter is included in the REL and the User-to-user information is derived from the uuidata component. User-to-User header starts with the first octet being the protocol discriminator and followed by the user information octets SIP Parameter values: BYE: User-to-User: uuidata derived from the User-to-user information (PIXIT) ISUP Parameter values: REL: User-to-user information Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation REL   BYE RLC 200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 377
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.11 Explicit call transfer (ECT)
TP611001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: ISUP-SIP/SS/ECT/ SIP selection criteria: ISUP selection criteria: PICS 12/1 AND NOT PICS 13/3 Test purpose: Loop prevention procedure supported, interworking of "call transfer" indication not supported Ensure that the SUT if a LOP(request) is received returns a LOP (response) with the indication "insufficient information" continue without disrupting the SIP signalling procedure. Ensure that the SUT if a FAC is received continue without disrupting the SIP signalling procedure. SIP Parameter values: No mapping ISUP Parameter values: LOP: Response "insufficient information" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation LOP LOP  FAC(Call transfer active) Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 378 TP611002 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: ISUP-SIP/SS/ECT/ SIP selection criteria: ISUP selection criteria: NOT PICS 12/1 AND NOT PICS 13/3 Test purpose: Loop prevention procedure not supported, interworking of "call transfer" indication not supported Ensure that the SUT if a LOP(request) is received and the loop prevention procedure is not supported continue without disrupting the SIP signalling procedure. Ensure that the SUT if a FAC is received continue without disrupting the SIP signalling procedure. SIP Parameter values: No mapping ISUP Parameter values: Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation LOP FAC(Call transfer active) Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 379 TP611003 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: ISUP-SIP/SS/ECT/ SIP selection criteria: ISUP selection criteria: PICS 12/1 AND PICS 13/3 Test purpose: Loop prevention procedure supported, interworking of "call transfer" indication in FAC supported Ensure that the SUT if a LOP(request) is received returns a LOP (response) with the indication "insufficient information" continue without disrupting the SIP signalling procedure. Ensure that the SUT if a FAC is received an INVITE is sent and the SDP contains an a-line set to "sendrecv". SIP Parameter values: Re-INVITE SDP a=sendrecv ISUP Parameter values: LOP: Response "insufficient information" FAC: Generic notification = "call transfer, active" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(hold) INVITE(sendonly)  200 OK INVITE(recvonly) ACK LOP LOP  FAC(Call transfer, active) INVITE(sendrecv)  200 OK INVITE(sendrecv) ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 380 TP611004 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: ISUP-SIP/SS/ECT/ SIP selection criteria: ISUP selection criteria: NOT PICS 12/1 AND PICS 13/3 Test purpose: Loop prevention procedure not supported, interworking of "call transfer" indication in FAC supported Ensure that the SUT if a LOP(request) is received and the loop prevention procedure is not supported continue without disrupting the SIP signalling procedure. Ensure that the SUT if a FAC is received an INVITE is sent and the SDP contains an a-line set to "sendrecv". SIP Parameter values: Re-INVITE SDP a=sendrecv ISUP Parameter values: FAC: Generic notification = "call transfer, active" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(hold) INVITE(sendonly)  200 OK INVITE(recvonly) ACK LOP FAC(Call transfer active) INVITE(sendrecv)  200 OK INVITE(sendrecv) ACK Conversation REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 381 TP611005 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: ISUP-SIP/SS/ECT/ SIP selection criteria: ISUP selection criteria: PICS 13/3 Test purpose: Interworking of "call transfer" indication in CPG supported Ensure that the SUT if a CPG Generic notification "call transfer, active" is received an INVITE is sent and the SDP contains an a-line set to "sendrecv". SIP Parameter values: Re-INVITE SDP a=sendrecv ISUP Parameter values: CPG: Generic notification = "call transfer, active" Comments: ISUP/BICC SUT SIP IAM INVITE ACM   180 Ringing Ringing tone ANM   200 OK INVITE ACK Conversation CPG(hold) INVITE(sendonly)  200 OK INVITE(recvonly) ACK LOP CPG(Call transfer active) INVITE(sendrecv)  200 OK INVITE(sendrecv) ACK Conversation REL BYE RLC   200 OK BYE
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.12 Anonymous Call Rejection (ACR)
TP612001 ACR-CB Reference: ES 283 027 [1], clause 4.7.1.3.1 Selection criteria: TSS reference: ISUP-SIP/SS/ACR Preconditions: Test purpose: Mapping of 433 Anonymity Disallowed to REL cause 24 Ensure that the 433 Anonymity Disallowed final response received to due the ACR service is mapped into a REL cause 24 "call rejected due to ACR supplementary service" SIP Parameter values: 433 Anonymity Disallowed ISUP Parameter values: REL cause value 24 "call rejected due to ACR supplementary service" Comments: ISUP MGCF SIP IAM INVITE  100 Trying REL(24)   433 Anonymity Disallowed RLC ACK ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 382 TP612002 ACR-CB Reference: ES 283 027 [1], clause 4.7.1.3.1 Selection criteria: TSS reference: ISUP-SIP/SS/ACR Preconditions: Test purpose: Mapping of 603 Decline to REL cause 21 Ensure that the 603 Decline final response received to due the ACR service is mapped into a REL cause 21 "call rejected" SIP Parameter values: 603 Decline ISUP Parameter values: REL cause value 21 "call rejected" Comments: ISUP MGCF SIP IAM INVITE  100 Trying REL(21)   603 Decline RLC ACK
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.13 Call waiting (CW)
FFS
f837441d0decd0bfe6419bfc72a0ce86
186 009-2
6.3.2.14 Malicious call identification (MCID)
TP614001 MCID Reference: clause 4.7.1.2 Selection criteria: PICS 1/6 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of XML mcid request (McidRequestIndicator) Ensure that the XML mcid McidRequestIndicator contained in a received INFO request mapped into the MCID request indicator requested in the sent IDR SIP Parameter values: INFO XML mcid request McidRequestIndicator = "1" ISUP Parameter values: IDR: MCID request indicator: MCID requested Comments: ISUP MGCF SIP IAM INVITE  100 Trying IDR(MCID request indicator)   INFO (XML mcid request) 200 OK INFO ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 383 TP614002 MCID Reference: clause 4.7.1.2 Selection criteria: PICS 1/6 AND PICS 1/7 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of XML mcid request (HoldingIndicator) Ensure that the XML mcid HoldingIndicator is mapped into the MCID request indicator holding requested in the sent IDR SIP Parameter values: INFO: XML mcid request HoldingIndicator = "1" ISUP Parameter values: IDR: Holding indicator (national use): holding requested Comments: ISUP MGCF SIP IAM INVITE  100 Trying IDR(MCID request indicator)   INFO (XML mcid request) 200 OK INFO ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE TP614003 MCID Reference: clause 4.7.1.2 Selection criteria: PICS 1/6 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of IRS (McidResponseIndicator) Ensure that MCID response indicator provided, contained in an IRS is mapped into the XML mcid response McidResponseIndicator. SIP Parameter values: INFO: XML mcid request McidRequestIndicator = "1" INFO: XML mcid response McidResponseIndicator = "1" ISUP Parameter values: IDR: MCID request indicator: MCID requested IRS: MCID response indicator: MCID provided Comments: ISUP MGCF SIP IAM INVITE  100 Trying IDR(MCID request indicator)   INFO (XML mcid request) 200 OK INFO IRS (MCID response indicator) INFO (XML mcid response)  200 OK INFO ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 384 TP614004 MCID Reference: clause 4.7.1.2 Selection criteria: PICS 1/6 AND NOT PICS 1/7 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of IRS (HoldingProvidedIndicator) Ensure that MCID response indicator holding provided, contained in an IRS is mapped into the XML mcid response HoldingProvidedIndicator. SIP Parameter values: INFO: XML mcid request HoldingIndicator = "1" INFO: XML mcid response HoldingProvidedIndicator = "0" ISUP Parameter values: IDR: Holding indicator (national use): IRS: Hold provided indicator (national use) Comments: ISUP MGCF SIP IAM INVITE  100 Trying IDR(MCID request indicator)   INFO (XML mcid request) 200 OK INFO IRS (no MCID response indicator) INFO (XML mcid response)  200 OK INFO ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 385 TP614005 MCID Reference: clause 4.7.1.2 Selection criteria: PICS 1/6 AND PICS 1/7 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of IRS (HoldingProvidedIndicator) Ensure that MCID response indicator holding provided, contained in an IRS is mapped into the XML mcid response HoldingProvidedIndicator (Holding indicator is not for national use). SIP Parameter values: INFO: XML mcid request HoldingIndicator = "1" INFO: XML mcid response HoldingProvidedIndicator = "1" ISUP Parameter values: IDR: Holding indicator: holding requested IRS: Hold provided indicator holding provided Comments: ISUP MGCF SIP IAM INVITE  100 Trying IDR(MCID request indicator)   INFO (XML mcid request) 200 OK INFO IRS (no MCID response indicator) INFO (XML mcid response)  200 OK INFO ACM   180 Ringing ANM   200 OK INVITE ACK Communication REL BYE RLC   200 OK BYE ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 386 Annex A (informative): Bibliography • ITU-T Recommendation Q.731.7 (1997): "Stage 3 description for number identification supplementary services using Signalling System No. 7: Malicious call identification (MCID)". • ITU-T Recommendation Q.732.2 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call diversion services: "Call Forwarding Busy (CFB)". • ITU-T Recommendation Q.732.3 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding No Reply (CFNR)". • ITU-T Recommendation Q.732.4 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding Unconditional (CFU)". • ITU-T Recommendation Q.732.5 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Deflection (CD)". • ITU-T Recommendation Q.732.7 (1996): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Explicit Call Transfer". • ITU-T Recommendation Q.733.1 (1992): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call waiting (CW)". • ITU-T Recommendation Q.733.2 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call hold (HOLD)". • ITU-T Recommendation Q.733.3 (1997): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls to busy subscriber (CCBS)". • ITU-T Recommendation Q.733.4 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Terminal portability (TP)". • ITU-T Recommendation Q.733.5 (1999): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls on no reply". • ITU-T Recommendation Q.735.1 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Closed user group (CUG)". • ITU-T Recommendation Q.735.3 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Multi-level precedence and pre-emption". • ITU-T Recommendation Q.735.6 (1996): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Global Virtual Network Service (GVNS)". • ITU-T Recommendation Q.736.1 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: International Telecommunication Charge Card (ITCC)". • ITU-T Recommendation Q.736.3 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: Reverse charging (REV)". • ITU-T Recommendations Q.1902.1 to Q.1902.4 (2001): "Bearer Independent Call Control Protocol (BICC)". • IETF RFC 3267: "Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". • IETF RFC 2046 (1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". • IETF RFC 2327 (1998): "SDP: Session Description Protocol". • IETF RFC 2806 (2000): "URLs for Telephone Calls". ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 387 • IETF RFC 3204 (2001): "MIME media types for ISUP and QSIG Objects". • IETF RFC 3262 (2002): "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". • IETF RFC 3311 (2002): "The Session Initiation Protocol UPDATE Method". • IETF RFC 3323 (2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)". • IETF RFC 3326 (2002): "The Reason Header Field for the Session Initiation Protocol". • ISO/IEC 9646-2 (1994): "Conformance testing methodology and framework - Part 2: Abstract Test Suite Specification". • ISO/IEC 9646-3/DAM 1 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation; Amendment 1: TTCN extensions". • ISO/IEC 9646-5 (1994): "Conformance testing methodology and framework - Part 5: Requirements on test laboratories and clients for the conformance assessment process". ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 388 History Document history V2.1.1 March 2009 Publication V2.2.1 March 2011 Publication
ce6ebf51ec076d886e2cd294039516a9
186 008-1
1 Scope
The present document describes the performance benchmark methology for the IMS based services MMTel, Video Telephony and IMS - PES. The terminology and concepts are described in TR 101 577 [i.11]. The present document is the first part of the multi-part deliverable which consists of four parts. The present document contains the overall benchmark descriptions, architectures, processes, and information models that are common to all specific benchmarking scenarios. TS 186 008-2 [i.1] contains the specific benchmarking use-cases and scenarios, along with scenario specific metrics and design objectives. It also defines the SUT configuration parameters. This part also contains any required extensions to the overall descriptions present in the present document, if necessary for the specific scenario. TS 186 008-3 [i.2] defines an initial benchmark test through the specification of a traffic set, traffic-time profile and benchmark test procedure. TS 186 008-4 [i.3] defines Reference Load network quality parameters for the use cases defined in TS 186 008-2 [i.1].
ce6ebf51ec076d886e2cd294039516a9
186 008-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 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.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
2.1 Normative references
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 101 563 (V1.2.1): "Speech and multimedia Transmission Quality (STQ); IMS/PES exchange performance requirements". [2] ETSI TS 123 002 (V11.4.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 11.4.0 Release 11)".
ce6ebf51ec076d886e2cd294039516a9
186 008-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 186 008-2: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 2: Subsystem Configurations and Benchmarks". [i.2] ETSI TS 186 008-3: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 3: Traffic Sets and Traffic Profiles". [i.3] ETSI TS 186 008-4: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 4: Reference Load network quality parameters". [i.4] Recommendation ITU-T P.862: "Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs". ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 8 [i.5] Recommendation ITU-T P.862.1: "Mapping function for transforming P.862 raw result scores to MOS-LQO". [i.6] Recommendation ITU-T P.56: "Objective measurement of active speech level". [i.7] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifications (3GPP TR 21.905)". [i.8] Recommendation ITU-T P.863 (01/2011): "Perceptual objective listening quality assessment". [i.9] IEEE 802.16: "A Technical Overview of the WirelessMAN™Air Interface for Broadband Wireless Access". [i.10] IEEE 802.1, 802.1Q-2011: "IEEE Standard for Local and metropolitan area networks--Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks". [i.11] ETSI TR 101 577 (V1.1.1): "Methods for Testing and Specifications (MTS); Performance Testing of Distributed Systems; Concepts and Terminology". [i.12] IEEE 802.3: "Ethernet Working Group".
ce6ebf51ec076d886e2cd294039516a9
186 008-1
3 Definitions and abbreviations
ce6ebf51ec076d886e2cd294039516a9
186 008-1
3.1 Definitions
The IMS benchmarking definitions are described in TR 101 577 [i.11]. For the purposes of the present document, the following terms and definitions apply: background load: workload applied to an SUT during a benchmark test, for the purpose of consuming SUT resources during a benchmark test and changing the traffic intensity at which the capacity of the SUT is reached benchmark report: document generated at the conclusion of a test procedure containing the metrics measured during the execution of the test and/or computed from the data collected in the benchmark log benchmark test: procedure by which a test system interacts with a System Under Test to measure its behaviour and produce a benchmark report configuration: specification of a subset of IMS/PES architectural elements and metrics for which collection of benchmark tests can be defined design objective: probabilistic model of delay and failure requirements for SUT, associated with a use-case, specified by threshold values and probabilities for delay and scenario failure Design Objective Capacity (DOC): largest load an SUT can sustain while not exceeding design objectives defined for a use-case idle load: load that is not dependent on the traffic or other external activities maximum capacity: maximum processor load that a processor can handle without rejecting new calls metric: performance measurement of SUT reported in a benchmark report parameter: attribute of a SUT, test system, system load, or traffic set whose value is set externally and prior to a benchmark test, and whose value affects the behaviour of the benchmark test processor load: part of time the processor executes work, normally expressed in percent NOTE: The processor load consists of Idle load, Traffic load and Usage load. Reference Call (RC): basic ISUP to ISUP call connected through two MGW in the same MGC domain ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 9 SAPS increase amount: increment by which the average SAPS changes between steps of a profile test parameters: parameters whose values determine the behaviour of a benchmark test test procedure: specification of the steps to be performed by a benchmark test test scenario: specific path through a use-case, whose implementation by a test system creates a system load test system: collection of hardware and software which presents a system load to a system under test and collects data on the system under test's performance, from which metrics can be computed traffic load: load that results from handling traffic events that are directly related to calls NOTE: This load varies with the traffic intensity. traffic-time profile: evolution of the average scenario over a time interval traffic set: mixture of traffic scenarios usage load: load that is reserved for the administrations operation and maintenance activities during busy hour workload: number of reference calls per second (RC/s) NOTE: It is calculated by multiplying calls per second by its corresponding WLF. workload factor (WLF): traffic load for different types of calls in relation to the traffic load of the reference call (ISUP call)
ce6ebf51ec076d886e2cd294039516a9
186 008-1
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 121 905 [i.7] and the following apply: AGCF Access Gateway Control Function ATCA Advanced Telecom Architecture BYE BYE message CDMA Code Division Multiple Access CN Core Network CPU Central Processor Unit CS Circuit Switched DO Design Objective DOC Design Objective Capacity ETH Ethernet GSM Global System for Mobile Communications II NNI Inter-IMS Network to Network Interface IM IPMultimedia IMS IP Multimedia Subsystem IP Internet Protocol ISC S-CSCF – Application Server (ISC) interface ISDN Integrated Service Digital Network ISUP ISDN User Part ITU-T ITU's Telecommunication Standardization Sector JAIN Java APIs for Integrated Networks LAN Local Area Network MGW Media Gateway MHT Mean Holding Time MMTel Multi-MediaTelephony NGN Next Generation Networks NNI Network Network Interface OMG Object Management Group PCI Peripheral Component Interconnect Express PES PSTN Emulation Solution PESQ PESQ, Perceptual Evaluation of Speech Quality POLQA Perceptual Objective Listening Quality Assessment POTS Plain old telephone service ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 10 RC Reference Call SAF Service Availability Forum SAPS Session Attempts Per Second SIGTRAN Steam Control Transmission Protocol SIP Session Initiation Protocol SIP-I SIP-I define a mapping from SIP to ISUP SP Service Provider SUA SCCP-User Adaptation Layer SUT System Under Test TA Tones and Announcement TDM Time-division multiplexing TEMs Telecom Equipment Manufacturers TR Technical Report UDI Unrestricted Digital Information UDI/TA Unrestricted Digital Information with tones and announcements UE User Equipment UMTS Universal Mobile Telecommunications System WLAN Wireless Local Area Network WLF Work load factor
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4 Benchmark information model
In this clause, "benchmark information model" refers to the structure of the information elements that define the benchmark. This information model is depicted in figure 2. The information model consists of three primary elements: use-cases, which describe the behaviour of an individual user, and which in turn define scenarios; benchmark tests, which generate a workload by aggregating the behaviour of individual scenarios in a controlled manner, and collect log files of measurements during the test; and benchmark test reports, which report metrics interpreted from the benchmark test log files. ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 11 Figure 2: IMS benchmark information model
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.1 Use-case
The top level of the individual behavioural model is the use-case. A use-case describes the goal that a user has in interacting with a system, the various actors (e.g. other users, network elements) that participate in the use-case, the basic course of events that are carried out by the user and the SUT, the design objective of the use-case, the possible outcomes that apply to the use-case, and the metrics to be collected. The goal and actors of a use-case are documented in narrative text and diagrams; the other elements are complex information elements, which are described in their respective clauses.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.1.1 Call Flow
The calls flows define the characteristic message flows, the tones and announcement for a specific interface.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.1.2 Load Profile
To facilitate the calculation of processing capacity and the appropriate load profile the concept of workload factor has been defined based on the reference call for each combination of traffic case and traffic signalling interface. The reference call (RC) is defined as a basic ISUP to ISUP call connected through two MGW in the same domain. Based on the workload factors for all different types of calls, the call intensities and the services used, one can express the total traffic load in an equivalent number of reference calls per second. ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 12 The dimensioning of any type of network depends on a number of different parameters such as utilization per channel, calls per second, mean holding time, type of accesses being involved, and type of services being requested.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.1.3 Metrics
The metrics of a use-case describe the measurements collected from the execution of a scenario attempt. Typical metrics include response times and message rates. If a scenario is selected for execution in a benchmark test, its metrics are collected. See clause 7 for more detail.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.1.4 Use-case outcomes
A use-case outcome is a set of possible outcomes of the scenarios of a use-case. An outcome may be simply "correct", it may reflect an error or failure condition; or it may reflect a correct behaviour that took an excessive amount of time to occur. An instance of a scenario that experiences an error, failure, or timeout outcome is referred to as an inadequately handled scenario attempt.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.1.5 Scenarios and scenario attempts
A scenario is a trace of a path through a use-case. It is analogous to "call attempt", but applies to all interactions within an IMS/PES network, different Bearer, and application interactions. A scenario may succeed, fail, or succeed functionally. The terms "scenario attempt" and "scenario attempts per second" are used in the present document in place of "call attempt" and "call attempts per second" because IMS is a transaction-oriented system with transactions of a variety of types Traffic sets, and indeed the real world, do not operate according to only one transaction type, so the more generalized term is necessary. It would be incorrect and misleading to attempt to report the capacity of a system in "call attempts per second", "registration attempts per second", etc., for system loads that were other than purely call attempts, registration attempts, etc.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.1.6 Design Objective (DO)
The Design Objective (DO) describes the maximal acceptable rate handled scenario attempts for a use-case.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.1.7 Scenario
A scenario describes a single interaction sequence among the actors of a use-case. It is documented by a set of preconditions on its actors (typically specified by parameter values). In case of IMS/PES the scenario is defined as a set of different Bearer Capabilities (e.g. speech, 3,1 kHz audio, UDI, UDI/TA), services (fax, modem) or dial mode.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.2 Benchmark test
A benchmark by definition measures the behaviour of a population of users. To accomplish this, the behaviours of individual users shall be aggregated into input traffic to the SUT. The input traffic shall be realistic, in the sense that a population of users would perform such actions in the real world, and in the sense that statistical variation in user behaviour is similar to statistical variation that would occur in the real world.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.2.1 Traffic set
The traffic set is a collection of scenarios which are determined to be likely to co-occur in a real-world scenario. The scenarios do not need to come from the same use-case. Within a traffic set, each scenario has an associated relative occurrence frequency, interpreted as the probability with which it would occur in the course of the test procedure. ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 13
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.2.2 Background load
Background load is a workload presented to the SUT in order to consume its resources. It may consist of a stream of traffic presented to the SUT by an external system apart from the test system; or it may be a workload presented to the processing elements, network, or storage subsystem of the SUT. The purpose of background traffic is to make possible the measurement of a design objective capacity in SUT when the capacity of the test system is insufficient to reach the design objective capacity. If a benchmark test is published in which background load is used, then the following requirements apply: • The hardware used to generate the background load shall be fully specified. If the background load is generated by software running directly on the SUT, then the components of the SUT on which the background load is executed shall be fully specified. • The software used to generate the background load shall be provided in source form, including make files and any other configuration files required to compile the software.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.2.3 Traffic-time profile
The traffic-time profile is a function describing the average scenario attempt arrival rate as a function of elapsed time during a benchmark test. A traffic-time profile should be chosen in such a manner that, for a given scenario attempt arrival rate, sufficient samples are generated that metrics can be collected with an appropriate confidence bound. Following Call Profiler Traffic Patterns are used today: Saw Tooth Blast Ramp Steady Call Rate Rolling Blast Poisson Distribution. To get a realistic scenario a combination of at least two scenarios is needed.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.2.4 Test parameters
The benchmark test parameters are used to control the behaviour of the test script. The data elements required to configure the test system are listed in table 1. Table 1 is a non-exhaustive list of test parameters defined for the benchmark standard. The list is expected to grow over time, as additional subsystems and system configurations are developed. ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 14 Table 1: Test parameters Parameter Description Start time Amount of time that a system load is presented to a SUT at the start of a test Stop time Amount of time that a system load is presented to a SUT at the end of a test TotalProvisionedSubscribers The number of simulated subscribers provisioned in the network PercentSimulatedSubscriber The average percentage of simulated subscribers Simulated Maximum simultaneous call legs The number of simulated Maximum simultaneous call legs Traffic per subscriber Traffic per subscriber; default value 0,1 Erlang PX_PercentRegisteredSubscribers The average percentage of simulated subscribers that are registered simultaneously. PX_PercentRoamingSubscribers The average percentage of simulated subscribers that are roaming (i.e. register in a non-local network). PX_Simulated Subscriber Registration Parameters Parameters and distributions of the probabilistic model of simulated subscriber operation MHT Mean Holding Time of a call ; default value 110 seconds Ringing time Duration between (180 ringing and 200 OK INVITE ) Default value 1 s to 5 s NoS number of subscribers originating traffic per subscriber CAPS/BHCA Call attempts per second/busy hour call attempts WLF for Call Controller The workload factor for Call Controller for specific configuration. Default value 1 to 3 WLF for Gateway Controller The workload factor for Gateway Controller for specific configuration. Default value 1 to 3 WLF for MGW The workload factor for Media Gateways for specific configuration. Default value 1 to 3 TDM Trunks Number of TDM trunks ETH Number of ETH Connections Type of call MMTel to MMTel Video Telephony IMS-PES to IMS-PES MMTel to IMS-PES Protocol call type and interfaces SIP-I ISUP SIGTRAN (M2PA; M2UA; M3UA; SUA) SIP II NNI (Ici,Izi) SIP NNI (Mx Interface) Gm Interface MGCF/MGW/I-BCF/TrMGW performance tests SIP-I to SIP-I SIP-I to ISUP SIP-I to NNI NNI to NNI SIGTRAN to SIGTRAN (M2PA; M2UA; M3UA; SUA) ISUP (SIGTRAN) to NNI Transport Interfaces Voice over LTE (VoLTE) (LTE-Uu, S1-U, S-11, S6a, S11, S5/S8, Rx, Gx, Mw, ISC and Ut interfaces) Ethernet xDSL ISDN POTS (Z)
ce6ebf51ec076d886e2cd294039516a9
186 008-1
4.3 Benchmark report
A test report is a document, with accompanying data files, that provides a full description of an execution of a benchmark test on a test system. The SUT and test system, as well as their parameters, are described in sufficient detail that an independent test site can replicate the test. The results of the test include data, represented as charts and data sets, depicting the behaviour of the SUT over the elapsed time of the test; reports of the relevant metrics that are conventionally used to compare benchmark results of differing SUTs; and a full description of other observations and exceptions noted during the test. ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 15
ce6ebf51ec076d886e2cd294039516a9
186 008-1
5 System Under Test (SUT)
The IMS performance benchmark covers benchmark tests for the MMTel, Video Telephony, and MMTel - IMS PES. Figure 3 depicts the IMS Reference Architecture. The components of the architecture are the primary building blocks, which are either defined by the IMS standard, or defined by external standards and referenced by IMS. The links between the primary building block represent reference points over which the building blocks communicate with each other. The reference architecture is a logical architecture; no mapping of functional elements to hardware or software component is mandated. And conversely, IMS products as deployed in the real world do not factor neatly into the elements of the reference architecture, which complicates the process of comparing similar products with a benchmark. The problem can be simplified by observing that there are classes of products which have common subsets of reference architecture elements. For classes defined in this manner, common sets of benchmarks can be defined. The classes defined in this manner are called IMS subsystems, or simply subsystems, and are expected to grow over time, as the IMS marketplace becomes richer. TS 186 008-2 [i.1] of this multi-part deliverable maintains a list and description of subsystems. In order to proceed from a subsystem description to a benchmark test, a complete description of all aspects of the subsystem relevant to the performance of the benchmark shall be present; this is referred to as the system configuration, or SUT configuration. This description starts with an enumeration of the elements of the reference architecture, and an enumeration of all reference points that are external to the subsystem (i.e. reference points between elements within the subsystem are "internal"). However, the configuration requires a specification of the hardware elements (e.g. servers, CPUs, network configuration and bandwidth) and software elements (e.g. operating system, database system), because even though the metrics reported by the benchmark tests are measured with respect to such metrics as total round-trip delay of messages and system capacity, the behaviour of IMS systems is still an area of study and a thorough understanding of how CPU and network bandwidth utilization behaves during operation is of interest. • Figure 4 depicts the Inter-IMS Network to Network Interface between two IM CN subsystem networks. • Figure 5 depicts the IMS/LTE Basic Configuration. • Figure 6 depicts the LTE End - to - End Configuration. • Figure 7 depicts the AGCF/VGW session processing model for IMS PES. ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 16 E-CSCF P-CSCF S-CSCF MGCF HSS Cx IP Multimedia Networks IMS- MGW CS Network Mn Mb Mg Mm MRFP Mb Mr Mb Legacy mobile signalling Networks I-CSCF Mw Mw Gm BGCF Mj Mi BGCF Mk Mk C, D, Gc, Gr UE Mb Mb Mb MRFC SLF Dx Mp CS CS Rx Mm LRF Ml Le BGCF Mi LCS Client Cx Dx Sh Ut Mw ISC IBCF Mx Mx Mx Ma Dh TrGW Izi Ici, Mm Ix Mg MRB ISC Cr Rc I4 AS EATF Mx Legend: Bold lines: interfaces supporting user traffic; Dashed lines: interfaces supporting only signalling. NOTE 1: The reference point CS (Circuit Switched) is not specified in the present document. NOTE 2: The reference point I5 is not shown in this figure. Figure 3: Overview of IMS Functional Entities [2] ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 17 IM CN subsystem network A IM CN subsystem network B Ici Izi II-NNI Mx Ix Mx Mx Mx TrGW Ix Mx TrGW IBCF S-CSCF I-CSCF P-CSCF S-CSCF I-CSCF MSC Server enhanced for ICS or SRVCC Mx IBCF Signalling Bearer ATCF Mx ATCF Mx MSC Server enhanced for ICS or SRVCC P-CSCF Mx Mx Mx Mx BGCF BGCF NOTE: Interface (II-NNI) between two IM CN subsystem networks. Figure 4: Inter-IMS Network to Network Interface between two IM CN subsystem networks Figure 5: IMS/LTE Basic Configuration ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 18 IMS UA MME S-GW HSS P-CSCF IMS-ALG IMS-AGW P-GW V-PCRF UE eNodeB IMS Core LTE-Uu S11 S5 SGi LTE-Uu I/S-CSCF Sh I S C Cx Ut Ut VPLMN HPLMN H-PCRF Mx IMS UA UE Diameter Agent Diameter Agent S6a S9 S9 S6a Diameter App ID = 0 IBCF/TRGW Ici/Izi eNodeB MME S-GW P-GW S5 S6a P-CSCF/ IMS-ALG/ IMS-AGW SGi Rx Mw S1-MME S1-U Sec- GW S11 Gx Gx Rx S1-MME S1-U Sec- GW Rx Rx Gx Gx Cx Sh MMTel / RCS Application Servers IPX IBCF/TrGw Mx Ici/Izi ENUM Server ENUM ENUM MRF Mr’ Mr MRFP Mb Mb ENUM Mb Gm Figure 6: LTE End - to - End Configuration MGC SIP UA MGF MGF VGW AGCF RTP FM SIP UA FM MGC S-CSCF S-CSCF AS AS P-CSCF Figure 7: AGCF/VGW session processing models ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 19
ce6ebf51ec076d886e2cd294039516a9
186 008-1
5.1 Creation of subscriber data base
The subscriber data base is the data-set required to configure the SUT in order to execute a benchmark test. Using the same data, the test system should be able to generate correct traffic. The present document does not try to specify a complete set, but rather just the subset that will ensure comparable results. All other provisioning information required for correct configuration of a SUT is to be set at the discretion of the SUT provider. One requirement for a fair benchmark is that the input data is similar for all test-runs. In order for this to happen we have two choices: a) Provide data base for the subscriber base. However, because we have to ensure scalability for the benchmark, this solution is not feasible. b) Provide rules to generate this data and data generators. Algorithms using random generators will be avoided for data that could possibly influence the results.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
6 Test system
The test system is used to generate the appropriate load on the SUT. The present document does not mandate any specific test system to be used, although the details of the test system shall be reported in the benchmark report. The test system should have two main functions: • Traffic generation: the test system shall be able to execute use-cases' scenarios following the traffic-time profile. It shall also be able to reproduce the appropriate traffic set (a mix of scenarios with a weight for each of them). • Network emulation: optionally, network characteristics on the different interfaces should be emulated by the test system.
ce6ebf51ec076d886e2cd294039516a9
186 008-1
7 Benchmark metrics examples
The metrics reported by a benchmark test is measured in real time during the execution of the test, or may be computed after completion of the test from event logs collected during the execution. Enclosed is a benchmark matrix based on the TS 101 563 [1]. ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 20 Table 2: Benchmark metrics examples Selay parameters Description Call request delay Call request delay is defined as the interval from the instant at which the INVITE message has been received from the SIP subscriber until the 100 Trying from the SBC/P-CSCF is passed back to the subscriber. Alerting sending Call request delay is defined as the interval from the instant at which the 180 Ringing is received from the terminating subscriber until the 180 Ringing is passed back to the originating subscriber. Call set up delay The time interval starts when the digit collection function determines that the address information received in the INFO or subsequent INVITE message is sufficient for session initiation, and ends when the INVITE message on the Ic or terminating Gm interface has been sent. Through-connection delay The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating Gm interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating Gm interface. Connection release delay Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating Gm interface until the instant when 200 OK is sent and a corresponding BYE message is sent at the terminating or originating Gm interface respectively. Speech quality analysis Speech Quality PESQ (Recommendation ITU-T P.862 [i.4]) and Recommendation ITU-T P.862.1 [i.5]. P.863 POLQA "Perceptual objective listening quality assessment" (Recommendation ITU-T P.863 [i.8]) Speech Level - Active Level Recommendation ITU-T P.56 [i.6]. Speech Level - Peak Speech Level - Noise Speech Level - Signal to Interval Noise ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 21 History Document history V1.1.1 October 2007 Publication V1.2.1 November 2012 Publication V1.2.2 June 2013 Publication
bdb476a5c99a057a039583429b41eaf8
185 010
1 Scope
The present document describes the protocols used for the reference points internal to the Customer Premises Network (CPN), between the Customer Network Gateway (CNG) and the Customer Network Devices (CNDs). This description is based on the architecture and stage 2 information flows contained in TS 185 003 [1] and TS 185 006 [2]. The reference points between the IPTV CND [3] and the CNG are not covered by the present document. These reference points are detailed in TS 185 011 [12].
bdb476a5c99a057a039583429b41eaf8
185 010
2 References
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. 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.
bdb476a5c99a057a039583429b41eaf8
185 010
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 185 003 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Customer Network Gateway Architecture and Reference Points". NOTE: The latest version in the V2.y.z series applies. [2] ETSI TS 185 006 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Customer Devices architecture and Reference Points". NOTE: The latest version in the V2.y.z series applies. [3] draft-saito-mmusic-sdp-ike-03 (July 27 2008): "Media Description for IKE in the Session Description Protocol (SDP)". [4] IETF RFC 3261: "SIP: Session Initiation Protocol". [5] ETSI ES 283 003 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". NOTE: The latest version in the V2.y.z series applies. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 8 [6] UPnP™: "UPnP™ Device Architecture 1.0 (24 April 2008)". NOTE: Available at http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf. [7] UPnP™: "MediaServer:3 Device Template Version 1.01 (30 September 2008)". NOTE: Available at http://www.upnp.org/specs/av/UPnP-av-MediaServer-v3-Device.pdf. [8] ETSI TS 124 504 (V8.4.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification (3GPP TS 24.504 version 8.4.0 Release 8)". [9] ETSI TS 124 411 (V8.1.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification (3GPP TS 24.411 version 8.1.0 Release 8)". [10] ETSI TS 124 529 (V8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification (3GPP TS 24.529 version 8.0.0 Release 8)". [11] ETSI TS 124 410 (V8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; NGN Signalling Control Protocol; Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification (3GPP TS 24.410 version 8.0.0 Release 8)". [12] ETSI TS 185 011 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Specification of Protocols for Customer Network Devices enabling the IMS-based IPTV service usage". NOTE: The latest version in the V2.y.z series applies. [13] ETSI TS 124 406 (V8.0.0) : "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification (3GPP TS 24.406 version 8.0.0 Release 8)". [14] IETF RFC 4572: "Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)". [15] ETSI TS 183 006 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification". NOTE: The latest version in the V2.y.z series applies. [16] ETSI ES 283 030 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service Capability; Protocol Specification [3GPP TS 24.141 V7.0.0, modified and OMA-TS-Presence_SIMPLE-V1_0, modified]". NOTE: The latest version in the V2.y.z series applies. [17] IETF RFC 2833: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". [18] IETF RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)". [19] ETSI TS 124 508 (V8.1.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification (3GPP TS 24.508 version 8.1.0 Release 8)". ETSI ETSI TS 185 010 V2.1.1 (2009-07) 9 [20] ETSI TS 124 229 (V7.9.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 7.9.0 Release 7)". [21] ETSI TS 183 065 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networks(TISPAN); Customer Network Gateway Configuration Function; e3 Interface based upon CWMP". NOTE: The latest version in the V2.y.z series applies. [22] ETSI TS 124 503 (V8.4.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified] (3GPP TS 24.503 version 8.4.0 Release 8)". [23] IETF RFC 2131: "Dynamic Host Configuration Protocol". [24] ETSI TS 183 019 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment; User-Network Interface Protocol Definitions". NOTE: The latest version in the V2.y.z series applies. [25] Broadband Forum TR-069 Amendment 2: "CPE WAN Management Protocol v1.1"; Release 3; December 2007. [26] Broadband Forum TR-098 Amendment 2: "Internet Gateway Device Data Model for TR-069"; Release 3; September 2008. [27] ETSI TS 124 407 (V 8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification (3GPP TS 24.407 version 8.0.0 Release 8)". [28] IEEE 802.1X: "IEEE Standard for Local and metropolitan area networks - Port-Based Network Access Control". [29] IETF RFC 3748: "The Extensible Authentication Protocol (EAP) specification". [30] Wi-Fi Alliance: "WPA (includes WPA2) Pointer Document, version 3.0". NOTE: Available at http://www.wi-fi.org. [31] IEEE 802.11i (2004): "Enhanced security". [32] Wi-Fi Alliance: "Wi-Fi Protected Setup Specification, version 1.0". NOTE: Available at http://www.wi-fi.org. [33] ETSI TS 183 041 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3: Protocol specifications [Endorsement of 3GPP TS 24.247 Release 6". NOTE: the latest version in the V2.y.z series applies. [34] ETSI TS 183 005 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Conference (CONF); Protocol specification". NOTE: The latest version in the V2.y.z series applies. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 10 [35] ETSI TS 183 016 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol Specification". NOTE: The latest version in the V2.y.z series applies. [36] ETSI TS 183 008 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification". NOTE: The latest version in the V2.y.z series applies. [37] ETSI TS 124 238: "Universal Mobile Telecommunications System (UMTS); LTE; Session Initiation Protocol (SIP) based user configuration; Stage 3 (3GPP TS 24.238 version 8.1.0 Release 8)". [38] IETF RFC 4244: "An extension to the Session Initiation Protocol (SIP) for Request History Information". [39] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". [40] ETSI TS 183 047 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN IMS Supplementary Services; Advice Of Charge (AOC)". NOTE: The latest version in the V2.y.z series applies. [41] ETSI TS 183 054 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Protocol specification Closed User Group (CUG)". NOTE: The latest version in the V2.y.z series applies. [42] ETSI TS 183 051 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Support of SMS and MMS over NGN IMS subsystem; Stage 3 [Endorsement of 3GPP TS 24.341 Release 7". NOTE: The latest version in the V2.y.z series applies. [43] ETSI TS 183 007 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification". NOTE: The latest version in the V2.y.z series applies. [44] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging". [45] IETF RFC 3994: "Indication of Message Composition for Instant Messaging". [46] IETF RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)". [47] IETF RFC 3265: "Session Initiation Protocol (SIP) - Specific Event Notification". [48] IETF RFC 3515: "The Session Initiation Protocol (SIP) REFER Method". [49] IETF RFC 3891: "The Session Initiation Protocol (SIP) Referred-By Mechanism". [50] IETF RFC 3892: "The Session Initiation Protocol (SIP) "Replaces" Header". [51] ETSI TS 183 028 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Common Basic Communication procedures; Protocol specification". NOTE: The latest version in the V2.y.z series applies. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 11 [52] ETSI TS 183 004 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification". NOTE: The latest version in the V2.y.z series applies. [53] ETSI TS 183 011 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification". NOTE: The latest version in the V2.y.z series applies. [54] ETSI TS 183 029 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification". NOTE: The latest version in the V2.y.z series applies. [55] ETSI TS 183 010 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Signalling Control Protocol; Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification". NOTE: The latest version in the V2.y.z series applies. [56] UPnP™: "MediaRenderer:2 Device Template Version 1.01 (30 September 2008)". NOTE: Available at http://www.upnp.org/specs/av/UPnP-av-MediaRenderer-v2-Device.pdf. [57] UPnP™: "AVTransport:2 Service Template Version 1.01 (30 September 2008)". NOTE: Available at http://www.upnp.org/specs/av/UPnP-av-AVTransport-v2-Service.pdf. [58] UPnP™: "ContentDirectory:3 Service Template Version 1.01 (30 September 2008)". NOTE: Available at http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v3-Service.pdf. [59] UPnP™: "ScheduledRecording:2 Service Template Version 1.01 (30 September 2008)". NOTE: Available at http://www.upnp.org/specs/av/UPnP-av-ScheduledRecording-v2-Service.pdf. [60] ETSI ES 282 003 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". NOTE: The latest version in the V2.y.z series applies. [61] 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 version 8.8.0 Release 8)". [62] Broadband Forum TR-104: "DSL Home™ Provisioning Parameters for VoIP CPE"; Release 1; September 2005. [63] Broadband Forum TR-106 Amendment 2: "Data Model Template for TR-069 Enabled Devices"; Release 3; November 2008. [64] Broadband Forum TR-135: "Data Model for TR-069 Enabled STB"; Release 3; December 2007. [65] Broadband Forum TR-140 Issue 1.1: "TR-069 Data Model for Storage Service Enabled Devices"; Release 3; December 2007. [66] IETF RFC 3193: "Securing L2TP using IPsec". [67] ETSI TS 124 505 (V 8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Conference (CONF); Protocol specification (3GPP TS 24.505 version 8.0.0 Release 8)". ETSI ETSI TS 185 010 V2.1.1 (2009-07) 12 [68] ETSI TS 124 516 (V 8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol specification (3GPP TS 24.516 version 8.0.0 Release 8)". [69] ETSI TS 124 447 (V 8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; NGN IMS Supplementary Services; Advice Of Charge (AOC) (3GPP TS 24.447 version 8.0.0 Release 8)". [70] ETSI TS 124 454 (V 8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Protocol specification Closed User Group (CUG) (3GPP TS 24.454 version 8.0.0 Release 8)". [71] ETSI TS 124 430 (V 8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; Presence Service Capability; Protocol Specification [3GPP TS 24.141 V7.0.0, modified and OMA-TS-Presence_SIMPLE-V1_0, modified] (3GPP TS 24.430 version 8.0.0 Release 8)". [72] ETSI TS 124 441: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3: Protocol specifications [Endorsement of 3GPP TS 24.247 Release 6] (3GPP TS 24.441 version 8.0.0 Release 8)". [73] ETSI TS 123 521 (V 8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Support of Short Message Service (SMS) over NGN IMS subsystem; Stage 2; [Endorsement of 3GPP TS 23.204 Release 7] (3GPP TS 23.521 version 8.0.0 Release 8)". [74] ETSI TS 124 628 (V 8.2.0): "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 version 8.2.0 Release 8)". [75] ETSI TS 124 604 (V 8.3.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 version 8.3.0 Release 8)". [76] ETSI TS 124 611 (V 8.2.0): "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 version 8.2.0 Release 8)". [77] ETSI TS 124 629 (V 8.2.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.629 version 8.2.0 Release 8)". [78] ETSI TS 124 610 (V 8.3.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610 version 8.3.0 Release 8)". [79] ETSI TS 124 605 (V 8.3.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 version 8.3.0 Release 8)". [80] ETSI TS 124 606 (V 8.1.0): "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 version 8.1.0 Release 8)". ETSI ETSI TS 185 010 V2.1.1 (2009-07) 13 [81] ETSI TS 124 607 (V 8.2.0): "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 version 8.2.0 Release 8)". [82] ETSI TS 124 608 (V 8.2.0): "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 version 8.2.0 Release 8)". [83] ETSI TS 124 616 (V 8.3.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Malicious Communication Identification (MCID)using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.616 version 8.3.0 Release 8)". [84] ETSI TS 124 647 (V 8.1.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.647 version 8.1.0 Release 8)". [85] ETSI TS 124 141 (V 8.3.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.141 version 8.3.0 Release 8)". [86] ETSI TS 124 247 (V 8.2.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.247 version 8.2.0 Release 8)". [87] ETSI TS 124 341 (V 8.1.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Support of SMS over IP networks; Stage 3 (3GPP TS 24.341 version 8.1.0 Release 8)". [88] 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 version 8.2.0 Release 8)".
bdb476a5c99a057a039583429b41eaf8
185 010
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] "UPnP Remote Access Transport Agent (RATA) Config:1 Service".
bdb476a5c99a057a039583429b41eaf8
185 010
3 Definitions and abbreviations
bdb476a5c99a057a039583429b41eaf8
185 010
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply: announcement: service related message sent to a user that can be of any type of media e.g. a voice message or a video-clip transfer target: party which the communication is transferred to and which replaces the transferor in the communication transferee: party which stays in the communication which is transferred ETSI ETSI TS 185 010 V2.1.1 (2009-07) 14 transferor: party that initiates the transfer of the active communication that it has with the transferee
bdb476a5c99a057a039583429b41eaf8
185 010
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply: 3DES-CBC 3'ple Data Encryption Standard - Cipher Block Chaining mode 3DES-CTR 3'ple Data Encryption Standard - CounTeR mode AC Access Controller ACL Access Control List ACR Anonymous Communication Rejection AES Advanced Encryption Standard AES-CBC Advanced Encryption Standard - Cipher Block Chaining mode AES-CTR Advanced Encryption Standard - CounTeR mode AKA Authentication and Key Agreement ALG Application Layer Gateway AP Access Point ASP Active Server Page(s) B2BUA Back-to-Back User Agent CCRP Compulsory Configuration Renewal Procedure CD Communication Deflection CDIVN Communication DIVersion Notification CFB Communication Forwarding on Busy user CFNL Communication Forwarding on Not Logged-in CFNR Communication Forwarding on No Reply CFNRc Communication Forwarding on subscriber Not Reachable CFU Communication Forwarding Unconditional CHAP Challenge Handshake Authentication Protocol CLI Customer Line Identifier CND Customer Network Device CND-AtF CND Attachment Function CNDCP CND Configuration Protocol CNG Customer Network Gateway CNG-AtF CNG-Attachment Function CNG-AuF CNG-Authentication Function CNGCF CNG Configuration Function CNG-NFF CNG-NAPT and Firewall Function CNG-PPF CNG-Plug and Play Function CPN Customer Premises Network CWMP CPE WAN Management Protocol DHCP Dynamic Host Configuration Protocol DPD Dead Peer Detection DTMF Dual-Tone Multi Frequency EAP Extensible Authentication Protocol ECT Explicit Communication Transfer FQDN Fully Qualified Domain Name HEX HEXadecimal HMAC Hash Message Authentication Code HTTP HyperText Transfer Protocol HTTPS HyperText Transfer Protocol Secure ICB Incoming Communication Barring ICSI IMS Communication Service Identifier ID IDentity IETF International Engineering Task Force IKE Internet Key Exchange IMPU IP Multimedia PUblic identity IMS IP Multimedia Subsystem IP Internet Protocol IPsec Internet Protocol secure transmission IPTV Internet Protocol TeleVision IPv6 Internet Protocol (version 6) ETSI ETSI TS 185 010 V2.1.1 (2009-07) 15 Kbps Kilo bits per second L2TP Layer 2 Tunnelling Protocol LAN Local Area Network MAC Media Access Control MIME Multipurpose Internet Mail Extensions MMS Multimedia Messaging Service MODP MODular exPonential Group MWI Message Waiting Indication NACF Network Access Configuration Function NAPT Network Address Port Translation NAT Network Address Translation NGN Next Generation Networks OCB Outgoing Communication Barring OIP Originating Identification Presentation OIR Originating Identification Restriction PBC Push Button Configuration P-CSCF Proxy Call Session Control Function PIN Personal Identification Number PPP Point to Point Protocol PPPoE Point-to-Point Protocol over Ethernet QoS Quality of Service RA Remote Access RAC Remote Access Client RACS Resource and Admission Control Subsystem RADA Remote Access Discovery Agent RAS Remote Access Server RATA Remote Access Transport Agent RBAC Role Based Access Control RPC Remote Procedure Call RSA Rivest-Shamir-Adleman encryption RTP Real-time Transport Protocol RTSP Real Time Streaming Protocol SDP Session Description Protocol SHA Secure Hash Algorithm SIP Session Initiation Protocol SIT SITuation SMS Short Message Service SSID Service Set IDentifier STB Set Top Box TIP Terminating Identification Presentation TIR Terminating Identification Restriction TISPAN Telecommunication and Internet converged Services and Protocols for Advanced Networking UA User Agent UAC User Agent Client UAS User Agent Server UDP Unicast Datagram Packet UE User Equipment UPnP™ Universal Plug and Play URI Uniform Resource Identifier URL Uniform Resource Locator URN Uniform Resource Name VoIP Voice over IP VPN Virtual Private Networks WAN Wide Area Network Wi-Fi Wireless Fidelity WPA Wi-Fi Protected Access XML eXtensible Markup Language ETSI ETSI TS 185 010 V2.1.1 (2009-07) 16
bdb476a5c99a057a039583429b41eaf8
185 010
4 Overview
The clause briefly describes applicability of the protocols discussed further in the present document to the reference points and functional entities defined in [1] and [2] as depicted in figure 4.1. The IMS CND functions are described within the TS 185 006 [2] dedicated to Customer Network Devices. Figure 4.1: Customer Network Device and Customer Network Gateway usage of the local reference points
bdb476a5c99a057a039583429b41eaf8
185 010
4.1 Protocols and Reference Points
The u reference point is described in clause 5. The C reference point is described in clause 6, detailing procedures based on UPnP™. The Gm' reference point is described in clause 7, detailing procedures based on SIP. The e3' reference point is described in clause 8, detailing procedures based on HTTP. The au reference point is described in clause 9, detailing procedures based on EAP. The e1' reference point is described in clause 10, detailing procedures based on DHCP.
bdb476a5c99a057a039583429b41eaf8
185 010
5 Procedures at the u Reference Point
NOTE: This clause is not elaborated in Release 2. Content intended for this clause is procedures based on HTTP, for example HTTP authentication and access control. Various methods for HTTP authentication will be elaborated and detailed. Examples of such authentication methods could be HTTP Cookie based authentication, HTTP Digest Authentication, HTTPS and/or HTTP Basic Authentication. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 17 Solutions for access control will be elaborated and detailed. Examples of such solutions might be Role Based Access Control and/or the usage of Blacklists.
bdb476a5c99a057a039583429b41eaf8
185 010
6 Procedures at the C Reference Point
6.1 Procedures for using UPnP™
bdb476a5c99a057a039583429b41eaf8
185 010
6.1.1 Remote Access Functions
Architectural information is found in clauses 7.4 of TS 185 003 [1] and 8.4 in TS 185 006 [2]. The definition of the protocols on the C reference point conforms to the UPnP™ architecture. Using the C reference point for Remote Access (RA) is described in the following clauses: device discovery in clause 6.1.1.1 and performing actions (Push, Pull, etc.) in clauses 6.1.1.2 to 5. NOTE: UPnP™ has defined architecture for UPnP™ Remote Access 1.0 including two entities called Remote Access Discovery Agent (RADA) and Remote Access Transport Agent (RATA). This is currently work in progress. RADA functionality is located in the CNG-PPF and RATA functionality is found in the CNG-SIP Proxy B2BUA. Both are detailed in TS 185 003 [1]. For the utilization of the C reference point for Remote Access the precondition of a tunnel setup shall be fulfilled. The tunnel setup is performed using SIP signalling procedures on the Gm reference point. Further on security negotiation may be performed. These procedures are described in annex A "Remote Access Procedures". The information regarding which CND or CND's that are registered within the home network (CPN) is discovered and maintained by RADA and is used to compile an Access Control List (ACL) managed by the CNG-SIP Proxy B2BUA. To support the Remote Access there are two possible alternatives: 1) The CNG-SIP Proxy B2BUA should implement the complete B2BUA sub-block as described in TS 185 003 [1]. This is described in the upper part of figure 6.1. 2) The CNG-SIP Proxy B2BUA should implement the SIP Proxy sub-block and additionally the NGN side SIP UA termination of the B2BUA sub-block. This is described in the lower part of figure 6.1. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 18 Gm CNG - SIP Proxy B2BUA CNG - SIP Proxy B2BUA SIP Registrar SIP/IMS adapter B2BUA SIP Proxy B2BUA (Remote Access NGN SIP UA termination) Gm NGN NGN Figure 6.1: Possible Remote Access implementation alternatives in the CNG-SIP Proxy B2BUA
bdb476a5c99a057a039583429b41eaf8
185 010
6.1.1.1 Device Discovery
The CNG-PPF collects available UPnP™ devices at a regular interval in accordance with UPnP™ Device Architecture 1.0 [6]. This is done using M-SEARCH and NOTIFY messages.
bdb476a5c99a057a039583429b41eaf8
185 010
6.1.1.2 Push of Content
Over the C reference point this is an UPnP™ AVTransport; Play (as specified in [57]) action, etc. on home device providing UPnP™ MediaServer [5].
bdb476a5c99a057a039583429b41eaf8
185 010
6.1.1.3 Pull of Content
Over the C reference point this is UPnP™ ContentDirectory; Browse (as specified in [58]) provided by the UPnP™ MediaServer [5] and AVTransport; Play (as specified in [57]) actions, etc., provided by the UPnP™ MediaRenderer [56].
bdb476a5c99a057a039583429b41eaf8
185 010
6.1.1.4 Streaming of Content
Over C reference point this is behaving as the previous clause (Pull of content). NOTE: Bandwidth allocation during tunnel setup in NGN Release 2 does not take into account the different directions, e.g. RTSP in both (sendrecv) and RTP in one (recvonly). Streaming Service Provider managed IPTV content from CPN is not specified in NGN Release 2. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 19
bdb476a5c99a057a039583429b41eaf8
185 010
6.1.1.5 Remote Control
Over C reference point this is UPnP™ ScheduledRecording::CreateRecordSchedule action, etc. on home device providing UPnP™ ScheduledRecording service [59].
bdb476a5c99a057a039583429b41eaf8
185 010
7 Procedures at the Gm' Reference Point
bdb476a5c99a057a039583429b41eaf8
185 010
7.1 General
In this clause, procedures at the Gm' reference points are specified both for non-IMS and IMS SIP devices. • Non-IMS SIP device: devices complying with the definition of "Non-IMS capable device - SIP Device" in [2]. • IMS SIP device: devices complying to the definition of "IMS capable device" in [2], with the exception that in this context only IMS devices using unencrypted signalling (not using IMS AKA authentication) are valid. NOTE: The references to procedures at the Gm reference point in this clause are valid for TISPAN NGN Release 2 implementations. For 3GPP Release 8 implementations, see the references indicated by annex B.
bdb476a5c99a057a039583429b41eaf8
185 010
7.2 Procedures for non-IMS SIP devices
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.1 SIP Profiles
Non-IMS SIP devices complying with the present document could support IETF SIP to various degrees. These levels of support are specified by using the concept of SIP Profiles. Each SIP Profile corresponds to a defined functionality.
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.1.1 Basic Conversational Profile
Support for the Basic Conversational Profile is the minimum level of SIP support for a non-IMS SIP CND. In the Basic Conversational Profile the following features shall be supported: • Registration - registration procedures are detailed in clause 7.2.3. The support for the Registration functionality over the Gm' reference point corresponds to the support for registration, re-registration and de-registration functionalities over Gm as detailed in ES 283 003 [5]. • Call Initiation - call initiation procedures are detailed in clause 7.2.4. The support for the call initiation functionality over the Gm' reference point corresponds to the support for call initiation functionality over Gm as detailed in ES 283 003 [5]. • Call Release - call release procedures are detailed in clause 7.2.4. The support for the call release functionality over the Gm' reference point corresponds to the support for call release functionality over Gm as detailed in ES 283 003 [5]. • Call Modification - session modification are detailed in clause 7.2.4. The support for session modification functionality over the Gm' reference point corresponds to the support for session modification over Gm as detailed in ES 283 003 [5]. • Announcements - announcements are detailed in clause 7.2.4.7. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 20 The support for announcements over the Gm' reference point corresponds to the support for Announcements over Gm as detailed in TS 183 028 [51].
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.1.2 Extended Conversational Profile
To be compliant with the Extended Conversational Profile support of the Basic Conversational Profile shall be extended with the following features: • Indicating User Agent Capabilities in SIP - Procedures for indicating User Agent Capabilities are detailed in clause 7.2.8. • The support for Indication User Agent Capabilities in SIP corresponds to the usage of RFC 3840 [18] for registration procedures. • Capability Exchange (OPTIONS) - Procedures for Capability Exchange are detailed in clause 7.2.8. The support for Capability Exchange corresponds to the usage of the SIP OPTIONS method as defined in RFC 3261 [4]. • Messaging - Procedures for Messaging are detailed in clause 7.2.6. The support for Messaging corresponds to the procedures detailed in TS 183 041 Messaging Protocol Specification [33]. • DTMF Handling - DTMF procedures are detailed in clause 7.2.7. The support for the DTMF functionality over the Gm' reference point corresponds to the support for DTMF functionality over Gm as detailed in ES 283 003 [5].
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.1.3 Conversational Supplementary Services Profile
To be compliant with the Conversational Supplementary Services Profiles, support of the Basic Conversational Profile shall be extended with the following features: • Service Activation/De-activation - Procedures for Service Activation/De-activation are detailed in clause 7.2.5. • Communication Diversion - Procedures for Communication Diversion are detailed in clause 7.2.5. The support for Communication Diversion corresponds to the procedures specified by TS 183 004 [52]. • Communication Rejection - Procedures for Communication Rejection are detailed in clause 7.2.5. The support for Communication Rejection corresponds to the procedures detailed in TS 183 011 [53]. • Explicit Call Transfer - Procedures for Explicit Call Transfer are detailed in clause 7.2.5. The support for Explicit Call Transfer corresponds to the procedures detailed in TS 183 029 [54]. • Communication Hold - Procedures for Communication Hold are detailed in clause 7.2.5. The support for Communication Hold corresponds to the procedures detailed in TS 183 010 [55]. • 3 Party Conference - Procedures for 3 Party Conference are detailed in clause 7.2.5. The support for 3 Party Conference is based on procedures for Communication Hold and media mixing being performed locally in the CND. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 21 • Message Waiting Indication - Procedures for Message Waiting Indication are detailed in clause 7.2.5. The support for Message Waiting Indication corresponds to the procedures detailed in TS 124 406 [13]. • Originating Identification - Procedures for Originating Identification are detailed in clause 7.2.5. The support for Originating Identification corresponds to the procedures detailed in TS 183 007 [43]. • Terminating Identification - Procedures for Termination Identification are detailed in clause 7.2.5. The support for Terminating Identification corresponds to the procedures detailed in TS 183 008 [36]. • Malicious Communication Identification - Procedures for Malicious Communication Identification are detailed in clause 7.1.5.10. The support for Malicious Communication Identification corresponds to the procedures detailed in TS 183 016 [35].
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.2 IETF RFC support
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.2.1 Basic Conversational Profile
In order to be compliant with the Basic Conversational Profiles, support of the following IETF specification shall be supported: • RFC 3261 [4].
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.2.2 Extended Conversational Profile
In order to be compliant with the Extended Conversational Profile, support of the following IETF specifications shall be supported: • RFC 3840 [18]. • RFC 3428 [44]. Additionally the following IETF specifications may be supported: • RFC 2833 [17]. • RFC 3994 [45].
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.2.3 Conversational Supplementary Services Profile
In order to be compliant with the Conversational Supplementary Services Profile, the following IETF specifications shall be supported: • RFC 3265 [47]. • RFC 3842 [46]. • RFC 3515 [48]. • RFC 3891 [49]. • RFC 3892 [50]. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 22
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.3 Registration
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.3.1 Registration of CND-SIP UA, general
The registration procedures for a CND-SIP UA shall be compliant with RFC 3261 [4], clause 10. A CND-SIP UA can register a user identity (local or public) with its contact address at any time after it has learned its registration domain and acquired an IP address of the CND where it is executing. However, the CND-SIP UA shall not initiate a new registration procedure if it has not received a final response from the registrar for the ongoing registration and if the previous REGISTER request has not timed out. The user identity (local or public), registration domain (local or public) and optionally the registration port may be manually configured for the CND-SIP UA. It may also be configured automatically, for example by using the e3' reference point. HTTP Digest Authentication should be used as authentication method when registering the CND-SIP UA. If so, authentication credentials (user and password) shall be made available to the CND-SIP UA in one of the following ways: 1) pre-configuration; 2) provisioning (auto-configuration); 3) manual configuration. The CND-SIP UA shall send its REGISTER requests to the registration port, if specified by configuration. If no registration port is specified the CND-SIP UA shall send its REGISTER requests to the SIP default port values as specified in RFC 3261 [4]. On sending a REGISTER request, the CND-SIP UA shall populate the header fields as follows: a) a From header set to the SIP URI that contains the user identity to be registered (local or public); b) a To header set to the SIP URI that contains the user identity to be registered (local or public); c) a Contact header set to include SIP URI(s) containing the IP address of the CND-SIP UA in the hostport parameter or FQDN; d) a Via header set to include the IP address or FQDN of the non-IMS SIP UA in the sent-by field; e) a Request-URI set to the SIP URI containing the registration domain. On receiving the 200 (OK) response to the REGISTER request, the CND-SIP UA shall store the expiration time of the registration for the user identity found in the To header value. It should be possible to de-register the CND-SIP UA by manual user interaction, or at normal termination of the CND-SIP UA.
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.3.2 Registration of CND-SIP UA, using local SIP-URI
The local user identity field should contain a value that is administered by the CNG-SIP Proxy B2BUA and the value of the registration domain field should be the registration domain handled by the CNG-SIP Proxy B2BUA. When a CND-SIP UA is registered in the CNG-SIP Proxy B2BUA with a local identity it will be available for local services. If the local SIP account provided by the CNG-SIP Proxy B2BUA is associated with an IMS identity, the CND-SIP UA will also be available for NGN services. This association could be done by configuration in the CNG-SIP Proxy B2BUA. If authentication procedures applies at registration of the CND-SIP UA locally at the CNG-SIP B2BUA, the HTTP Digest method, as specified in RFC 3261 [4], shall be. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 23 The CND-SIP UA shall not use the same Contact value to register multiple local SIP-URIs.
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.3.3 Registration of CND-SIP UA, using public SIP-URI not preconfigured in CNG
The public user identity field should contain a value corresponding to a service provided by the NGN side of the CNG. The value of the registration domain field should be that of the service provided by the NGN side of the CNG. When a CND-SIP UA is registered in the CNG-SIP Proxy B2BUA with a public identity that is not pre-configured in the CNG, the CNG should forward the registration request according to the following principles: (i) If the CNG-SIP Proxy B2BUA is associated with a P-CSCF it may forward all registration requests to that server in a transparent fashion. In parallel the CNG-SIP Proxy B2BUA may create a local registration entry for the CND-SIP UA in order to enable local services for the CND-SIP UA. Any peering decisions are made by the NGN. (ii) As an alternative (optionally triggered by configuration) the CNG-SIP Proxy B2BUA should forward the registration requests to the destination specified in the Request-URI of the REGISTER request sent by the CND-SIP UA. In this case the CND-SIP UA should not be included in the local services (such as local communication, QoS or admissions control). 7.2.3.4 Registration of CND-SIP UA, using public SIP-URI that is pre-configured in CNG The public user identity field should contain a value corresponding to a service provided by the NGN side of the CNG. The value of the registration domain field should be that of the service provided by the NGN side of the CNG. When a CND-SIP UA is registered in the CNG-SIP Proxy B2BUA with a public identity that is pre-configured in the CNG the following principles apply: (i) If the CNG-SIP Proxy B2BUA is a SIP Proxy it should forward the REGISTER request to the destination specified by the Request-URI. It should at the same time create a local registration entry for the CND-SIP UA. (ii) If the CNG-SIP Proxy B2BUA is a B2BUA it should refresh its public registration with new data, for example if new capabilities are added by the CND-SIP UA. At the same time it should create a local registration entry for the CND-SIP UA.
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.4 Basic Call
The procedures for a CND-SIP UA related to Basic Calls are compliant with the following clauses within RFC 3261 [4]: • clause 7 • clause 8 • clause 9 • clause 12 • clause 13 • clause 14 • clause 15 • clause 17 • clause 18 • clause 19 ETSI ETSI TS 185 010 V2.1.1 (2009-07) 24 • clause 20 • clause 21
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.4.1 Call Initiation
bdb476a5c99a057a039583429b41eaf8
185 010
7.2.4.1.1 Outgoing call
On sending an INVITE request, the CND-SIP UA shall populate the header fields as follows: a) a From header set to the SIP URI that contain the local user identity of the caller (registered in the CNG-SIP B2BUA) or in cases where privacy is required, the CND-SIP UA shall set the From header display name to "Anonymous" and the URI shall be set to a meaningless value, such as sip:anonymous@example.com; b) a To header set to the SIP URI that contains the public or local user identity of the callee; c) a Contact header set to include SIP URI(s) containing the IP address of the CND-SIP UA in the hostport parameter or FQDN; d) a Via header set to include the IP address or FQDN of the non-IMS SIP UA in the sent-by field; e) a Request-URI set to the SIP URI containing the user identity of the callee (local or public) and a domain part either specified by the caller or the domain of the CNG-SIP B2BUA. HTTP Digest authentication mechanism may be used for outgoing Call Initiation over Gm'. An INVITE request generated by a CND-SIP UA shall contain a SDP offer and at least one media description. The SDP offer shall reflect the calling user's capabilities and user preferences for the session. The CND-SIP UA shall order the SDP offer with the most preferred codec listed first. When the CNG-SIP B2BUA receives an INVITE from the CND-SIP UA addressed to the domain of the CNG-SIP B2BUA, it shall first check if the caller contained in the From-header is registered (either explicitly or implicitly) within the CNG-SIP B2BUA registrar. If an explicitly stated (not anonymous) caller is not registered, the CNG-SIP B2BUA shall reject the call by sending a 403 Forbidden response. Furthermore, and in case of anonymous calls, the CNG-SIP B2BUA should additionally use any of the methods below to verify the caller: (i) If HTTP Digest authentication is used for the INVITE the CNG-SIP B2BUA may use the user part of the authentication mechanism to verify the user. (ii) If no authentication mechanism is used, the CNG-SIP B2BUA should check if the Contact information corresponds to information in the contact list found in the CNG-SIP B2BUA registrar for the caller. If the CNG-SIP B2BUA is unable to verify the caller, it should reject the call by sending a 403 Forbidden response. After verification of the caller, the CNG-SIP B2BUA should check if the callee is registered locally within the CNG-SIP B2BUA registrar. If so, the procedures of 7.2.4.1.2 shall apply. If it is not a local call, the CNG-SIP B2BUA should check if the local identity of the caller is associated with a public identity. If this is the case the CNG-SIP B2BUA shall initiate a call to the NGN on the behalf of the local caller using the public identity and following the procedures specified for the Gm reference point. In this process the CNG-SIP B2BUA shall initiate media forwarding from the NGN to the CPN in order to be able to receive early media from the NGN. If the local identity of the caller is not associated with a public identity (either explicitly by configuration or implicitly by following the registration procedures as specified in 7.2.3.3 (i) or 7.2.3.4 (i), the CNG-SIP B2BUA shall reject the call by sending a 403 Forbidden response. When the CNG-SIP B2BUA receives an INVITE from the CND-SIP UA addressed to a domain other than it own it may forward the INVITE request to its P-CSCF in a transparent fashion. Any peering decisions will be made by the NGN. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 25 When receiving a provisional response from the NGN, the CNG-SIP B2BUA shall send the provisional response on Gm' (where reliability of provisional responses is not required). On Gm the CNG-SIP B2BUA implements the full IMS UE procedures and thus sends PRACK to the NGN. Upon receiving provisional responses containing early media streams from the NGN, the CNG-SIP B2BUA shall set up the media forwarding in the CNG if preconditions are met. A port shall be allocated for reception of media from the CPN and port forwarding shall be set up by using the CNG-NFF. Upon reception of a final response the CNG-B2BUA shall send a final response with the same response code on Gm' to the calling CND-SIP UA. If the final response is 200 OK containing an SDP answer, the CNG-SIP B2BUA should follow the procedures specified in TS 124 229 [20], clause 6. Also the CNG-SIP B2BUA should initiate media port forwarding from the CPN to the NGN. Upon reception of multiple 200 OK on Gm the CNG-SIP B2BUA terminates these multiple dialogs according to the procedures specified for Gm specified in TS 124 229 [20], clause 5.1.3. The reception of the multiple 200 OK does in this case not initiate any activity by the CNG-SIP B2BUA on the Gm' reference point. Upon receiving the final response, the CND-SIP UA shall send the ACK request according to the procedures specified in RFC 3261 [4].