hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
5.3.2 Use of TTCN-3
|
For the purposes of the present document, the description of the use of TTCN-3 described in clause 5.3.2 of TS 102 790-3 [3] applies. ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 10 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, grants that users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the type of ATS defined in the present document, the PIXIT are divided in PIXIT items for UE, AS and general PIXIT items that apply for all types of IUT. Each PIXIT item corresponds to a Module Parameter of the ATS. NOTE: The PIXIT definitions are part of a SIP TTCN-3 library that contains additional PIXIT definitions that are not used in this ATS and are therefore not presented in the following tables. A.2.1 PIXIT for UE Testing Table A.1: PIXIT items for UE testing Id Identifier Type / Description 1 PX_IMS_TS_PCSCF_IPADDR charstring, for TS/P-CSCF IP address to exchange SIP messages. 2 PX_IMS_TS_PCSCF_PORT integer, for IUT/P-CSCF port number to exchange SIP messages. 3 PX_IMS_TS_UE1_IPADDR charstring, for IP address used by the UE1 to exchange SIP messages. 4 PX_IMS_TS_UE1_PORT integer, for port number used by the UE1 to exchange SIP messages. 5 PX_IMS_SUT_UE1_BEARER_IPADDR charstring, for IP address used by the TS to exchange media streams for UE1. 6 PX_IMS_SUT_UE1_HOME_DOMAIN charstring, for identity of the tester UE1 local domain. 7 PX_IMS_SUT_UE1_PUBLIC_USER charstring, for identity of the tester UE1 local user. 8 PX_IMS_SUT_UE1_PRIVAT_USERNAME charstring, for RFC 2617 [10], clause 3.2.2 username of UE1: The name of user in the specified realm. 9 PX_IMS_SUT_UE1_PRIVAT_PASSWD charstring, for RFC 2617 [10], clause 3.2.2.2 passwd of UE1: A known shared secret, the password of user of the specified username. 10 PX_IMS_SUT_UE1_QOP charstring, for RFC 2617 [10], clause 3.2.1 qop options of UE1: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection. 11 PX_IMS_SUT_UE1_REGISTRAR charstring, for home (SUT) REGISTRAR domain of UE1. 12 PX_UE_REGISTRATION boolean, En-/disable UE registration. 13 PX_UE_REG_EVENT_SUBSCRIPTION boolean, En-/disable UE reg event subscription. 14 PX_SIP_TWAIT float, for TWait default value for waiting an operator action. 15 PX_IMS_SUT_UE2_HOME_DOMAIN charstring, for identity of the tester UE2 local domain. ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 11 Id Identifier Type / Description 16 PX_IMS_SUT_UE2_PUBLIC_USER charstring, for identity of the tester UE2 local user. 17 PX_IMS_SUT_UE3_HOME_DOMAIN charstring, for identity of the tester UE3 local domain. 18 PX_IMS_SUT_UE3_PUBLIC_USER charstring, for identity of the tester UE3 local user. A.2.2 PIXIT for AS Testing In addition to the PIXIT in table A.2, PICIT items A.1/6, A.1/7 and items from A.1/15 to A.1/18 apply. Table A.2: PIXIT items for AS testing Id Identifier Type / Description 1 PX_IMS_TS_UE4_IPADDR charstring, for IP address used by the UE4 to exchange SIP messages. 2 PX_IMS_TS_UE4_PORT integer, for port number used by the UE4 to exchange SIP messages. 3 PX_IMS_TS_SCSCF_IPADDR charstring, for TS/S-CSCF IP address to exchange SIP messages. 4 PX_IMS_TS_SCSCF_PORT integer, for TS/S-CSCF port number to exchange SIP messages. 5 PX_IMS_SUT_UE4_BEARER_IPADDR charstring, for IP address used by the TS to exchange media streams for UE4. 6 PX_IMS_SUT_UE4_HOME_DOMAIN charstring, for identity of the tester UE4 local domain. 7 PX_IMS_SUT_UE4_PUBLIC_USER charstring, for identity of the tester UE4 local user. 8 PX_IMS_SUT_UE4_PRIVAT_USERNA ME charstring, for RFC 2617 [10], clause 3.2.2 username of UE4: The name of user in the specified realm. 9 PX_IMS_SUT_UE4_PRIVAT_PASSWD charstring, for RFC 2617 [10], clause 3.2.2.2 passwd of UE4: A known shared secret, the password of user of the specified username. 10 PX_IMS_SUT_UE4_QOP charstring, for RFC 2617 [10], clause 3.2.1 qop options of UE4: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection. 11 PX_IMS_SUT_UE4_REGISTRAR charstring for home (SUT) REGISTRAR domain of UE4. 12 PX_Timeout_CFNR float default timer value for PX_Timeout_CFNR. 13 PX_CDIV_Start_Time_Subscribe charstring default start time value for CDIV subscription. 14 PX_CDIV_End_Time_Subscribe charstring default end time value for CDIV subscription. 15 PX_CDIV_Start_Time_Notify charstring default start time value for CDIV notification. 16 PX_CDIV_End_Time_Notify charstring default end time value for CDIV notification. NOTE: UE1: Simulated calling (originating) UE. UE2, UE3: Simulated UE involved in call diversion (e.g. diverting user role). UE4: Simulated called (terminating) UE. A.2.3 General PIXIT The following PIXIT items apply for all types of IUT. Table A.3: General PIXIT items (SDP and Synchronization) Id Identifier Type / Description 1 PX_SIP_SDP_dyn charstring, for SDP dynamic port. 2 PX_SIP_SDP_b_modifier charstring, for SDP bandwidth modifier. 3 PX_SIP_SDP_b_bandwidth integer, for SDP bandwidth value. 4 PX_SIP_SDP_encoding charstring, for SDP media attribute encoding supported by the IUT. 5 PX_TSYNC_TIME_LIMIT float, Default time limit for a sync client to reach a synchronization point. 6 PX_TSHUT_DOWN_TIME_LIMIT float, Default time limit for a sync client to finish its execution of the shutdown default. ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 12 Annex B (informative): TTCN-3 library modules B.1 Electronic annex, zip file with TTCN-3 code The TTCN-3 library modules are contained in archive ts_18601403v030101p0.zip which accompanies the present document. ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 13 Annex C (informative): Validation Report C.1 Test Suite Validation Level Level 3 validation (strong) was achieved. C.2 TTCN-3 Edition Release 4.3.1 of the TTCN-3 documents [7] were used. C.3 TTCN-3 Tool(s) The following TTCN-3 tools were used: • Elvior TestCast® • Ericsson® Titan • Testing Technologies TTWorkbench® C.3.1 TTCN-3 Tool Elvior TestCast® C.3.1.1 Identification of the TTCN-3 Tool Elvior TestCast® Elvior TestCast® T3 Version 6.4.3, no plugins necessary. C.3.1.2 Compilation status Full compilation, without any errors. C.3.2 TTCN-3 Tool Ericsson® Titan C.3.2.1 Identification of the TTCN-3 Tool Ericsson® Titan Ericsson® Titan as in file ttcn3-1.8.pl4-mingw, no plugins necessary. C.3.2.2 Compilation status Partial compilation, as xml data structure were not supported by this version. ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 14 C.3.3 TTCN-3 Tool Testing Technologies TTWorkbench® C.3.3.1 Identification of the TTCN-3 Tool Testing Technologies TTWorkbench® Testing Technologies TTworkbench® Basic, Version: 13, Build id: 2011.10.17.13.21.07.953 with plugin TTplugin-XSD Version 1.1.4. C.3.3.2 Compilation status Full compilation, without any errors. C.3.4 Test Platform(s) The test cases were run on the execution environment of the Testing Technology TTworkbench® tool mentioned in clause C.3.3. ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 15 History Document history V3.1.1 January 2012 Publication
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
1 Scope
|
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for Communications Diversion (CDIV) services, TS 183 004 [1]. A further part of the present document specifies the Protocol Implementation Conformance Statement (PICS), Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the present document. Within the TISPAN NGN Release 1 Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). The Communications Diversion (CDIV) services enables diverting user, to divert the communications addressed to diverting user to an other destination.
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
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.
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
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 183 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification". [2] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 8.7.0 Release 8)". [3] RFC 4244: "An Extension to the Session Initiation Protocol for Request History Information". [4] RFC 4458: "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)". [5] IETF RFC 3261 (June 2002) "SIP: Session Initiation Protocol". ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 6 [6] ETSI TS 183 007: "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". [7] ETSI TS 183 011: "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". [8] ETSI TS 183 028: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Common Basic Communication procedures; Protocol specification". [9] ETSI TS 183 008: "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". [10] ETSI TS 186 014-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Communication Diversion (CDIV); Part 1: Protocol Implementation conformance Statement (PICS)". [11] ETSI TS 183 029: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification". [12] ISO/IEC 9646-1: "Information technology; Open Systems Interconnection; Conformance testing methodology and framework; Part 1: General concepts". [13] ETSI TS 181 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services". [14] ETSI TS 181 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Direct Communication Service in NGN; Service Description [Endorsement of OMA-ERELD-PoC-V1]".
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
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. Not applicable.
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
3 Definitions and abbreviations
| |
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-1 [12] apply.
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project; www.3gpp.org ACR Anonymous Communication Rejection AoC Advice of Charge AS SIP Application Server BGCF Border Gateway Control Function CD Communication Deflection CDIV Communication DIVersion ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 7 CFB Communication Forwarding Busy CFNL Communication Forwarding on Not Logged-in CFNR Communication Forward No Reply CFU Communication Forward Unconditional HOLD Communication Hold IFC Initial Filter Criteria IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service Data Network MCID Malicious Communication IDentification NGN Next Generation Network OIP Originating Identification Presentation OIR Originating Identification Restriction PSTN Public Switched Telephone Network SIP Session Initiation Protocol TIP Terminating Identification Presentation TIR Terminating Identification Restriction UA User Agent UE User Equipment
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
4 Test Suite Structure (TSS)
|
Table 1: Test suite structure Netw DivertigS-CSCF CDIV_N01 ASdivertingUser CDIV_N02 ASNotification CDIV_N03 CDIV_N04 CDIV_N05 CDIV_N06 CDIV_N07 CDIV_N08 CDIV_N09 CDIV_N10 ASdiverted-to CDIV_N11 User OrigUE CDIV_U01 Diverted-toUE CDIV_U02 DivertingUE CDIV_U03 Interaction TIP CDIV_N11_xxx TIR CDIV_N12_xxx OIP CDIV_N13_xxx OIR CDIV_N14_xxx ACR-CB CDIV_N15_xxx ECT CDIV_N16_xxx ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 8
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5 Test Purposes (TP)
| |
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.1 Introduction
|
For each test requirement a TP is defined.
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.1.1 TP naming convention
|
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see figure 1). Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "CDIV" <iut> = type of IUT: U User N Network yyy service <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999) Figure 1: TP identifier naming convention scheme
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.1.2 Test strategy
|
As the base standard TS 183 004 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 186 014-1 [10].
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.1.3 Configuration
|
For Application Server procedure testing, the ISC interface should be used. In case when the ISC interface is not explicitly available it is also applicable to use any NNI interface such as the Mw, Mg or the Mx interface. The use of the Gm interface is explicitly stated.
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2 Signalling requirements
| |
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.1 Actions at the diverting S-CSCF
|
TSS Netw/DivertigS-CSCF TP CDIV_N01_001 Reference Selection expression Test purpose The S-CSCF forwards the request to the AS based on the initial filter criteria roles indicating the UE B is subscribed to CFU simulation service. Ensure that the S-CSCF is able to forward a request to the AS based on the initial filter criteria for the CDIV service if the called user is subscribed to the communication diversion service. SIP header values: Comments: SIP#1 (Mw) S-CSCF SIP#2 (ISC) INVITE 1 INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 9
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2 Actions at the AS of the diverting User
|
TSS Netw/ASdivertingUser TP CDIV_N02_001 Reference 4.5.2.6.1 Selection expression PICS 1/2 Test purpose Served user has activated CFB, maximum number of diversion exceeded. Ensure that the 486 (Busy here) final response is sent to the original user if the served user has activated the CFB simulation service and the served user is busy and if the maximum number of diversions is exceeded. SIP header values: INVITE: sip:SIP#n@ example.com SIP/2.0 History-Info: <sip: non significant uri value >;index=1, Build additional entries with non significant uri values <sip:SIP#n; cause=VA_CAUSE>;index=1.n.1 Remark: for each redirection a history-entry is added the History-Info header and the relevant index is incremented according the rules described in 4.5.2.6.2.3/ [1]. In short: each redirection is represented by a "." (dot) in the latest history-entry. Comments: SIP#1 AS SIP#n SIP#n+1 INVITE 1 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK INVITE 2 INVITE 2 486 (Busy here) 486 (Busy here) ACK ACK BYE 1 BYE 1 200 OK BYE 200 OK BYE TSS Netw/ASdivertingUser TP CDIV_N02_002 Reference 4.5.2.6.1 Selection expression PICS 1/3 Test purpose Served user has activated CFNR, maximum number of diversion exceeded. Ensure that the 480 (Temporarily unavailable) final response is sent to the original user if the served user does not answer the communication request and if the maximum number of diversions is exceeded. SIP header values: INVITE: sip:SIP#n@ example.com SIP/2.0 History-Info: <sip: non significant uri value>;index=1, Build additional entries with non significant uri values <sip:SIP#n; cause=VA_CAUSE>;index=1.n.1 Remark: for each redirection a history-entry is added the History-Info header and the relevant index is incremented according the rules described in 4.5.2.6.2.3/ [1]. In short: each redirection is represented by a "dot" in the latest history-entry. Comments: SIP#1 AS SIP#n SIP#n+1 INVITE INVITE 180 Ringing 180 Ringing No reply timer expires 480 (Temporarily unavailable) CANCEL ACK 200 OK CANCEL 487 Request Terminated ACK ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 10 TSS Netw/ASdivertingUser TP CDIV_N02_003 Reference 4.5.2.6.1 Selection expression PICS 1/1 Test purpose Served user has activated CFU, maximum number of diversion exceeded. Ensure that the 480 (Temporarily unavailable) final response is sent to the original user if the served user has activated the CFU simulation service and if the maximum number of diversions is exceeded. SIP header values: INVITE: sip:SIP#n@ example.com SIP/2.0 History-Info: <sip: non significant uri value >;index=1, Build additional entries with non significant uri values <sip:SIP#n; cause=VA_CAUSE>;index=1.n.1 Remark: for each redirection a history-entry is added the History-Info header and the relevant index is incremented according the rules described in 4.5.2.6.2.3/ [1]. In short: each redirection is represented by a "dot" in the latest history-entry. Comments: SIP#1 AS SIP#n SIP#n+1 INVITE 480 (Temporarily unavailable) ACK TSS Netw/ASdivertingUser TP CDIV_N02_004 Reference 4.5.2.6.1 Selection expression PICS 1/4 OR PICS 1/5 Test purpose Served user has activated CD, maximum number of diversion exceeded. Ensure that the 480 (Temporarily unavailable) final response is sent to the original user if the served user has activated the CD simulation service and if the maximum number of diversions is exceeded. SIP header values: INVITE: sip:SIP#n@ example.com SIP/2.0 History-Info: <sip: non significant uri value >;index=1, Build additional entries with non significant uri values <sip:SIP#n; cause=VA_CAUSE>;index=1.n.1 Remark: for each redirection a history-entry is added the History-Info header and the relevant index is incremented according the rules described in 4.5.2.6.2.3/ [1]. In short: each redirection is represented by a "dot" in the latest history-entry. Comments: SIP#1 AS SIP#n SIP#n+1 INVITE INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK 480 (Temporarily unavailable) ACK ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 11 TSS Netw/ASdivertingUser TP CDIV_N02_005 Reference 4.5.2.6.2.2/ [1] Selection expression Test purpose Request URI is set to the diverted to destination History-info header contained in the INVITE. The served user subscribes to the CDIV service defined as CDIV in table 2. The first diversion has already undergone, no History header has been received. Ensure that the Request URI shall be set to the public user identity where the communication is to be diverted. Ensure that two hist-info entries shall be generated. Ensure that the first entry shall include the hi-targeted-to-uri of the served user. The Index is set to index=1. SIP header values: INVITE: sip:SIP#3@ example.com SIP/2.0 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=VA_CAUSE>;index=1.1 Comments: SIP#1 AS SIP#2 SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE TSS Netw/ASdivertingUser TP CDIV_N02_006 Reference 4.5.2.6.2.2/ [1] Selection expression PICS 4/1 OR PICS 4/2 Test purpose To header is sent unchanged. The served user subscribes to the CDIV service defined as CDIV in table 2. The To header is sent unchanged if the user does not reveal its identity. SIP header values: INVITE 1: To: userB@domain INVITE 2: To: userB@domain Comments: SIP#1 AS SIP#2 SIP#3 INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 12 TSS Netw/ASdivertingUser TP CDIV_N02_007 Reference 4.5.2.6.2.2/ [1] Selection expression PICS 4/1 OR PICS 4/2 Test purpose To header changed with respect to the OIR service. The served user subscribes to the CDIV service defined as CDIV in table 2. The first diversion has already undergone, no History header has been received. Ensure that when the served user wishes privacy, the served user is subscribed to the OIR Service, the "To header" shall be changed to the URI where the communication is diverted to. OIP Subscription option values: Permanent mode = yes or Temporary mode default presentation restricted = yes SIP header values: INVITE 1: To: userB@domain INVITE 2: To: userC@domain Comments: SIP#1 AS SIP#2 SIP#3 INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE TSS Netw/ASdivertingUser TP CDIV_N02_008 Reference 4.5.2.6.2.2/ [1] Selection expression PICS 3/5 Test purpose To header changed with respect to the subscription option "Served user allows the presentation of his/her URI to diverted-to user" set to false. The served user subscribes to the CDIV service defined as CDIV in table 2. The first diversion has already undergone, no History header has been received. Ensure that if the served used has the subscription option "Served user allows the presentation of his/her URI to diverted-to user" set to false, then the "To header" shall be changed to the URI the URI where the communication is diverted to. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 1: To: userB@domain INVITE 2: To: userC@domain Comments: SIP#1 AS SIP#2 SIP#3 INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 13 TSS Netw/ASdivertingUser TP CDIV_N02_009 Reference 4.5.2.6.2.3/ [1] Selection expression Test purpose The request-URI is set to the public user identity of the diverted to user multiple diversion. The served user subscribes to the CDIV service defined as CDIV in table 2. Subsequent diversion has already undergone, a History header has been received. When multiple diversions has undergone ensure that the Request URI – shall be set to the public user identity where the communication is diverted to. SIP header values: INVITE 1: History-Info: <sip:SIP#1?Privacy=history>;index=1, <sip:SIP#n-1; cause=302?Privacy=history>;index=1.1 INVITE 2: INVITE sip:SIP#n@ example.com SIP/2.0 Comments: SIP#1 AS SIP#n-1 SIP#n INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE TSS Netw/ASdivertingUser TP CDIV_N02_010 Reference 4.5.2.6.2.3/ [1] Selection expression Test purpose A new History-Info entry is added to the received History-Info header. The served user subscribes to the CDIV service defined as CDIV in table 2. Subsequent diversion has already undergone, a History header has been received. Ensure that when a multiple diversion has undergone, a new History-Info entry shall be added to the History-Info header field. SIP header values: INVITE 1: History-Info: <sip:SIP#1>;index=1, <sip:SIP#n-1; cause=302>;index=1.1 INVITE 2: History-Info: <sip:SIP#1>;index=1, <sip:SIP#n-1; cause=302>;index=1.1 <sip:SIP#n; cause=VA_CAUSE>;index=1.1.1 Comments: SIP#1 AS SIP#n-1 SIP#n INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 14 TSS Netw/ASdivertingUser TP CDIV_N02_011 Reference 4.5.2.6.2.3/ [1] Selection expression PICS 4/1 OR PICS 4/2 Test purpose Additional History-Info entry with respect to the OIR service. The served user subscribes to the CDIV service defined as CDIV in table 2. Subsequent diversion has already undergone, a History header has been received. When a multiple diversion has undergone, a new History-Info entry shall be added to the History-Info header field. Ensure that the history entry representing the served user privacy header "history" shall be escaped within the hi-targeted-to-uri, if the served user wishes privacy the served user is subscribed to the OIR Service. OIP Subscription option values: Permanent mode = yes or Temporary mode default presentation restricted = yes SIP header values: INVITE 1: History-Info: <sip:SIP#1>;index=1, <sip:SIP#n-1; cause=302>;index=1.1 INVITE 2: History-Info: <sip:SIP#1>;index=1, <sip:SIP#n-1; cause=302?Reason=history >;index=1.1 <sip:SIP#n; cause=VA_CAUSE>;index=1.1.1 Comments: SIP#1 AS SIP#n-1 SIP#n INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 15 TSS Netw/ASdivertingUser TP CDIV_N02_012 Reference 4.5.2.6.2.3/ [1] Selection expression PICS 3/6 Test purpose Additional History-Info entry with respect to the subscription option "Served user allows the presentation of his/her URI to diverted-to user" set to false. The served user subscribes to the CDIV service defined as CDIV in table 2. Subsequent diversion has already undergone, a History header has been received. When a multiple diversion has undergone, a new History-Info entry shall be added to the History-Info header field. Ensure that the history entry representing the served user privacy header "history" shall be escaped within the hi-targeted-to-uri, if the served used has the subscription option "Served user allows the presentation of his/her URI to diverted-to user" set to false. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 1: History-Info: <sip:SIP#1>;index=1, <sip:SIP#n-1; cause=302>;index=1.1 INVITE 2: History-Info: <sip:SIP#1>;index=1, <sip:SIP#n-1; cause=302?Reason: history >;index=1.1 <sip:SIP#n; cause=VA_CAUSE>;index=1.1.1 Comments: SIP#1 AS SIP#n-1 SIP#n INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 16 TSS Netw/ASdivertingUser TP CDIV_N02_013 Reference 4.5.2.6.2.3/ [1] Selection expression PICS 3/6 Test purpose The To header is set with respect to the subscription option "Served user allows the presentation of his/her URI to diverted-to user" set to false. The served user subscribes to the CDIV service defined as CDIV in table 2. Subsequent diversion has already undergone, a History header has been received. When a multiple diversion the communication has undergone: ensure that if the served user does not want to reveal its identity to the diverted-to party and the server used has the subscription option "Served user allows the presentation of his/her URI to diverted-to user" set to false, then the To header shall be changed the URI where the communication is diverted to. In all other cases the To header shall not be changed. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 1: History-Info: <sip:SIP#1>;index=1, <sip:SIP#n-1; cause=302>;index=1.1 INVITE 2: To: To: user#n@domain Comments: SIP#1 AS SIP#n-1 SIP#n INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE TSS Netw/ASdivertingUser TP CDIV_N02_014 Reference 4.5.2.6.2.3/ [1] Selection expression PICS 4/1 OR PICS 4/2 Test purpose The To header is set with respect to the OIR service of the served user. The served user subscribes to the CDIV service defined as CDIV in table 2. Subsequent diversion has already undergone, a History header has been received. When this a multiple diversion the communication has undergone: ensure that if the served user does not want to reveal its identity to the diverted-to party and the served user wishes privacy (e.g. the served user is subscribed to the OIR Service) then the To header shall be changed the URI where the communication is diverted to. OIP Subscription option values: Permanent mode = yes or Temporary mode default presentation restricted = yes SIP header values: INVITE 1: History-Info: <sip:SIP#1>;index=1, <sip:SIP#n-1; cause=302>;index=1.1 INVITE 2: To: To: user#n@domain Comments: SIP#1 AS SIP#n-1 SIP#n INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 17 Table 2 Cause value Redirecting Reason 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 404 Subscriber not Logged in 487 Deflection during alerting Cause Value in hi- targeted-to-uri VA_CAUSE 503 Call diversion information Subscriber Not reachable
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2.1 Notification procedure of the originating and terminating user
| |
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2.1.1 Communication Forwarding Unconditional (CFU)
|
TSS Netw/ASNotification TP CDIV_N03_001 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/1 AND PICS 3/3 Test purpose The served user subscribes to the CFU simulation service; originating user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFU simulation service. The origination user is not notified. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 18 TSS Netw/ASNotification TP CDIV_N03_002 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/1 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFU simulation service; originating user is notified. When Communication Diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user. A Privacy header value history is escaped in the first and the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=302?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 19 TSS Netw/ASNotification TP CDIV_N03_003 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/1 AND PICS 3/3 AND PICS 2/2 Test purpose The served user subscribes to the CFU simulation service; originating user is notified. Additionally an announcement is played. When Communication Diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user. Additional the AS initiates an announcement to be included towards the calling user in order to inform about the diversion. Announcements may be played. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing An announcement toward the calling user 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 20 TSS Netw/ASNotification TP CDIV_N03_004 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/1 AND PICS 3/3 AND PICS3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFU simulation service; originating user is notified, the URI of the served user is received. When Communication Diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user. The P-Asserted-Identity includes the URI of the diverting user. The served user allows the presentation of his/her URI to the originating user. The URI of the served user is contained in first entry of the History-Info header. A Privacy header value history is escaped in the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=302?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 21 TSS Netw/ASNotification TP CDIV_N03_005 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/1 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFU simulation service; originating user is notified, the URI of the diverted-to user is received. When Communication Diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user. The 181 (Call Is Being Forwarded) response contains the P-Asserted-Identity header field and Privacy header field. The P-Asserted-Identity includes the URI of the diverting user. The served user allows the presentation of diverted- to URI to the originating user. The URI of the diverted-to user is contained in second entry of the History-Info header. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = yes Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 History-Info: <sip:SIP#2?Privacy=history >;index=1, <sip:SIP#3; cause=302>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 22 TSS Netw/ASNotification TP CDIV_N03_006 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/1 AND PICS 3/6 Test purpose The served user subscribes to the CFU simulation service; the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFU simulation service. The diverted to user is not notified. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=302>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N03_007 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/1 AND PICS 3/6 Test purpose The served user subscribes to the CFU simulation service; the diverted to user is notified. URI of served user is sent. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFU simulation service. The diverted to user is notified. Served user allows the presentation of his/her URI to the diverted-to user. No Privacy header is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = yes SIP header values: INVITE P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=302>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 23 TSS Netw/ASNotification TP CDIV_N03_008 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/1 AND PICS 3/1 Test purpose The served user subscribes to the CFU simulation service; Indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded Unconditional. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N03_009 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/1 AND PICS 2/1 AND PICS 3/1 Test purpose The served user subscribes to the CFU simulation service; Indication of communication diversion to the diverting user using the MESSAGE request triggered by a timer. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded Unconditional. The MESSAGE request that is be sent due to an timer value that can be provided by the user. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) triggered by a timer value provided the served user Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 24 TSS Netw/ASNotification TP CDIV_N03_010 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/1 AND PICS 2/4 AND PICS 3/1 Test purpose The served user subscribes to the CFU simulation service; periodically indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded Unconditional. The diverting user will be informed periodically with a MESSAGE request the information where the call is diverted to. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 25 TSS Netw/ASNotification TP CDIV_N03_011 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/1 AND PICS 3/1 AND PICS 3/2 Test purpose The served user subscribes to the CFU simulation service; Indication of communication diversion to the diverting user using the MESSAGE request when a new outgoing communication is requested. Ensure that a diverting user will be informed with a MESSAGE request to the diverting user after the diverting user has initiated a new outgoing communication the information where the call is forwarded Unconditional. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes Served user receives reminder indication on outgoing communication that CDIV is currently activated = yes SIP header values: MESSAGE (text/plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 2 INVITE MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 26 TSS Netw/ASNotification TP CDIV_N03_012 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/1 AND PICS 2/3 AND PICS 3/1 Test purpose The served user subscribes to the CFU simulation service; Communication Diversion Notification applies. Ensure that when the diverting user has subscribed the Communication Diversion Notification service, the served user receives a NOTIFY request containing the information regarding the current communication diversion unconditional. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: SUBSCRIBE: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-subs-info > <comm-div-selection-criteria> < originating-user-selection-criteria>SIP#1 <diverting-user-selection-criteria>SIP#2 <diverted-to-user-selection-criteria>SIP#3 < diversion-time-selection-criteria >(Date-time) < diversion-reason-selection-criteria >302 <comm-div-ntfy-trigger-criteria> <notification-time-selection-criteria>(Date/Time range PIXIT) </comm-div-info> NOTIFY: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-ntfy-info> <originating-user-info>SIP#1 <diverting-user-info>SIP#2 <diverted-to-user-info>SIP#3 <diversion-time-info> (time range <diversion-reason-info>302 <diversion-rule-info-type> <diversion-rule> (any text) </comm-div-info> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SUBSCRIBE SUBSCRIBE 200 OK SUBSCRIBE 200 OK SUBSCRIBE NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 1 Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 27
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2.1.2 Communication Forwarding on Busy user (CFB)
|
TSS Netw/ASNotification TP CDIV_N04_001 Reference 4.5.2.6/ [1] Selection expression PICS 1/2 Test purpose The served user subscribes to the CFB simulation service. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFB simulation service. SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N04_002 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/2 AND PICS 3/3 Test purpose The served user subscribes to the CFB simulation service; originating user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFB simulation service. The origination user is not notified. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 28 TSS Netw/ASNotification TP CDIV_N04_003 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/2 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFB simulation service; originating user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFB simulation service. The originating user receives notification that a communication has been forwarded. A 181 (Call Is Being Forwarded) response shall be sent towards the originating user. A Privacy header value history is escaped in the first and the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=486?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 29 TSS Netw/ASNotification TP CDIV_N04_004 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/2 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFB simulation service. The originating user receives the URI of the served user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFB simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of his/her URI to the originating user. A 181 (Call Is Being Forwarded) response shall be sent towards the originating user. The URI of the served user is contained in first entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of his/her URI to originating user in diversion notification = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=486?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 30 TSS Netw/ASNotification TP CDIV_N04_005 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/2 AND PICS 3/3AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFB simulation service. The originating user receives the URI of the diverted-to user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFB simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of his/her URI to the originating user. A 181 (Call Is Being Forwarded) response shall be sent towards the originating user. The URI of the diverted-to user is contained in second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of his/her URI to originating user in diversion notification = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=486>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 31 TSS Netw/ASNotification TP CDIV_N04_006 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/2 AND PICS 3/6 Test purpose The served user subscribes to the CFB simulation service; the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFB simulation service. The diverted to user is not notified. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=486>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N04_007 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/2 AND PICS 3/6 Test purpose The served user subscribes to the CFB simulation service; the diverted to user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFB simulation service. The diverted to user is notified. Served user allows the presentation of his/her URI to the diverted-to user. No Privacy header is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = yes SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=486;>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 32 TSS Netw/ASNotification TP CDIV_N04_008 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/2 AND PICS 3/1 Test purpose The served user subscribes to the CFB simulation service; Indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded on busy user. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text /plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N04_009 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/2 AND PICS 2/1 AND PICS 3/1 Test purpose The served user subscribes to the CFB simulation service; Indication of communication diversion to the diverting user using the MESSAGE request triggered by a timer. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded on busy user. The MESSAGE request that is be sent due to an timer value that can be provided by the user. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text /plain) triggered by a timer value provided the served user Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 33 TSS Netw/ASNotification TP CDIV_N04_010 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/2 AND PICS 2/4 AND PICS 3/1 Test purpose The served user subscribes to the CFB simulation service; periodically indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded on busy user. The diverting user will be informed periodically with a MESSAGE request the information where the call is diverted to. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text /plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 34 TSS Netw/ASNotification TP CDIV_N04_011 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/2 AND PICS 3/1 AND PICS 3/2 Test purpose The served user subscribes to the CFB simulation service; Indication of communication diversion to the diverting user using the MESSAGE request when a new outgoing communication is requested. Ensure that a diverting user will be informed with a MESSAGE request to the diverting user after the diverting user has initiated a new outgoing communication the information where the call is forwarded on busy user. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes Served user receives reminder indication on outgoing communication that CDIV is currently activated = yes SIP header values: MESSAGE (text /plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 486 Busy Here ACK CFB performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 35 TSS Netw/ASNotification TP CDIV_N04_012 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/2 AND PICS 2/3 AND PICS 3/1 Test purpose The served user subscribes to the CFB simulation service; Communication Diversion Notification applies. Ensure that when the diverting user has subscribed the Communication Diversion Notification service, the served user receives a NOTIFY request containing the information regarding the current communication diversion busy. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: SUBSCRIBE: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-subs-info > <comm-div-selection-criteria> < originating-user-selection-criteria>SIP#1 <diverting-user-selection-criteria>SIP#2 <diverted-to-user-selection-criteria>SIP#3 < diversion-time-selection-criteria >(Date-time) < diversion-reason-selection-criteria >486 <comm-div-ntfy-trigger-criteria> <notification-time-selection-criteria>(Date/Time range PIXIT) </comm-div-info> NOTIFY: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-ntfy-info> <originating-user-info>SIP#1 <diverting-user-info>SIP#2 <diverted-to-user-info>SIP#3 <diversion-time-info> (time range <diversion-reason-info> 486 <diversion-rule-info-type> <diversion-rule> (any text) </comm-div-info> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SUBSCRIBE SUBSCRIBE 200 OK SUBSCRIBE 200 OK SUBSCRIBE NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 1 INVITE 486 Busy Here ACK CFB performed NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 36
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2.1.3 Communication Forwarding on no Reply (CFNR)
|
TSS Netw/ASNotification TP CDIV_N05_001 Reference 4.5.2.6/ [1] Selection expression PICS 1/3 Test purpose The served user subscribes to the CFNR simulation service. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N05_002 Reference 4.5.2.6.3/ [1] Selection expression PICS 1/3 Test purpose The served user subscribes to the CFNR simulation service Forking is provided CFNR timer is not refreshed Ensure that the communication is forwarded to multiple diverted to users (forking) if the served user is subscribed to the CFNR simulation service. After receiving the first 180 (Ringing) response the no reply timer shall be started. Ensure that a further received 180 (Ringing) response does not refresh the timer. SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#2 forked SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing INVITE 180 Ringing CFNR performed after first 180 was received CANCEL 200 OK CANCEL 487 Request Terminated ACK INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 37 TSS Netw/ASNotification TP CDIV_N05_003 Reference 4.5.2.6.3/ [1] Selection expression PICS 1/3 Test purpose The served user subscribes to the CFNR simulation service the CFNR timer is terminated when a 200 OK was received. Ensure that if the served user is subscribed to the CFNR simulation service when a 180 response is received. Ensure that with receiving a 200 (OK) response the no reply timer shall be terminated and the call follows the Basic call procedure. Other open early dialogs shall be terminated. SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing No CFNR performed 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N05_004 Reference 4.5.2.6.3/ [1] Selection expression PICS 1/3 Test purpose The served user subscribes to the CFNR simulation service. Dialogue to the served user is terminated. Ensure that the served user is subscribed to the CFNR simulation service and the no reply timer expires. Ensure that if the dialog(s) to the diverting user shall be terminated e.g. by sending a CANCEL request. SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 38 TSS Netw/ASNotification TP CDIV_N05_005 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/3 AND PICS 3/3 Test purpose The served user subscribes to the CFNR simulation service; originating user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The origination user is not notified. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 39 TSS Netw/ASNotification TP CDIV_N05_006 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/3 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNR simulation service; originating user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The originating user receives notification that a communication has been forwarded. A 181 (Call Is Being Forwarded) response shall be sent towards the originating user. A Privacy header value history is escaped in the first and the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=408?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed 181 Call is Being Forwarded INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 40 TSS Netw/ASNotification TP CDIV_N05_007 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/3 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNR simulation service. The originating user receives the URI of the served user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of his/her URI to the originating user. The URI of the served user is contained in first entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of his/her URI to originating user in diversion notification = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=408?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed 181 Call is Being Forwarded INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 41 TSS Netw/ASNotification TP CDIV_N05_008 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/3 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNR simulation service. The originating user receives the URI of the diverted- to user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of diverted-to URI to the originating user. The URI of the diverted-to user is contained in second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of his/her URI to originating user in diversion notification = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=408>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed 181 Call is Being Forwarded INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 42 TSS Netw/ASNotification TP CDIV_N05_009 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/3 AND PICS 3/6 Test purpose The served user subscribes to the CFNR simulation service; the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The diverted to user is not notified. . A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=408>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 43 TSS Netw/ASNotification TP CDIV_N05_010 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/3 AND PICS 3/6 Test purpose The served user subscribes to the CFNR simulation service; the diverted to user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. Served user allows the presentation of his/her URI to the diverted-to user. No Privacy header is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = yes SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=408;>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 44 TSS Netw/ASNotification TP CDIV_N05_011 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 3/1 Test purpose The served user subscribes to the CFNR simulation service; Indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded on no Reply. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text /plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 45 TSS Netw/ASNotification TP CDIV_N05_012 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 2/1 AND PICS 3/1 Test purpose The served user subscribes to the CFNR simulation service; Indication of communication diversion to the diverting user using the MESSAGE request triggered by a timer. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded on no Reply. The MESSAGE request that is be sent due to an timer value that can be provided by the user. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text /plain) triggered by a timer value provided the served user Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 46 TSS Netw/ASNotification TP CDIV_N05_013 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 2/4 AND PICS 3/1 Test purpose The served user subscribes to the CFNR simulation service; periodically indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS send a MESSAGE request to the diverting user including the information where the call is forwarded on no Reply. The diverting user will be informed periodically with a MESSAGE request the information where the call is diverted to. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 47 TSS Netw/ASNotification TP CDIV_N05_014 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 3/1 AND PICS 3/2 Test purpose The served user subscribes to the CFNR simulation service; Indication of communication diversion to the diverting user using the MESSAGE request when a new outgoing communication is requested. Ensure that a diverting user will be informed with a MESSAGE request to the diverting user after the diverting user has initiated a new outgoing communication the information where the call is forwarded on no Reply. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes Served user receives reminder indication on outgoing communication that CDIV is currently activated = yes SIP header values: MESSAGE (text/plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE INVITE 3 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 48 TSS Netw/ASNotification TP CDIV_N05_015 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 2/3 AND PICS 3/1 Test purpose The served user subscribes to the CFNR simulation service; Communication Diversion Notification applies. Ensure that when the diverting user has subscribed the Communication Diversion Notification service, the served user receives a NOTIFY request containing the information regarding the current communication forwarding no reply. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: SUBSCRIBE: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-subs-info > <comm-div-selection-criteria> < originating-user-selection-criteria>SIP#1 <diverting-user-selection-criteria>SIP#2 <diverted-to-user-selection-criteria>SIP#3 < diversion-time-selection-criteria >(Date-time) < diversion-reason-selection-criteria >408 <comm-div-ntfy-trigger-criteria> <notification-time-selection-criteria>(Date/Time range PIXIT) </comm-div-info> NOTIFY: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-ntfy-info> <originating-user-info>SIP#1 <diverting-user-info>SIP#2 <diverted-to-user-info>SIP#3 <diversion-time-info> (time range <diversion-reason-info>408 <diversion-rule-info-type> <diversion-rule> (any text) </comm-div-info> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SUBSCRIBE SUBSCRIBE 200 OK SUBSCRIBE 200 OK SUBSCRIBE NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 1 INVITE 180 Ringing 180 Ringing T no reply expired CANCEL 200 OK CANCEL 487 Request Terminated ACK CFNR performed NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 49
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.3.1.4 Communication Forwarding on no Reply (CFNR) ringing continues
|
TSS Netw/ASNotification TP CDIV_N06_001 Reference 4.5.2.6.3/ [1] Selection expression PICS 1/3 AND PICS 2/5 Test purpose The served user subscribes to the CFNR simulation service (ringing continues). Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service the early dialogue remains established until the final response is received from the diverted to user. SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N06_002 Reference 4.5.2.6.3/ [1] Selection expression PICS 1/3 AND PICS 2/5 Test purpose The served user subscribes to the CFNR simulation service (ringing continues) Forking is provided the CFNR timer is not refreshed. Ensure that the communication is forwarded to multiple diverted to user if the served user is subscribed to the CFNR simulation service. After receiving the first 180 (Ringing) response the no reply timer shall be started. Ensure that a further received 180 (Ringing) response does not refresh the timer. SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#2 forked SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing INVITE 180 Ringing CFNR performed after first 180 was received INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 50 TSS Netw/ASNotification TP CDIV_N06_003 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 3/3 Test purpose The served user subscribes to the CFNR simulation service (ringing continues); originating user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The origination user is not notified. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 51 TSS Netw/ASNotification TP CDIV_N06_004 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNR simulation service (ringing continues); originating user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The originating user receives notification where the call is diverted to. A 181 (Call Is Being Forwarded) response shall be sent towards the originating user. The 181 (Call Is Being Forwarded) response contains the P-Asserted-Identity header field and Privacy header field. A Privacy header value history is escaped in the first and the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=408?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 181 Call is Being Forwarded 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 52 TSS Netw/ASNotification TP CDIV_N06_005 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNR simulation service (ringing continues). The originating user receives the URI of the served user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of his/her URI to the originating user The URI of the served user is contained in first entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=408?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 181 Call is Being Forwarded 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 53 TSS Netw/ASNotification TP CDIV_N06_006 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNR simulation service (ringing continues). The originating user receives the URI of the diverted-to user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of the diverted-to URI to the originating user The URI of the diverted-to user is contained in second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = yes Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2?Privacy=history >;index=1, <sip:SIP#3; cause=408 >;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 181 Call is Being Forwarded 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 54 TSS Netw/ASNotification TP CDIV_N06_007 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 3/6 Test purpose The served user subscribes to the CFNR simulation service (ringing continues); the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The diverted to user is not notified. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=408>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 55 TSS Netw/ASNotification TP CDIV_N06_008 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 3/6 Test purpose The served user subscribes to the CFNR simulation service (ringing continues); the diverted to user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNR simulation service. The diverted to user is notified. Served user allows the presentation of his/her URI to the diverted-to user. No Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = yes SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=408;>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 56 TSS Netw/ASNotification TP CDIV_N06_009 Reference / 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 3/1 Test purpose The served user subscribes to the CFNR simulation service; Indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded on no Reply ringing continues. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 57 TSS Netw/ASNotification TP CDIV_N06_010 Reference / [1] 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 2/1 AND PICS 3/1 Test purpose The served user subscribes to the CFNR simulation service; Indication of communication diversion to the diverting user using the MESSAGE request triggered by a timer. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded on no Reply ringing continues. The MESSAGE request that is be sent due to an timer value that can be provided by the user. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) triggered by a timer value provided the served user Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 58 TSS Netw/ASNotification TP CDIV_N06_011 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 2/4 AND PICS 3/1 Test purpose The served user subscribes to the CFNR simulation service; periodically indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is forwarded on no Reply ringing continues. The diverting user will be informed periodically with a MESSAGE request the information where the call is diverted to. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 59 TSS Netw/ASNotification TP CDIV_N06_012 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/3 AND PICS 2/5 AND PICS 3/1 AND PICS 3/2 Test purpose The served user subscribes to the CFNR simulation service; Indication of communication diversion to the diverting user using the MESSAGE request when a new outgoing communication is requested. Ensure that a diverting user will be informed with a MESSAGE request to the diverting user after the diverting user has initiated a new outgoing communication the information where the call is forwarded on no Reply ringing continues. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes Served user receives reminder indication on outgoing communication that CDIV is currently activated = yes SIP header values: MESSAGE (text/plain) Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing CFNR performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK CANCEL 200 OK CANCEL 487 Request Terminated ACK INVITE INVITE 3 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE Communication BYE 3 BYE 200 OK (BYE) 200 OK (BYE) BYE 1 BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 60
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2.1.5 Communication Forwarding on Not Logged-in (CFNL)
|
TSS Netw/ASNotification TP CDIV_N07_001 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/6 AND PICS 3/3 Test purpose The served user subscribes to the CFNL simulation service; originating user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNL simulation service. The origination user is not notified. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N07_002 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/6 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNL simulation service; originating user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNL simulation service. The originating user receives notification that a communication has been forwarded. In all entries in the History-Info header a Privacy parameter value history is escaped. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2, Privacy id History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=404?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 61 TSS Netw/ASNotification TP CDIV_N07_003 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/6 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNL simulation service. The originating user receives the URI of the served user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNL simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of his/her URI to the originating user. The URI of the served user is contained in first entry of the History-Info header. A Privacy header value history is escaped in the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=404?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 62 TSS Netw/ASNotification TP CDIV_N07_004 Reference 4.5.2.6.3/ [1] Selection expression PICS 1/6 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the CFNL simulation service. The originating user receives the URI of the diverted- to user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNL simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of the diverted-to URI to the originating user. The URI of the diverted-to user is contained in second entry of the History-Info header. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = yes Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2?Privacy=history >;index=1, <sip:SIP#3; cause=404 >;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N07_005 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/6 AND PICS 3/6 Test purpose The served user subscribes to the CFNL simulation service; the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNL simulation service. The diverted to user is not notified. The URI of the served user is contained in first entry of the History-Info header. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=404>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 63 TSS Netw/ASNotification TP CDIV_N07_006 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/6 AND PICS 3/6 Test purpose The served user subscribes to the CFNL simulation service; the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFNL simulation service. The diverted to user is notified. Served user allows the presentation of his/her URI to the diverted-to user. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = yes SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=404;>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 64 TSS Netw/ASNotification TP CDIV_N07_007 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/6 AND PICS 2/3 AND PICS 3/1 Test purpose The served user subscribes to the CFNL simulation service; Communication Diversion Notification applies. Ensure that when the diverting user has subscribed the Communication Diversion Notification service, the served user receives a NOTIFY request containing the information regarding the current communication deflection. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: SUBSCRIBE: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-subs-info > <comm-div-selection-criteria> < originating-user-selection-criteria>SIP#1 <diverting-user-selection-criteria>SIP#2 <diverted-to-user-selection-criteria>SIP#3 < diversion-time-selection-criteria >(Date-time) < diversion-reason-selection-criteria >487 <comm-div-ntfy-trigger-criteria> <notification-time-selection-criteria>(Date/Time range PIXIT) </comm-div-info> NOTIFY: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-ntfy-info> <originating-user-info>SIP#1 <diverting-user-info>SIP#2 <diverted-to-user-info>SIP#3 <diversion-time-info> (time range <diversion-reason-info>487 <diversion-rule-info-type> <diversion-rule> (any text) </comm-div-info> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SUBSCRIBE SUBSCRIBE 200 OK SUBSCRIBE 200 OK SUBSCRIBE NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY REGISTER(Expires: 0) REGISTER(Expires: 0) 200 OK REGISTER 200 OK REGISTER INVITE 1 CFNL performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) REGISTER(Expires: x) REGISTER(Expires: x) 200 OK REGISTER 200 OK REGISTER NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 65 TSS Netw/ASNotification TP CDIV_N07_008 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/6 AND PICS 2/3 AND PICS 3/1 Test purpose The served user subscribes to the CFNL simulation service; Communication Diversion Notification does not apply. Ensure that when the diverting user has subscribed the Communication Diversion Notification service, the served user receives no NOTIFY request after the T CDIVN Buffer was expired and the user is logged in again. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: SUBSCRIBE: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-subs-info > <comm-div-selection-criteria> < originating-user-selection-criteria>SIP#1 <diverting-user-selection-criteria>SIP#2 <diverted-to-user-selection-criteria>SIP#3 < diversion-time-selection-criteria >(Date-time) < diversion-reason-selection-criteria >487 <comm-div-ntfy-trigger-criteria> <notification-time-selection-criteria>(Date/Time range PIXIT) </comm-div-info> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SUBSCRIBE SUBSCRIBE 200 OK SUBSCRIBE 200 OK SUBSCRIBE NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY REGISTER(Expires: 0) REGISTER(Expires: 0) 200 OK REGISTER 200 OK REGISTER INVITE 1 CFNL performed Start T CDIVN Buffer INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) Timeout T CDIVN Buffer REGISTER(Expires: x) REGISTER(Expires: x) 200 OK REGISTER 200 OK REGISTER No NOTIFY! ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 66
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2.1.6 Communication Deflection immediate response (CDi)
|
TSS Netw/ASNotification TP CDIV_N08_001 Reference 4.5.2.6/ [1] Selection expression PICS 1/4 Test purpose The served user subscribes to the Communication Deflection immediate response simulation service. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. SIP header values: 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N08_002 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/4 AND PICS 3/3 Test purpose The served user subscribes to the Communication Defection immediate response simulation service; originating user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The origination user is not notified. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no SIP header values: 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 67 TSS Netw/ASNotification TP CDIV_N08_003 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/4 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the Communication Defection immediate response simulation service; originating user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The originating user receives notification that a communication has been forwarded. A Privacy header value history is escaped in the first and the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2, Privacy id History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=480?Privacy=history>;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 68 TSS Netw/ASNotification TP CDIV_N08_004 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/4 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the Communication Defection immediate response simulation service. The originating user receives the URI of the served user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of his/her URI to the originating user. The URI of the served user is contained in first entry of the History-Info header. A Privacy header value history is escaped in the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=480?Privacy=history>;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 69 TSS Netw/ASNotification TP CDIV_N08_005 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/4 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the Communication Defection immediate response simulation service. The originating user receives the URI of the diverted-to user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of the diverted-to URI to the originating user. The URI of the diverted-to user is contained in second entry of the History-Info header. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = yes Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2?Privacy=history >;index=1, <sip:SIP#3; cause=480 >;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 70 TSS Netw/ASNotification TP CDIV_N08_006 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/4 AND PICS 3/6 Test purpose The served user subscribes to the Communication Defection immediate response simulation service; the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The diverted to user is not notified. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=480>;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed 181 Call is Being Forwarded INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N08_007 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/4 AND PICS 3/6 Test purpose The served user subscribes to the Communication Defection immediate response simulation service; the diverted to user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The diverted to user is notified. Served user allows the presentation of his/her URI to the diverted-to user. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = yes SIP header values: INVITE 2 P-Asserted-Identity History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=480;>;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed 181 Call is Being Forwarded INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 71 TSS Netw/ASNotification TP CDIV_N08_008 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/4 AND PICS 3/1 Test purpose The served user subscribes to the CDi simulation service; Indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is deflected immediate response. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 72 TSS Netw/ASNotification TP CDIV_N08_009 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/4 AND PICS 2/1 AND PICS 3/1 Test purpose The served user subscribes to the CDi simulation service; Indication of communication diversion to the diverting user using the MESSAGE request triggered by a timer. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is deflected immediate response. The MESSAGE request that is be sent due to an timer value that can be provided by the user. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) triggered by a timer value provided the served user 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 73 TSS Netw/ASNotification TP CDIV_N08_010 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/4 AND PICS 2/4 AND PICS 3/1 Test purpose The served user subscribes to the CDi simulation service; periodically indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is deflected immediate response. The diverting user will be informed periodically with a MESSAGE request the information where the call is diverted to. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE Timer TCDIV_IND expired MESSAGE MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 74 TSS Netw/ASNotification TP CDIV_N08_011 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/4 AND PICS 3/1 AND PICS 3/2 Test purpose The served user subscribes to the CDi simulation service; Indication of communication diversion to the diverting user using the MESSAGE request when a new outgoing communication is requested. Ensure that a diverting user will be informed with a MESSAGE request to the diverting user after the diverting user has initiated a new outgoing communication the information where the call is deflected immediate response. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes Served user receives reminder indication on outgoing communication that CDIV is currently activated = yes SIP header values: MESSAGE (text/plain) 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed 181 Call is Being Forwarded INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE INVITE 3 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE 3 BYE 200 OK (BYE) 200 OK (BYE) BYE 1 BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 75
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2.1.7 Communication Deflection during alerting (CDa)
|
TSS Netw/ASNotification TP CDIV_N09_001 Reference 4.5.2.6/ [1] Selection expression PICS 1/5 Test purpose The served user subscribes to the Communication Deflection during alerting simulation service. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. SIP header values: 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASNotification TP CDIV_N09_002 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/5 AND PICS 3/3 Test purpose The served user subscribes to the Communication Defection during alerting simulation service; originating user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The origination user is not notified. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no SIP header values: 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 76 TSS Netw/ASNotification TP CDIV_N09_003 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/5 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the Communication Defection during alerting simulation service; originating user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The originating user receives notification that a communication has been forwarded. A Privacy header value history is escaped in the first and the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity, Privacy id History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=487?Privacy=history>;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed 181 Call is Being Forwarded INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 77 TSS Netw/ASNotification TP CDIV_N09_004 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/5 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the Communication Defection during alerting simulation service. The originating user receives the URI of the served user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of his/her URI to the originating user. The URI of the served user is contained in first entry of the History-Info header. A Privacy header value history is escaped in the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=487?Privacy=history>;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed 181 Call is Being Forwarded INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 78 TSS Netw/ASNotification TP CDIV_N09_005 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/5 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the Communication Defection during alerting simulation service. The originating user receives the URI of the diverted-to user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The originating user receives notification that a communication has been forwarded and the served user allows the presentation of diverted-to URI to the originating user. The URI of the diverted-to user is contained in second entry of the History-Info header. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = yes Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity: SIP#2 History-Info: <sip:SIP#2?Privacy=history >;index=1, <sip:SIP#3; cause=487 >;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed 181 Call is Being Forwarded INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 79 TSS Netw/ASNotification TP CDIV_N09_006 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/5 AND PICS 3/6 Test purpose The served user subscribes to the Communication Defection during alerting simulation service; the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The diverted to user is not notified. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE 2 P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=487>;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 80 TSS Netw/ASNotification TP CDIV_N09_007 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/5 AND PICS 3/6 Test purpose The served user subscribes to the Communication Defection during alerting simulation service; the diverted to user is notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the Communication Defection immediate response simulation service. The diverted to user is not notified. Served user allows the presentation of his/her URI to the diverted-to user. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = yes SIP header values: INVITE 2 P-Asserted-Identity History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=487;>;index=1.1 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 81 TSS Netw/ASNotification TP CDIV_N09_008 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/5 AND PICS 3/1 Test purpose The served user subscribes to the CDa simulation service; Indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is deflected during alerting. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 82 TSS Netw/ASNotification TP CDIV_N09_009 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/5 AND PICS 2/1 AND PICS 3/1 Test purpose The served user subscribes to the CDa simulation service; Indication of communication diversion to the diverting user using the MESSAGE request triggered by a timer. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is deflected during alerting. The MESSAGE request that is be sent due to an timer value that can be provided by the user. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) triggered by a timer value provided the served user 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 83 TSS Netw/ASNotification TP CDIV_N09_010 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/5 AND PICS 2/4 AND PICS 3/1 Test purpose The served user subscribes to the CDa simulation service; periodically indication of communication diversion to the diverting user using the MESSAGE request. Ensure that when the diverting user is registering the AS sends a MESSAGE request to the diverting user including the information where the call is deflected during alerting. The diverting user will be informed periodically with a MESSAGE request the information where the call is deflected during alerting. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: MESSAGE (text/plain) 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed INVITE 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE Timer TCDIV_IND expired MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 84 TSS Netw/ASNotification TP CDIV_N09_011 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/5 AND PICS 3/1 AND PICS 3/2 Test purpose The served user subscribes to the CDa simulation service; Indication of communication diversion to the diverting user using the MESSAGE request when a new outgoing communication is requested. Ensure that a diverting user will be informed with a MESSAGE request to the diverting user after the diverting user has initiated a new outgoing communication the information where the call is deflected during alerting. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes Served user receives reminder indication on outgoing communication that CDIV is currently activated = yes SIP header values: MESSAGE (text/plain) 302 Moved Temporarily: Contact: < SIP#3> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE 180 Ringing 180 Ringing 302 Moved Temporarily ACK CDa performed INVITE 2 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE INVITE 3 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK MESSAGE MESSAGE 200 OK MESSAGE 200 OK MESSAGE BYE 3 BYE 200 OK (BYE) 200 OK (BYE) BYE 1 BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 85 TSS Netw/ASNotification TP CDIV_N09_012 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/5 AND PICS 2/3 AND PICS 3/1 Test purpose The served user subscribes to the CDa simulation service; Communication Diversion Notification applies. Ensure that when the diverting user has subscribed the Communication Diversion Notification service, the served user receives a NOTIFY request containing the information regarding the current communication deflection. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: SUBSCRIBE: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-subs-info > <comm-div-selection-criteria> < originating-user-selection-criteria>SIP#1 <diverting-user-selection-criteria>SIP#2 <diverted-to-user-selection-criteria>SIP#3 < diversion-time-selection-criteria >(Date-time) < diversion-reason-selection-criteria >487 <comm-div-ntfy-trigger-criteria> <notification-time-selection-criteria>(Date/Time range PIXIT) </comm-div-info> NOTIFY: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-ntfy-info> <originating-user-info>SIP#1 <diverting-user-info>SIP#2 <diverted-to-user-info>SIP#3 <diversion-time-info> (time range <diversion-reason-info>487 <diversion-rule-info-type> <diversion-rule> (any text) </comm-div-info> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SUBSCRIBE SUBSCRIBE 200 OK SUBSCRIBE 200 OK SUBSCRIBE NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 1 INVITE INVITE 302 Moved Temporarily ACK CDi performed NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 86
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.2.1.8 Communication Forwarding on Subscriber Not Reachable (CFNRc)
|
TSS Netw/Netw/ASNotification TP CDIV_N10_001 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/7 AND PICS 3/3 Test purpose The served user subscribes to the (CFNRc) simulation service; originating user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the (CFNRc) simulation service. The origination user is not notified. The not reachable indication is sent in the CFNRc_VA final response. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE CFNRc_VA ACK Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 87 TSS Netw/ASNotification TP CDIV_N10_002 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/7 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the (CFNRc) simulation service; originating user is notified. The served user is subscribed to the (CFNRc) simulation service. When Communication Diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user. A Privacy header value history is escaped in the first and the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=503?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE CFNRc_VA ACK Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 88 TSS Netw/ASNotification TP CDIV_N10_003 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/7 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the (CFNRc) simulation service; originating user is notified, the URI of the served user is received. The served user is subscribed to the (CFNRc) simulation service. When Communication Diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user. The P-Asserted-Identity includes the URI of the diverting user. The served user allows the presentation of his/her URI to the originating user. The URI of the served user is contained in first entry of the History-Info header. A Privacy header value history is escaped in the second entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no Served user allows the presentation of his/her URI to originating user in diversion notification = yes SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=503?Privacy=history>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE CFNRc_VA ACK Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 89 TSS Netw/ASNotification TP CDIV_N10_004 Reference 4.5.2.6.4/ [1] Selection expression PICS 1/7 AND PICS 3/3 AND PICS 3/4 AND PICS 3/5 Test purpose The served user subscribes to the (CFNRc) simulation service; originating user is notified, the URI of the diverted- to user is received. The served user is subscribed to the (CFNRc) simulation service. When Communication Diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user. The 181 (Call Is Being Forwarded) response contains the P-Asserted-Identity header field and Privacy header field. The P-Asserted-Identity includes the URI of the diverting user. The served user allows the presentation of diverted- to URI to the originating user. The URI of the diverted-to user is contained in second entry of the History-Info header. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = yes Served user allows the presentation of his/her URI to originating user in diversion notification = no SIP header values: 181 Call is Being Forwarded: P-Asserted-Identity SIP#2 History-Info: <sip:SIP#2?Privacy=history >;index=1, <sip:SIP#3; cause=503>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE CFNRc_VA ACK Communication diversion is performed 181 Call is Being Forwarded INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 90 TSS Netw/ASNotification TP CDIV_N10_005 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/7 AND PICS 3/6 Test purpose The served user subscribes to the (CFNRc) simulation service; the diverted to user is not notified. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the (CFNRc) simulation service. The diverted to user is not notified. A Privacy header value history is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = no SIP header values: INVITE P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2?Privacy=history>;index=1, <sip:SIP#3; cause=503>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE CFNRc_VA INVITE 1 ACK Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 91 TSS Netw/ASNotification TP CDIV_N10_006 Reference 4.5.2.6.2/ [1] Selection expression PICS 1/7 AND PICS 3/6 Test purpose The served user subscribes to the (CFNRc) simulation service; the diverted to user is notified. URI of served user is sent. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the (CFNRc) simulation service. The diverted to user is notified. Served user allows the presentation of his/her URI to the diverted-to user. No Privacy header is escaped in the first entry of the History-Info header. Subscription options: Served user allows the presentation of his/her URI to diverted-to user = yes SIP header values: INVITE P-Asserted-Identity SIP#1 History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=503>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 INVITE CFNRc_VA ACK Communication diversion is performed INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 92 TSS Netw/ASNotification TP CDIV_N10_007 Reference 4.5.2.6.5/ [1] Selection expression PICS 1/7 AND PICS 2/3 AND PICS 3/1 Test purpose The served user subscribes to the CFNRc simulation service; Communication Diversion Notification applies. Ensure that when the diverting user has subscribed the Communication Diversion Notification service, the served user receives a NOTIFY request containing the information regarding the current communication forwarding not reachable. Subscription options: Served user receives notification that a communication has been forwarded (indication of communication diversion to the diverting user) = yes SIP header values: SUBSCRIBE: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-subs-info > <comm-div-selection-criteria> < originating-user-selection-criteria>SIP#1 <diverting-user-selection-criteria>SIP#2 <diverted-to-user-selection-criteria>SIP#3 < diversion-time-selection-criteria >(Date-time) < diversion-reason-selection-criteria >503 <comm-div-ntfy-trigger-criteria> <notification-time-selection-criteria>(Date/Time range PIXIT) </comm-div-info> NOTIFY: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-ntfy-info> <originating-user-info>SIP#1 <diverting-user-info>SIP#2 <diverted-to-user-info>SIP#3 <diversion-time-info> (time range <diversion-reason-info>503 <diversion-rule-info-type> <diversion-rule> (any text) </comm-div-info> Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SUBSCRIBE SUBSCRIBE 200 OK SUBSCRIBE 200 OK SUBSCRIBE NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 1 INVITE INVITE CFNRc_VA ACK Communication diversion is performed NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 93 Table 3 CFNRc_VA Not reachable indication CFNRc_VA_01 408 Request timeout response CFNRc_VA_02 503 Service unavailable CFNRc_VA_03 500 Server internal error
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.3 Actions at the AS of the diverted to User
|
TSS Netw/Netw/ASdiverted-to TP CDIV_N11_001 Reference 4.5.2.7/ [1] Selection expression Test purpose Previous stored History-Info header returned in a 180 Ringing. The SUT in the Idle state, receives an INVITE message for the diverted-to-user without TIR with Cause Value in the last History Index; cause-param =CAUSE_VAL defined in the table 4, the History-Info header is stored. When the SUT receives a 180 Ringing, the stored History-Info header is covered in this response without escaped Privacy header in the last index if the response does not contain a History-Info header. SIP header values: INVITE: History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x 180 Ringing History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x Comments: SIP#1 SUT SIP#2 INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASdiverted-to TP CDIV_N11_002 Reference 4.5.2.7/ [1] Selection expression Test purpose Previous stored History-Info header returned in a 181 Being Forwarded. The SUT in the Idle state, receives an INVITE message for the diverted-to-user without TIR with Cause Value in the last History Index; cause-param =CAUSE_VAL defined in the table 4, the History-Info header is stored. When the SUT receives a 181 Being Forwarded, the stored History-Info header is covered in this response without escaped Privacy header in the last index if the response does not contain a History-Info header. SIP header values: SIP header values: INVITE: History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x 181 Being Forwarded History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x Comments: SIP#1 SUT SIP#2 INVITE 1 INVITE 2 181 Call is Being Forwarded 181 Call is Being Forwarded 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 94 TSS Netw/ASdiverted-to TP CDIV_N11_003 Reference 4.5.2.7/ [1] Selection expression Test purpose Previous stored History-Info header returned in a 200 OK response. The SUT in the Idle state, receives an INVITE message for the diverted-to-user without TIR with Cause Value in the last History Index; cause-param = CAUSE_VAL defined in the table 4, the History-Info header is stored. When the SUT receives a 200 OK INVITE, the stored History-Info header is covered in this response without escaped Privacy header in the last index if the response does not contain a History-Info header. SIP header values: SIP header values: INVITE: History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x 200 OK INVITEg History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x Comments: SIP#1 SUT SIP#2 INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASdiverted-to TP CDIV_N11_004 Reference 4.5.6.2.7/ [1], 4.6.3/ [1] Selection expression PICS 4/3 Test purpose Diverted to user is subscribed to the TIR service. The SUT in the Idle state, receives an INVITE message for the diverted-to-user with TIR with Cause Value in the last History Index; cause-param = CAUSE_VAL defined in the table 4, the History-Info header is stored. When the SUT receives a 180 Ringing, the stored History-Info header is covered in this response with escaped Privacy=history header in the last index if the response does not contain a History-Info header. SIP header values: SIP header values: INVITE: History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x 180 Ringing History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL; ?Privacy=history, index=1.x Comments: SIP#1 SUT SIP#2 INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 95 TSS Netw/ASdiverted-to TP CDIV_N11_005 Reference 4,5,6,2,7/ [1], 4.6.3/ [1] Selection expression PICS 4/3 Test purpose Diverted to user is subscribed to the TIR service. The SUT in the Idle state, receives an INVITE message for the diverted-to-user with TIR with Cause Value in the last History Index; cause-param = CAUSE_VAL defined in the table 4. the History-Info header is stored. When the SUT receives a 181 Being Forwarded, the stored History-Info header is covered in this response with escaped Privacy=history header in the last index if the response does not contain a History-Info header. SIP header values: SIP header values: INVITE: History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x 181 Being Forwarded History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL; ?Privacy=history, index=1.x Comments: SIP#1 SUT SIP#2 INVITE 1 INVITE 2 181 Call is Being Forwarded 181 Call is Being Forwarded 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Netw/ASdiverted-to TP CDIV_N11_006 Reference 4,5,6,2,7/ [1] 4.6.3/ [1] Selection expression PICS 4/3 Test purpose Diverted to user is subscribed to the TIR service. The SUT in the Idle state, receives an INVITE message for the diverted-to-user with TIR with Cause Value in the last History Index; cause-param = CAUSE_VAL defined in the table 4, the History-Info header is stored. When the SUT receives a 200 OK INVITE, the stored History-Info header is covered in this response with escaped Privacy=history header in the last index if the response does not contain a History-Info header. SIP header values: SIP header values: INVITE: History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL, index=1.x 200 OK INVITE History-Info header: hi-targeted-to-uri of diverted-to user; cause=CAUSE_VAL; ?Privacy=history, index=1.x Comments: SIP#1 SUT SIP#2 INVITE 1 INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 96 Table 4 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.4 Void
| |
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.5 Actions at the user equipment
| |
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.5.1 Actions at the originating UE
|
TSS OrigUE TP CDIV_U01_001 Reference 4.5.2.1 Selection expression PICS 5/1 Test purpose Communication diversion information received in a 181 Call is Being Forwarded. Ensure that an User Equipment is able to receive a 181 Call is Being Forwarded and the 181 Response contains a History-Info header. Ensure that the information contained in the History-Info header (identities, reason of CDIV) is displayed at the device. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: 181 Call is Being Forwarded History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: UE Test Equipment INVITE INVITE 181 Call is Being Forwarded 181 Call is Being Forwarded 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 97 TSS OrigUE TP CDIV_U01_002 Reference 4.5.2.1/ [1] Selection expression PICS 5/2 Test purpose Communication diversion information received in a 180 Ringing. Ensure that an User Equipment is able to receive a 180 Ringing and the 180 Response contains a History-Info header. Ensure that the information contained in the History-Info header (identities, reason of CDIV) is displayed at the device. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: 180 Ringing History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: UE Test Equipment INVITE INVITE 181 Call is Being Forwarded 181 Call is Being Forwarded 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS OrigUE TP CDIV_U01_003 Reference 4.5.2.1/ [1] Selection expression PICS 5/3 Test purpose Communication diversion information received in a 200 OK INVITE. Ensure that an User Equipment is able to receive a 200 OK INVITE and the 200 OK final Response contains a History-Info header. Ensure that the information contained in the History-Info header (identities, reason of CDIV) is displayed at the device. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: 200 OK (INVITE) History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: UE Test Equipment INVITE INVITE 181 Call is Being Forwarded 181 Call is Being Forwarded 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 98
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.5.2 Action at the diverted to UE
|
TSS Diverted-toUE TP CDIV_U02_001 Reference 4.5.2.15/ [1] Selection expression PICS 5/4 Test purpose Communication diversion information received in an INVITE request. Ensure that an User Equipment is able to receive a INVITE request and the INVITE contains a History-Info header. Ensure that the information contained in the History-Info header (identities, reason of CDIV) is displayed at the device. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: INVITE: History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: UE Test Equipment INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Diverted-toUE TP CDIV_U02_002 Reference 4.5.2.6.2/ [1], 4.5.2.7/ [1] Selection expression PICS 5/5 Test purpose The User Equipment is able to sent a History-Info header in 180 response. Ensure that an User Equipment is able to sent a History-Info header in a 180 provisional response containing a History-Info header received in the initial INVITE. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: INVITE: History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 180 Ringing: History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: UE Test Equipment INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 99 TSS Diverted-toUE TP CDIV_U02_003 Reference 4.5.2.6.2/ [1], 4.5.2.7/ [1] Selection expression PICS 5/6 Test purpose The User Equipment is able to sent a History-Info header in 200 OK INVITE final response. Ensure that an User Equipment is able to sent a History-Info header in a 200 OK final response containing a History-Info header received in the initial INVITE. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: INVITE: History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 200 OK: History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: UE Test Equipment INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE)
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.2.5.3 Actions at the diverting UE
|
TSS DivertingUE TP CDIV_U03_001 Reference 4.5.2.6.4/ [1] Selection expression PICS 5/7 Test purpose Communication diversion using the MESSAGE request method. Ensure that the User Equipment is able to receive a MESSAGE request containing the notification about a performed communication diversion by the network. Ensure that the text contained in the text/plain MIME extension is displayed. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: MESSAGE Content-Type: text/plain … text (PIXIT) … Comments: UE Test Equipment MESSAGE MESSAGE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 100 TSS DivertingUE TP CDIV_U03_002 Reference 4.5.2.6.5/ [1], 4.10/ [1] Selection expression PICS 5/8 Test purpose Communication diversion using the CDIVN service, subscription of the service. Ensure that the User Equipment is able to subscribe the communication diversion notification service (CDIVN). A SUBSCRIBE request is sent. The Event header contains the package name "comm-div-info" and a MIME body containing a XML instance of http://uri.etsi.org/ngn/params/xml/comm-div-info. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: SUBSCRIBE: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-subs-info > <comm-div-selection-criteria> < originating-user-selection-criteria > <diverting-user-selection-criteria> <diverted-to-user-selection-criteria> < diversion-time-selection-criteria > < diversion-reason-selection-criteria > CAUSE_VAL <comm-div-ntfy-trigger-criteria> <notification-time-selection-criteria> </comm-div-info> NOTIFY: Event:comm-div-info Comments: UE Test Equipment SUBSCRIBE SUBSCRIBE 200 OK (SUBSCRIBE) 200 OK (SUBSCRIBE) NOTIFY NOTIFY 200 OK (NOTIFY) 200 OK (NOTIFY) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 101 TSS DivertingUE TP CDIV_U03_003 Reference 4.5.2.6.5/ [1], 4.10/ [1] Selection expression PICS 5/8 Test purpose Communication diversion using the CDIVN service, notification applies. Ensure that the User Equipment is able to receive notification based on the communication diversion notification service (CDIVN). A NOTIFY request is received. The Event header contains the package name "comm-div-info". The Event header contains the package name "comm-div-info" and a MIME body containing a XML instance of "http://uri.etsi.org/ngn/params/xml/comm-div-info". Ensure that the notification is displayed at the User Equipment. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 5. SIP header values: SIP header values: NOTIFY: Event:comm-div-info application/comm-div-info+xml <comm-div-info> <comm-div-ntfy-info> <originating-user-info> <diverting-user-info> <diverted-to-user-info> <diversion-time-info> <diversion-reason-info> CAUSE_VAL <diversion-rule-info-type> <diversion-rule> (any text) </comm-div-info> Comments: UE Test Equipment CDIVN is activated NOTIFY NOTIFY 200 OK (NOTIFY) 200 OK (NOTIFY) Table 5 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 102
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.3 Interaction with other services
| |
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.3.1 Terminating Identification Presentation (TIP)
|
TSS Interaction/TIP TP CDIV_N12_001 Reference 4.6.2 Selection expression PICS 4/3 Test purpose The served user subscribes to the CDIV simulation service; the P-Asserted header is passed on unchanged. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CDIV simulation service. Ensure that a P-Asserted-Identity and History header field received in the diverting AS is passed unmodified to the originating entity. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 6. SIP header values: 180: Ringing: P-Asserted-Identity with the URI of the diverted-to user, Privacy is not "id" and not "header" History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 200 OK: P-Asserted-Identity with the URI of the diverted-to user, Privacy is not "id" and not "header" History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause= CAUSE_VAL ;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed (CFU, CFB, CFNR, CD, CFNL, CFNRc) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) Table 6 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 103
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.3.2 Terminating Identification Restriction (TIR)
|
TSS Interaction/TIR TP CDIV_N13_001 Reference 4.6.3 Selection expression PICS 4/3 AND PICS 4/4 Test purpose The served user subscribes to the CDIV simulation service; the diverted-to URI is not sent to the originating user. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CDIV simulation service. A P-Asserted-Identity and History header field received in the diverting AS is passed unmodified to the originating entity. Ensure that if the served (diverting) user selects the option that the originating user is notified, but without the diverted-to number, then the AS shall not send the connected user's identity when the communication is answered. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 7. Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no TIR subscription: Originating user has the override category = no SIP header values: 200 OK 1: P-Asserted-Identity with the URI of the diverted-to user History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=302>;index=1.1 200 OK 2: P-Asserted-Identity with the URI of the diverted-to user History-Info: <sip:SIP#2>;index=1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed (CFU, CFB, CFNR, CD, CFNL, CFNRc) INVITE 180 Ringing 180 Ringing 200 OK 1 (INVITE) 200 OK 2(INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) Table 7 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 104 TSS Interaction/TIR TP CDIV_N13_002 Reference 4.6.3 Selection expression PICS 4/3 AND PICS 4/4 Test purpose The served user subscribes to the CDIV simulation service, the diverted-to URI is sent to the originating user if the terminating user has the override category. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CDIV simulation service. A P-Asserted-Identity and History header field received in the diverting AS is passed unmodified to the originating entity. The originating user has the "Override category". Ensure that if the served (diverting) user selects the option that the originating user is notified, but without the diverted-to number, then the AS shall send the connected user's identity when the communication is answered. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 8 Subscription options: Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes Served user allows the presentation of diverted to URI to originating user in diversion notification = no TIR subscription: Originating user has the override category = yes SIP header values: 200 OK 1: P-Asserted-Identity with the URI of the diverted-to user History-Info: <sip:SIP#2>;index=1, <sip:SIP#3; cause=302>;index=1.1 200 OK 2: P-Asserted-Identity with the URI of the diverted-to user History-Info: <sip:SIP#2>;index=1 <sip:SIP#3; cause=302>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed (CFU, CFB, CFNR, CD, CFNL, CFNRc) INVITE 180 Ringing 180 Ringing 200 OK 1 (INVITE) 200 OK 2(INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) Table 8 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 105
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.3.3 Originating Identification Presentation (OIP)
|
TSS Interaction/OIP TP CDIV_N14_001 Reference 4.6.4 Selection expression PICS 4/1 Test purpose The diverted-to user subscribes to the OIP simulation service. When a communication has been diverted and the diverted-to user has been provided with the originating identification presentation simulation service, the S-CSCF of the diverted-to user shall sent the number of the original originating user, if this originating user has not subscribed to or invoked the originating identification restriction simulation service. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 9. SIP header values: INVITE: P-Asserted-Identity with the URI of the originating user Privacy value "id" or "header" or "user" not present History-Info: <sip:SIP#2>;index=1 <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed (CFU, CFB, CFNR, CD, CFNL, CFNRc) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) Table 9 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 106
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.3.4 Originating Identification Restriction (OIR)
|
TSS Interaction/OIR TP CDIV_N15_001 Reference 4.6.5 Selection expression PICS 4/1 AND PICS 4/2 Test purpose The served user subscribes to the CDIV simulation service; the terminating user does not have the override category. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFU simulation service. When the originating identification restriction simulation service has been invoked, the originating user's address shall not be presented to the diverted-to user. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 10. SIP header values: INVITE 1: P-Asserted-Identity, Privacy "id" INVITE 2: P-Asserted-Identity, Privacy "id" History-Info: <sip:SIP#2>;index=1 <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed (CFU, CFB, CFNR, CD, CFNL, CFNRc) INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) TSS Interaction/OIR TP CDIV_N15_002 Reference 4.6.5 Selection expression PICS 4/1 AND PICS 4/2 Test purpose The served user subscribes to the CDIV simulation service, the terminating user has the override category. Ensure that the communication is forwarded to the diverted to user if the served user is subscribed to the CFU simulation service. When the originating identification restriction simulation service has been invoked, the originating user's address shall be presented to the diverted-to user, the diverted-to user has an override capability. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 10. SIP header values: INVITE 1: P-Asserted-Identity, Privacy "id" INVITE 2: P-Asserted-Identity History-Info: <sip:SIP#2>;index=1 <sip:SIP#3; cause= CAUSE_VAL>;index=1.1 Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 Communication diversion is performed (CFU, CFB, CFNR, CD, CFNL, CFNRc) INVITE 2 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 107 Table 10 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable 5.3.5 Anonymous Communication Rejection and Communication Barring (ACR/CB) TSS Interaction/ACR-CB TP CDIV_N16_001 Reference 4.6.9 Selection expression PICS 4/6 Test purpose CDIV the diverted-to user has subscribed to a call barring service "inhibition of incoming forwarded communication". Ensure that the communication is rejected with 603 (Decline) if the called user has subscribed to the call barring service "inhibition of incoming forwarded communication" and the received INVITE contains a History-Info header indication this call is a forwarded. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 11. SIP header values: INVITE: History-Info: <sip:SIP#1;index=1, <sip:SIP#2; cause= CAUSE_VAL>;index=1.1 Comments: SIP#1 Terminating AS SIP#2 INVITE 1 603 (Decline) ACK Table 11 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 108 TSS Interaction/ACR-CB TP CDIV_N16_002 Reference 4.6.9 Selection expression PICS 4/5 Test purpose The served user has subscribed to a call barring service Outgoing Communication Barring (OCB). Ensure that the communication is rejected with 603 (Decline) if the called user has subscribed to the call barring service Outgoing Communication Barring (OCB) if the forwarded to number is restricted. The Cause Value in the latest History Index; cause-param =CAUSE_VAL defined in the table 12. SIP header values: Comments: SIP#1 SUT SIP#2 (served user) SIP#3 INVITE 1 603 (Decline) ACK Table 12 Cause value Redirecting Reason 404 Unknown 302 Unconditional 486 User busy 408 No reply 480 Deflection immediate 503 Mobile subscriber not reachable 487 Deflection during alerting Cause Value in History Index; cause-param = "cause" EQUAL CAUSE_VAL 503 Call diversion information Subscriber not reachable ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 109
|
acce4c0496385459b0879a9e3a000bdd
|
186 014-2
|
5.3.6 Explicit Communication Transfer (ECT)
|
TSS Interaction/ECT TP CDIV_N17_001 Reference 4.6.10.1.2 Selection expression PICS 4/7 Test purpose Forwarded Communication, handling of Refer-To header. Ensure that a forwarded communication is able to transfer and the Refer-To header of the REFER request sent to the Transferee contains a Refer-To header containing the CDIV Session Identifier. The CFU, CFB, CFNR, CD CFNL and CFNRc apply. SIP header values: REFER 1: Refer-To:<SIP#4> REFER 2: Refer-To: <CDIV Session Identifier> Configuration: SIP#1: originating user, Transferer SIP#2: CDIV served user, (Transferee) SIP#3: CDIV diverted-to user, Transferee SIP#4: Transfer target Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SIP#4 Forwarded communication is active REFER 1 REFER 2 REFER 2 202 Accepted 202 Accepted 202 Accepted INVITE INVITE INVITE INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK BYE ACK 200 OK BYE ACK Transferred communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 110 TSS Interaction/TIP TP CDIV_N17_002 Reference 4.6.10.1.3 Selection expression PICS 4/7 Test purpose Forwarded Communication, handling of Refer-To header. Ensure that a forwarded communication is able to transfer and the AS replaces the Request URI (CDIV Session Identifier) of the INVITE request received from the Transferee with the value of the Transfer target previously stored from the Refer-To header received in the REFER request and sends the INVITE request toward the Transfer target. The INVITE request contains also the History-Info header. The CFU, CFB, CFNR, CD CFNL and CFNRc apply. SIP header values: INVITE 1: Request URI: <CDIV Session Identifier> INVITE 2: Request URI:<SIP#4> History-Info: <sip:SIP#2 >;index=1, <sip:SIP#3; cause=302>;index=1.1 Configuration: SIP#1: originating user, Transferer SIP#2: CDIV served user, (Transferee) SIP#3: CDIV diverted-to user, Transferee SIP#4: Transfer target Comments: SIP#1 SUT SIP#2 (served user) SIP#3 SIP#4 Forwarded communication is active REFER REFER REFER 202 Accepted 202 Accepted 202 Accepted INVITE 1 INVITE 1 INVITE 2 INVITE 2 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK BYE 200 OK 200 OK 200 OK BYE ACK ACK Transferred communication BYE BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 014-2 V2.1.1 (2009-05) 111 History Document history V2.1.1 May 2009 Publication
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
1 Scope
|
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Testsuite Structure and Testpurposes defined in TS 186 009-2 [1]. The TSS&TP have been developed to test the interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol (BICC) or ISDN User Part, Profiles A and B. The ATS is sometimes referred to in the present document as "SIP-ISUP-Interworking ATS". The test notation used in the ATS is TTCN-3 (ES 201 873-1 [8]). The following test specification- and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (IXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
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. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 6
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
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 186 009-2 (Release 2): "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN)subsystem and Circuit Switched (CS) networks; Part 2: Test Suite Structure and Test Purposes (TSS&TP) ". NOTE: The latest version v2.y.z applies [2] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [3] ETSI TS 186 009-1 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN)subsystem and Circuit Switched (CS) networks; Part 1: Protocol Implementation Conformance Statement (PICS)". NOTE: The latest version v2.y.z applies [4] ETSI TS 129 163 (V7.12.0): "Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163 Release 7).". [5] ETSI TS 129 527: " Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; Endorsement of the SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks [3GPP TS 29.163 (Release 7), modified] (3GPP TS 29.527 version 8.2.0 Release 8)". [6] ITU-T Recommendation Q.2150.1 (2001): "Signalling Transport Converter on MTP3 and MTP3b". [7] ETSI TS 102 027-3 (V3.1.1): "Methods for Testing and Specification (MTS); Conformance Test Specification for SIP (IETF RFC 3261); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma". [8] ETSI ES 201 873-1 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [9] ETSI ES 201 873-5 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)". [10] ETSI ES 201 873-6 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)". [11] ISO/IEC 9646-1 (1992): "Information Technology - Open Systems Interconnection - Conformance Testing Methodology and Framework - Part 1: General concepts". [12] ISO/IEC 9646-7 (1994): "Conformance testing methodology and framework - Part 7: Implementation Conformance Statement". [13] ITU-T Recommendation Q.761 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". [14] ITU-T Recommendation Q.762 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". [15] ITU-T Recommendation Q.763 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP); ISDN user part formats and codes". [16] ITU-T Recommendation Q.764 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 7 [17] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [18] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". [19] ETSI EN 300 356-1 (V4.2.1): "Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 for the international interface; Part 1: Basic services [ITU-T Recommendations Q.761 to Q.764 (1999) modified]". [20] ITU-T Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic call control". [21] ETSI EN 300 097-1: "Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1: Protocol specification ". [22] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". [23] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
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. Not applicable.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
3 Definitions and abbreviations
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in: • SIP/ISUP interworking reference specification is defined in TS 129 163 [4] and TS 129 527 [5]; • ISDN layer 3 reference specification is defined in EN 300 356-1 [19]; • ISDN User Part (ISUP) reference specification are defined in EN 300 356-1 [19]; • ISO/IEC 9646-1 [11] and ISO/IEC 9646-7 [12]; • ES 201 873-1 [8] (TTCN-3). and the following apply: Abstract Test Case (ATC): complete and independent specification of the actions required to achieve a specific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state and ending in a stable testing state Abstract Test Method (ATM): description of how an IUT is to be tested, given at an appropriate level of abstraction to make the description independent of any particular realization of a Means of Testing, but with enough detail to enable abstract test cases to be specified for this method Abstract Test Suite (ATS): test suite composed of abstract test cases Implementation Under Test (IUT): implementation of one or more OSI protocols in an adjacent user/provider relationship, being part of a real open system which is to be studied by testing Means of Testing (MOT): combination of equipment and procedures that can perform the derivation, selection, parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a conformance log ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 8 PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes the PICS PIXIT proforma: document, in the form of a questionnaire, which when completed for the IUT becomes the PIXIT point of Control and Observation: point within a testing environment where the occurrence of test events is to be controlled and observed, as defined in an Abstract Test Method pre-test condition: setting or state in the IUT which cannot be achieved by providing stimulus from the test environment Protocol Implementation Conformance Statement (PICS): statement made by the supplier of a protocol claimed to conform to a given specification, stating which capabilities have been implemented Protocol Implementation eXtra Information for Testing (PIXIT): statement made by a supplier or implementor of an IUT (protocol) which contains or references all of the information related to the IUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT SIP number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [18] System Under Test (SUT): real open system in which the IUT resides
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ITU-T Recommendation Q.762 [14] and the following apply: ASP Abstract Service Primitive NOTE: Exchanged between entities inside the TS or between the user of the ATS (operator) and the TS. ATC Abstract Test Case ATM Abstract Test Method ATM Asynchroneous Transfer Mode ATS Abstract Test Suite BCI Backward Call Indicators BICC Bearer Independent Call Control CIC Circuit Identification Code DSS1 Digital Subscriber System No. 1 EDS Encoding/Decoding System FCI Forward Call Indicators G/W Type 1 GateWay Type 1 G/W Type 2 GateWay Type 1 IETF Internet Engineering Task Force ISDN Integrated Services Digital Network ISUP ISDN User Part IUT Implementation Under Test IWU InterWorking Unit LT Lower Tester MOT Means Of Testing MTP Message Transfer Part NCI Nature of Connection Indicators NGN Next Generation Network OCN Original Called Number PA Platform Adapter PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing PTC Parallel Test Component RDN Redirecting Number RNN Redirection Number SA System Adapter SDP Session Description Protocol SIP Session Initiation Protocol ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 9 SN Signalling Node STC Signalling Transport Converter NOTE: According to ITU-T Recommendation Q.2150.1 [6]. SUT System Under Test TC Test Case TCI TTCN-3 Control Interface TCP Test Coordination Procedures TD Test Description TE Test Equipment TISPAN Telecommunications and Internet converged Services and Protocols for Advanced Networking TL Test Logging TM Test Management TMR Transmission Medium Requirement TP Test Purpose TS Test System TSS Test Suite Structure TSS&TP Test Suite Structure and Test Purposes TTCN Tree and Tabular Combined Notation TTCN-3 Testing and Test Control Notation edition 3
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4 Abstract Test Method (ATM)
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.1 Network architecture
|
Figures 1 and 2 show the network architecture for SIP-ISUP/BICC Interworking Units. Figure 1 shows the network architecture for SIP-ISUP Interworking. SIP ISUP <-----------------------------------------> IWU <------------------------------------------> Figure 1: Interworking between SIP and ISUP Figure 2 shows the network architecture for SIP-BICC Interworking. SIP BICC <------------------------------------------> <-----------------------------------------> IWU <------------------------------------------> ATM bearer control Figure 2: Interworking between SIP and BICC NOTE: There are 3 profiles defined for IWU: Profile A, Profile B and Profile C (out of scope of the present document). Figures 1 and 2 in clause 5 of TS 186 009-2 [1] show the substructures of the IWU for Profiles A and B in terms of gateways and signalling nodes. In the ATS the SUT (IWU) represents either a G/W Type 1 (Profile A) or the combination of G/W Type 2 and SN (Profile B). ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 10
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.2 Protocol architecture
|
Figures 1 and 2 above show that there are 2 interfaces of the IWU (representing the SUT in the testing environment described in the present document): a SIP interface and an ISUP- or BICC interface. Since the ISUP and BICC protocols are very similar (the latter one being derived from ISUP), they are treated here as one protocol. NOTE: No signalling is used within the SIP-ISUP-Interworking ATS to control the ATM bearer in case of BICC (ASPs are used). Figure Error! Bookmark not defined. shows the protocol architecture in 2 branches. SUT IUT IUT SIP/IMS Extension ISUP BICC SIP RFC 3261 STC STC Compression algorithms (2) UDP TCP MTP 3 MTP 3b Security Algoritms (2) MTP Layer 2 AAL IPV4/IPV6 (1) (LAN) G.703/G.704 ATM NOTE 1: Both IPV4 and IPV6 addressing should be supported. NOTE 2: Optional security and compression algorithms should be supported. Figure 3: Protocol architecture of the SIP-ISUP-Interworking ATS
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3 Test architecture
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3.1 Interconnection of TS and SUT
|
Figure 4 shows the interconnection of TS and SUT in terms of signalling message flows. SIP SUT ISUP/ BICC <------------------------> <------------------------> IWU <------------------------> ATM bearer control (only for BICC) Test System Figure 4: Interconnection of TS and SUT ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 11
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3.2 Test system architecture
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3.2.1 General
|
Test systems that implement this ATS shall conform to the requirements as defined in this clause.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3.2.2 Structure
|
An abstract architecture for a test system (TS) implementing a TTCN-3 ATS is displayed in figure 5 and also stated in ES 201 873-5 [9]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adapter (SA) Platform Adapter (PA) Figure 5: Abstract Test System Architecture A TS has two interfaces, the TTCN-3 Control Interface (TCI) and the TTCN-3 Runtime Interface (TRI), which specify the interface between Test Management (TM) and TTCN-3 Executable (TE) entities, and TE, SUT Adapter (SA) and Platform Adapter (PA) entities, respectively. Out of these two interfaces the TRI has been standardized in ES 201 873-5 [9], whereas the specification and implementation of the TCI is in ES 201 873-6 [10]. The part of TS that deals with interpretation and execution of TTCN-3 modules, i.e. the Executable Test Suite (ETS), is shown as part of the TTCN-3 Executable (TE). This ETS corresponds either to the executable code produced by a TTCN-3 compiler or a TTCN-3 interpreter from the TTCN-3 ATS in a TS implementation. The remaining part of the TS, which deals with any aspects that cannot be concluded from information being present in the TTCN-3 ATS alone, can be decomposed into Test Management (TM), SUT Adapter (SA) and Platform Adapter (PA) entities. In general, these entities cover a TS user interface, test execution control, test event logging, communication of test data with the SUT, and timer implementation. The part of SA used for SIP message transfer shall implement the TRI adaptation as well as the SIP transport protocol architecture described in clause 4.2. The Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, with the TE and Test Logging (TL) entity within the TM shall comply with the conventions defined in clause 4.3.2 of TS 102 027-3 [7]. The part of SA used for ISUP/BICC message transfer shall implement the TRI adaptation as well as the ISUP/BICC transport protocol architecture described in clause 4.2. For BICC, in addition, the ATM bearer control shall be implemented. The Encoding/Decoding System (EDS) entity, as far as applied to ISUP/BICC messages, shall comply with the conventions and requirements defined in the following clauses. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 12
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA)
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3.2.3.1 Control of the SUT Adapter (SA) by using ASPs
|
Table 1 lists the ASPs used in the SIP-ISUP-Interworking ATS. Detailed descriptions of the ASPs together with their parameters follow. Table 1: List of ASPs ASP Name Short description InitializeIsupBicc_req Initialize ISUP/BICC part of the test system. InitializeIsupBicc_cnf Answer whether all necessary ISUP/BICC test system initializations have been successfully performed. ISUP_BICC_MSG_req Used to send an ISUP/BICC message. ISUP_BICC_MSG_ind Used to receive an ISUP/BICC message. BearerSetup_req For BICC: request TS to setup the bearer connection between TS and SUT. BearerSetup_acc For BICC: answer to BearerSetup_req. BearerSetup_ind For BICC: indication that the bearer has been setup. BearerRelease_req For BICC: request to release established bearer connection. BearerRelease_cnf For BICC: confirmation that the requested bearer is released. BearerRelease_ind For BICC: indication that the bearer has been released (when no BearerRelease_req has been issued before). s_IsupBicc_conversation Check that conversation is possible on the bearer. s_IsupBicc_ringing Check that ringing occurs. Tables 2 to 13 contain the descriptions of the ASPs used in the present document, including the ASP parameters (if any) and the types of values these may assume. No ASP parameter is optional. Table 2: ISUP_BICC_MSG_req ASP structure ASP Name: ISUP_BICC_MSG_req Port: sysPort Direction: TE->SA Description: ASP used to send an ISUP/BICC message. Parameter Type Description isupBiccSelection SelectIsupOrBicc Selector used to distinguish between ISUP and BICC testing. "00000000"B means "ISUP" and any other value means "BICC". serviceIndicatorOctet ServiceIndicatorOctet The contents of this ASP parameter is only evaluated in SA if ISUP has been selected in "isupBiccSelection". routingLabel RoutingLabel The contents of this ASP parameter is only evaluated in SA if ISUP has been selected in "isupBiccSelection". circuitIdentityCode CircuitIdentityCode The contents of this ASP parameter is only evaluated in SA if ISUP has been selected in "isupBiccSelection". callInstanceCode CallInstanceCode The contents of this ASP parameter is only evaluated in SA if BICC has been selected in "isupBiccSelection". iSUP_BICC_MSG ISUP_BICC_MSG ISUP_BICC_MSG is a union over all ISUP/BICC message bodie types, where a message body starts with the "message type" field. This body is common for ISUP and BICC messages. When using this ASP, a particular message(body) template is selected from the union for transmission. Comments: The SA takes from the ASP, depending on the value of parameter "isupBiccSelection", either the ordered combination of "serviceIndicatorOctet", "routingLabel" and "circuitIdentityCode" (ISUP), or "callInstanceCode" (BICC"), puts it in front of encoded parameter "iSUP_BICC_MSG", and sends the so constructed message at the ISUP or BICC interface respectively. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 13 Table 3: ISUP_BICC_MSG_ind ASP structure ASP Name: ISUP_BICC_MSG_ind Port: sysPort Direction: SA->TE Description: ASP used to receive an ISUP/BICC message. Parameter Type Description isupBiccSelection Bit8 Selector used to distinguish between ISUP and BICC testing. "00000000"B means "ISUP" and any other value means "BICC". serviceIndicatorOctet ServiceIndicatorOctet The contents of this ASP parameter is only evaluated in TE if ISUP has been selected in "isupBiccSelection". routingLabel RoutingLabel The contents of this ASP parameter is only evaluated in TE if ISUP has been selected in "isupBiccSelection". circuitIdentityCode CircuitIdentityCode The contents of this ASP parameter is only evaluated in TE if ISUP has been selected in "isupBiccSelection". callInstanceCode CallInstanceCode The contents of this ASP parameter is only evaluated in TE if BICC has been selected in "isupBiccSelection". iSUP_BICC_MSG ISUP_BICC_MSG ISUP_BICC_MSG is a union over all ISUP/BICC message bodie types, where a message body starts with the "message type" field. This body is common for ISUP and BICC messages. When using this ASP, a particular message(body) template is selected from the union for receive matching. Comments: The SA takes from the received message, depending on the value of parameter "isupBiccSelection", either the ordered combination of "serviceIndicatorOctet", "routingLabel" and "circuitIdentityCode" (ISUP), or "callInstanceCode" (BICC"), and puts it into the associated ASP parameters. The complementary ASP parameters "callInstanceCode" (ISUP) and combination of "serviceIndicatorOctet", "routingLabel" and "circuitIdentityCode" (BICC) are filled by the SA with "0"-bits according to the lengths of their types. The TE does not evaluate the contents of the complementary parameters (but needs the correct lengths to identify the start of "iSUP_BICC_MSG". The received message (body) is put by the SA into parameter "iSUP_BICC_MSG" and is matched in the ATS with an according receive template. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 14 Table 4: InitializeIsupBicc_req ASP structure ASP Name: InitializeIsupBicc_req Port: IsupBiccPort Direction: TE->SA Description: Initialize ISUP/BICC part of the test system. Parameter Type Description isupBiccSelection Bit8 Selector used to distinguish between ISUP and BICC testing. "00000000"B means "ISUP" and any other value means "BICC". ts_pointCode Bit14 Signalling point code of the TS (ISUP). sut_pointCode Bit14 Signalling point code of the SUT (ISUP). ts_address_sip octetstring Address (e.g. IP) of the TS (SIP side). The use of this address is to enable the TS to communicate with the SUT at the SIP side to establish and maintain the lower layer connections. ts_address_isup_bicc octetstring Address (e.g. IP) of the TS (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. sut_address_sip octetstring Address (e.g. IP) of the SUT (SIP side). The use of this address is to enable the TS to communicate with the SUT at the SIP side to establish and maintain the lower layer connections. sut_address_isup_bicc octetstring Address (e.g. IP) of the SUT (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. Comments: This ASP is used at the beginning of each test case to initiate the necessary initialization of the test system, particularly the interfaces to the SUT. If parameter isupBiccSelection indicates "bicc", the values of parameters "ts_pointCode" and "sut_pointCode" shall be ignored by the SA. If parameter isupBiccSelection indicates "isup", the values of parameters "ts_address_isup_bicc" and "sut_address_isup_bicc" may be ignored, if they are not necessary. Among the initializing actions there shall be: a) Verification that the ISUP/BICC link is operable between SUT and TS. b) Verification that the TS is ready to send and receive SIP messages. NOTE: It is a matter of TS implementation whether the TS, upon this request, sets up and initializes lower layer connections, if these are not setup. Other initialization actions may be TS-specific. Table 5: InitializeIsupBicc_cnf ASP STRUCTURE ASP Name: InitializeIsupBicc_cnf Port: sysPort Direction: LT->TTCN Description: Answer whether all necessary ISUP/BICC test system initializations have been successfully performed. The result can be positive or negative. The result will be positive only if the TS is able to send and receive messages at the ISUP/BICC-interface of the SUT. Parameter Type Description result boolean Indicating success or non-success of the whole initialization. Comments: ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 15 Table 6: BearerSetup_req ASP structure ASP Name: BearerSetup_req Port: IsupBiccPort Direction: TE->SA Description: For BICC: request TS to setup the bearer connection between TS and SUT. Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. Comments: Table 7: BearerSetup_acc ASP structure ASP Name: BearerSetup_acc Port: IsupBiccPort Direction: SA->TE Description: For BICC: answer to BearerSetup_req. The answer can be positive (bearer connection setup successful) or negative (bearer connection setup failed). Parameter Type Description result boolean The answer is positive when the bearer connection setup was successful and negative when the bearer connection setup failed. Comments: Table 8: BearerSetup_ind ASP structure ASP Name: BearerSetup_ind Port: IsupBiccPort Direction: SA->TE Description: For BICC: indication that the bearer has been setup. Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. Comments: Table 9: BearerRelease_req ASP structure ASP Name: BearerRelease_req Port: bcPort Direction: TE->SA Description: For BICC: request to release the established bearer connection. Parameter Type Description cic CIC Circuit identity code identifying the bearer connection. Comments: Table 10: BearerRelease_cnf ASP structure ASP Name: BearerRelease_cnf Port: bcPort Direction: SA->TE Description: For BICC: confirmation that the requested bearer is released. Parameter Type Description result boolean Indication of whether the bearer is successfully released. Comments: At release collision the result is still "true". ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 16 Table 11: BearerRelease_ind ASP structure ASP Name: BearerRelease_ind Port: bcPort Direction: SA->TE Description: For BICC: indication that the bearer has been released (when no BearerRelease_req has been issued before). Parameter Type Description cic CIC Circuit identity code identifying the bearer connection. Comments: Table 12: s_IsupBicc_conversation ASP structure ASP Name: s_IsupBicc_conversation Port: operatorPort_IsupBicc Direction: SA-<>TE Description: Check that conversation is possible on the through-connected bearer. Parameter Type Description text charstring Request operator to check the conversation. answer boolean Check result entered by the operator. Comments: This ASP has been implemented as a signature. "text" is an "input" parameter and "answer" is an output parameter. Table 13: s_IsupBicc_ringing ASP structure ASP Name: s_IsupBicc_ringing Port: operatorPort_IsupBicc Direction: SA-<>TE Description: Check that occurs on the through-connected bearer. Parameter Type Description text charstring Request operator to check the ringing. answer boolean Check result entered by the operator. Comments: This ASP has been implemented as a signature. "text" is an "input" parameter and "answer" is an output parameter.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3.2.3.2 Sending and receiving SIP and ISUP/BICC messages
|
4.3.2.3.2.1 General Before starting a test case, the SA shall be prepared to provide the transport of SIP and ISUP/BICC messages by establishing appropriate connections on the lower layers (see figure Error! Bookmark not defined.). 4.3.2.3.2.2 Sending and receiving SIP/IMS messages In order to forward messages received into the SA to the test suite and to send them to the SUT a clear and unique association between the TTCN-3 TSI ports and the real IP and port addresses used by the SUT is needed during test execution. The SA retrieves this information via values of TTCN-3 module parameters, i.e. PIXITs, and mappings to TSI ports, i.e. triMap operation invocations. TSI port names are the main source for the relating TSI ports with SUT IP addresses and ports. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 17 The following table provides the relationships for TSI ports and SUT IP addresses and ports: Table 14: TSI port mappings TSI port SUT (IP address, Port Id) Test system (IP address, Port id) IMSCN1 PX_IMS_SUT_IMGCF_IPADDR, PX_IMS_SUT_IMGCF_PORT PX_IMS_TS_ICSCF_IPADDR, PX_IMS_TS_ICSCF_PORT NOTE 1: TSI portnames are defined in SipIsup_TestSystem module as part of the ImsComponent type. Module parameters for the address information are defined in LibIms_PIXIT module (see clause 5.3.1 for complete list of modules). NOTE 2: For test configuration a TTCN-3 configuration functions has been implemented with the required mapping and unmapping statements (see clause 5.3.1 for complete list of modules), e.g. f_cf_imsIsupUp map one Ims related port of the test system to the SUT and one Isup port to the SUT IP/E1 module. 4.3.2.3.2.3 Security and messages compression feature Security transport layer, and signalling compression may be used transparently to the ATS. 4.3.2.3.2.4 Additional SA constraints In order to execute this test suite the SA should support: - communication channel handling (at least UDP and possibly also TCP) - IPv4 transport.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
4.3.2.3.3 Encoding/Decoding System requirements
|
4.3.2.3.3.1 Encoding/Decoding System requirements for basic SIP messages/headers SIP is a text-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use a EDS to parse received encoded messages into TTCN-3 type structures and values, and encode structured TTCN-3 type structures and values into encoded messages. This EDS is not part of the ATS. Still all encoded messages, i.e. the messages as they are transmitted by the SA to or received by the SA from the SUT, shall be logged. The following terms shall be used for the conventions defined below: Syntactic delimiter syntactic delimiters are characters like "=" or ";" that are used to separate encoded values. LWS linear white spaces as defined in RFC 3261 [17]. Parameter name name of header parameters as defined in RFC 3261 [17]. Parameter value the value of a parameter as defined in RFC 3261 [17]. Undefined method an undefined method is a method other than: "INVITE", "ACK", "OPTIONS", "BYE", "CANCEL" and "REGISTER". Undefined header an undefined header is a header other than general-header, entity-header, request-header and response header as defined in RFC 3261 [17]. Unexpected header an unexpected header is a header, which shall not be present in a specific request message. This definition complies to the definition of NOT APPLICABLE in RFC 3261 [17], section 20 for request messages. Decoder requirements TTCN-3 fields should not contain syntactic delimiters like white space, semicolon, equal characters etc. in fully decoded fields. Instead the information provided by a parser shall be used to build the decoded message in TTCN-3. Decoded messages shall use the TTCN-3 enumeration types where ever appropriate, e.g. for the method and the header field name. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 18 For charstring fields the following decoding rules shall be applied by the EDS: 1) Subsequent LWS shall compress to a single space character " ". 2) Decoded parameter names shall use only lower case letters. 3) Parameter values containing an integer value shall be decoded to a TTCN-3 integer value where a TTCN-3 integer type is used for a SIP parameter value. The following decoding rules shall be applied by the EDS to each received message in the following order: 1) In case a request message indicating an undefined method is received by the test system, the message shall not be passed in the TE to the ETS. However the message is subject to logging as defined in clause 4.3.2.3.3 ("Logging conventions"). 2) In case an undefined header has been received the header field shall be decoded as UndefinedHeader field. RFC 3261 [17] allows for multiple header field values of the same kind to either arrive in one or multiple occurrences of the corresponding header field. The SIP ATS has been written assuming only the first format. Therefore, should the EDS receive multiple header fields of the same kind in a SIP message, e.g. of a Via header field, it shall convert them into the equivalent single header field with multiple values. This can be achieved by adding the value of, e.g. the second received Via header field as the last value to the value(s) of the first Via header field. Encoder requirements Encoders shall follow all encoding rules that are defined in RFC 3261 [17] when encoding structured values received from templates. This applies in particular to but it is not restricted to section 7.3.1 of RFC 3261 [17]. Values of type Raw shall be send to the SUT without any modification. 4.3.2.3.3.2 Encoding/Decoding System requirements for ISUP/BICC 4.3.2.3.3.2.1 General ISUP/BICC messages are sent and received in the test suite by embedding them in ASPs ISUP_BICC_MSG_req and ISUP_BICC_MSG_ind respectively. The ASPs contain all information to route the ISUP/BICC messages to/from the SUT. ISUP messages and parameters are structured by using tables (see ITU-T Recommendation Q.763 [15]). NOTE 1: The term "parameter" is used as defined in the ISUP protocol context. It corresponds e.g. to the term "Information Element" in other protocols. All structure elements are bitstrings, hexstrings or octetstrings. For ISUP message/parameter elements a specific way is defined to extend bitstring- or hexstring elements over octet boundaries. This is known as "LowToHigh encoding", as shown in the following example: EXAMPLE 1: Coding of element "Circuit Identity Code" (CIC), consisting of 12 bits. Octet # Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Octet 1 CIC (LSB) Octet 2 spare CIC (MSB) Figure 6: Bit field structure of the "CIC" parameter The 8 least significant bits of the CIC value fill octet 1 (the least significant bit of CIC is assigned to bit 1 of octet 1), and the 4 most significant bits of the CIC value fill the lower 4 bits of octet 2. NOTE 2: When a bitstring (hexstring) is presented as a sequence of bits (semi-octets) from left to right, the leftmost bit (semi-octet) is the most significant and the rightmost bit (semi-octet) is the least significant. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 19 EXAMPLE 2: Adress digits Several ISUP parameters have an element "Adress digits", where the individual digits are BCD-encoded (i.e. e.g. digit "0" is encoded as "0000"B, digit "9" is encoded as "1001"B. When an address string is given as a sequence of ASCII digits, as a user would type them in, e.g. "0123456789", the encoded value is as shown on figure 7. Octet # Bits 8 7 6 5 Bits 4 3 2 1 Octet 1 0001 0000 Octet 2 0011 0010 Octet 3 0101 0100 Octet 4 0111 0110 Octet 5 1001 1000 Figure 7: Hex (BCD) field structure of an "address digits" element This also corresponds to a "LowToHigh" encoding. In this particular case however, for the sake of ATS user convenience, a conversion function is used in the ATS in the following way: • All module parameters containing address digits have type "charstring" (resp. IA5String), which means that the user enters digits as ASCII characters "1", "2" and so on. • Inside the address parameter templates the conversion function converts the ASCII string into a BCD-coded octetstring, taking also care of: - "sending complete" digit (only applicable to the Called Party Number); - filler (final semi-octet, if the number of coded digits is odd. The encoding of octetstrings however is not LowToHigh, as shown in the following example: EXAMPLE 3: octetstring value The octetstring value "01234ABCDE"O is encoded as shown on figure 8. Octet # Bits 8 7 6 5 Bits 4 3 2 1 Octet 1 0000 0001 Octet 2 0010 0011 Octet 3 0100 1010 Octet 4 1011 1100 Octet 5 1101 1110 Figure 8: Octetstring field encoding 4.3.2.3.3.2.2 Decoding of parameters containing strings of variable length Typical fields addressed here are e.g. the "adress digits" field in the "Called Party Number" parameter, or the "diagnostics" field in the "Cause Indicators" parameter. The above mentioned strings of variable length are the last elements of the related parameter, which has a preceding length field. A "real" decoder deduces the length (and thereby the value) of such fields from the value of the "length" field of the parameter and the position of the decoder where the field starts. The decoder of the test system shall also be able to decode such fields when the value of the template is "?" or "*". ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 20 In order to support this encoding the relevant types have a trailing "with { encode ..." statement, like in the following example (Called Party Number): EXAMPLE 4: .... with { encode (paramLen) "tag=""CDN_paramLen"";"; encode (addressSignals) "length=valueOf(getTag(""CDN_paramLen"")).toInt()-2;"; } End 4.3.2.3.3.2.3 Decoding of parameters containing extension bits Some parameters transport IEs from the DSS1 protocol (ITU-T Recommendation Q.931 [20]), such as the Bearer Capability IE: • IEs of this kind contain extension bits specifying the presence of succeeding octets. • The decoder shall be able to evaluate the extension bits to deduce the presence of optional octets in case wildcards "?" or "*" are specified in templates of such IEs. 4.3.2.3.3.2.4 Receipt of unknown ISUP/BICC messages Unknown messages in this context are messages not defined in the dated version of ITU-T Recommendation Q.763 [15] referred to in the present document. Unknown messages shall not be passed to TE by the test system. 4.3.2.3.3.2.5 Receipt of unknown ISUP/BICC parameters Unknown parameters in this context are parameters not defined in the dated version of ITU-T Recommendation Q.763 [15] referred to in the present document, or defined parameters not being assigned in ITU-T Recommendation Q.763 [15] to the particular received message carrying this parameter. Unknown parameters shall not be passed to TE by the test system (i.e. they shall be removed from the carrying known message before passing this message to TE). 4.3.2.3.3.2.6 Ordering of optional ISUP/BICC parameters and multiple occurrence of parameters According to ITU-T Recommendation Q.763 [15] optional parameters may occur in any order in a message, and some (few) parameters may occur more than once. For the controlled test environment specified in this ATS the following assumption has been made: • Parameters that may occur more than once appear at most two times in a message. For each message that may contain optional parameters the list of parameters has been specified in the ATS as a set. The decoder shall be able to decode the parameters of a received message correctly, even if they appear in an odder different from the one specified in the message template (and type). 4.3.2.3.3.2.7 Platform adaptation requirements For the execution of this test suite implementations of the following external functions have to be provided (cp. module LibSip_Steps): 1) rndStr() return charstring; returns a random charstring; 2) putInLowercase(charstring par_string) return charstring; returns the equivalent string in lower case: 3) getIpAddr(charstring host_name) return charstring; resolves a domain name to its equivalent IPv4 address; ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 21 4) calculateDigestResponse(charstring nonce, charstring cnonce, charstring user, charstring realm, charstring passwd, charstring alg, charstring nonceCount, charstring method, charstring qop, charstring URI, charstring HEntity) return charstring; generates a digest response according to RFC 2617 [22] (HTTP Authentication: Basic and Digest Access Authentication), and RFC 1321 [23] The MD5 Message-Digest Algorithm. (See RFC 2617 [22], section 5 Sample implementation, for example usage, as the signature of calculateDigestResponse is according to the example given in the RFC.). 4.3.2.3.3.3 Logging conventions As the ATS defines on an abstract level the message exchange between TS and SUT the messages encoded messages send and received shall be logged. The TM entity in the TS shall provide access to this log.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5 The ATS development process
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 6 of TS 186 009-2 [1]. The requirements applicable to this TP are given by a reference to RFC 3261 [17] (SIP) and TS 129 163 [4] or TS 129 527 [5] (ISUP). There are no explicit formulations of requirements. NOTE: During the ATS development comments have been made on TS 186 009-2 [1] (TSS&TP) and TS 186 009-1 [3] (PICS). These are not referred to in detail in the present document. Part of the comments related to inconsistent namings of the TP tables in TS 186 009-2 [1]. Re-naming of the TP tables was agreed by TISPAN. Annex C contains a list showing the pairings of original TP identifiers in TS 186 009-2 [1] and the naming used in the ATS.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.2 ATS structure
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.2.1 Test case grouping
|
The ATS structure defined in table 15 is based on the structuring of Test Purposes in clause 5 of TS 186 009-2 [1]. The group names in columns 1 to 3 of table 15 are those assigned in the ATS; they are based on the names provided in clause 5 of TS 186 009-2 [1], but use the naming conventions defined for the ATS (see clause 5.3.2.2). Table 15: ATS structure Group Subgroup Sub-Subgroup Group Index Basic call SIP-ISUP 1 Sending of the Initial address message (IAM) 101 Sending of the Subsequent address message (SAM) 102 Sending of COT 103 Receipt of the Address complete message (ACM) 104 Receipt of the Call progress message (CPG) 105 Receipt of the answer message (ANM) 106 Receipt of the Connect message (CON) 107 Receipt of the Release message (REL) 108 Autonomous release at I-MGCF 1081 Receipt of the BYE, CANCEL message / sending of a REL message 109 Receipt of Reset circuit message (RSC), Circuit group reset message (GRS) or Circuit group blocking message (CGB) with the indication hardware failure oriented 110 Receipt of the SUSPEND Message (SUS) 111 Receipt of the RESUME Message (RES) 112 ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 22 Group Subgroup Sub-Subgroup Group Index ISUP-SIP 3 Sending of the INVITE message 301 Receipt of the Subsequent address message (SAM) 302 Sending of the Address complete message (ACM) 303 Sending of the Call progress message (CPG) 304 Sending of the answer message (ANM) 305 Sending of the Connect message (CON) 306 Receipt of the Release message (REL) 307 Sending of the Release Message (REL) 308 Autonomous release 309 Receipt of Reset circuit message (RSC) 310 Receipt of Circuit group reset message (GRS) 311 Receipt of Circuit group blocking message (CGB) with the indication hardware failure oriented 312 Supplementary Services SIP-ISUP 5 Calling Line Identification (CLI) 501 Call Hold (HOLD) 502 Terminal Portability (TP) 503 Conference Calling (CONF) 504 Three-Party (3PTY) 505 Connected Line Identification (COL) 506 Malicious call identification (MCID) 507 Subaddressing (SUB) 508 Call Diversion (CDIV) 509 Call Waiting (CW) 510 User to User Signalling (UUS) 511 Explicit Call transfer (ECT) 512 Completion of Call to Busy Subscriber (CCBS) 513 Completion of Calls on No reply (CCNR) 514 Anonymous Call Rejection (ACR) 515 Closed user group (CUG) 516 ISUP-SIP 6 Calling Line Identification (CLI) 601 Call Hold (HOLD) 602 Terminal Portability (TP) 603 Conference Calling (CONF) 604 Three-Party (3PTY) 605 Connected Line Identification (COL) 606 Subaddressing (SUB) 607 Closed User Group (CUG) 608 Call Diversion (CDIV) 609 User to User Signalling (UUS) 610 Explicit Call transfer (ECT) 611 Anonymous Call Rejection (ACR) 612 Call waiting (CW) 613 Malicious call identification (MCID) 614 NOTE: All subgroups except for "Autonomous release at I-IWU"/1081 use 3 digits to number test cases inside this subgroup. For "Autonomous release at I-IWU"/1081 only 2 digits are available.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.2.2 Test case identifiers
|
The test case names are built up according to the following scheme: <"TC">"_"<Group index>"_"<TC number> where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the 3-digit number in column 4 of table 15 (which uniquely identifies the path of groups/subgroups); ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 23 c) <TC number> is a running 3-digit decimal number, starting in each subgroup path with "001". NOTE 1: See note in table 15 for the one exception from this rule and its reason. EXAMPLE: TC_101_001: i) the identifier has Group index "101", i.e. it is in the subgroup having complete path: BasicCall/SIP-ISUP/Sending of the Initial address message (IAM)/ ii) the identifier is the first test case of this group/subgroup. NOTE 2: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 009-2 [1] and test case names. The TP identifier of TC_101_001 is TP101001. See however annex C for the list of re-named test purposes.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3 ATS specification framework
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3.1 ATS Library
|
For this interworking ATS there are 2 applicable base protocols: a) SIP protocol (RFC 3261 [17]); and b) ISUP protocol (ITU-T Recommendation Q.76n series [13] to [16], plus associated standards for supplementary services, etc.). Since e.g. the data structures of these 2 base protocols are independent, and other objects like test cases are common, the TTCN-3 library modules are basically organized as: • ATSCommon modules (generated for the present ATS); • LibIms modules; • LibSip modules; • ISUP modules; • LibCommon modules (taken from an improved version of TS 102 351 [2]). Table 16 shows the organization of the ATS as library of modules. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 24 Table 16: Library of modules Module Class Module Id Description AtsCommon SipIsup_PICS Module Parameter declarations associated with PICS. SipIsup_PIXITS SIP-ISUP common Module Parameter declarations associated with PIXIT. SipIsup_Testcases Test case defintions SipIsup_TestConfiguration Functions which implement the configuration of the SUT adapter and mapping of test components for establishing and tearing down different test configurations. SipIsup_TestExecution Module control: execute test cases depending on selection conditions; repeat parameterized test cases based on the "Variant-tables" defined in the test prose. SipIsup_TestSystem Common functions, components, ASPs controlling the test system. SipIsup_IMS_TCFunctions Test case functions LibIms LibIms_PIXITS IMS specific common Module Parameter (e.g. addresses related to SUT components and TS) declarations associated with PIXIT. LibIms_Interface IMS component LibIms_SIPTypesAndValues IMS specific user and interface specific profile data (see note 3) LibIms_Templates Modified templates with IMS specific header fields LibIms_Steps functions using IMS specific types LIbSip LibSip_PIXITS SIP general common Module Parameter (e.g. SDP/SIP procedure options) declarations associated with PIXIT. LibSip_Interface SIP component LibSip_SIPTypesAndValues SIP message types and constants, simple user profiles (see note 3) LibSip_SDPTypes SDP types and constants LibSip_Templates Basic and modified templates with SIP specific header fields LibSip_Steps SIP specific behaviour function library LibSip_XMLTypes XML types for SIP tests XSDAUX Basic types used in XML IsupAts SipIsup_ISUP_Constants Constant declarations, mostly corresponding to field values of ISUP messages/parameters. SipIsup_ISUP_ModuleParams Module parameters (all associated with PIXIT). SipIsup_ISUP_ParamTypes ISUP data types (parameter types according to ITU-T Recommendation Q.763 [15] and types required for ASPs). SipIsup_ISUP_MsgTypes ISUP data types (message types according to ITU-T Recommendation Q.763 [15] and ASP type declarations). SipIsup_ISUP_ParamTemplates Templates for ISUP message parameters. SipIsup_ISUP_MsgTemplates Templates for ISUP messages. SipIsup_ISUP_Steps Test step declarations, including preambles, postambles and default. SipIsup_ISUP_TCFunctions Test case functions running on the Isup/Bicc component. LibCommon LibCommon_AbstractData Generic data types for a stack and its operations. LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean). LibCommon_DataStrings Bit and Octet string types. LibCommon_Sync Co-ordination/synchronization of test components. LibCommon_TextStrings Basic character and string types with fixed length. LibCommon_Time Time handling functions and moduleparameter. LibCommon_VerdictControl Basic functions for setting of test component verdicts.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3.2 Use of TTCN-3
| |
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3.2.1 General
|
TTCN-3 as defined in ES 201 873-1 [8] is used as ATS specification language. A number of requirements have been identified for the development and production of the TTCN-3 specification for the SIP/ISUP Interworking ATS: • Top-down design. • A uniquely defined testing architecture and test method. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 25 • Uniform TTCN-3 style and naming conventions. • TTCN-3 is human-readability. • TTCN-3 specification is feasible, implementable, compilable and maintainable. • Test cases shall be designed in a way to be easily adaptable, upwards compatible with the evolution of the base protocol and protocol interworking of future releases. • The test declarations, data structures and data values shall be largely reusable. • Modularity and modular working method. • Minimizing the requirements of intelligence on the emulators of the lower testers. • Giving enough design freedom to the test equipment manufacturers. Fullfilling these requirements should ensure the investment of the test equipment manufacturers and users of the ATS having stable testing means for a relatively long period.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3.2.2 TTCN-3 naming conventions
|
Like in other software projects using a programming language, the use of naming conventions supports or increases: a) the readability; b) the detection of semantic errors; c) the shared work of several developers; d) the maintainability. The naming conventions applied to the SIP/ISUP Interworking ATS are based on the following underlying principles: • when constructing meaningful identifiers, the general guidelines specified for naming in clause 9 of [2] should be followed; • for the SIP ATS part, which is based on a subset of TS 102 027-3 [7], with extensions, the naming conventions defined in TS 102 027-3 [7] should be followed; • the names of TTCN-3 objects being associated with standardized data types (e.g. in the base protocols) should reflect the names of these data types as close as possible (of course not conflicting with syntactical requirements or other conventions being explicitly stated); • the subfield names of TTCN-3 objects being associated with standardized data type should also be similar to corresponding element names in the base standards (be recognizable in the local context); • in most other cases, identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents; • prefixes should be separated from the body of the identifier with an underscore ("_"); • only test case names, module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. Table 17 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix and capitalization. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 26 Table 17: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Module Use upper-case initial letter none IPv6Templates TSS grouping Use all upper-case letters as specified in clause 7.1.2.1.1 none TP_RT_PS_TR Item group within a module Use lower-case initial letter none messageGroup ISUP message type Use upper-case initial letter and message name abbreviations as defined in [14]. none IAM ISUP parameter type Use upper-case initial letter and parameter name abbreviations taken from [15]. none CalledPartyNumber SIP message type Use upper-case initial letter none Request, Response note 4 SIP header type Use upper-case initial letter none MaxForwards note 4 Basic common data types (e.g. bit string types of fixed length) Use upper-case initial letter none Take from common module Other Data types Use upper-case initial letter none SetupContents Template None m_ m_IAM_Basic note 1 note 5 Message template with wildcard or matching expression None mw_ mw_AnyUserReply note 2 note 5 Signature template Use lower-case initial letter s_ s_callSignature Port instance Use lower-case initial letter none signallingPort Test component ref Use lower-case initial letter none userTerminal Constant Use lower-case initial letter c_ c_maxRetransmission External constant Use lower-case initial letter cx_ cx_macId Function Use lower-case initial letter f_ f_authentication() External function Use lower-case initial letter fx_ fx_calculateLength() Altstep (incl. Default) Use lower-case initial letter a_ a_receiveSetup() Test case Use naming as specified in clause 5.2.2 TC_ TC_101_001 Variable (local) Use lower-case initial letter v_ v_macId Variable (defined within a component) Use lower-case initial letters vc_ vc_systemName Timer (local) Use lower-case initial letter t_ t_wait Timer (defined within a component) Use lower-case initial letters tc_ tc_authMin Module parameter Use initial upper case letters PX PX_MAC_ID note 3 Parameterization Use lower-case initial letter p_ p_macId Enumerated Value Use lower-case initial letter e_ e_syncOk NOTE 1: This prefix must be used for all template definitions which do not assign or refer to templates with wildcards or matching expressions, e.g. templates specifying a constant value, parameterized templates without matching expressions, etc. NOTE 2: This prefix must be used in identifiers for templates which either assign a wildcard or matching expression (e.g. ?, *, value list, if present, pattern, etc.) or reference another template which assigns a wildcard or matching expression NOTE 3: In this case it is acceptable to use underscore as a word delimiter. NOTE 4: This convention has been used in TS 102 027-3 [7] (SIP ATS). NOTE 5: Names of ISUP messages and parameters (IEs) start with a syllable being composed of capital letters only, like IAM e.g. This is different for SIP. Naming conventions concerning the first letter of a template (after prefix "m_" or "mw_", may be handled differently for ISUP/BICC and SIP respectively. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 27
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3.2.3 Additional TTCN-3 IMS/SIP and ISUP naming convention
|
In addition to the general TTCN-3 naming conventions listed in the previous section the following rules have been applied to templates. Table 18: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Message template Use lower-case initial letter, followed by message type in upper-case letters (for requests) or "Response" keyword m_ m_BYE_Request_UE Message template with wildcard or matching expression Use lower-case initial letters mw_ mw_SUBSCRIBE_Request_IMS SIP Templates have been defined in a 3-step approach. First, a dummy template is defined for every message type and direction, e.g. m_ACK_Dummy and mw_ACK_Dummy. Secondly, for each message type and direction a base template has been defined that modifies respective dummy templates and includes all mandatory header fields. Template identifiers of this modifications include the keyword "Base", e.g. m_ACK_Request_Base, mw_ACK_Request_Base. More specific templates are then derived on the basis of these base templates and modify fields that need to be restricted for a very speicifc purpose, e.g. m_ACK_Request_route, etc.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3.2.4 Additional concepts and conventions
|
IMS procedures and tests requires the inclusion of user identification and network address information in SIP messages. Since this information depends on the specific SUT at hand it is defined using module parameters. Due to the big amount of such parameters a profile concept have been introduced for particular parameter collections (records) that are related to IMS users and interfaces. The so-called user profile information (cp. module LibSip_SIPTypesAndValue) contains the following elements: userprofile identifier, current IP port and address to exchange SIP messages, IP port and address for further contact, IP address used by the TS to exchange media streams, public identity (home domain, username), quality-of-protection parameters, authentication parameters (RFC 2617 [22], section 3.2.2). A list of user profile identifiers (module LibIMS_SIPTypesAndValue) introduces available settings for UE with different locations and homes: e.g. c_userProfile_UE1atSUThome should be used in case where UE1 is a registered user of SUT and currently not visiting another IMS. User profiles are construced from module parameters (cp. module LibIMS_Steps). Additionally some interface information is needed to indicate or validate IMS component addresses to be used in SIP header fields like Via, Route, etc.. They are defined in a similar way as user profiles (cp. LibIms_SIPTypeAndValues) and contain IP address, port and domain information. For example c_interfaceProfile_IMS_SUT_IBCF1 defines an IBCF access point at the SUT. Interface profiles are also constructed based on module parameters (cp. module LibIMS_Steps).
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3.2.5 PICS information
|
No TTCN-3 control part has been defined for this test suite. If applicable PICS information is evaluated at the begining of each test case definition using an "if" statement. Log information is provided in case that a test has not been executed due to PICS setting violation. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 28
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.3.2.6 TTCN-3 comment tags
|
Any TTCN-3 definition in the Test Suite Repository or Library should contain embedded comment tags. These comment tags can be used by tools to extract information from the TTCN-3 code to create, for example, a HTML-based reference documentation. Comment tags which cover one or more lines should be specified using block comments, as illustrated: /* ----------------------- * @desc This line of text is now identified as a description * which covers multiple lines * -----------------------*/ Comments tags specified within a single line may be specified using line comments, as illustrated: // @author John Doe or: /* @author John Doe */ Table 19 lists the tags that can be used in ETSI TTCN-3 test specifications with a short description of the intended use of each tag. Tools may support other, non standard tags. Such tags should not be used in TTCN-3 modules standardized by ETSI. NOTE: Tools may also extract other information from the TTCN-3 code based, for example, on TTCN- 3 keywords. The definition of that extraction is beyond the scope of the present document. Table 19: TTCN-3 Comment Tags Tag Description @author This tag should be used to specify the names of the authors or an authoring organization which either has created or is maintaining a particular piece of TTCN-3 code. @desc This is probably the most import of all the tags. It should be used to describe the purpose of a particular piece of TTCN-3 code. The description should be concise yet informative and describe the function and use of the construct. @remark This tag may be used to add additional information, such as highlighting a particular feature or aspect not covered in the description. @img This tag may be used to associate images with a particular piece of TTCN-3 code. @see This tag may be used to refer to other TTCN-3 definitions in the same or another module. @url This tag should be used to associate references to external files or web pages with a particular piece of TTCN-3 code, e.g. a protocol specification or standard. @return This tag should only be used with functions. It is used to provide additional information on the value returned by the given function. @param This tag is used to document the parameters of parameterized TTCN-3 definitions. @version This tag is used to state the version of a particular piece of TTCN-3 code. The following provides some basic guidelines on the usage of tags for specific TTCN-3 definitions: • each TTCN-3 module should use the @author, @version and @desc tags; • the @desc tag should be used with all TTCN-3 definitions. However, this should not be taken to the extreme. For example, it is probably not useful to tag literally every single constant or template declaration. It is left to the discretion of the writer to find the right level of use. At least all major constructs such as test cases and functions should have a comprehensive description: - when a TTCN-3 definition uses module parameters, it is also recommended to mention this explicitly in the description; - descriptions for behavioural constructs should mention if they set the test component verdict and also all known limitations of the construct; - descriptions for type definitions, e.g. component types, should mention if the type has been designed to be type compatible to another type or vice versa to be used as a basis for other type definitions. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 29 • the @see tag should be used to make dependencies between TTCN-3 definitions which are described by a @desc tag more explicit in the documentation, e.g. if some TTCN-3 definition uses a module parameter then its TTCN-3 definition should be referenced to using a @see tag; • where applicable, parameterized constructions such as functions, altsteps and templates should use the @param and @return tags. The @param tags should first list the parameter name and then a brief description of how this parameter is used by the construct; • the @url tag should be used to refer to the specification from which the TTCN-3 definition was derived from, e.g. a type definition could refer to a particular RFC IETF page. In some cases it may be necessary to use the @desc tag instead for this purpose as documents often are hard to access internally, i.e., it may only be possible to specify a reference to a complete document but impossible to point to a very specific clause in the present document; • the @url and @img tag may be used to link to relevant documentation such as Test Purposes or original requirements or even drawings of test configurations. Generally, the corresponding Test Purpose (in the TSS&TP) and to the corresponding Requirement (in the Requirements Catalogue) should be linked from the relevant TTCN-3 test case definition; • the @remark tag may be used with any TTCN-3 definition. It should be used sparingly, e.g. possibly to indicate how a TTCN-3 definition should not be used.
|
bd27bfecf4e216ed521ebf95e7320382
|
186 009-3
|
5.4 ATS archive
|
Annex B contains the ATS archive (.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 30 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, grants that users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the interworking type of ATS defined in the present document, the PIXIT are divided in common, SIP-related PIXIT and ISUP/BICC-related PIXIT. A.2.1 Common PIXIT related to SIP and ISUP/BICC The PIXIT items of table A.1 apply for SIP and ISUP/BICC and contain values that are used on both sides of the interworking function. Table A.1: Common PIXIT items related to SIP and ISUP/BICC Item Module Parameter Description Type Value 1.1 PX_TC_VA Number of test case variant according to table entry in table to test purpose description, if present integer 1.2 PX_SIP_MESSAGE_VA Number of SIP message variant according to table entry in table to test purpose description, if present integer 1.3 PX_BearerCapabilityInformation TransferCapability Bearer Capability Information Transfer Capability used for mapping between ISUP: Bearer Capability information element within USI parameter and SIP: SDP offer or PSTN XML BearerCapability Used in TC_301_014, TC_301_015 and TC_301_023 bitstring(5) 1.4 PX_BearerCapabilityInformation TransferCapability2 Second Bearer Capability Information Transfer Capability used for mapping between ISUP: Bearer Capability information element within ATP parameter and SIP: PSTN XML BearerCapability Used in TC_304_008, TC_304_009, TC_304_010, TC_305_005, TC_305_006, TC_305_008, TC_306_006, TC_306_007 and TC_306_009 bitstring(5) ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 31 Item Module Parameter Description Type Value 1.5 PX_HighLayerCharacteristicsIde ntification High layer characteristics identification used for mapping between ISUP: High layer compatibility information element within ATP or UTSI parameter and SIP: PSTN XML HighLayerCompatibility Used in TC_105_012, TC_105_013, TC_106_006, TC_106_007, TC_107_008, TC_107_009, TC_301_031, TC_301_032 TC_301_033, TC_304_011, TC_304_012, TC_305_004, TC_305_007, TC_306_005 and TC_306_008 bitstring(7) 1.6 PX_HighLayerCharacteristicsIde ntification2 Second High layer characteristics identification used for mapping between ISUP: High layer compatibility information element within ATP parameter and SIP: PSTN XML HighLayerCompatibility Used in TC104_015, TC_104_016, TC_301_033, TC_305_004, TC_305_007, TC_306_005 and TC_306_008 bitstring(7) 1.7 PX_LowLayerInformationTransf erCapability Low layer Information Transfer Capability used for mapping between ISUP: Low layer compatibility information element within ATP parameter and SIP: PSTN XML LowLayerCompatibility Used in TC_104_018, TC_104_019, TC_106_008, TC_107_010, TC_301_030, TC_305_003 and TC_306_004 bitstring(5) 1.8 PX_ProgressIndicator Progress description used for mapping between ISUP: Progress indicator information element within ATP parameter and SIP: PSTN XML ProgressIndicator Used in TC_104_008, TC_104_020, TC_105_006, TC_107_004, TC_301_029, TC_305_002 and TC_306_003 bitstring(7) 1.9 PX_CUG_NetworkIndicator NetworkIndicator description used for mapping between ISUP: Networkindicator information element within CUG parameter and SIP: CUG XML NetworkIndicator Used in TC_516_003, TC_516_004, TC_608_003 and TC_608_004 hexstring(1) 1.10 PX_CUG_InterlockBinaryCode InterlockBinaryCode description used for mapping between ISUP: InterlockBinaryCode information element within CUG parameter and SIP: CUG XML InterlockBinaryCode Used in TC_516_003, TC_516_004, TC_608_003 and TC_608_004 hexstring(2) 1.11 PX_CauseValue Cause value used for mapping between ISUP: Cause value within CAUI parameter and SIP: Q.850 cause value in Reason header Used in TC_110_001, TC_110_002, TC_307_003, TC_308_002, TC_308_004 and TC_308_005 integer 1.12 PX_Timeout_Tiw1 Nominal timeout value of ISUP/SIP interworking protocol timer TOIW1. float 1.13 PX_Timeout_Tiw3 Nominal timeout value of ISUP/SIP interworking protocol timer TOIW3. float ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 32 Item Module Parameter Description Type Value 1.14 PX_SIP_privacy Privacy value used for TC606006-606008 PrivacyValu e 1.15 PX_SIP_privacy_VA Value used for preselected privacy values (0=id, 1=user, 2=header) integer 1.16 PX_SIP_NameAddr_From NameAddr default value for From field NameAddr 1.17 PX_SIP_NameAddr_UserB Default value for diverted user field Used in group 509 NameAddr 1.18 PX_SIP_NameAddr_UserC Default value for diverted user field Used in group 509 NameAddr 1.19 PX_SIP_NameAddr_UserD Default value for diverted user field Used in group 509 NameAddr 1.20 PX_SIP_NameAddr_UserE Default value for diverted user field Used in group 509 NameAddr 1.21 PX_SIP_NameAddr_ChangedFr om Default value for CHANGED From field Used in TC_606_008 NameAddr 1.22 PX_SIP_NameAddr_PAsserted NameAddr default value for PAsserted (with sip scheme) field Used in group 501 NameAddr 1.23 PX_SIP_NameAddrTel_PAssert ed NameAddr default value for PAsserted (with tel scheme) field Used in group 501 NameAddr 1.24 PX_SIP_NameAddrTel_PAssert ed_otherCC Default value for PAsserted (with tel scheme) field Used in groups 501 and 606 NameAddr 1.25 PX_SIP_DummyUser_userInfo Default value for user info (dummy user number) Used in group 609 charstring 1.26 PX_SIP_User2userIData Default value for User2userInfoData Used in group 610 charstring 1.27 PX_SIP_XML_Conference_AS_ URI Default value for conference application server uri Used in groups 504 and505 charstring 1.28 PX_SIP_XML_Conference_ISU P_userInfo Default value for ISUP user number Used in groups 504 and 505 charstring 1.29 PX_SIP_XML_Conference_Du mmyUser_userInfo Default value for dummy user number Used in groups 504 and 505 charstring 1.30 PX_SIP_XML_Conference_Ref eredBy_userInfo Default value for referedBy field Used in TC_504_013 NameAddr A.2.2 SIP/IMS -related PIXIT For the SIP side of the ATS the PIXIT defined in TS 102 351 [2] apply. In addition the SIP-related PIXIT of table A.2 apply, which have been provided for the particular purposes of this ATS. Each PIXIT item corresponds to a Module Parameter of the ATS. Table A.2: Additional SIP-related PIXIT items Item Module Parameter Description Type Value 2.1 PX_SIP_SDP_dyn SDP dynamic port. charstring 2.2 PX_SIP_SDP_b_modifier SDP bandwidth modifier. charstring 2.3 PX_SIP_SDP_b_bandwidth SDP bandwidth value. integer 2.4 PX_SIP_SDP_encoding SDP media attribute encoding supported by the IUT. charstring 2.5 PX_SIP_SDP_encoding_unavail SDPmedia attribute encoding unavailable by the IUT. charstring 2.6 PX_SIP_SDP_encoding_unsup SDP media attribute encoding unsupported by the IUT. charstring 2.7 PX_SIP_SDP_transport SDP media T. charstring 2.8 PX_SIP_ISUP_LANGUAGE Used CPC language. charstring 2.9 PX_SIP_ISUP_CPC_VALUE Used CPC language. charstring ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 33 Item Module Parameter Description Type Value 2.10 PX_SIP_100rel True if 100rel mechanism is supported in SIP. boolean 2.11 PX_SIP_precondition True if precondition mechanism is supported in SIP. boolean 2.12 PX_SIP_UDP True if UDP Transport is used by the IUT to run campaign. boolean 2.13 PX_SIP_TRANSPORT Used Transport in upper case "UDP"/"TCP". charstring 2.14 PX_SIP_BYE_CAUSE Release cause to be used in BYE and in Failure messages. integer 2.15 PX_SIP_CheckConversation True, if conversation check is implemented. boolean 2.16 PX_SIP_CheckDTMF True, if DTMF check is implemented. boolean 2.17 PX_SIP_SendAnnouncement True, if Announcement sending is implemented. boolean 2. 18 PX_SIP_CheckRinging True, if ringing check is implemented. boolean 2.19 PX_SIP_T1 T1 RTT estimate (500 ms). float 2.20 PX_T2 T2 Maximum retransmit interval for non-INVITE requests and INVITE response (4 000 ms). float 2.21 PX_T4 T4 Maximum duration a message will remain in the network. float 2.22 PX_SIP_TF TDELAY default value for timeout on outgoing SIP request (ie 64*T1). float 2.23 PX_SIP_TWAIT TWait default value for waiting an operator action. float 2.24 PX_SIP_TACK TAck default value for waiting an acknowledgement. float 2.25 PX_SIP_TRESP TResp default value for waiting for a response from the IUT. float 2.26 PX_SIP_TNOACT TNoAct default value for waiting no message from the IUT Value given for PX_TNOACT should be less than value of SHORT_REGISTRATION constant (which is currently "3" (seconds)). float 2.27 PX_SIP_TSYNC TSYNC default value to synchronise ptc. float 2.28 PX_SIP_TGUARD TGUARD default value for an extra long timer to limit test execution. float 2.29 PX_TRespRetention TRespRetention minimum time that a Proxy will wait before sending a final response. float 2.30 PX_IMS_TS_ICSCF_IPADDR TS/I-CSCF IP address to exchange SIP messages. charstring 2.31 PX_IMS_TS_ICSCF_PORT IUT/I-CSCF port number to exchange SIP messages. integer 2.32 PX_IMS_TS_ICSCF_HOME_D OMAIN TS/I-CSCF domain. charstring 2.33 PX_IMS_SUT_IMGCF_IPADDR SUT/I-MGCF IP address to exchange SIP messages. charstring 2.34 PX_IMS_SUT_IMGCF_PORT SUT/I-MGCF port number to exchange SIP messages. integer 2.35 PX_IMS_SUT_IMGCF_HOME_ DOMAIN SUT/I-MGCFdomain. charstring ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 34 A.2.3 ISUP/BICC-related PIXIT Tables A.3 to A.6 list the ISUP/BICC-related PIXIT items associated with the ATS. Each PIXIT item corresponds to a Module Parameter of the ATS. Default values are not provided. Table A.3: General SS/SUT-related ISUP/BICC PIXIT items Item IModule Parameter Description Type Value 3.1 PX_ISUP_Isup Select whether ISUP (true) or BICC (false) testing is done (depending on whether the SUT implements ISUP or BICC on the outgoing circuits under test). boolean 3.2 PX_ISUP_NW_IND Network indicator inside the Service Indicator octet (SIO). bitstring(2) 3.3 PX_ISUP_SLS Signalling Link Selection (SLS) value of the ISUP link between TS and SUT. bitstring(4) 3.4 PX_ISUP_PC_SUT Point code of the SUT (ISUP interface). bitstring(14) 3.5 PX_ISUP_PC_TS Point code of the TS (ISUP interface). bitstring(14) 3.6 PX_SUT_ADRESS_ISUP_BICC Address (e.g. IP) of the SUT (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. charstring 3.7 PX_TS_ADRESS_ISUP_BICC Address (e.g. IP) of the TS (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. octetstring 3.8 PX_ISUP_TX_CIC_cicv1 Default Circuit Identity Code value for signalling connection 1). bitstring(12) 3.9 PX_ISUP_TX_CIC_cicv2 Default Circuit Identity Code value for signalling connection 2). bitstring(12) 3.10 PX_ISUP_TX_CIC_caicv1 Default Call Instance Code value for signalling connection 1). octetstring(4) 3.11 PX_ISUP_TX_CIC_caicv2 Default Call Instance Code value for signalling connection 2). octetstring(4) Table A.4: Timer-related ISUP/BICC PIXIT items Item IModule Parameter Description Type Value 4.31 PX_ISUP_TAC Time to control the reception of a message. float 4.32 PX_ISUP_TNOAC Time to control that IUT sends nothing. float 4.33 PX_ISUP_TSYNC Time to control synchronization. float 4.34 PX_ISUP_TSYNC_TIME_LIMIT Time to control synchronization. float 4.35 PX_ISUP_TDONE Time to control PTC.stop. float 4.36 PX_ISUP_TWAIT Time to control that IUT reacts prior to Upper Tester action. float 4.37 PX_TDelay Time to delay messages before sending. float 4.38 PX_Timeout_T7 Nominal timeout value of ISUP protocol timer T7. float 4.39 PX_Timeout_T8 Nominal timeout value of ISUP protocol timer T8. float 4.40 PX_Timeout_T9 Nominal timeout value of ISUP protocol timer T9. float 4.41 PX_Timeout_T39 Nominal timeout value of ISUP protocol timer T39. float ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 35 Table A.5: Operator-check-related ISUP/BICC PIXIT items Item IModule Parameter Description Type Value 5.1 PX_IsupBicc_CheckConversatio n True if conversation check is implemented and used. Otherwise false (see note 1). boolean 5.2 PX_IsupBicc_CheckRinging True if ringing check is implemented and used. Otherwise false (see note 2). boolean NOTE 1: If true, test execution will stop at positions where the TP indicates "conversation" until the operator enters the check result. NOTE 2: If true, test execution will stop at positions where the TP indicates "ringing" until the operator enters the check result. Table A.6: ISUP/BICC PIXIT items associated with message fields Item Module Parameter Description Type Value Called party number - sending 6.4.1.1 PX_ISUP_IAM_CLD_digits_txD ef Default "address digits" value sent in the "Called party number" parameter in the IAM message, containing the complete address and "sending complete". See ITU-T T Rec. Q.763 [15], 3.9. IA5String 6.4.1.2 PX_ISUP_TX_CLD_natAddr_tx Def Default "nature of address" value sent in the "Called party number" parameter in the IAM message, containing the complete address and "sending complete". See ITU-T T Rec. Q.763 [15], 3.9. bitstring(7) 6.4.1.3 PX_ISUP_IAM_CLD_digits_txD ef_inat Default "complete address digits" value sent in the "Called party number" parameter in the IAM message, when the nature of address is specified as "international number". See ITU-T T Rec. Q.763 [15], 3.9. IA5String 6.4.1.4 PX_ISUP_IAM_CLD_digits_txD ef_nat Default "complete address digits" value sent in the "Called party number" parameter in the IAM message, when the nature of address is specified as "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.9. IA5String 6.1.2.1 PX_ISUP_IAM_CLD_digits_anal ysis "address digits" value sent in the "Called party number" parameter in the IAM message, when "sending complete" is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by analysis of the number. See ITU-T T Rec. Q.763 [15], 3.9. IA5String 6.1.2.2 PX_ISUP_TX_CLD_natAddr_an alysis "nature of address" value sent in the "Called party number" parameter in the IAM message, when "sending complete" is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by analysis of the number. See ITU-T T Rec. Q.763 [15], 3.9. bitstring(7) ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 36 Item Module Parameter Description Type Value 6.1.3.1 PX_ISUP_IAM_CLD_digits_time out "address digits" value sent in the "Called party number" parameter in the IAM message, when "sending complete" is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by timeout. See ITU-T T Rec. Q.763 [15], 3.9. IA5String 6.1.3.2 PX_ISUP_TX_CLD_natAddr_ti meout "nature of address" value sent in the "Called party number" parameter in the IAM message, when "sending complete" is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by timeout. See ITU-T T Rec. Q.763 [15], 3.9. bitstring(7) 6.1.4.1 PX_ISUP_IAM_CLD_digits_max "address digits" value sent in the "Called party number" parameter in the IAM message, containing the maximum number of digits according to the national numbering plan, and no "sending complete". See ITU-T T Rec. Q.763 [15], 3.9. IA5String 6.1.4.2 PX_ISUP_TX_CLD_natAddr_m ax "nature of address" value sent in the "Called party number" parameter in the IAM message, containing the maximum number of digits according to the national numbering plan, and no "sending complete". See ITU-T T Rec. Q.763 [15], 3.9. bitstring(7) 6.1.5.1 PX_ISUP_IAM_CLD_digits_less "address digits" value (less than minimum number digits to route the call) sent in the "Called party number" parameter in the IAM message. IA5String 6.1.5.2 PX_ISUP_IAM_CLD_natAddr_l ess "nature of address" value (number of digits less than minimum number digits to route the call) sent in the "Calling party number" parameter in the IAM message. See ITU-T T Rec. Q.763 [15], 3.9. bitstring(7) 6.1.6.1 PX_ISUP_IAM_CLD_digits_min "address digits" value sent in the "Called party number" parameter in the IAM message, containing the minimum number of digits required for routing, and no "sending complete". See ITU-T T Rec. Q.763 [15], 3.9. IA5String 6.1.6.2 PX_ISUP_TX_CLD_natAddr_mi n "nature of address" value sent in the "Called party number" parameter in the IAM message, containing the minimum number of digits required for routing, and no "sending complete". See ITU-T T Rec. Q.763 [15], 3.9. bitstring(7) Calling party number - receiving 6.2.1 PX_ISUP_IAM_CLI_digits_rxIna t Default "address digits" value received in the "Calling party number" parameter in the IAM message, when the Called party number is "international". See ITU-T T Rec. Q.763 [15], 3.10. IA5String 6.2.2 PX_ISUP_IAM_CLI_digits_rxNa t Default "address digits" value received in the "Calling party number" parameter in the IAM message, when the Called party number is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.10. IA5String ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 37 Item Module Parameter Description Type Value Calling party number - sending 6.3.1 PX_ISUP_IAM_CLI_digits_txIna t Default "address digits" value sent in the "Calling party number" parameter in the IAM message, when the Called party number is "international". See ITU-T T Rec. Q.763 [15], 3.10. IA5String 6.3.2 PX_ISUP_IAM_CLI_digits_txNat Default "address digits" value sent in the "Calling party number" parameter in the IAM message, when the Called party number is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.10. IA5String Generic number - receiving 6.4.1 PX_ISUP_IAM_GEN_digits_rxIn at "address digits" value received in the "Generic number" parameter in the IAM message, when the Nature of Address is "international number". See ITU-T T Rec. Q.763 [15], 3.26. IA5String 6.4.2 PX_ISUP_IAM_GEN_digits_rxN at "address digits" value received in the "Generic number" parameter in the IAM message, when the Nature of Address is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.26. IA5String 6.4.3 PX_ISUP_ANM_GEN_digits_rxI nat "address digits" value received in the "Generic number" parameter in the ANM message, when the Nature of Address is "international number". See ITU-T T Rec. Q.763 [15], 3.26. IA5String 6.4.4 PX_ISUP_ANM_GEN_digits_rx Nat "address digits" value received in the "Generic number" parameter in the ANM message, when the Nature of Address is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.26. IA5String Generic number - sending 6.5.1 PX_ISUP_IAM_GEN_digits_txIn at "address digits" value sent in the "Generic number" parameter in the IAM message, when the Nature of Address is "international number". See ITU-T T Rec. Q.763 [15], 3.26. IA5String 6.5.2 PX_ISUP_IAM_GEN_digits_txN at "address digits" value sent in the "Generic number" parameter in the IAM message, when the Nature of Address is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.26. IA5String 6.5.3 PX_ISUP_ANM_GEN_digits_txI nat "address digits" value sent in the "Generic number" parameter in the ANM message, when the Nature of Address is "international number". See ITU-T T Rec. Q.763 [15], 3.26. IA5String 6.5.4 PX_ISUP_ANM_GEN_digits_tx Nat "address digits" value sent in the "Generic number" parameter in the ANM message, when the Nature of Address is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.26. IA5String Conected number - receiving 6.6.1 PX_ISUP_ANM_CPN_digits_rxI nat "address digits" value received in the "Connected number" parameter in the ANM message, when the Nature of Address is "international number". See ITU-T T Rec. Q.763 [15], 3.28. IA5String 6.6.2 PX_ISUP_ANM_CPN_digits_rx Nat "address digits" value received in the "Connected number" parameter in the ANM message, when the Nature of Address is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.28. IA5String ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 38 Item Module Parameter Description Type Value Conected number - receiving 6.7.1 PX_ISUP_ANM_CPN_digits_txI nat "address digits" value sent in the "Connected number" parameter in the ANM message, when the Nature of Address is "international number". See ITU-T T Rec. Q.763 [15], 3.28. IA5String 6.7.2 PX_ISUP_ANM_CPN_digits_tx Nat "address digits" value sent in the "Connected number" parameter in the ANM message, when the Nature of Address is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.28. IA5String Original called number - receiving 6.8.1 PX_ISUP_IAM_OCN_digits_rxIn at "address digits" value received in the "Original called number" parameter in the IAM message, when the Nature of Address is "international number". See ITU-T T Rec. Q.763 [15], 3.39. IA5String 6.8.2 PX_ISUP_IAM_OCN_digits_rxN at "address digits" value received in the "Original called number" parameter in the IAM message, when the Nature of Address is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.39. IA5String Original called number - sending 6.9.1 PX_ISUP_TX_OCN_natOfAddr essInd Default value for element natureOfAddressIndicator inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.39. bitstring(7) 6.9.2 PX_ISUP_TX_OCN_addrSignal s Default value for element addressSignals inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.39. IA5String Redirecting number - receiving 6.10.1 PX_ISUP_IAM_RDN_digits_rxIn at "address digits" value received in the "Redirecting number" parameter in the IAM message, when the Nature of Address is "international number". See ITU-T T Rec. Q.763 [15], 3.44. IA5String 6.10.2 PX_ISUP_IAM_RDN_digits_rxN at "address digits" value received in the "Redirecting number" parameter in the IAM message, when the Nature of Address is "national (sign.) number". See ITU-T T Rec. Q.763 [15], 3.44. IA5String Redirecting number - sending 6.11.1 PX_ISUP_TX_RDN_natOfAddre ssInd Default value for element natureOfAddressIndicator inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.44. bitstring(7) 6.11.2 PX_ISUP_TX_RDN_addrSignal s Default value for element addressSignals inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.44. IA5String ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 39 Item Module Parameter Description Type Value Redirection number - receiving 6.12 PX_ISUP_RX_RNN_addrSignal s Default value for element addressSignals inside Redirection number parameter (RNN); Optional(O) format (to be received in ACM or CPG messages). See ITU-T T Rec. Q.763 [15], 3.46. IA5String Redirection number - receiving 6.13.1 PX_ISUP_TX_RNN_natOfAddre ssInd Default value for element natureOfAddressIndicator inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field in ANM or CPG messages). See ITU-T T Rec. Q.763 [15], 3.46. bitstring(7) 6.13.2 PX_ISUP_TX_RNN_addrSignal s Default value for element addressSignals inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.46. IA5String Subsequent number 6.14.1 PX_ISUP_SAM_SQN_digits_txL ess_AllowRoute "address digits" value sent in the "Subsequent number" parameter in a SAM message, containing enough number digits to allow the routing to the SIP side, where the IAM contained less than the minimum digits to route the call through to the SIP side. See ITU-T T Rec. Q.763 [15], 3.51. 6.14.2 PX_ISUP_SAM_SQN_digits_tx_ 2nd "address digits" value sent in the "Subsequent number" parameter in the SAM message, containing the second part of the number, where the IAM contained already enough digits to route the call through to the SIP side. See ITU-T T Rec. Q.763 [15], 3.51. 6.14.3 PX_ISUP_SAM_SQN_digits_tx_ 3rd "address digits" value sent in the "Subsequent number" parameter in the second SAM message, containing the third part of the number, where the IAM contained already enough digits to route the call through to the SIP side. See ITU-T T Rec. Q.763 [15], 3.51. 6.14.4 PX_ISUP_SAM_SQN_digits_tx_ 4th "address digits" value sent in the "Subsequent number" parameter in the SAM message, containing the fourth and final part of the number, where the IAM contained already enough digits to route the call through to the SIP side. See ITU-T T Rec. Q.763 [15], 3.51. 6.14.5 PX_ISUP_SAM_SQN_digits_tx_ 4th_max "address digits" value sent in the "Subsequent number" parameter in the third SAM message, containing the fourth and final part of the number with the amount of digits leading to the overall maximum of digits allowed according to the numbering plan, where the IAM contained already enough digits to route the call through to the SIP side. See ITU-T T Rec. Q.763 [15], 3.51. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 40 Item Module Parameter Description Type Value Backward call indicators 6.15.1 PX_ISUP_TX_BCI_v_chargeInd Default value for element chargeIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(2) 6.15.2 PX_ISUP_TX_BCI_v_cldPStatIn d Default value for element calledPartysStatusIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(2) 6.15.3 PX_ISUP_TX_BCI_v_cldPCatIn d Default value for element calledPartysCategoryIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(2) 6.15.4 PX_ISUP_TX_BCI_v_eTOeMet hodInd Default value for element end_to_endMethodIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(2) 6.15.5 PX_ISUP_TX_BCI_v_interwInd Default value for element interworkingIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(1) 6.15.6 PX_ISUP_TX_BCI_v_eTOeInfoI nd Default value for element end_to_endInformationIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(1) 6.15.7 PX_ISUP_TX_BCI_v_iSDNUser PartInd Default value for element iSDNUserPartIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(1) 6.15.8 PX_ISUP_TX_BCI_v_holdingIn d Default value for element holdingIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(1) 6.15.9 PX_ISUP_TX_BCI_v_iSDNAcce ssInd Default value for element iSDNAccessIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(1) ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 41 Item Module Parameter Description Type Value 6.15.10 PX_ISUP_TX_BCI_v_echoCont rDevInd Default value for element echoControlDeviceIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(1) 6.15.11 PX_ISUP_TX_BCI_v_sCCPMet hodInd Default value for element sCCPMethodIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.5. bitstring(2) Calling party category 6.16 PX_ISUP_TX_CGC_cliPCatego ry Default value for element callingPartysCategory inside Calling party"s category parameter (CGC); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.11. bitstring(8) Forward call indicators 6.17.1 PX_ISUP_TX_FCI_natInternatC allInd Default value for element natInternatCallIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(1) 6.17.2 PX_ISUP_TX_FCI_endToEndM ethodInd Default value for element endToEndMethodIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(2) 6.17.3 PX_ISUP_TX_FCI_interwInd Default value for element interworkingIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(1) 6.17.4 PX_ISUP_TX_FCI_eTOeInfoInd ic Default value for element endToEndInfoIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(1) 6.17.5 PX_ISUP_TX_FCI_iSDNUserPa rtInd Default value for element iSDNUserPartIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(1) 6.17.6 PX_ISUP_TX_FCI_iSDNUserPa rtPrefInd Default value for element iSDNUserPartPrefIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(2) ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 42 Item Module Parameter Description Type Value 6.17.7 PX_ISUP_TX_FCI_iSDNAccess Ind Default value for element iSDNAccessIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(1) 6.17.8 PX_ISUP_TX_FCI_sCCPMetho dInd Default value for element sCCPMethodIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(2) 6.17.9 PX_ISUP_TX_FCI_reserved Default value for element reserved inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.23. bitstring(4) Nature of connection indicators 6.18.1 PX_ISUP_TX_NCI_satelliteInd Default value for element satelliteIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.35. bitstring(2) 6.18.2 PX_ISUP_TX_NCI_contCheckIn d Default value for element continuityCheckIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.35. bitstring(2) 6.18.3 PX_ISUP_TX_NCI_echoContrD evInd Default value for element echoControlDeviceIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.35. bitstring(1) Range and status 6.19.1 PX_ISUP_TX_RAS_range Default value for element range inside Range and status parameter (RAS); Variable(V) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.43. bitstring(8) 6.19.2 PX_ISUP_TX_RAS_status Default value for element status inside Range and status parameter (RAS); Variable(V) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.43. octetstring Redirection number restriction 6.21 PX_ISUP_TX_RNS_presRestrIn d Default value for element presRestrIndicator inside Redirection number restriction parameter (RNS); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.46. bitstring(2) ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 43 Item Module Parameter Description Type Value Transmission medium required 6.20 PX_ISUP_TX_TMR_transmMed Req Default value for element transmissionMediumRequirement inside Transmission medium requirement parameter (TMR); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.54. bitstring(8) Hop counter 6.21 PX_ISUP_TX_HPC_hopCounte r Default value for element hopCounter inside Hop counter parameter (HPC); Optional(O) format (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.763 [15], 3.80. bitstring(5) User-to-user information 6.22.1 PX_ISUP_UUI_userInfo_rx Default "user-to-user information" value received in the "User-to-user information" parameter. See ITU-T T Rec. Q.763 [15], 3.61. octetstring 6.22.2 PX_ISUP_UUI_userInfo_tx Default "user-to-user information" value sent in the "User-to-user information" parameter. See ITU-T T Rec. Q.763 [15], 3.61. octetstring Cause indicators 6.23 PX_ISUP_CAU_location "Location" value sent in the "Cause indicators" parameter. bitstring(4) Unknown parameter/message identifier 6.24.1 PX_ISUP_TX_unknown_param eter_type Default value for an unknown parameter type (to be sent when the TP does not specify a specific value for that field). bitstring(8) 6.24.2 PX_ISUP_TX_unknown_messa ge_type Default value for an unknown message type (to be sent when the TP does not specify a specific value for that field). bitstring(8) Bearer capability 6.25 PX_userInfoLayer1 Default value for bit field element "User Information Layer 1 Protocol Indicator" in IE Bearer Capability encapsulated in "User service information" or "Access transport" parameter (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.931 [20], 4.5.5. bitstring(5) Called party subaddress 6.26.1 PX_ISUP_RX_cdps_information Called party subaddress information value received in the "Calling party subaddress" in the ATP parameter in the IAM message. See ITU-T T Rec. Q.931 [20], 4.5.8. octetstring 6.26.2 PX_ISUP_TX_cdps_information Default value for called party subaddress information (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.931 [20], 4.5.8. octetstring 6.26.3 PX_ISUP_TX_cdps_odd_even_i ndicator Default value for called party subaddress odd even indicator (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.931 [20], 4.5.8. bitstring(1) ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 44 Item Module Parameter Description Type Value Calling party subaddress 6.27.1 PX_ISUP_RX_cgps_information Calling party subaddress information value received in the "Calling party subaddress" in the ATP parameter in the IAM message. See ITU-T T Rec. Q.931 [20], 4.5.11. octetstring 6.27.2 PX_ISUP_TX_cgps_information Default value for calling party subaddress information (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.931 [20], 4.5.11. octetstring 6.27.3 PX_ISUP_TX_cgps_odd_even_i ndicator Default value for calling party subaddress odd even indicator (to be sent when the TP does not specify a specific value for that field). See ITU-T T Rec. Q.931 [20], 4.5.11. bitstring(1) Connected subaddress 6.26.1 PX_ISUP_RX_cons_information Connected subaddress information value received in the "Calling party subaddress" in the ATP parameter in the ANM message. See EN 300 097-1 [21], 7.2. octetstring 6.26.2 PX_ISUP_TX_cons_information Default value for connected subaddress information (to be sent when the TP does not specify a specific value for that field). See EN 300 097-1 [21], 7.2. octetstring 6.26.3 PX_ISUP_TX_cons_odd_even_i ndicator Default value for connected subaddress odd even indicator (to be sent when the TP does not specify a specific value for that field). See EN 300 097-1 [21], 7.2. bitstring(1) NOTE: For Module Parameters containing address digits the following requirement applies: each digit is represented either as one of the IA5 characters "0" to "9", or as one of the special IA5 characters "*", "#", "a", "b" or "c". ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 45 Annex B (informative): TTCN-3 library modules B.1 Electronic annex, zip file with TTCN-3 code The TTCN-3 library modules are contained in archive ts_18600903v020101p0.zip which accompanies the present document. ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 46 History Document history V2.1.1 September 2009 Publication
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
1 Scope
|
The present document specifies the network PICS (Protocol Implementation Conformance Statement) of the Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part EN 283 027 [20]. The references [20] and [26] are identical.
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • For a non-specific reference, the latest version 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.
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
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] ITU-T Recommendations Q.761 to Q.764 (2000): "Signalling System No.7 ISDN User Part (ISUP)". [2] ITU-T Recommendation Q.731.7 (1997): "Stage 3 description for number identification supplementary services using Signalling System No. 7: Malicious call identification (MCID)". [3] ITU-T Recommendation Q.732.2 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call diversion services". [4] ITU-T Recommendation Q.732.7 (1996): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Explicit Call Transfer". [5] ITU-T Recommendation Q.737.1 (1997): "Stage 3 description for additional information transfer supplementary services using Signalling System No. 7: User-to-user signalling (UUS)". [6] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [7] IETF RFC 3262 (2002): "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". [8] ISO/IEC 9646-7 (1995): "Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [9] ETSI EN 383 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control (BICC) Protocol or ISDN User Part (ISUP) [ITU-T Recommendation Q.1912.5, modified]". [10] ITU-T Recommendation Q.1912.5 (03/2004): "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control or ISDN User Part". ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 6 [11] ITU-T Recommendation E.164 (2005): "The international public telecommunication numbering plan". [12] IETF RFC 768 (1980): "User Datagram Protocol". [13] IETF RFC 761 (1980): "DoD standard Transmission Control Protocol". [14] ITU-T Recommendation Q.767 (1991): "Application of the ISDN user part of CCITT signalling system No. 7 for international ISDN interconnections". [15] ITU-T Recommendation Q.731.1 (1996): "Stage 3 description for number identification supplementary services using Signalling System No. 7: Direct-dialling-In (DDI)". [16] ITU-T Recommendation Q.731.5 (1993): "Stage 3 description for number identification supplementary services using Signalling System No. 7: Connected line identification presentation (COLP)". [17] ITU-T Recommendation Q.118 (1997): "Abnormal conditions - Special release arrangements". [18] ITU-T Technical Report TRQ.2815 / Q.Sup45 (2003): "Requirements for interworking BICC/ISUP network with originating/destination networks based on Session Initiation Protocol and Session Description Protocol". [19] ITU-T Recommendation Q.1902.4: "Bearer Independent Call Control protocol (Capability Set 2): Basic call procedures". [20] ETSI ES 283 027 (V2.5.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) Endorsement of the SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks [3GPP TS 29.163 (Release 7), modified]". [21] ETSI TS 183 008: "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". [22] ETSI TS 183 010: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Signalling Control Protocol; Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification". [23] ETSI TS 183 029: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification". [24] ETSI TS 183 005: Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); NGN Signalling Control Protocol; Conference (CONF) PSTN/ISDN simulation services. [25] ETSI TS 183 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification". [26] ETSI TS 129 527 (V8.2.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; Endorsement of the SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks [3GPP TS 29.163 (Release 7), modified] (3GPP TS 29.527 version 8.2.0 Release 8)". [27] ITU-T Recommendation Q.1902.2: "Bearer Independent Call control protocol (Capability Set 2) and Signalling System No.7 ISDN User Part: General functions of messages and parameters". [28] 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". [29] ITU-T Recommendation Q.730: "ISDN user part supplementary services". ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 7 [30] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". [31] ITU-T Recommendation Q.731.3: "Stage 3 description for number identification supplementary services using Signalling System No. 7 : Calling line identification presentation (CLIP)".
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
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. Not applicable.
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
3 Definitions and abbreviations
| |
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: Abstract Test Case (ATC): complete and independent specification of the actions required to achieve a specific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state and ending in a stable testing state Abstract Test Method (ATM): description of how an SUT is to be tested, given at an appropriate level of abstraction to make the description independent of any particular realization of a Means of Testing, but with enough detail to enable abstract test cases to be specified for this method Abstract Test Suite (ATS): test suite composed of abstract test cases Implementation Under Test (IUT): implementation of one or more OSI protocols in an adjacent user/provider relationship, being part of a real open system which is to be studied by testing Means of Testing (MOT): combination of equipment and procedures that can perform the derivation, selection, parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a conformance log PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes the PICS PIXIT proforma: document, in the form of a questionnaire, which when completed for the SUT becomes the PIXIT Point of Control and Observation (PCO): point within a testing environment where the occurrence of test events is to be controlled and observed, as defined in an Abstract Test Method pre-test condition: setting or state in the SUT which cannot be achieved by providing stimulus from the test environment Protocol Implementation Conformance Statement (PICS): statement made by the supplier of a protocol claimed to conform to a given specification, stating which capabilities have been implemented Protocol Implementation eXtra Information for Testing (PIXIT): statement made by a supplier or implementor of an SUT (protocol) which contains or references all of the information related to the SUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the SUT SIP number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [11] System Under Test (SUT): real open system in which the SUT resides user: access protocol entity at the User side of the user-network interface where a T reference point or coincident S and T reference point applies ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 8
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ATC Abstract Test Case ATM Abstract Test Method ATS Abstract Test Suite BICC Bearer Independent Call Control protocol CIC Circuit Identification Code ICS Implementation Conformance Statement ISDN Integrated Services Digital Network ISUP ISDN User Part IUT Implementation Under Test MOT Means Of Testing PCO Point of Control and Observation PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing SIP Session Initiation Protocol SUT System Under Test TP Test Purpose TSS&TP Test Suite Structure and Test Purposes TSS Test Suite Structure TTCN Tree and Tabular Combined Notation
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
4 Scenarios
|
4.1 SIP Profile A and B for interworking between SIP and BICC/ISUP IP IP, ATM or TDM BICC or ISUP Profile scope SIP Proxy G/W Type 1 SIP Figure 1: Profile Scope for SIP Interworking with BICC/ISUP with a Type 1 Gateway ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 9 IP IP, ATM or TDM BICC or ISUP Profile scope SIP BICC CSF-T SIP Proxy G/W Type 2 SN Figure 2: Profile Scope for SIP Interworking with BICC/ISUP with a Type 2 Gateway 4.2 SIP Profile C for Interworking Between SIP with MIME Encoding of ISUP and BICC/ISUP IP IP, ATM or TDM BICC or ISUP Profile scope SIP with MIME encoding of ISUP BICC or ISUP IP, ATM or TDM IP G/W Type 3 G/W Type 3 Figure 3: Profile Scope for SIP with MIME encoding of ISUP Interworking with BICC/ISUP with Type 3 Gateways ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 10 IP IP, ATM or TDM BICC or ISUP Profile scope SIP with MIME encoding of ISUP IP CSF-T BICC SN G/W Type 3 G/W Type 4 BICC or ISUP IP, ATM or TDM Figure 4: Profile Scope for SIP, with MIME Encoding of ISUP, Interworking with BICC/ISUP with Type 3 and 4 Gateways IP IP, ATM or TDM BICC or ISUP Profile scope SIP with MIME encoding of ISUP G/W Type 3 SIP Proxy* Figure 5: Profile Scope for SIP with MIME encoding of ISUP Interworking with BICC/ISUP with Type 3 Gateways ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 11 IP IP, ATM or TDM BICC or ISUP Profile scope SIP (with MIME encoding of ISUP) BICC CSF-T SIP Proxy G/W Type 4 SN Figure 6: Profile Scope for SIP, with MIME Encoding of ISUP, Interworking with BICC/ISUP with Type 4 Gateway IP SIP with MIME encoding of ISUP BICC IP or ATM G/W Type 3 NNI SIP Proxy* Profile scope Figure 7: Profile for SIP, with MIME Encoding of ISUP, Interworking with BICC/ISUP with Type 3 Gateway
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5 PICS proforma
| |
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.1 Instructions for completing the PICS proforma
| |
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.1.1 Other information
|
More detailed instructions are given at the beginning of the different clauses of the PICS proforma. The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5.4. ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 12
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.1.2 Purposes and structure
|
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in reference specification [1] to [25] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of information: • instructions for completing the PICS proforma; • identification of the implementation; • identification of the reference protocol specification; • PICS proforma tables (containing the global statement of conformance).
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.1.3 Conventions
|
The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [8]. Item column It contains a number that identifies the item in the table. Item description column It describes each respective item (e.g. parameters, timers, etc.). Reference column It gives reference to the specification(s) [1] to [25], except where explicitly stated otherwise. Status column The following notations, defined in ISO/IEC 9646-7 [8], are used for the status column: m mandatory - the capability is required to be supported. n/a not applicable - in the given context, it is impossible to use the capability. No answer in the support column is required. o optional - the capability may be supported or not. o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. ci conditional - the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression that is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." shall be used to avoid ambiguities. If an ELSE clause is omitted, "ELSE n/a" shall be implied. NOTE: Support of a capability means that the capability is implemented in conformance to the specification(s) [1] to [25]. ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 13 Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [8], are used for the support column: • Y or y supported by the implementation. • N or n not supported by the implementation. • N/A or n/a or "no answer required" (allowed only if the status is N/A, directly or after evaluation of a conditional status). Values allowed column This column contains the values or the ranges of values allowed. Values supported column The support column shall be filled in by the supplier of the implementation. In this column the values or the ranges of values supported by the implementation shall be indicated. References to items For each possible item answer (answer in the support column) within the PICS proforma, a unique reference exists. It is defined as the table identifier, followed by a slash character "/", followed by the item number in the table. If there is more than one support column in a table, the columns shall be discriminated by letters (a, b, etc.) respectively. EXAMPLE: 5/4 is the reference to the answer of item 4 in table 5.
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.2 Identification of the implementation
|
Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the ICS should be named as the contact person.
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.2.1 Date of the statement
|
Date of the statement:
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.2.2 Implementation Under Test (IUT) identification
|
IUT name: IUT version:
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.2.3 System Under Test (SUT) identification
|
SUT name: Hardware configuration: Operating system: ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 14
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.2.4 Product supplier
|
Name: Address: Telephone number: Facsimile number: Additional information:
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.2.5 Client
|
Name: Address: Telephone number: Facsimile number: Additional information:
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.2.6 PICS contact person
|
Name: Telephone number: Facsimile number: Additional information:
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3 PICS proforma tables
| |
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3.1 Global statement of conformance
|
(Yes/No) Are all mandatory capabilities implemented? NOTE: Answering "No" to this question indicates non-conformance to the reference protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming.
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3.2 Roles
|
Table 1: Roles Item Item description column Reference Status Support 1 The SUT is a SIP-I implementation? ITU-T RecommendationTRQ.2815 [18] o 2 connected with a BICC Network? ITU-T Recommendation Q.1902.2 [27] o.12 3 connected with a ISUP Network? ITU-T Recommendation Q.764 [1] o.12 4 Is the SUT connected with a µ-law network? ES 283 027, clauses 7.2.3.1.2.5 and 7.2.3.2.2.2 [20] o 5 Is the SUT an outgoing international exchange? ITU-T Recommendation Q.764 [1] o 6 Is the SUT an incoming international exchange? ITU-T Recommendation Q.764 [1] o o.12: It is mandatory to support one of these items. ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 15
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3.3 Connection types
|
Table 2: Connection types Item Item description column Reference Status Support 1 The SUT support the media type "audio" and media format 0, 8? ES 283 027, clause 7.2.3.1.2.5 [20] o.21 2 The SUT support the media type "audio" and media format 9? ES 283 027, clause 7.2.3.1.2.5 [20] o.21 3 The SUT support the media type "audio" and attribute value CLEARMODE? ES 283 027, clause 7.2.3.1.2.5 [20] o.21 4 The SUT support the media type "image" and media format t38? ES 283 027, clause 7.2.3.1.2.5 [20] o.21 5 The SUT support the dynamic assignment for codec? ES 283 027, clause 7.2.3.1.2.5 [20] o.21 6 The SUT use the transport protocol udptl? RFC 768 [12] o 7 The SUT use the transport protocol tcptl? RFC 761 [13] o 8 Support the transcoding of the AMR codec to G.711 PCM RFC 3267 [28] o o.21: It is mandatory to support at least one of these items.
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3.4 Forward address signalling
|
Table 3: Forward address signalling Item Item description column Reference Status Support 1 SIP use the en bloc operation in the forward address signalling (sending)? ES 283 027, clause 7.2.3.2.1 [20] o.31 2 SIP use the overlap operation in the forward address signalling (sending)? ES 283 027, clause 7.2.3.2.1a [20] o.31 3 SIP support the en bloc operation in the forward address signalling (receiving)? ES 283 027, clause 7.2.3.1.1 [20] o 4 SIP support the overlap operation in the forward address signalling (receiving)? ES 283 027, clause 7.2.3.1.1 [20] o 5 ISUP use the en bloc operation in the forward address signalling (sending)? ES 283 027, clause 7.2.3.1.1 [20] o.31 6 ISUP use the overlap operation in the forward address signalling (sending)? ES 283 027, clause 7.2.3.1.1 [20] o.31 7 ISUP support the en bloc operation in the forward address signalling (receiving)? ES 283 027, clause 7.2.3.2.1 [20] o 8 ISUP support the overlap operation in the forward address signalling (receiving)? ES 283 027, clause 7.2.3.2.1 [20] o 9 SIP support INVITE requests without determining the end of address signalling. ES 283 027, clause 7.2.3.2.1a [20] o o.31: It is mandatory to support at least one of these items.
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3.5 Role independent capabilities
|
Table 4: Role independent capabilities Item Item description column Reference Status Support 1 The SUT use the Continuity check procedures during call setup? ES 283 027 [20], clause 7.2.3.1.1 o 2 The SUT support the Continuity check procedures during call setup? ES 283 027 [20], clause 7.2.3.2.1 m 3 The SUT support hop counter procedure? ES 283 027 [20], clause 7.2.3.1.2.9 o ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 16 Item Item description column Reference Status Support 4 The SUT support internal resource reservations (preconditions used)? ES 283 027 [20], clause 7.2.3.2.1 o 5 The SUT support the reliability of provisional responses? RFC 3262 [7] o 6 The SUT perform the automatic repeat attempt? Clause 2.8.1 of ITU-T Rec Q.764 [1]; Clause 12.4 of ITU-T Recommendation Q.1902.4 [19] o 7 The SUT support the propagation delay determination procedure? Clause 2.6 of ITU-T Recommendation Q.764; clause 8.5 of ITU-T Recommendation Q.1902.4 [19] o 8 The SUT perform the automatic repeat attempt in case of dual seizure? Clause 2.9.1 of ITU-T Recommendation Q.764 [1]; clause 13.2 of ITU-T Recommendation Q.1902.4 [19] o 9 The SUT send ACM after determination of end of address signalling? Network option o 10 The SUT is control exchange for the Suspend procedure? o 11 The SUT use internal resource reservations (preconditions used)? ES 283 027 [20], clause 7.2.3.2.1 o 12 The SUT controls charging? Clause 2.1.4.2 of ITU-T Recommendation Q.764 [1] o 13 The SUT satisfy the call using a new address provided in a Contact header field received in a 3xx response? Clause 13.2.2.2 of RFC 3261 [6] o 14 The SUT perform transcoding of media stream at the I-MGCF? ES 283 027 [20], clause 7.2.3.2.2.2 o 15 Does the MGCF provides the interworking of an ACM or CPG with the indication “inband info available” in a 183 response AND the interworking of a 183 response with P-Early-Media-Media header authorizing early media in a early ACM or CPG with “inband info available” indication? ES 283 027 [20], clause 2.7.3.1 and 7.2.3.2 o 16 Does the SUT sends the IAM FCi interworking indicator set to “0” and the IAM FCi ISDN user part/BICC indicator set to “1” and the IAM FCi ISDN access indicator is set to “1” and the Nature of connection indicators, Satellite indicator set to “00”, if the TMR is sent with 64 kBit/s? ES 283 027 [20], clause 7.2.3.1.2.3 c41 17 Does the SUT sends the ACM BCi Interworking indicator set to “0” and and the ACM BCi ISDN user part/BICC indicator set to “1” and the ACM BCi ISDN access indicator set to “1”if the INVITE was sent with CLEARMODE codec? ES 283 027 [20], clause 7.2.3.2.5.1/ c41 18 Is the PSTN XML mime extension used to carry DSS1 information elements? ES 283 027, annex F.3 [20] o 19 The signalling procedures for connection type allowing fallback are supported 2.5/Q.764 [1] o 20 Does the SUT support the Information request procedure? ES 283 027 [20], clause 7.2.3.2.1.3 o c41: IF 2/3 THEN o ELSE n/a. ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 17
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3.6 Supplementary Services Major Capabilities
|
Table 5: Supplementary Services Major Capabilities Item Item description column Reference in ITU-T Rec Q.1912.5 [10] Status Support 1 The SUT support the service Calling Line Identification Presentation (CLIP)? 7.4.1 m 2 The SUT support the service Calling Line Identification Restriction (CLIR)? 7.4.1 m 3 The SUT support the service Connected Line Identification Presentation (COLP)? 7.4.2 o 4 The SUT support the service Connected Line Identification Restriction (COLR)? 7.4.2 o 5 The SUT support the service Call Hold (HOLD)? 7.4.10 o 6 The SUT support the service Terminal Portability (TP)? 7.4.13 o 7 The SUT support the service Closed User Group (CUG)? 7.4.16 o 8 The SUT support the service Sub-addressing (SUB)? 7.4.5 o 9 The SUT support the service Malicious Call Identification (MCID)? 7.4.4 o 10 The SUT support the service Conference Call, add-on (CONF)? 7.4.14 o 11 The SUT support the service Explicit Call Transfer (ECT)? 7.4.8 o 12 The SUT support the service Call Forwarding Busy (CFB)? 7.4.6 o 13 The SUT support the service Call Forwarding No Reply (CFNR)? 7.4.6 o 14 The SUT support the service Call Forwarding Unconditional (CFU)? 7.4.6 o 15 The SUT support the service Call Deflection (CD)? 7.4.7 o 16 The SUT support the service Call Waiting (CW)? 7.4.9 o 17 The SUT support the service Completion Call to busy subscriber The SUT (CCBS)? 7.4.11 o 19 The SUT support the Three-Party (3PTY) service? 7.4.14 o 20 The SUT support the service Completion Call on No Reply (CCNR)? 7.4.12 o 21 The SUT support the service Anonymous Call Rejection (ACR)? 7.4.23 c.51 22 The SUT support the generic notification procedure for supplementary services 1.3.4 / ITU-T Rec. Q.730 [29] o c.51: IF 1/9 THEN o ELSE n/a. Table 6: Calling Line Identification (CLI) Item Item description column Reference Status Support 1 The SUT include a network provided E.164 calling party number if the P-Asserted -Identity header field has not been received or not in the format '+'CC+NDC+SN; address signal: network provided? Table 3 [20] o 2 The SUT include a network provided E.164 calling party number if the P-Asserted -Identity header field has not been received or not in the format '+'CC+NDC+SN, the From header field is in the format '+'CC+NDC+SN; address signal: derived from the From header field? Table 3 [20] o 3 The SUT include an additional calling party number if a From header field has been received in the format '+'CC+NDC+SN; address signal: derived from the From header field? Table 3 [20] o 4 The SUT discard the calling party number in case of bilateral agreements if it is "presentation restricted"? Clause 3.5.2.3.1 of ITU-T Rec. Q.731.1 [15] o 5 The SUT discard the additional calling party number in case of bilateral agreements if it is "presentation restricted"? Clause 3.5.2.3.1 of ITU-T Rec. Q.731.1 [15] o 6 The SUT discard the calling party number, if the address is marked not available? 3.5.2.3.1/ITU-T Rec. Q.731.3 [31] o 7 The SUT discard the additional calling party number in case of bilateral agreements if it is "presentation allowed"? Network option o 8 The SUT discard the calling party number in case of bilateral agreements if it is "presentation allowed"? Network option o ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 18 Item Item description column Reference Status Support 9 The SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "presentation allowed" if no P-Asserted - Identity header field has not been received or not in the format '+'CC+NDC+SN? Table 3 [20] o 10 The SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "presentation restricted" if no P-Asserted - Identity header field has not been received or not in the format '+'CC+NDC+SN? Table 3 [20] o 11 The SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "address not available" if no P-Asserted - Identity header field has not been received or not in the format '+'CC+NDC+SN? Table 3 [20] o 12 The SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "presentation restricted by the network" if no P-Asserted -Identity header field has not been received or not in the format '+'CC+NDC+SN? Table 3 [20] o Table 7: COnnected Line identification (COL) Item Item description column Reference Status Support 1 The SUT discard the connected number in case of bilateral agreements if it is "presentation restricted "? Clause 5.5.2.4.1 of ITU-T Rec. Q.731.5 [16] o 2 The SUT discard the additional connected number in case of bilateral agreements if it is "presentation restricted"? Clause 5.5.2.4.1 of ITU-T Rec. Q.731.5 [16] o 3 The SUT discard the connected number in case of bilateral agreements if it is "presentation allowed"? Network option o 4 The SUT discard the additional connected number in case of bilateral agreements if it is "presentation allowed"? Network option o 5 The SUT is adding a prefix to an international connected number? Clause 5.5.2.3.1 of ITU- T Rec.Q.731.5 [16] o 6 The SUT invokes the COLP service by setting the "Connected Line Identity Request indicator" parameter of the "Optional forward call indicator" of the IAM to "requested" 7.4.2.1.1 [20] o Table 8: HOLD Item Item description column Reference Status Support 1 The SUT support that a party can put the other party on hold after alerting has commenced? 7.4.10 [20] o 2 The SUT support 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? 7.4.10 [20] o 3 Does the network support the hold and resume of media streams using the UPDATE method in the confirmed dialogue? 5.1/ RFC 3264 [30] o 4 Does the SUT support the temporarily stops sending one or more unicast media streams 7.4.10 [20] o Table 9: Malicious Call Identification (MCID) Item Item description column Reference Status Support 1 The SUT returns an IRS with bit A of the MCID response indicator set to 0 "MCID not included", if the network does not support the MCID service? Clause 7.5.2.3.2 of ITU-T Rec. Q.731.7 [2] o ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 19 Table 10: Call DIVersion service (CDIV) Item Item description column Reference Status Support 1 The SUT discard the original called number if case of bilateral agreements? Clause 3.5.2.3.1 of ITU-T Rec. Q.732.2 [3] o 2 The SUT discard the redirecting number if case of bilateral agreements? Clause 3.5.2.3.1 of ITU-T Rec. Q.732.2 [3] o 3 The SUT add a prefix to an international original called number? Clause 3.5.2.4.1 of ITU-T Rec. Q.732.2 [3] o 4 The SUT add a prefix to an international redirecting number? Clause 3.5.2.4.1 of ITU-T Rec. Q.732.2 [3] o 5 The SUT discard the redirection number in case of bilateral agreements? Clause 3.5.2.3.1 of ITU-T Rec. Q.732 [3] o 6 Te SUT supports the mapping if History-Info header into the ISUP relevant parameters and messages 4.7.1.1 [20] o 7 The SUT supports the mapping of ISUP messages and parameters into SIP messages and History-Info header 4.7.1.1 [20] o Table 11: User-to-user service Item Item description column Reference Status Support 1 The SUT understand an explicit user-to-user request? Clauses 1.1.5.2.5.2.2, 1.2.5.2.5.2.1 and 1.3.5.2.5.2.1 of ITU-T Rec. Q.737.1 [5] o 2 The SUT support the rejection procedure of an explicit service request or discarding of user-to-user information as described in clause 1.1.5.x.5.2 of ITU-T Rec. Q.737.1 [5]? Clause 1.1.5.2.2.2 of ITU-T Rec. Q.737.1 [5] o 3 The SUT reject an user-to-user request service 3 not essential after call set-up using the FRJ message? 1.3.5.2.5.2.2/ITU-T Rec. Q.737 [5] o Table 12: ECT Item Item description column Reference Status Support 1 The SUT return a LOP (response) message with the indication "insufficient information"? Clause 7.7 of ITU-T Rec. Q.732.7 [4] o
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3.7 IMS simulation services
|
Table 13: Simulation services Item Item description column Reference Status Support 1 The SUT support the IMS simulation service Terminating Identificatio Presentatio/Restriction 7.5.2.3 [20] o 2 The SUT support the HOLD simulation service 4/ [22] o 3 The SUT support the ECT simulation service 4/ [23] o 4 The SUT support the CONF simulation service 4/ [24] o 5 The SUT support the CDIV simulation service 4/ [24] o ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 20
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.