.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 3 |
+| 6 Network Scenarios..... | 3 |
+| 7 Signalling requirements and conformance test cases ..... | 4 |
+| 8 Test cases for the exchange of signalling information ..... | 7 |
+| Appendix A – Verifying of the configuration of network service scenarios..... | 37 |
+| Bibliography..... | 41 |
+
+
+
+## Recommendation ITU-T Q.3905
+
+## Conformance test plan for number portability requirements defined by ITU-T Q-Suppl.4
+
+# 1 Scope
+
+This Recommendation describes conformance test plan for number portability requirements defined by ITU-T Q-series Recommendations – Supplement 4. The conformance test plan for number portability includes test configurations, network scenarios and test cases to verify conformance number portability solutions against requirements defined by ITU-T Q-series Recommendations – Supplement 4.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ITU-T Q.3933] ITU-T Recommendation Q.3933 (2015), *Reference benchmarking, background traffic profiles and KPIs for VoIP and FoIP in fixed networks*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined in [b-ITU-T Q-Suppl.4]:
+
+**3.1.1 address:** A string or combination of decimal digits, symbols and additional information which identifies the specific termination point(s) of connection in a public network(s) or, where applicable, in interconnected private network(s).
+
+**3.1.2 end user's number:** The ITU-T E.164 number used by the calling party to establish a call to the end user. This number is also used for presentation services like calling line identification (CLI) and connected line identification presentation (COLP).
+
+**3.1.3 donor network:** The initial network where a number was located before ever being ported.
+
+**3.1.4 donor service provider:** The service provider from whom the number was initially ported.
+
+**3.1.5 originating network:** The network serving a calling end user.
+
+**3.1.6 portable number:** An entire E.164 number identified by an appropriate authority which is subject to number portability.
+
+**3.1.7 ported number:** An end user's E.164 number that has been subject to number portability.
+
+**3.1.8 recipient network:** The network where a number is located after being ported.
+
+**3.1.9 recipient service provider:** The service provider to whom the number is ported.
+
+**3.1.10 routing number:** A number that is derived and used by the network to route the call towards a ported number.
+
+**3.1.11 initiating network:** A network that requires and obtains the routing information for number portability.
+
+**3.1.12 originating network:** The network serving a calling end user.
+
+**3.1.13 transit network(s):** A network between two networks.
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-------|--------------------------------------------|
+| ACQ | All Call Query |
+| BS | Base Station |
+| CCS | Common Channel Signaling |
+| CdPN | Unchanged Called Party Number |
+| CLI | Calling Line Identification |
+| CLIP | Calling Line Identification Presentation |
+| CLIR | Calling Line Identification Restriction |
+| COLP | Connected Line Identification Presentation |
+| COLR | Connected Line Identification Restriction |
+| DB | Database |
+| DDI | Direct Dial-in |
+| DLE | Destination Local Exchange |
+| HLR | Home Location Register |
+| IAM | Initial Address Message |
+| ISDN | Integrated Services Digital Network |
+| IN | Intelligent Network |
+| MOS-a | Mean Opinion Score-audio |
+| MSC | Mobile Switching Centre |
+| MSN | Multiple Subscriber Number |
+| NP | Number Portability |
+| NPCDB | Number Portability Central Database |
+| NPDB | Number Portability Database |
+| NPLDB | Number Portability Local Database |
+| NP ID | NP Indicator |
+| OLE | Originating Local Exchange |
+| OR | Onward Routing |
+| POI | Point of Interconnection |
+| PSTN | Public Switched Telephone Network |
+
+| | |
+|--------|-------------------------------|
+| REX | Recipient Exchange |
+| RNID | Recipient Network ID |
+| SCP | Service Control Point |
+| SMS | Short Message Service |
+| SMSC | Short Message Center |
+| SMS-GW | Short Message Service Gateway |
+| SRF | Signaling Relay Function |
+| SSP | Service Switching Point |
+| TS | Transit Exchange |
+| QoS | Quality of Service |
+
+## 5 Conventions
+
+None.
+
+# 6 Network Scenarios
+
+[b-ITU-T Q-Suppl.4] describes three network service scenarios for implementing number portability. In accordance with the functionality, there are two groups of service scenarios:
+
+- The first group is based on the method "all call query";
+- The second is based on the method "onward routing".
+
+The first scenario deals with the originating network/exchange which is not connected directly to number portability database (NPDB). In this case, the originating network/exchange forwards a request to the initiating network/exchange to obtain routing information.
+
+The second scenario is based on the fact that the initiating network/exchange also plays the role of the originating network/exchange of the calling subscriber. In this scenario, the request for routing information has to be sent to the number portability central database (NPCDB) through the donor network/exchange.
+
+In the third scenario donor network/exchange acts as an initiating network/exchange and requests the routing information in their number portability local database (NPLDB).
+
+The first and second scenarios belong to the first group which is related to "all call query", while the third scenario belongs to the second group which is related to "onward routing".
+
+Accordingly, the signalling transfer for the methods "all call query" and "onward routing" are shown in Figures 6-1 and 6-2 accordingly [b-ITU-T E.164 Suppl.2].
+
+
+
+Diagram illustrating the signalling transfer for the method 'all call query'. A 'Calling subscriber' (represented by a telephone icon) is connected to an 'Originating network' (represented by a circle containing a 'DB' cylinder). The 'Originating network' has a 'Lasting relation' (solid line) to a 'Transit network' (circle) and a 'Temporary relation' (dashed line) to a 'Donor network' (circle). The 'Transit network' has a 'Lasting relation' (solid line) to a 'Recipient network' (circle). The 'Donor network' has a 'Temporary relation' (dashed line) to the 'Called subscriber' (represented by a telephone icon). The 'Recipient network' has a 'Lasting relation' (solid line) to the 'Called subscriber'. Signalling messages are shown: 'a1) IAM' from the Originating network to the Transit network, 'a2) IAM' from the Transit network to the Recipient network, and 'b) IAM' from the Originating network to the Recipient network. A legend at the bottom left indicates that solid lines represent 'Lasting relation' and dashed lines represent 'Temporary relation'. The diagram is labeled 'Q.3905(16)\_F6-1' in the bottom right corner.
+
+**Figure 6-1 – The signalling transfer for the method "all call query"**
+
+
+
+```
+
+graph LR
+ CS[Calling subscriber] --> ON(Originating network)
+ ON -- IAM --> TNA(Transit network(s) (A))
+ TNA -- IAM --> DN(Donor network)
+ DN -- "a1) IAM" --> TNB(Transit network(s) (B))
+ DN -- "b) IAM" --> RN(Recipient network)
+ TNB -- IAM --> RN
+ RN --> CSub[Called subscriber]
+
+```
+
+Diagram illustrating the signalling transfer for the method 'onward routing'. A calling subscriber connects to an originating network, which sends an IAM (Initial Address Message) to transit network(s) (A). Transit network(s) (A) then sends an IAM to the donor network. The donor network contains a DB (Database). From the DB, two possible paths are shown: a1) IAM to transit network(s) (B), and b) IAM to the recipient network. Finally, the recipient network sends an IAM to the called subscriber.
+
+**Figure 6-2 – The signalling transfer for the method "onward routing"**
+
+This test specification shows the principle used to test all service scenarios mentioned above.
+
+## 7 Signalling requirements and conformance test cases
+
+This clause provides a list of requirements and relevant test specifications for number portability defined by [b-ITU-T Q-Suppl.4].
+
+**Table 1 – List of requirements and relevant testing specifications for implementing number portability**
+
+| Category | Ref. ITU-T Q-Suppl.4 (clause 8, pp. 12-13) | Description of requirement (except from [b-ITU-T Q-Suppl.4]) | #Test case | M/O |
+|----------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----|
+| LNP | R-1 | The signaling mechanisms that support number portability should not place any restrictions on the PSTN and ISDN services, including basic, supplementary and non-circuit-related based services | 8.01 | O |
+| MNP/LNP | R-2 | Number portability solutions shall allow that transit network(s) be used between originating and donor/initiating networks | 8.02 | M |
+| MNP/LNP | R-3 | Number portability solutions shall allow that transit network(s) be used between donor/initiating and recipient networks | | |
+| MNP/LNP | R-4 | Number portability solutions shall not interfere with carrier selection | 8.03 | O |
+| MNP/LNP | R-5 | Interoperability of various methods must be provided e.g., the signalling must be capable of providing interworking between onward routing and other methods | 8.04 | M |
+| MNP/LNP | R-6 | NP should not result in the looping of calls or messages | 8.05 | M |
+| MNP/LNP | R-7 | Outgoing international calls or messages shall be unaffected | 8.06 | O |
+| MNP/LNP | R-8 | It shall be possible to signal an indication that the NP status, if available, of the portable number | 8.07 | O |
+
+**Table 1 – List of requirements and relevant testing specifications for implementing number portability**
+
+| Category | Ref. ITU-T Q-Sup.4 (clause 8, pp. 12-13) | Description of requirement (except from [b-ITU-T Q-Suppl.4]) | #Test case | M/O |
+|----------|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----|
+| | | has been determined. The indication may be included for either ported or non-ported numbers | | |
+| MNP/LNP | R-9 | Only the E.164 number (not including prefixes, etc.) should be considered eligible to be ported | 8.08 | M |
+| MNP/LNP | R-10 | The entire E.164 number and not only part of it should be ported | | M |
+| LNP | R-11 | Single numbers within a MSN can only be ported if a different access is provided to the ported number | 8.09 | O |
+| MNP/LNP | R-12 | Groups of contiguous numbers (e.g., DDI/multiline groups) can be ported | 8.10 | M |
+| MNP/LNP | R-13 | Porting of single numbers within a DDI range is not allowed | | M |
+| MNP/LNP | R-14 | The privacy of the user which has ported his/her number should be guaranteed. That means that the calling/called party should not be informed that the called/calling party has ported his number | 8.11 | M |
+| MNP/LNP | R-15 | Number portability should not affect the dialing procedures for calls incoming to the ported number | 8.12 | M |
+| MNP/LNP | R-16 | The dialing procedures for calls outgoing from the ported customer should be the same as those of non-ported customers served by the same service provider | 8.13 | M |
+| MNP/LNP | R-17 | Introducing service provider portability must not adversely affect conformance with national or international propagation and echo standards | 8.14 | O |
+| MNP/LNP | R-18 | Calling line identification presentation (CLIP) supplementary service and calling line identification restriction (CLIR) supplementary service shall work in the same way as for subscribers not porting the number. For the CLIP supplementary service, if the call is originated by a calling user which has been ported, the calling line identification is the ported number. This is valid for both PSTN and ISDN subscribers | 8.15 | O |
+| MNP/LNP | R-19 | Connected Line Identification Presentation (COLP) supplementary service and Connected Line Identification Restriction (COLR) supplementary service shall work in the same way as for subscribers not porting the number. For the COLP supplementary service, if the called user's number has been ported, the | 8.16 | O |
+
+**Table 1 – List of requirements and relevant testing specifications for implementing number portability**
+
+| Category | Ref. ITU-T Q-Sup.4 (clause 8, pp. 12-13) | Description of requirement (except from [b-ITU-T Q-Suppl.4]) | #Test case | M/O |
+|----------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----|
+| | | connected line identity presented to the calling user is the ported number. This is valid for both PSTN and ISDN subscribers | | |
+| MNP/LNP | R-20 | Calls from a ported number to the emergency services should be supported by the same functionality as calls from non-ported numbers to the emergency services | 8.17 | M |
+| LNP | R-21 | Variable number length must be supported | 8.18 | O |
+| LNP | R-22 | Overlap signalling must be supported before and after obtaining the routing number | 8.19 | O |
+| MNP/LNP | R-23 | The redirection counter, used for the diversion services, must not be stopped at redirection by a number portability procedure | 8.20 | O |
+| MNP/LNP | R-24 | There shall be transparent support for NP at transit nodes | | M |
+| MNP/LNP | R-25 | It shall be possible to transfer both an unchanged called party number (CdPN) and a routing number (RN) unambiguously | 8.21 | M |
+| MNP/LNP | R-26 | It shall be possible to indicate one or all of the following destinations with the routing number (RN):
i) Recipient network ID (RNID) and/or;
ii) point of interconnection (POI) and/or;
iii) recipient exchange (REX).
(NOTE – This list is not exhaustive.) | 8.22 | O |
+| MNP/LNP | R-27 | An indication in the forward direction to indicate a call to a ported number | 8.23 | M |
+| LNP | R-28 | In an environment of number portability, calls from ported numbers must convey both logical and physical calling party information | 8.24 | O |
+| MNP/LNP | R-29 | RN need not be in E.164 format | 8.25 | O |
+| MNP/LNP | R-30 | For incoming international calls, the incoming gateway in the network should be considered as the originating network for number portability | 8.26 | O |
+| MNP/LNP | R-31 | The number used to route the call is constructed as one of the following:
i) Concatenated address = routing number + DN (as a single piece of information);
ii) separated address = routing number and DN (as two separate pieces of information);
iii) DN only. | 8.27 | M |
+
+**Table 1 – List of requirements and relevant testing specifications for implementing number portability**
+
+| Category | Ref. ITU-T Q-Suppl.4 (clause 8, pp. 12-13) | Description of requirement (except from [b-ITU-T Q-Suppl.4]) | #Test case | M/O |
+|-----------------|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------|
+| LNP | R-32 | SCCP addressing based on RN for the called party should be supported | 8.28 | O |
+| MNP/LNP | R-33 | The sum total of the networks involved in addressing and routing non-circuit-related messages pertaining to a ported number shall be able to detect that the number has been ported and drive the identity of the appropriate destination of the message. The division of responsibilities of this among the networks depends on the architecture chosen | 8.29 | O |
+| MNP/LNP | R-34 | Number portability solutions should be backward compatible with nodes and services not updated for NP | 8.30 | M |
+
+NOTE 1 – M: mandatory tests, O: optional tests, R: requirements which are defined by [b-ITU-T Q-Suppl.4].
+
+NOTE 2 – For simplifying and unification of testing procedures below, it is proposed to use the term "NPDB" which specifies number portability database in general.
+
+## 8 Test cases for the exchange of signalling information
+
+This clause presents the test cases which describe a signal information exchange between an operator-recipient network/exchange, an operator-donor network/exchange and a NPDB for two methods of number portability – "all call query" and "onward routing".
+
+The signalling information in this case includes the information of the subscriber's number, information of number porting, the routing information and indication of the subscriber party number, received from a NPDB.
+
+During the provision of all tests, the transport of voice and data must be analysed. The compliance with quality of service (QoS) key performance indicators (KPIs) e.g., [ITU-T Q.3933] must be ensured according to the national requirements or standards.
+
+NOTE – The following test cases basically describe the testing scenario for MNP services. However these cases are also possible to be used for the testing of LNP services.
+
+### -----Test case # 8.01-----
+
+**Title:** Influence of signalling exchange mechanisms on public switched telephone network (PSTN) and integrated services digital network (ISDN) services
+
+"The signalling mechanisms that support number portability, should not place any restrictions on the PSTN and ISDN services, including: basic, supplementary and non-circuit-related based services".
+
+This is an optional test suite which is out of the scope of this Recommendation.
+
+#### -----End of the test-----
+
+### -----Test case # 8.02-----
+
+**Title:** Transit networks and exchanges scenarios
+
+**Keywords:** NPDB, transit node/exchange, call routing.
+
+#### **Purpose:**
+
+Verify the various types of transit networks/exchanges for NP.
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+The testing model of the network contains two network scenarios:
+
+- 1) in the first scenario the transit networks/exchanges are not used between an originating network/exchange and the operator-donor's network/exchange. Also, they are not used between an initiating network/exchange and the operator-recipient's. In this regard, the routing of the voice-call from a calling party to the called party is established directly between customers;
+- 2) in the second scenario the transit networks/exchanges are used between an originating network/exchange and the operator-donor's network/exchange. Also, transit networks/exchanges are used between an initiating network/exchange and the operator-recipient's network/exchange. In this regard, the routing of the voice-call from a calling party to the called party is established through the transit networks/exchanges.
+
+#### **Test set-up:**
+
+The network configurations for these scenarios are presented in Figures 8-1 and 8-2 (the path of transmission of a voice-call is highlighted in green for method "all call query" and blue for method "onward routing"). Green and blue colours highlight the traffic ways in case of using the methods "all call query" and "onward routing". The route of SMS transmission is also available for the above methods.
+
+
+
+Figure 8-1: Network configuration for the first scenario of the test case 8.02. This diagram shows three main network domains: 'Initiating network/exchange', 'Donor network/exchange', and 'Recipient network/exchange'. The 'Initiating network/exchange' contains a 'Calling subscriber' connected to a 'BS', which is connected to an 'MSC'. The 'MSC' is connected to an 'SMS-GW', which is connected to an 'SMSC', which is connected to an 'SRF'. The 'SRF' is connected to an 'NPCDB' and an 'HLR'. The 'Donor network/exchange' contains an 'MSC' connected to an 'SRF', which is connected to an 'NPLDB', which is connected to an 'HLR', which is connected to an 'SMSC', which is connected to an 'SMS-GW'. The 'SMS-GW' is connected to a 'Service platform' and 'Content providers'. The 'Recipient network/exchange' contains an 'MSC' connected to a 'BS' (labeled 'Called (ported) subscriber'), which is connected to an 'SRF', which is connected to an 'NPLDB', which is connected to an 'HLR', which is connected to an 'SMSC', which is connected to an 'SMS-GW'. The 'SMS-GW' is connected to the 'Service platform' and 'Content providers'. The 'Initiating network/exchange' is connected to the 'Donor network/exchange' via a blue line. The 'Donor network/exchange' is connected to the 'Recipient network/exchange' via a green line. The 'Service platform' and 'Content providers' are connected to the 'Donor network/exchange' via a blue line.
+
+Q.3905(16)\_F8-1
+
+**Figure 8-1 – Network configuration for the first scenario of the test case 8.02**
+
+
+
+Figure 8-2: Network configuration for the second scenario of the test case 8.02. This diagram is similar to Figure 8-1 but includes two 'Transit network' blocks, each containing two 'TS' (Traffic Switch) units. The 'Initiating network/exchange' is connected to the first 'Transit network', which is connected to the 'Donor network/exchange'. The 'Donor network/exchange' is connected to the second 'Transit network', which is connected to the 'Recipient network/exchange'. The 'Service platform' and 'Content providers' are connected to the 'Donor network/exchange' via a blue line.
+
+Q.3905(16)\_F8-2
+
+**Figure 8-2 – Network configuration for the second scenario of the test case 8.02**
+
+#### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+#### **Test procedure:**
+
+- 1) the request for establishing of a voice-call connection between calling and called party has to be sent from the originating network to the operator recipient;
+- 2) the traffic generated between initiating network/exchange and the operator-recipient's network/exchange should be captured by the traffic analyser. The traffic analyser should be allowed to capture the signalling exchange between an initiating network/exchange and a NPDB-side. Among others, the information should include the E.164 number and optionally its status (ported or not-ported E.164 number);
+- 3) establish a voice-call between subscribers of an originating network and the operator-recipient's network;
+- 4) exchange messages (e.g., SMS/MMS) between subscribers of an originating network and the operator-recipient's network;
+- 5) perform measurements of signalling traffic between the originating network/exchange and the operator-donor's network/exchange (repeat steps 1-4);
+- 6) perform testing for the second scenario (repeat steps 1-5).
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the connection between subscribers was established.
+
+The test is considered failed if the procedures mentioned above were not successfully carried out.
+
+-----**End of the test**-----
+
+### -----**Test case # 8.03**-----
+
+**Title:** Number portability solutions shall not interfere with carrier selection
+
+The carrier selection should not influence the establishment of voice-call connection in general.
+
+This is an optional test suite which is out of the scope of this Recommendation.
+
+-----**End of the test**-----
+
+### -----**Test case # 8.04**-----
+
+**Title:** Compatibility between various methods of number portability
+
+**Keywords:** onward routing, all call query, the indicator of the status of number porting.
+
+#### **Purpose:**
+
+Checking the compatibility of various methods of number portability.
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+Network configuration for emulating methods of "onward routing" and "all call query".
+
+#### Test set-up:
+
+
+
+Figure 8-3: Network configuration for the test case 8.04. The diagram illustrates a complex network setup involving multiple network domains: PSDN network, Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and Originating network/exchange. Key components include Calling and Called (ported) subscribers, SSP, SCP/DB, HLR, NPCDB, SRF, MSC, BS, SMSC, SMS-GW, Service platform, and Content providers. A blue line represents the voice call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Donor network, and finally to the Called (ported) subscriber in the Recipient network. A green line represents the signaling path, starting from the Calling subscriber in the Originating network, through the BS, MSC, SMSC, and SMS-GW, to the Service platform, and then to the Called (ported) subscriber in the Recipient network. The Donor network contains an SRF connected to an NPLDB and an HLR, which is also connected to an SMSC and SMS-GW. The Recipient network contains an SRF connected to an NPLDB and an HLR, which is also connected to an SMSC and SMS-GW. The Initiating network contains an HLR, NPCDB, and SRF connected to an MSC, which is connected to two BSs. The PSDN network contains a Calling subscriber connected to an SSP, which is connected to an SCP/DB. The Originating network contains a Calling subscriber connected to a BS, which is connected to an MSC, which is connected to an SMSC and SMS-GW, which is connected to the Service platform.
+
+Q.3905(16)\_F8-3
+
+**Figure 8-3 – Network configuration for the test case 8.04**
+
+##### Testing equipment:
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+#### Test procedure:
+
+- 1) establish a connection between calling and called party for the methods "onward routing" and "all call query";
+
+NOTE – The voice call to the called party (the ported subscriber) for the method "onward routing" should be sent from a fixed-line telephony network and/or a network of a foreign state. The voice call to the called party (the ported subscriber) for the method "all call query" should be sent from the calling party which is served in the same region as the called party (ported number);
+
+- 2) all responses received from NPLDB of the operator-donor for the method "onward routing" should be monitored by the traffic analyser. These responses should contain the routing information about the operator-recipient's network and optional the indicator of the porting number status;
+- 3) all responses received from NPCDB for the method "all call query" should be monitored by the traffic analyser. These responses should contain the routing information about the operator-recipient's network and optionally, the indicator of the porting number status;
+- 4) after collecting all data received from steps 2-3, the data should be analysed (syntaxes of NPDB for the methods "onward routing" and "all call query");
+
+- 5) check the information contained in the responses during the establishment of the connection between the calling and called party user for two types of NPDB (NPLDB and NPCDB).
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the interaction between NPLDB and NPCDB for the methods "onward routing" and "all call query" was possible.
+
+The test is considered failed if the response's syntax received from NPDB was not accepted by another NPDB.
+
+-----End of the test-----
+
+### -----Test case # 8.05-----
+
+**Title:** Influence of the call looping to the number portability solution.
+
+**Keywords:** Call looping, ported number, NPDB.
+
+#### **Purpose:**
+
+- 1) verify that in absence of looping the voice call establishment or the transfer of messages based on NP is successful;
+- 2) verify that with looping the voice call establishment or the transfer of messages based on NP is successful.
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+Ported and non-ported number subscriber should be available.
+
+#### **Test set-up:**
+
+
+
+The diagram illustrates the network configuration for test case 8.05, showing three main network domains connected in series:
+
+- Originating network/exchange:** Contains a **Calling subscriber** connected to a **BS**, which is connected to an **MSC**.
+- Initiating network/exchange:** Contains the **MSC** from the originating network, which is connected to two **BS** units. Above the **MSC** is a database block containing **HLR**, **NPCDB**, and **SRF**.
+- Recipient network/exchange:** Contains an **MSC** connected to a **BS**, which is connected to a **Called (ported) subscriber**. Below the **MSC** is a database block containing **SRF**, **NPLDB**, and **HLR**.
+- Donor network/exchange:** Positioned between the Initiating and Recipient networks, it contains an **MSC** connected to a database block containing **SRF**, **NPLDB**, and **HLR**.
+
+The call path is indicated by a thick green line, showing a loop between the Initiating network/exchange and the Recipient network/exchange via the Donor network/exchange.
+
+Network configuration diagram for test case 8.05 showing three network domains: Originating network/exchange, Initiating network/exchange, and Recipient network/exchange. The diagram illustrates the flow of a call from a calling subscriber through various network elements including Base Stations (BS), Mobile Switching Centers (MSC), and databases (NPLDB, NPCDB, HLR, SRF). A thick green line represents the call path, showing a loop between the Initiating and Recipient networks.
+
+**Figure 8-4 – Network configuration for test case 8.05**
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+#### **Test procedure:**
+
+- 1) in the first step, the request for establishing of a connection between calling and called party (a test call/message) has to be sent (in this case called party number is the ported number);
+- 2) the traffic of the request should be analysed by the traffic analyser (between NPDB and calling user). It is considered that all calls are made with the same method "all call query";
+- 3) analyse the response from step 2 (response of NPDB) which contains the indicator of the status and the routing number of the operator-recipient;
+- 4) based on the response establish a connection to the served user and analyse the signalling information;
+- 5) checking the establishment with looping Steps 1-4 should be repeated with looping on the calling party side. The looping is based on a wrong data base routing information. The call shall be routed to a non-existing called party user;
+- 6) repeat steps 1-5 for the case when the ported user is a fixed line user.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if in the case of call looping the call was released.
+
+The test is considered failed if the tests described above were not successful.
+
+-----**End of the test**-----
+
+-----**Test case # 8.06**-----
+
+**Title:** Outgoing international calls
+
+**Keywords:** Verifying the influence of number portability on outgoing international calls.
+
+#### **Purpose:**
+
+Verifying the influence of number portability on outgoing international calls.
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+In this test case the ported number belongs to another country.
+
+#### Test set-up:
+
+
+
+The diagram illustrates the network configuration for test case 8.06. It consists of five main network domains represented by dashed boxes:
+
+- International network:** Contains a **Calling subscriber**, **SMSC**, and **SSP**.
+- Long-distance network:** Contains an **SSP** and **SCP/DB**.
+- Initiating network/exchange:** Contains an **HLR**, **NPCDB**, **SRF**, **MSC**, and two **BS**.
+- Donor network/exchange:** Contains an **MSC**, **SRF**, **NPLDB**, and **HLR**.
+- Recipient network/exchange:** Contains an **MSC**, **SRF**, **NPLDB**, and **HLR**.
+- Originating network/exchange:** Contains a **BS** and a **Calling (ported subscriber)**.
+
+Connections are shown between these components across the network boundaries. A blue line represents the path from the **Calling subscriber** in the **International network** through the **SMSC**, **SSP**, and **SCP/DB** to the **MSC** in the **Initiating network/exchange**. A green line represents the path from the **Calling (ported subscriber)** in the **Originating network/exchange** through the **BS**, **MSC**, **SRF**, **NPLDB**, and **HLR** to the **MSC** in the **Recipient network/exchange**.
+
+Figure 8-5 – Network configuration for test case 8.06. The diagram shows a complex network topology with five main network domains: International network, Long-distance network, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The International network contains a Calling subscriber, SMSC, and SSP. The Long-distance network contains an SSP and SCP/DB. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BS. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, SRF, NPLDB, and HLR. The Originating network/exchange contains a BS and a Calling (ported subscriber). Connections are shown between these components across the network boundaries.
+
+Figure 8-5 – Network configuration for test case 8.06
+
+##### Testing equipment:
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+#### Test procedure:
+
+- 1) establish a connection with number portability based on an outgoing international call using the method "all call query";
+- 2) monitor the signalling traffic between the calling originating local exchange (OLE) and the destination local exchange (DLE) which is located in the other country;
+- 3) repeat steps 1 and 2 for case of using the method "onward routing";
+- 4) repeat steps 1-3 for the case when the ported user is a fixed line user.
+
+#### Pass/fail criteria:
+
+The test can be considered successful if the establishment of a connection between called and calling party (the user of the other country and user with ported number) was established successfully.
+
+The test is considered failed if the outgoing international call was not successful.
+
+-----End of the test-----
+
+-----Test case # 8.07-----
+
+**Title:** Indication of number portability
+
+**Keywords:** Checking the possibility of an indication of the NP status of subscriber number.
+
+**Purpose:**
+
+Verify the NP status indication of the subscriber number.
+
+**Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+**Preconditions and dependencies:**
+
+The NPDB receives requests about the NP status of called number (from an originating or initiating network). Available NPDB methods: "onward routing" or "all call query".
+
+**Test set-up:**
+
+
+
+The diagram illustrates the network configuration for test case 8.07, showing three main network domains connected by dashed lines:
+
+- Initiating network/exchange:** Contains an **Originating network/exchange** with a **Calling subscriber** connected to a **BS**, which is connected to an **MSC**. The **MSC** is connected to an **SRF**, which is connected to an **NPCDB** and an **HLR**. There are also two **BS** units connected to the **MSC**.
+- Donor network/exchange:** Contains an **MSC** connected to an **SRF**, which is connected to an **NPLDB** and an **HLR**.
+- Recipient network/exchange:** Contains an **MSC** connected to an **SRF**, which is connected to an **NPLDB** and an **HLR**. The **MSC** is connected to a **BS**, which is connected to a **Called (ported) subscriber**.
+
+Connections between domains: A blue line connects the **MSC** in the Initiating network to the **MSC** in the Donor network. A green line connects the **MSC** in the Donor network to the **MSC** in the Recipient network. A green line also connects the **BS** in the Initiating network to the **BS** in the Recipient network. A label **Q.3905(16)\_F8-6** is present in the bottom right corner.
+
+Figure 8-6 – Network configuration for test case 8.07. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC is connected to a BS, which is connected to a Called (ported) subscriber. The diagram also shows the flow of signaling messages between the networks.
+
+**Figure 8-6 – Network configuration for test case 8.07**
+
+**Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+**Test procedure:**
+
+- 1) OLE sends a request to the NPLDB for establishing a connection for the method "onward routing";
+- 2) this request should be monitored by the traffic analyser on the side of the operator-donor network;
+- 3) monitor the NPLDB response by the traffic analyser and verify the correctness of the received information. The call number should have the status "the ported subscriber number" and the response should contain the routing information about the operator-recipient's network/exchange;
+- 4) repeat steps 1-3 for method "all call query";
+
+- 5) the information received from the NPDB for both methods should be the same – the NP status should indicate that the subscriber number is a ported number.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the responses received from the two NPDB contained the routing information about the operator-recipient's network/exchange and information that the number was ported.
+
+The test is considered failed if the NP status contained incorrect information.
+
+-----End of the test-----
+
+### -----Test case # 8.08-----
+
+**Title:** Verifying the possibility of porting when the called party has different ITU-T E.164 number formats
+
+**Keywords:** Number which has been written in format E.164; number which has been written in other format; telephone prefix.
+
+#### **Purpose:**
+
+Verify the possibility of porting when the called party has different E.164 number formats (e.g., length of the number or parts of it).
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+The OLE sends a request to the NPDB.
+
+#### **Test set-up:**
+
+OLE, NPDB, DLE.
+
+##### **Testing equipment:**
+
+- 1) The NPDB-based solution.
+
+#### **Test procedure:**
+
+- 1) Send two requests with two different profiles to NPDB;
+ - a) the first request should contain the telephone number using E.164 format;
+ - b) the second request should contain the telephone number using other format (non-E.164 format);
+
+NOTE – The requests specified above should contain the subscriber number without prefixes and other auxiliary or information signs.
+
+- 2) NPDB should analyse the first request and send to recipient's side the notification message. In the second request the NPDB should send a notification message which does not correspond to E.164 format;
+- 3) analyse the NPDB notification messages;
+- 4) repeat steps 1-3 for the case when a part of the E.164 number is in the request;
+- 5) analyse the NPDB response in both case.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the NPDB sends a notification identifying a failure.
+
+The test is considered failed if one of the criteria mentioned above does not come true.
+
+-----**End of the test**-----
+
+-----**Test case # 8.09**-----
+
+**Title:** Porting of MSN
+
+**Keywords:** Porting of MSN
+
+**Purpose:**
+
+Verifying the possibility of porting when the called party has an MSN.
+
+**Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+**Preconditions and dependencies:**
+
+The OLE sends a request to the NPDB.
+
+**Test set-up:**
+
+OLE, NPDB, DLE.
+
+**Testing equipment:**
+
+- 1) The NPDB-based solution.
+
+**Test procedure:**
+
+- 1) a request is sent to the NPDB which should contain the information of a ported MSN user;
+- 2) NPDB should analyse the request and send the correct response to the OLE.
+
+**Pass/fail criteria:**
+
+The test can be considered successful if the NPDB sent a response with the correct MSN Number.
+
+The test is considered failed if the criteria mentioned above does not come true.
+
+-----**End of the test**-----
+
+-----**Test case # 8.10**-----
+
+**Title:** Verifying the possibility to port a group of numbers
+
+**Keywords:** The request for number porting, the request for group number porting, NPDB.
+
+**Purpose:**
+
+Verify the possibility to port a group of numbers. The possibility to port one number from the group of numbers is not allowed.
+
+**Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+**Preconditions and dependencies:**
+
+The possibility to port a group of numbers, including some partial subscriber numbers.
+
+#### Test set-up:
+
+
+
+Figure 8-7 – Network configuration for test case 8.10. The diagram shows four network domains: Originating network/exchange, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Originating network contains a BS connected to a Calling subscriber. The Initiating network contains an MSC connected to two BSs, one of which is connected to the Calling subscriber. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR, and a BS connected to a Called (ported) subscriber. Connections are shown between the Calling subscriber and the Initiating network, between the Initiating network and the Donor network, and between the Donor network and the Recipient network. A legend indicates that blue lines represent the traffic analyser and green lines represent the NPDB-based solution. The diagram is labeled Q.3905(16)\_F8-7.
+
+**Figure 8-7 – Network configuration for test case 8.10.**
+
+##### Testing equipment:
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### Test procedure:
+
+- 1) The first request to NPDB contains the necessary default information for porting;
+- 2) The second request should contain the information of group of numbers which are already ported;
+- 3) verify the group requests and the possibility of porting;
+- 4) ensure that the first response is correct and the group of number could be ported;
+- 5) ensure that the second response consist of the failure and the group of numbers could not be ported;
+- 6) establish a connection between the pre-configured subscriber number and one of the numbers which are from the ported group of numbers;
+- 7) verify the possibility of porting the single number from the group of numbers. This result should be the same as that of step 5.
+
+#### Pass/fail criteria:
+
+The test can be considered successful if the request for group number porting was correctly answered from the NPDB and it was not possible to port one number from the group of numbers.
+
+The test is considered failed if one of the criteria mentioned above does not come true.
+
+-----End of the test-----
+
+-----Test case # 8.11-----
+
+**Title:** Verifying the privacy of subscribers with ported numbers
+
+**Keywords:** The ported subscriber number, non-ported subscriber number, NPDB.
+
+#### **Purpose:**
+
+Verifying the possibility to save the privacy of users after porting their subscriber number.
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+OLE, NPDB, DLE.
+
+##### **Test set-up:**
+
+
+
+The diagram illustrates the network configuration for test case 8.11, showing three main network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber connected to a BS, which is connected to an MSC. This MSC is connected to the Donor network. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. This MSC is connected to a BS, which is connected to a Called (ported) subscriber. The diagram also shows the flow of signaling between the networks, with a blue line representing the signaling path and a green line representing the data path. The diagram is labeled Q.3905(16)\_F8-8.
+
+Figure 8-8 – Network Configuration for test case 8.11. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber connected to a BS, which is connected to an MSC. This MSC is connected to the Donor network. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. This MSC is connected to a BS, which is connected to a Called (ported) subscriber. The diagram also shows the flow of signaling between the networks, with a blue line representing the signaling path and a green line representing the data path. The diagram is labeled Q.3905(16)\_F8-8.
+
+**Figure 8-8 – Network Configuration for test case 8.11**
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### **Test procedure:**
+
+- 1) establish the connection between non-ported and ported number using the routing information contained in the NPDB;
+- 2) trace the exchange of signalling between non-ported and ported number;
+- 3) ensure that the user is informed with a tone and/or announcement if the number was successfully ported.
+
+##### **Pass/fail criteria:**
+
+The test can be considered successful if the user received a tone and/or announcement in case the number was successfully ported.
+
+The test is considered failed if the user did not receive an announcement.
+
+-----End of the test-----
+
+-----Test case # 8.12-----
+
+**Title:** Influence of number portability on incoming calls
+
+**Keywords:** Subscriber number, ported subscriber number, NPDB.
+
+**Purpose:**
+
+Checking the correctness of reception of an incoming call on ported number.
+
+**Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+**Preconditions and dependencies:**
+
+The (voice-call) connection has to be established between non-ported number and ported number.
+
+**Test set-up:**
+
+
+
+The diagram shows a network configuration for test case 8.12. It is divided into four main sections: PSDN network, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The PSDN network contains a Calling subscriber, SSP, and SCP/DB. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BS. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, BS, Called (ported) subscriber, SRF, NPLDB, and HLR. A blue line represents the call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. A green line represents the call path from the Calling subscriber in the Initiating network/exchange, through the BS, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. The diagram is labeled Q.3905(16)\_F8-9.
+
+Figure 8-9 – Network Configuration for test case 8.12. The diagram illustrates a network configuration for testing number portability. It consists of three main network domains: PSDN network, Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The PSDN network contains a Calling subscriber, SSP, and SCP/DB. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BS. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, BS, Called (ported) subscriber, SRF, NPLDB, and HLR. A blue line represents the call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. A green line represents the call path from the Calling subscriber in the Initiating network/exchange, through the BS, to the MSC in the Initiating network/exchange, then through the MSC in the Donor network/exchange, and finally to the Called (ported) subscriber in the Recipient network/exchange. The diagram is labeled Q.3905(16)\_F8-9.
+
+**Figure 8-9 – Network Configuration for test case 8.12**
+
+**Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+**Test procedure:**
+
+- 1) establish a connection between a non-ported and ported number. The request for establishing a connection between subscribers should be sent to NPDB for obtaining the routing information;
+
+- 2) verify that the NPDB sends the correct called party number in response to the OLE. The response should contain the routing information about the served called party (a ported subscriber number);
+- 3) establish a connection between calling and called party;
+- 4) ensure that the voice/data channel is correctly established;
+- 5) repeat steps 1-4 for case when the calling party is a fixed telephone subscriber.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the voice call connection to the ported number was successfully established.
+
+The test is considered failed if one of the criteria mentioned above does not come true.
+
+-----End of the test-----
+
+-----Test case # 8.13-----
+
+**Title:** Number portability on outgoing calls
+
+**Keywords:** Subscriber number, ported subscriber number, NPDB.
+
+#### **Purpose:**
+
+Ensure that the calls from a ported number can be provided to fixed and mobile telephone numbers.
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+The calling user is a ported number.
+
+##### **Test set-up:**
+
+
+
+The diagram illustrates the network configuration for test case 8.13. It consists of three main network domains enclosed in dashed boxes:
+
+- Recipient network/exchange:** Contains an MSC (Mobile Switching Center), BS (Base Station), SRF (Service Resource Function), NPDB (Number Portability Database), and HLR (Home Location Register). It includes a 'Calling subscriber' and a 'Calling (ported) subscriber' connected to the BS.
+- Cellular network:** Contains an HLR, NPDB, SRF, MSC, BS, and a 'Called subscriber' connected to the BS.
+- PSDN network:** Contains an SSP (Service Switching Point), SCP/DB (Service Control Point/Database), and a 'Called subscriber' connected to the SSP.
+
+Connections are shown between the calling subscribers in the Recipient network and the called subscribers in both the Cellular and PSDN networks. The call from the 'Calling (ported) subscriber' in the Recipient network is routed through its MSC, then to the SSP in the PSDN network, and finally to the 'Called subscriber' in the PSDN network. Another call from the 'Calling (ported) subscriber' is routed through its MSC to the MSC in the Cellular network, and finally to the 'Called subscriber' in the Cellular network.
+
+Q.3905(16)\_F8-10
+
+Network configuration diagram for test case 8.13 showing three network domains: Recipient network/exchange, Cellular network, and PSDN network. The Recipient network contains an MSC, BS, SRF, NPDB, and HLR, with a 'Calling subscriber' and 'Calling (ported) subscriber'. The Cellular network contains an HLR, NPDB, SRF, MSC, BS, and a 'Called subscriber'. The PSDN network contains an SSP, SCP/DB, and a 'Called subscriber'. Connections are shown between the calling subscribers in the Recipient network and the called subscribers in both the Cellular and PSDN networks, passing through the MSC and SSP respectively.
+
+**Figure 8-10 – Network configuration for test case 8.13**
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### **Test procedure:**
+
+- 1) establish a call from a ported user to a non-ported mobile user;
+- 2) establish a connection between calling and called party;
+- 3) ensure that the voice/data channel is correctly established;
+- 4) repeat steps 1-3 for case when the calling party is a fixed telephone subscriber.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the call from a ported call to a non-ported number was successfully established.
+
+The test is considered failed if one of the criteria mentioned above does not come true.
+
+-----End of the test-----
+
+-----Test case # 8.14-----
+
+**Title:** Influence of service provider portability on national or international radio resource allocation
+
+"Introducing service provider portability must not adversely affect conformance with national or international propagation and echo standards".
+
+The NPDB solution (in general) is a separate information system which does not have access to mechanisms of the radio resource's allocation and echo protection. It has no negative influence on allocation of national and international radio resources.
+
+This is an optional test suite which is out of the scope of this Recommendation.
+
+-----End of the test-----
+
+-----Test case # 8.15-----
+
+**Title:** Verifying the determination of ported number using the CLIP/CLIR service
+
+**Keywords:** NPDB, CLIP/CLIR.
+
+#### **Purpose:**
+
+Verify that the presentation and restriction of the calling party number is according to the CLIP/CLIR Recommendation for ported and not ported numbers
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+The non-ported and the ported user have been subscribed to the Supplementary services CLIP/CLIR.
+
+##### Test set-up:
+
+
+
+The diagram shows a network configuration for test case 8.15, involving three main network/exchange areas: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, BS, and a Calling subscriber. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, BS, SRF, NPLDB, HLR, and a Called (ported) subscriber. A PSDN network at the top contains a Calling subscriber, SSP, and SCP/DB. A blue line represents the call path from the Calling subscriber in the PSDN network, through the SSP, to the MSC in the Initiating network/exchange, then to the MSC in the Donor network/exchange, and finally to the MSC in the Recipient network/exchange. A green line represents the call path from the Calling subscriber in the Initiating network/exchange, through the BS, to the MSC in the Initiating network/exchange, then to the MSC in the Donor network/exchange, and finally to the MSC in the Recipient network/exchange. The diagram is labeled Q.3905(16)\_F8-11.
+
+Figure 8-11 – Network configuration for test case 8.15
+
+**Figure 8-11 – Network configuration for test case 8.15**
+
+##### Testing equipment:
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### Test procedure:
+
+- 1) establish a call from a ported to a non-ported user who subscribed to the supplementary service CLIP;
+- 2) after establishing a connection, verify that the CLIP information was correctly transferred to the called user;
+- 3) repeat steps 1-2 for the non-ported case;
+- 4) repeat steps 1-3 establishing a call from a non-ported to a ported user who subscribed to CLIP;
+- 5) repeat steps 1-4 for CLIR service. In this case the information concerning the calling party should not be displayed on the screen of the terminal device of the called party.
+
+##### Pass/fail criteria:
+
+The test can be considered successful if the verification of the supplementary service CLIP/CLIR was successful.
+
+The test is considered failed if the presentation and restriction of the calling party number was not provided in accordance with the CLIP/CLIR recommendation for ported and non-ported numbers.
+
+End of the test
+
+### -----Test case # 8.16-----
+
+**Title:** Influence of number portability on COLP/COLR service
+
+**Keywords:** NPDB, COLP/COLR
+
+#### **Purpose:**
+
+Verify that the connected number can be used according to the COLP/COLR recommendation for ported and not ported numbers.
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+The non-ported and the ported user have been subscribed to the Supplementary services COLP/COLR.
+
+#### **Test set-up:**
+
+
+
+Figure 8-12 – Network configuration for test case 8.16. The diagram shows a network architecture with four main components: Initiating network/exchange, Donor network/exchange, Transit network, and Recipient network/exchange. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Transit network contains two TS (Transit Switches). The Recipient network/exchange contains an MSC, SRF, NPLDB, HLR, and two BSs. A Calling subscriber is connected to the Initiating network/exchange. A Called (ported) subscriber and a Called subscriber are connected to the Recipient network/exchange. The diagram illustrates the flow of signaling and data between these components, with a specific call path highlighted in blue and green lines. The text 'Q.3905(16)\_F8-12' is visible in the bottom right corner of the diagram area.
+
+**Figure 8-12 – Network configuration for test case 8.16**
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### **Test procedure:**
+
+- 1) establish a connection between non-ported number (which has been subscribed to COLP supplementary service) and the ported number which has been subscribed to the service of the calling user "A";
+- 2) ensure that the information of the subscriber number "B" is displayed correctly on the terminal device of calling party "A";
+- 3) repeat steps 1-2 for the case when the called party is a non-ported number;
+
+- 4) repeat steps 1-3 for the case when the called party number has been subscribed to COLR service.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if COLP and COLR services worked correctly.
+
+The test is considered failed if the COLP/COLR information was not transferred correctly.
+
+-----End of the test-----
+
+-----Test case # 8.17-----
+
+**Title:** Influence of number portability on calls from ported numbers to emergency services
+
+**Keywords:** Emergency services, ported subscriber number, NPDB.
+
+#### **Purpose:**
+
+Verify that an outgoing call from a ported number can be provided successfully to an emergency service.
+
+#### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+The emergency call will be provided from a ported subscriber number.
+
+##### **Test set-up:**
+
+
+
+Q.3905(16)\_F8-13
+
+Network configuration diagram for test case 8.17. It shows a 'Recipient network/exchange' on the left containing an MSC, BS, SRF, NPLDB, and HLR. Two subscribers, 'Calling subscriber' and 'Calling (ported) subscriber', are connected to the BS. A 'PSDN network' on the right contains an SSP, SCP/DB, and 'Number of emergency services'. The MSC is connected to the SSP. A call path is shown from the ported subscriber through the BS, MSC, SRF, NPLDB, HLR, and then to the SSP and emergency services. A reference code Q.3905(16)\_F8-13 is present at the bottom right of the diagram.
+
+**Figure 8-13 – Network configuration for test case 8.17**
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### **Test procedure:**
+
+- 1) establish a connection between a ported number and number of the emergency service (for example, number 112);
+- 2) monitor the signalling with the traffic analyser during the call establishment;
+- 3) repeat steps 1-2 for the case when the calling party number is a non-ported number;
+
+- 4) ensure that the call routing from the ported number to the number of the emergency service is the same as the call from the non-ported number.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the call routing from the ported number to the number of the emergency service was established successfully.
+
+The test is considered failed if the connection establishment between ported number and the number of the emergency service failed or the ported number had limited access to the emergency service (e.g long delay, etc.).
+
+-----**End of the test**-----
+
+-----**Test case # 8.18**-----
+
+**Title:** Support of variable length of number
+
+"Variable number length must be supported".
+
+This is an optional test which is out of the scope of this Recommendation.
+
+-----**End of the test**-----
+
+-----**Test case # 8.19**-----
+
+**Title:** Support of overlap signalling before and after obtaining the routing number
+
+"Overlap signaling must be supported before and after obtaining the routing number".
+
+This is an optional test which is out of the scope of this Recommendation.
+
+-----**End of the test**-----
+
+-----**Test case # 8.20**-----
+
+**Title:** Influence on the redirection counter (during call forwarding) during the NP procedure
+
+**Keywords:** Readdressing, NPDB, ported subscriber, transit network/exchange.
+
+#### **Purpose:**
+
+Verify if the redirection counter will increase during the number portability procedure.
+
+##### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+##### **Preconditions and dependencies:**
+
+The ported number has subscribed and activated call forwarding unconditional (CFU).
+
+##### Test set-up:
+
+
+
+Figure 8-14 – Network configuration for test case 8.20. The diagram shows a network architecture with four main network/exchange blocks: Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and Originating network/exchange. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains a TS, MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains a TS, MSC, SRF, NPLDB, and HLR. The Originating network/exchange contains a BS and a Calling subscriber. The Recipient network/exchange also contains a Called (ported) subscriber, Number B, and a Called subscriber. The diagram illustrates the flow of traffic and signaling between these components, with a specific call path highlighted in blue and green. A small note 'Q.3905(16)\_F8-14' is visible in the bottom right corner of the diagram area.
+
+**Figure 8-14 – Network configuration for test case 8.20**
+
+##### Testing equipment:
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### Test procedure:
+
+- 1) the calling user "A" is calling user B which is not ported and has activated CFU. The redirection counter has the value 1;
+- 2) activate NP for user B;
+- 3) the calling user "A" is calling user B which is ported and has activated CFU. The redirection counter has the value 1.
+
+##### Pass/fail criteria:
+
+The test can be considered successful if the redirection counter was not influenced by number portability procedure.
+
+The test is considered failed if the criteria mentioned above does not come true.
+
+-----**End of the test**-----
+
+-----**Test case # 8.21**-----
+
+**Title:** The unambiguous transmission of called number and routing network number
+
+**Keywords:** Unchanged called party number (CdPN), routing number, a NPDB.
+
+#### Purpose:
+
+Ensure that the transmission of the CdPN and the routing number has not been changed during the NP procedure.
+
+##### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+##### **Preconditions and dependencies:**
+
+The called party number is a ported subscriber number.
+
+##### **Test set-up:**
+
+The testing configuration corresponds on Figure 8-4.
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### **Test procedure:**
+
+- 1) establish a connection between non-ported and ported subscriber number;
+- 2) check the CdPN on the NPDB side;
+- 3) verify the response of the NPDB which contains the routing information;
+- 4) ensure that the CdPN has not been changed;
+- 5) repeat steps 1-4 for the case if a transit network/exchange has been used between the operator-donor and the operator-recipient network/exchange.
+
+##### **Pass/fail criteria:**
+
+The test can be considered successful if the routing number of the operator-recipient network/exchange and the CdPN were transferred correctly.
+
+The test is considered failed if one of the criteria mentioned above does not come true.
+
+-----**End of the test**-----
+
+-----**Test case # 8.22**-----
+
+**Title:** Support of various types of indications
+
+**Keywords:** routing number, point of interconnection, recipient exchange.
+
+#### **Purpose:**
+
+Verify that that the transport of the following types of indication are supported:
+
+- 1) recipient network ID (RNID) and/or;
+- 2) point of interconnection (POI) and/or;
+- 3) recipient exchange (REX).
+
+##### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+##### **Preconditions and dependencies:**
+
+The exchange and point of association to a network should be selected.
+
+##### Test set-up:
+
+
+
+The diagram illustrates the network configuration for test case 8.22, showing three main network domains connected in series:
+
+- Initiating network/exchange:** Contains an **Originating network/exchange** with a **BS** and **Calling subscriber**. This is connected to an **MSC**. The **MSC** is connected to an **SRF**, which is connected to an **HLR** and an **NPCDB**.
+- Donor network/exchange:** Contains an **MSC** connected to an **SRF**, which is connected to an **NPLDB** and an **HLR**.
+- Recipient network/exchange:** Contains an **MSC** connected to an **SRF**, which is connected to an **NPLDB** and an **HLR**. The **MSC** is connected to a **BS** and a **Called (ported) subscriber**.
+
+The connections between the domains are as follows: The **MSC** in the **Initiating network/exchange** is connected to the **MSC** in the **Donor network/exchange**, which is connected to the **MSC** in the **Recipient network/exchange**. The diagram is labeled **Q.3905(16)\_F8-15**.
+
+Figure 8-15 – Network configuration for test case 8.22. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a BS and Calling subscriber, connected to an MSC. The MSC is connected to an SRF, which is connected to an HLR and an NPCDB. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC in the Recipient network is connected to a BS and a Called (ported) subscriber. The MSC in the Initiating network is connected to the MSC in the Donor network, which is connected to the MSC in the Recipient network. The diagram is labeled Q.3905(16)\_F8-15.
+
+**Figure 8-15 – Network configuration for test case 8.22**
+
+##### Testing equipment:
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### Test procedure:
+
+- 1) establish a call between the calling user "A" and the ported user "B";
+- 2) monitor the signalling between OLE and DLE;
+- 3) verify that the request for establishment contains the routing information about the operator-recipient's network/exchange;
+- 4) analyse the response from NPDB. The response should contain the following items:
+ - the information about the ported calling party number;
+ - the routing number and the presence of the identifier of the operator-recipient's network;
+ - the operator-recipient exchange;
+ - the point of interconnection.
+
+##### Pass/fail criteria:
+
+The test can be considered successful if the parameters describe above were transferred correctly.
+
+The test can be considered unsuccessful if the parameters describe above were not transferred correctly.
+
+-----**End of the test**-----
+
+-----**Test case # 8.23**-----
+
+**Title:** Indication of ported number in the forward direction
+
+**Keywords:** Call indication, NPDB, the ported subscriber number.
+
+#### **Purpose:**
+
+Checking of the ported number indication in the forward direction
+
+##### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+##### **Preconditions and dependencies:**
+
+The test configuration contains the OLE, the operator-recipient's network/exchange and transit network/exchange.
+
+##### **Test set-up:**
+
+
+
+The diagram illustrates the network configuration for test case 8.23. It is divided into four main sections: Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and a central Transit network. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, SRF, NPLDB, HLR, and a BS connected to a 'Called (ported) subscriber'. The Transit network is a shaded area between the Donor and Recipient networks. A 'Calling subscriber' is connected to a BS in the Initiating network/exchange. The diagram is labeled Q.3905(16)\_F8-16.
+
+Figure 8-16 – Network configuration for test case 8.23. The diagram shows a network configuration with four main components: Initiating network/exchange, Donor network/exchange, Recipient network/exchange, and a central Transit network. The Initiating network/exchange contains an HLR, NPCDB, SRF, MSC, and two BSs. The Donor network/exchange contains an MSC, SRF, NPLDB, and HLR. The Recipient network/exchange contains an MSC, SRF, NPLDB, HLR, and a BS connected to a 'Called (ported) subscriber'. The Transit network is a shaded area between the Donor and Recipient networks. A 'Calling subscriber' is connected to a BS in the Initiating network/exchange. The diagram is labeled Q.3905(16)\_F8-16.
+
+**Figure 8-16 – Network configuration for test case 8.23**
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### **Test procedure:**
+
+- 1) receive the routing information from the response of NPDB;
+- 2) establish a connection between calling and called party (the ported number);
+- 3) monitor the traffic during call forwarding from an OLE to the operator-recipient's network/exchange, with usage of a transit network/exchange;
+- 4) analyse traces and verify that the indication of the operator-recipient exchange/network is correct;
+
+##### **Pass/fail criteria:**
+
+The test can be considered successful if the connection between subscribers was established using the received routing information.
+
+The test is considered failed if the connection was not established and/or the indication of the network was incorrect.
+
+-----End of the test-----
+
+-----Test case # 8.24-----
+
+**Title:** Verifying the possibility of the physical and logical information transmission in the case when the calling party is ported
+
+"In an environment of number portability, calls from ported numbers must convey both logical and physical calling party information".
+
+This is an optional test suite which is out the scope of this Recommendation.
+
+-----End of the test-----
+
+-----Test case # 8.25-----
+
+**Title:** Usage of different formats of routing numbers
+
+**Keywords:** Routing number, operator-recipient's network/exchange, operator-donor network/exchange.
+
+**Purpose:**
+
+Usage of different formats of routing numbers.
+
+**Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+**Preconditions and dependencies:**
+
+The called party number is a ported subscriber number.
+
+**Test set-up:**
+
+
+
+The diagram illustrates the network configuration for test case 8.25, showing the flow of a call from an originating network to a recipient network through a donor network. The components and connections are as follows:
+
+- Originating network/exchange:** Contains a **Calling subscriber** connected to a **BS** (Base Station). The **BS** is connected to an **MSC** (Mobile Switching Center). The **MSC** is connected to an **SRF** (Service Routing Function). The **SRF** is connected to an **NPLDB** (Number Portability Lookup Database) and an **HLR** (Home Location Register). The **HLR** is also connected to an **NPCDB** (Number Portability Control Database).
+- Donor network/exchange:** Contains an **MSC** connected to an **SRF**. The **SRF** is connected to an **NPLDB** and an **HLR**.
+- Recipient network/exchange:** Contains an **MSC** connected to an **SRF**. The **SRF** is connected to an **NPLDB** and an **HLR**. The **MSC** is connected to a **BS**, which is connected to a **Called (ported) subscriber**.
+
+The call flow is indicated by a thick green line connecting the **Calling subscriber** to the **Called (ported) subscriber**, passing through the **MSC** in the originating network, the **MSC** in the donor network, and the **MSC** in the recipient network.
+
+Q.3905(16)\_F8-17
+
+Figure 8-17 – Network configuration for test case 8.25. The diagram shows a call flow from an originating network/exchange to a recipient network/exchange via a donor network/exchange. The originating network contains a calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an HLR and an NPCDB. The donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The MSC is connected to a BS, which is connected to a called (ported) subscriber. The call flow is indicated by a thick green line connecting the calling subscriber to the called subscriber.
+
+**Figure 8-17 – Network configuration for test case 8.25**
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### **Test procedure:**
+
+- 1) OLE has sent the request to the NPDB in order to establish a connection between calling (non-ported) party and called (ported) party;
+- 2) NPDB should generate the response containing the routing information about the operator-recipient's network and information about called party number;
+- 3) monitor and analyse the NPDB response.
+
+The response should contain the information about:
+
+- routing number;
+- national number;
+
+these numbers should be written using the E.164 format;
+
+- 4) the routing number should contain the code number of the operator-recipient's network and, optionally, the code of exchange of the given network;
+- 5) ensure that it is possible to use the syntax which is different from E.164 format, namely: the possibility of usage of hexadecimal digits, as in a range 0-F, and in a range 0-9.
+
+##### **Pass/fail criteria:**
+
+The test can be considered successful if an additional format (e.g., Hex) was supported.
+
+The test is considered failed if the usage of the additional syntax was impossible.
+
+**End of the test**
+
+**Test case # 8.26**
+
+**Title:** The incoming gateway in the network for incoming international calls should be considered as the OLE
+
+**Keywords:** Network of the foreign country, the international gateway, OLE, the ported number.
+
+#### **Purpose:**
+
+Verify that the incoming gateway for international call could be used as OLE during the NP procedure.
+
+##### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+##### **Preconditions and dependencies:**
+
+The international gateway fulfil the functions of an OLE.
+
+##### Test set-up:
+
+
+
+The diagram illustrates the network configuration for test case 8.26. It shows a call path from a calling subscriber in an international network, through a long-distance network, to an originating network/exchange, then through a donor network/exchange, and finally to a recipient network/exchange where the called (ported) subscriber is located. The path includes various network elements like SMSC, SSP, SCP/DB, HLR, NPCDB, SRF, MSC, NPLDB, and BS. The call is established via two routes: one direct (blue line) and one via the donor network (green line).
+
+Q.3905(16)\_F8-18
+
+Figure 8-18 – Network configuration for test case 8.26. The diagram shows a call path from a calling subscriber in an international network, through a long-distance network, to an originating network/exchange, then through a donor network/exchange, and finally to a recipient network/exchange where the called (ported) subscriber is located. The path includes various network elements like SMSC, SSP, SCP/DB, HLR, NPCDB, SRF, MSC, NPLDB, and BS. The call is established via two routes: one direct (blue line) and one via the donor network (green line).
+
+**Figure 8-18 – Network configuration for test case 8.26**
+
+##### Testing equipment:
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### Test procedure:
+
+- 1) establish a connection between a user in a foreign state (calling party) and ported subscriber (called party) for the methods "all call query" and "onward routing";
+- 2) monitor this establishment for both number portability methods;
+- 3) repeat steps 1-2 for the case when the ported called party is in the foreign country.
+
+##### Pass/fail criteria:
+
+The test can be considered successful if the connection between the foreign state and the ported subscriber number was successfully established.
+
+The test is considered failed if the connection was not established.
+
+-----End of the test-----
+
+-----Test case # 8.27-----
+
+**Title:** Different call routing formats
+
+**Keywords:** Routing number, operator-recipient's network/exchange, operator-donor's network/exchange.
+
+#### Purpose:
+
+Ensure that the following types of number formats can be used during the call establishment:
+
+- 1) concatenated address (the routing and called party number are forwarded together);
+- 2) separated address (the routing and called party number are forwarded separately);
+
+3) only the called party has been transferred.
+
+##### **Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+##### **Preconditions and dependencies:**
+
+The "all call query" method is used for NP.
+
+##### **Test set-up:**
+
+
+
+Figure 8-19 – Number configuration for test case 8.27. The diagram illustrates a network configuration across four dashed boxes representing different network/exchange domains. 1. Originating network/exchange (bottom left): Contains a 'Calling subscriber' connected to a 'BS' (Base Station), which is connected to an 'MSC' (Mobile Switching Center). 2. Initiating network/exchange (top left): Contains the 'MSC' from the originating network, an 'HLR' (Home Location Register), an 'NPCDB' (Number Portability Database), and an 'SRF' (Service Request Function). The 'SRF' is connected to the 'NPCDB' and the 'HLR'. 3. Donor network/exchange (middle): Contains an 'MSC', an 'SRF', an 'NPLDB' (Number Portability Lookup Database), and an 'HLR'. The 'SRF' is connected to the 'NPLDB' and the 'HLR'. 4. Recipient network/exchange (top right): Contains an 'MSC', an 'SRF', an 'NPLDB', and an 'HLR'. The 'SRF' is connected to the 'NPLDB' and the 'HLR'. A 'Called (ported) subscriber' is connected to a 'BS' in this network. A thick green line represents the call path: Calling subscriber -> BS -> MSC (Originating) -> MSC (Initiating) -> SRF (Initiating) -> NPCDB -> SRF (Initiating) -> HLR (Initiating) -> MSC (Initiating) -> MSC (Donor) -> SRF (Donor) -> NPLDB (Donor) -> SRF (Donor) -> HLR (Donor) -> MSC (Donor) -> MSC (Recipient) -> SRF (Recipient) -> NPLDB (Recipient) -> SRF (Recipient) -> HLR (Recipient) -> MSC (Recipient) -> BS -> Called (ported) subscriber. A small label 'Q.3905(16)\_F8-19' is in the bottom right corner of the diagram area.
+
+**Figure 8-19 – Number configuration for test case 8.27**
+
+##### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### **Test procedure:**
+
+- 1) OLE should send the request to the NPDB for establishment of a connection between calling and called party (ported subscriber number) using the concatenated address;
+- 2) the NPDB response should contain the information of the operator-recipient network and the number of the called party;
+- 3) transport of this response should be monitored;
+- 4) establish the connection between subscribers using the information which was received from NPDB;
+- 5) Repeat steps 1-4 using the separated address format;
+- 6) Repeat steps 1-4 when only the called party number has been transferred.
+
+##### **Pass/fail criteria:**
+
+The test can be considered successful if all three formats can be used for the call establishment.
+
+The test is considered failed if one of the types could not be used for the call establishment.
+
+-----**End of the test**-----
+
+-----**Test case # 8.28**-----
+
+**Title:** SCCP addressing
+
+"SCCP addressing based on RN for the called party should be supported".
+
+This is an optional test which is out of the scope of this Recommendation.
+
+-----**End of the test**-----
+
+-----**Test case # 8.29**-----
+
+**Title:** Identification of ported number for message transfer
+
+"The sum total of the networks involved in addressing and routing non-circuit-related messages pertaining to a ported number shall be able to detect that the number has been ported and drive the identity of the appropriate destination of the message. The division of responsibilities of this among the networks depend on the architecture chosen".
+
+This is an optional test which is out of the scope of this Recommendation.
+
+-----**End of the test**-----
+
+-----**Test case # 8.30**-----
+
+**Title:** Verifying that the exchanges which does not support NP can establish a connection without NPDB
+
+**Keywords:** Network node, network exchange, NPDB, the ported subscriber.
+
+**Purpose:**
+
+Verify that the exchanges which does not support NP can establish a connection without NPDB.
+
+**Standard (criteria):**
+
+Clause 8 of [b-ITU-T Q-Suppl.4].
+
+**Preconditions and dependencies:**
+
+The exchange does not support the number portability solution.
+
+##### Test set-up:
+
+
+
+The diagram illustrates the network configuration for test case 8.30, showing three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber and BS, connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. A Called (ported) subscriber and BS are connected to the Recipient network's MSC. A blue line represents the call path from the Calling subscriber to the Called (ported) subscriber. A green line represents the call path from the Calling subscriber to the Donor network's MSC. A red line represents the call path from the Donor network's MSC to the Recipient network's MSC. A yellow line represents the call path from the Recipient network's MSC to the Called (ported) subscriber. The diagram is labeled Q.3905(16)\_F8-20.
+
+Figure 8-20 – Network configuration for test case 8.30. The diagram shows three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. The Initiating network contains an Originating network/exchange with a Calling subscriber and BS, connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The Donor network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The Recipient network contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. A Called (ported) subscriber and BS are connected to the Recipient network's MSC. A blue line represents the call path from the Calling subscriber to the Called (ported) subscriber. A green line represents the call path from the Calling subscriber to the Donor network's MSC. A red line represents the call path from the Donor network's MSC to the Recipient network's MSC. A yellow line represents the call path from the Recipient network's MSC to the Called (ported) subscriber. The diagram is labeled Q.3905(16)\_F8-20.
+
+Figure 8-20 – Network configuration for test case 8.30
+
+##### Testing equipment:
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+##### Test procedure:
+
+- 1) establish a connection between the ported and non-ported number and monitor the forwarding of this call;
+- 2) emulate a node/exchange which does not support the NP procedure. This exchange should be between the initiating network/exchange and the operator-recipient's network/exchange;
+- 3) repeat step 1 for the case when the emulated node/exchange is used as an initiating network/exchange for calling party;
+- 4) the call from the given exchange should be forwarded to the nearest exchange/node of the initiating network which supports NP and monitor the forwarding of this call.
+
+##### Pass/fail criteria:
+
+The test can be considered successful if the nodes/exchanges which are not supporting portability are forwarded to a network which supports NP.
+
+The test is considered failed if the criteria mentioned above does not come true.
+
+-----End of the test-----
+
+## Appendix A
+
+### Verifying of the configuration of network service scenarios
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix contains the test cases which are verifying "all call query" and "onward routing" procedures.
+
+NOTE – The test cases presented below correspond to mobile number portability procedures defined in [b-ITU-T Q-Suppl.4]. However, these NP tests can also be for local number portability, including all network(s)/exchange(s) of the fixed network(s) which are used for the voice-call routing.
+
+-----**Test case # A.01**-----
+
+**Title:** Standard procedure for the "all call query" method
+
+**Keywords:** Routing information, originating network/exchange, initiating network/exchange, NPDB.
+
+#### **Purpose:**
+
+Verify the routing information procedure for ported numbers for the "all call query" method.
+
+#### **Standard (criteria):**
+
+Clauses 6.1.2, 6.2.1.1 of [b-ITU-T Q-Suppl.4].
+
+#### **Preconditions and dependencies:**
+
+The originating network/exchange (OLE) which is the host of the calling party, is not connected to NPDB. The called subscriber number is ported and stored in the operator-recipient's network.
+
+#### **Test set-up:**
+
+The network configuration should be allowed to transmit a voice/data call from an initiating network/exchange to an operator-recipient's network/exchange (the path is highlighted in green). All measured data have to be collected by protocol analyser at the reference points (see Figure A.1), which are highlighted in green. The network configuration is presented in Figure A.1.
+
+
+
+Figure A.1 – Network configuration for test case A.01. The diagram illustrates a call flow across three network domains: Initiating network/exchange, Donor network/exchange, and Recipient network/exchange. A calling subscriber in an 'Originating network/exchange' connects via a BS to an MSC in the 'Initiating network/exchange'. This MSC is linked to an SRF, which connects to an HLR and an NPCDB. The call path (indicated by a thick green line with nodes) then traverses to an MSC in the 'Donor network/exchange' (linked to its own SRF, NPLDB, and HLR) and finally to an MSC in the 'Recipient network/exchange' (also linked to an SRF, NPLDB, and HLR). From the recipient MSC, the call goes through a BS to the 'Called (ported) subscriber'. Dashed boxes group the components of each network exchange. A small label 'Q.3905(16)\_FA.1' is at the bottom right of the diagram.
+
+**Figure A.1 – Network configuration for test case A.01**
+
+#### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+#### **Test procedure:**
+
+- 1) a request from OLE for establishment of the connection to the NPDB has to be sent;
+NOTE – In the case when the originating network/exchange has no access to NPDB, the call should be forwarded to the initiating network/exchange to verify whether the number of the called party belongs to an operator-recipient's network;
+- 2) after establishing a test call, the request from the given network/exchange has to be sent to the NPDB to verify if the number of the called party is ported. Also, the request should provide information to obtain the routing information;
+- 3) in case the called party number is ported, the NPDB should inform the initiating network/exchange and an operator-recipient's network/exchange with the routing information which is needed for further call establishment. In addition, the information might include the optional indicators of the ported number (e.g., NP ID, the name of the operator-donor, the name of the operator-recipient, number, etc.). In this regard, the test suite should be allowed to send the reply to the called party providing the necessary information for call routing;
+- 4) In case the called party number is not ported the voice-call should be routed as a normal E.164 number. The relevant reply about the status of this number has to be provided from NPDB;
+- 5) after obtaining the routing information (mostly based on the test call) the operator-recipient's network/exchange should route the voice-call, using received routing information.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the called party number was determined correctly by using NPDB and the connection between calling party and called party was established.
+
+The test is considered failed if one of the criteria mentioned above does not come true.
+
+-----**End of the test**-----
+
+-----**Test case # A.02**-----
+
+**Title:** Special procedures for call routing using the "onward routing" method
+
+**Keywords:** Routing information, initiating network/exchange, operator-donor network/exchange.
+
+**Purpose:**
+
+Verify the special procedures for call routing using the "onward routing".
+
+**Standard (criteria):**
+
+Clause 6.2.2 of [b-ITU-T Q-Suppl.4].
+
+**Preconditions and dependencies:**
+
+Two network configurations are possible:
+
+- 1) the initiating network/exchange and the operator-donor network/exchange are not united in a network/exchange or a part of each other;
+- 2) the initiating network/exchange and the operator-donor network/exchange are united in a network/exchange.
+
+**Test set-up:**
+
+The network configuration allow to transmit a voice call from an initiating network/exchange to an operator-recipient network/exchange (the path is highlighted in blue). All measured data have to be collected by traffic analyzer at the reference point, which are highlighted in green. The network configuration is presented on Figure A.2.
+
+
+
+The diagram illustrates the network configuration for test case A.02. It consists of three main network domains: the Originating network/exchange, the Initiating network/exchange, the Donor network/exchange, and the Recipient network/exchange. The call path is highlighted in blue, and reference points for traffic analysis are highlighted in green.
+
+- Originating network/exchange:** Contains a Calling subscriber connected to a BS. The BS is connected to the Initiating network/exchange.
+- Initiating network/exchange:** Contains an MSC connected to the Donor network/exchange. The MSC is also connected to an SRF, which is connected to an NPCDB and an HLR. The MSC is connected to two BSs, one of which is connected to the Originating network/exchange.
+- Donor network/exchange:** Contains an MSC connected to the Recipient network/exchange. The MSC is also connected to an SRF, which is connected to an NPLDB and an HLR.
+- Recipient network/exchange:** Contains an MSC connected to a BS, which is connected to a Called (ported) subscriber. The MSC is also connected to an SRF, which is connected to an NPLDB and an HLR.
+
+The call path is highlighted in blue, and the reference points are highlighted in green. The diagram is labeled Q.3905(16)\_FA.2.
+
+Figure A.2 – Network configuration for test case A.02. The diagram shows a call path from an originating network/exchange to a recipient network/exchange via a donor network/exchange. The path is highlighted in blue, and reference points for traffic analysis are highlighted in green. The originating network/exchange contains a calling subscriber connected to a BS, which is connected to an MSC. The MSC is connected to an SRF, which is connected to an NPCDB and an HLR. The donor network/exchange contains an MSC connected to an SRF, which is connected to an NPLDB and an HLR. The recipient network/exchange contains an MSC connected to a BS, which is connected to a called (ported) subscriber. The MSC is also connected to an SRF, which is connected to an NPLDB and an HLR. The call path is highlighted in blue, and the reference points are highlighted in green.
+
+**Figure A.2 – Network configuration for test case A.02**
+
+#### **Testing equipment:**
+
+- 1) the traffic analyser;
+- 2) the NPDB-based solution.
+
+#### **Test procedure:**
+
+- 1) The test steps for the first configuration of circuit network are similar to standard procedure (which was described in previous test procedure);
+- 2) The test steps for the second configuration of circuit network will be the following:
+ - a) A request for establishing a connection between calling and called party (a test call) from an initiating network/exchange has to be sent;
+NOTE – In the case when the initiating network/exchange and an operator donor network/exchange is a united network/exchange, the call should not be forwarded for porting verifying to the initiating network/exchange.
+ - b) in this case if the called party number is in an operator-donor network (unported subscriber number) the connection between calling and called party should be established without any additional steps. The request for establishing a connection should be directly forwarded to the called party number side (in our case – to the operator-donor network/exchange);
+ - c) in a case when the called party number is not provided by an operator-donor network/exchange (ported subscriber number) then the test call cannot be served by the given initiating network/exchange. The call will be forwarded to another initiating network/exchange or NPDB;
+ - d) after obtaining the routing information from another initiating network/exchange of NPDB-side, the operator-recipient network/exchange should route the voice call, using received routing information, to the called party in order to establish the voice call connection between subscribers.
+
+#### **Pass/fail criteria:**
+
+The test can be considered successful if the connection between calling party and called party was established correctly.
+
+Test is considered failed if the establishment of a connection between the calling party and called party was impossible.
+
+-----End of the test-----
+
+# Bibliography
+
+- [b-ITU-T E.164 Suppl.2] Recommendation ITU-T E.164 – Supplement 2 (2014), *Number portability*.
+- [b-ITU-T Q-Suppl.3] Recommendation ITU-T Q-Suppl.3 (1988), *Number portability – Scope and capability set 1 architecture*.
+- [b-ITU-T Q-Suppl.4] Recommendation ITU-T Q-Suppl.4 (1998), *Number portability – Capability set 1 requirements for service provider portability (All call query and Onward routing)*.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..61932cbce2c05414a6f14541cf5d6b78d75ac513
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/raw.md
@@ -0,0 +1,1337 @@
+
+
+# **ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+# **Q.3906.1**
+
+(10/2010)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for the NGN –
+Testing for NGN networks
+
+---
+
+**Test scenarios and catalogue for testing fixed
+broadband access networks using a model
+network – Part I**
+
+Recommendation ITU-T Q.3906.1
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+# **SWITCHING AND SIGNALLING**
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3649 |
+| NGN applications | Q.3700–Q.3849 |
+| Testing for NGN networks | Q.3900–Q.3999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **Recommendation ITU-T Q.3906.1**
+
+# **Test scenarios and catalogue for testing fixed broadband access networks using a model network – Part I**
+
+## **Summary**
+
+Recommendation ITU-T Q.3906.1 describes main requirements to broadband testing on fixed networks. It could be useful as a basic Recommendation for interoperability testing on fixed broadband networks based on model networks.
+
+This Recommendation describes the principle of testing and describes the detailed procedures for testing and the expected results.
+
+## **History**
+
+| Edition | Recommendation | Approval | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0 | ITU-T Q.3906.1 | 2010-10-14 | 11 |
+
+## **Keywords**
+
+Model networks, next generation networks (NGN), public switched telephone network (PSTN), testing.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2012
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-------------------------------------------------|-------------|
+| 1 Scope | 1 |
+| 2 References | 1 |
+| 3 Definitions | 1 |
+| 3.1 Terms defined elsewhere | 1 |
+| 4 Abbreviations and acronyms | 1 |
+| 5 Conventions | 3 |
+| 6 General requirements for testing BBA networks | 3 |
+| 6.1 Testing scheme | 3 |
+| 6.2 Testing program | 4 |
+| 6.3 Methods of testing | 11 |
+
+
+
+## Recommendation ITU-T Q.3906.1
+
+# Test scenarios and catalogue for testing fixed broadband access networks using a model network – Part I
+
+# 1 Scope
+
+This Recommendation defines the list of checks to be performed during the functionality and interoperability testing of fixed broadband access (BBA) networks for PPPoE technology in operator and model networks.
+
+The Recommendation defines the tasks for testing BBA networks and provides a list of tests for a model network, while indicating the reason for choosing a type of network for specified test groups.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.3900] Recommendation ITU-T Q.3900 (2006), *Methods of testing and model network architecture for NGN technical means testing as applied to public telecommunication networks*.
+- [ITU-T Q.3901] Recommendation ITU-T Q.3901 (2008), *Testing topology for networks and services based on NGN technical means*.
+- [ITU-T Q.3903] Recommendation ITU-T Q.3903 (2008), *Formalized presentation of testing results*.
+- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 model network** [ITU-T Q.3900]: A network which simulates the capabilities similar to those available in present telecommunication networks, has a similar architecture and functionality and uses the same telecommunication technical means.
+
+**3.1.2 NGN technical means** [ITU-T Q.3900]: The NGN basic equipment which serves as a basis for building new generation network solutions, including for application in public telecommunication networks.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+ABG-FE Access Border Gateway Functional Entity
+
+ADSL Asymmetric Digital Subscriber Line
+
+| | |
+|----------|----------------------------------------------------------|
+| AG | Access Gateway |
+| AGC | Access Gateway Controller |
+| AGC-FE | Access Gateway Control Functional Entity |
+| AN | Access Node |
+| ARP | Address Resolution Protocol |
+| AS | Applications Server |
+| AS-FE | Application Support Functional Entity |
+| ATM | Asynchronous Transfer Mode |
+| BBA | Broadband Access |
+| BGC-FE | Breakout Gateway Control Functional Entity |
+| BRAS | Broadband Remote Access Server |
+| DHCP | Dynamic Host Configuration Protocol |
+| DSLAM | Digital Subscriber Line Access Multiplexer |
+| EAS | Ethernet Aggregation Switch |
+| HG | Home Gateway |
+| IBC-FE | Interconnection Border gateway Control Functional Entity |
+| IBG-FE | Interconnection Border Gateway Functional Entity |
+| ICMP | Internet Control Message Protocol |
+| I-CSC-FE | Interrogating Call Session Control Functional Entity |
+| IP | Internet Protocol |
+| ISDN | Integrated Services Digital Network |
+| KB | Knowledge Base |
+| LID | Light-Weight Identity protocol |
+| MAC | Media Access Control |
+| MG | Media Gateway |
+| MGC | Media Gateway Controller |
+| MGC-FE | Media Gateway Controller Functional Entity |
+| MGCP | Media Gateway Control Protocol |
+| MSAN | Multi-Service Access Node |
+| NGN | Next Generation Network |
+| NIT | Network Integration/Interconnection Testing |
+| OLT | Optical Line Terminal |
+| P-CSC-FE | Proxy Call Session Control Functional Entity |
+| PON | Passive Optical Network |
+| PPPoE | Point-to-Point Protocol over Ethernet |
+| PS | Proxy-Server (SIP) |
+| PSTN | Public Switched Telephone Network |
+
+| | |
+|----------|------------------------------------------------|
+| PVC | Permanent Virtual Circuit |
+| QoS | Quality of Service |
+| S-CSC-FE | Serving Call Session Control Functional Entity |
+| SCTP | Stream Control Transmission Protocol |
+| SG | Signalling gateway |
+| SG-FE | Signalling Gateway Functional Entity |
+| SIP | Session Initiation Protocol |
+| SNMP | Simple Network Management Protocol |
+| SMTP | Simple Mail Transfer Protocol |
+| SP | Signalling Point |
+| SS7 | Signalling System 7 |
+| SSH | Secure Shell |
+| STP | Signalling Transfer Point |
+| TCP | Transmission Control Protocol |
+| TE | Terminal Equipment |
+| TLS | Transport Layer Security |
+| TM | Technical Means |
+| UDP | User Datagram Protocol |
+| UNI | User Network Interface |
+| URI | Uniform Resource Identifier |
+| VDSL | Very-high data rate Digital Subscriber Line |
+| VLAN | Virtual Local Area Network |
+
+# **5 Conventions**
+
+None.
+
+# **6 General requirements for testing BBA networks**
+
+There are several testing stages in the functional and interoperability testing of broadband access (BBA) networks and technical means (TM). These stages include the functional testing of the BBA networks and interoperability testing of the BBA TM. The results of each of these tests shall be delivered to the global database in a format that conforms to [ITU-T Q.3903].
+
+## **6.1 Testing scheme**
+
+Tests are executed on the model network described in [ITU-T Q.3900]. The generalized testing scheme is shown in Figure 1.
+
+
+
+```
+
+graph TD
+ subgraph Branch_A
+ BRAS_A --- EAS_A[Ethernet Aggregation Switch]
+ AAA_A --- EAS_A
+ DHCP_A --- EAS_A
+ PPPoE_A --- EAS_A
+ H1A[Host_1] --- EAS_A
+ H2A[Host_2] --- EAS_A
+ H3A[Host_3] --- EAS_A
+ EAS_A --- Core1[IP Network Core-1]
+ end
+
+ subgraph Branch_B
+ BRAS_B --- EAS_B[Ethernet Aggregation Switch]
+ AAA_B --- EAS_B
+ DHCP_B --- EAS_B
+ PPPoE_B --- EAS_B
+ H1B[Host_1] --- EAS_B
+ H2B[Host_2] --- EAS_B
+ H3B[Host_3] --- EAS_B
+ EAS_B --- Core2[IP Network Core-2]
+ end
+
+ Core1 --- QoS[Network QoS parameters emulator] --- Core2
+
+ Core1 --- IPA[IP Protocols Analyzer]
+ Core2 --- IPA
+ IPA --- PP[Patch-panels and cross-cable equipment]
+
+ PP --- DSLAM_A[DSLAM_A/MSAN_A/EAS_A/OLT_A]
+ PP --- DSLAM_B[DSLAM_B/MSAN_B/EAS_B/OLT_B]
+
+ subgraph Access_A
+ DSLAM_A --- HG1A[HG1]
+ DSLAM_A --- HG2A[HG2]
+ DSLAM_A --- HG3A[HG3]
+ HG1A --- H1_1[Host_1]
+ HG1A --- H1_2[Host_2]
+ HG1A --- H1_3[Host_3]
+ end
+
+ subgraph Access_B
+ DSLAM_B --- HG1B[HG1]
+ DSLAM_B --- HG2B[HG2]
+ DSLAM_B --- HG3B[HG3]
+ HG1B --- H2_1[Host_1]
+ HG1B --- H2_2[Host_2]
+ HG1B --- H2_3[Host_3]
+ end
+
+```
+
+Figure 1 – General scheme for BBA network testing. The diagram illustrates a symmetrical network testbed. At the top, two identical branches (A and B) consist of BRAS, AAA, DHCP, and PPPoE servers connected to an Ethernet Aggregation Switch. Each switch connects to three local hosts (Host\_1, Host\_2, Host\_3) and an IP Network Core (Core-1 for A, Core-2 for B). Between the cores is a Network QoS parameters emulator. Below the cores, an IP Protocols Analyzer connects to a central 'Patch-panels and cross-cable equipment' block. This central block also connects to two DSLAM/MSAN/EAS/OLT units (A and B). Each DSLAM unit connects to three Home Gateways (HG1, HG2, HG3), and each HG connects to three hosts (Host\_1, Host\_2, Host\_3).
+
+**Figure 1 – General scheme for BBA network testing**
+
+## 6.2 Testing program
+
+### 6.2.1 Programme for testing the basic functionality of the BBA network
+
+Table 1 shows the program of basic functional testing for BBA networks and indicates information about the functions tested for each group of tests.
+
+**Table 1 – Programme of basic functionality testing for BBA networks**
+
+| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier |
+|---|---------------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------|
+| 1 | VLAN tags processing functionality checking | DSLAM/ MSAN | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of Multi PVC model used in UNI interface | T2 | DSLAM_VLAN_01 |
+| | | | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of Single PVC/Untagged model used in UNI interface | T2 | DSLAM_VLAN_02 |
+
+**Table 1 – Programme of basic functionality testing for BBA networks**
+
+| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier |
+|---|----------------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------|
+| | | | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of Single PVC/VLAN tagged model used in UNI interface | T2 | DSLAM_VLAN_03 |
+| | | | VLAN (S-Tag/C-Tag) tag pair assignment to Ethernet frames, transmitted in upstream direction | T2 | DSLAM_VLAN_04 |
+| | | | TLS user port configuration, assuring transparent transmission of initial IEEE 802.1Q tags via communication network, as assigned by a user | T2 | DSLAM_VLAN_05 |
+| | | | Configuration of a list of Ethernet frame types transmitted in upstream direction for a determined user port | T2 | DSLAM_VLAN_06 |
+| | | EAS | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of Untagged UNI architecture use on access stratum | T2 | EAS_VLAN_01 |
+| | | | S-VLAN (S-VID) identifiers assignment to Ethernet frames, transmitted in upstream direction in terms of VLAN tagged UNI architecture use on access stratum | T2 | EAS_VLAN_02 |
+| | | | VLAN (S-Tag/C-Tag) tag pair assignment to Ethernet frames, transmitted in upstream direction | T2 | EAS_VLAN_03 |
+
+**Table 1 – Programme of basic functionality testing for BBA networks**
+
+| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier |
+|---|------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------|
+| | | | TLS user port configuration, assuring transparent transmission of initial IEEE 802.1Q tags via communication network, as assigned by a user | T2 | EAS_VLAN_04 |
+| | | | Configuration of a list of Ethernet frame types transmitted in upstream direction for a specific user port | T2 | EAS_VLAN_05 |
+| | | BRAS | S-Tag tags assignment to unmarked Ethernet frames, transmitted downstream | T5 | BRAS_VLAN_01 |
+| | | | S-Tag/C-Tag (QinQ) tag pair assignment to unmarked Ethernet frames, transmitted downstream | T5 | BRAS_VLAN_02 |
+| 2 | QoS control functionality checking | DSLAM/MSAN | Priority bit marking in Ethernet frames, transmitted in upstream direction without IEEE 802.1Q tags assigned by user equipment | T2 | DSLAM_QOS_01 |
+| | | | Priority bit marking in Ethernet frames, transmitted in upstream direction with IEEE 802.1Q tags assigned by customer equipment | T2 | DSLAM_QOS_02 |
+
+**Table 1 – Programme of basic functionality testing for BBA networks**
+
+| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier |
+|---|--------------------------------------------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------|
+| | | EAS | Priority bit marking in Ethernet frames, transmitted in upstream direction without IEEE 802.1Q tags assigned by customer equipment | T2 | EAS_QOS_01 |
+| | | | Priority bit marking in Ethernet frames, transmitted in upstream direction with 802.1Q tags assigned by customer equipment | T2 | EAS_QOS_02 |
+| 3 | Security protection functionality checking | DSLAM/MSAN | Broadcast message blocking both in upstream and downstream directions | T2 | DSLAM_SEC_01 |
+| | | | Limiting the number of MAC-addresses of sources connected to one user port | T2 | DSLAM_SEC_02 |
+| | | | Ethernet frame filtering on the basis of MAC-source addresses and MAC-destination addresses | T2 | DSLAM_SEC_03 |
+| | | | Detecting replicated MAC-user addresses and resorting to a relevant mechanism of such situation remedy | T2 | DSLAM_SEC_04 |
+| | | EAS | Broadcast messages blocking both in upstream and downstream directions | T2 | EAS_SEC_01 |
+| | | | Limiting the number of MAC-addresses of sources connected to one user port | T2 | EAS_SEC_02 |
+| | | | Ethernet frame filtering on the basis of MAC-source addresses and MAC-destination addresses | T2 | EAS_SEC_03 |
+
+**Table 1 – Programme of basic functionality testing for BBA networks**
+
+| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier |
+|---|-----------------------------------------------------------------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------|
+| | | | Detecting replicated MAC-user addresses and resorting to a relevant mechanism of such situation remedy | T2 | EAS_SEC_04 |
+| | | BRAS | Preventing malicious user attacks due to IP-source address spoofing | T5 | BRAS_SEC_01 |
+| 4 | Subscriber line identification functionality checking | DSLAM/ MSAN | Functioning as a second-level DHCP Relay Agent and ensuring identification of DHCP subscriber connection points using data option (option 82) of DHCP protocol | T4 | DSLAM_LID_01 |
+| | | | Functioning as a PPPoE Intermediate Agent ensuring identification of subscriber lines | T4 | DSLAM_LID_02 |
+| | | EAS | Functioning as a second-level DHCP Relay Agent and ensuring identification of DHCP subscriber connection points using data option (option 82) of DHCP protocol | T4 | EAS_LID_01 |
+| | | | Functioning as a PPPoE Intermediate Agent ensuring identification of customer equipment | T4 | EAS_LID_02 |
+| 5 | Statistics acquisition, monitoring and control functionality checking | DSLAM/ MSAN | Remote monitoring using communication network control system including SNMP protocol | T2 | DSLAM_MNG_01 |
+| | | EAS | Remote monitoring using communication network control system including SNMP protocol | T2 | EAS_MNG_01 |
+
+**Table 1 – Programme of basic functionality testing for BBA networks**
+
+| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier |
+|---|-----------------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------|
+| | | BRAS | Remote monitoring checking with the use of communication network control system including SNMP protocol | T5 | BRAS_MNG_01 |
+| 6 | Multicast mode support functionality checking | DSLAM/ MSAN | Simultaneous connection of several users to one multicast group without subsequent load increase on the DSLAM/MSAN network interfaces | T2 | DSLAM_MC_01 |
+| | | | Limiting the total number of multicast groups to which a user can be connected at a time | T2 | DSLAM_MC_02 |
+| | | | Limiting the list of multicast groups available to a specific user | T2 | DSLAM_MC_03 |
+| | | EAS | Simultaneous connection of several users to one multicast group without subsequent load increase on EAS network interfaces | T2 | EAS_MC_01 |
+| | | | Limiting the total number of multicast groups to which a user can be connected at the same time | T2 | EAS_MC_02 |
+| | | | Limiting the total number of multicast groups to which a user can be connected at the same time | T2 | EAS_MC_03 |
+| | | BRAS | Limiting the total number of multicast groups transmitted within S-VLAN (MC-VLAN) | T5 | BRAS_MC_01 |
+| | | | Grownup statistics for multicast traffic for each MC-VLAN and for each multicast group | T5 | BRAS_MC_02 |
+
+**Table 1 – Programme of basic functionality testing for BBA networks**
+
+| # | Group of tests | Functional element of BBA network under test | Functionality checked | NGN function defined in [ITU-T Y.2012] | Test identifier |
+|---|-----------------------------------|----------------------------------------------|-----------------------------------------------------------------------------------|----------------------------------------|-----------------|
+| 7 | Access policy control and account | BRAS | Establishing PPPoE user sessions | T5 | BRAS_ACC_01 |
+| | | | Establishing IPoE (DHCP) user sessions | T5 | BRAS_ACC_02 |
+| | | | Functioning as a LNS server during termination of L2TP user tunnels | T5 | BRAS_ACC_03 |
+| | | | Account of rendered broadband access services for users initiating PPPoE sessions | T5 | BRAS_ACC_04 |
+| | | | Disconnecting a user upon expiration of established quota of received data volume | T5 | BRAS_ACC_05 |
+| | | | Limiting a bandwidth that is assigned to a user for data receiving/transmission | T5 | BRAS_ACC_06 |
+
+### 6.2.2 Programme for testing BBA TM interoperability
+
+Table 2 shows the programme for testing the interoperability of the BBA TM of the different vendors that compose the BBA network under test, instructions for the tests, purpose of the tests and lists the corresponding tests.
+
+**Table 2 – Program of interoperability testing for BBA TM**
+
+| # | Group of tests | Purpose | Test identifier |
+|---|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
+| 1 | Interoperability testing of AN (access nodes) and BRAS of different vendors | DSLAM/MSAN/EAS/OLT access nodes equipment is compatible with BRAS equipment from different vendors including processing of DHCP option 82 and PPPoE TAG which are installed with the use of AN equipment | AN-BRAS_COMP_01
AN-BRAS_COMP_02
AN-BRAS_COMP_03 |
+| 2 | Interoperability testing of AN equipment and home gateway equipment from different vendors | Equipment installed in user premises (home gateways, business routers, modems) is fully compatible with DSLAM/MSAN/OLT access nodes equipment from different vendors | DSL_COMP_01 |
+
+## 6.3 Methods of testing
+
+### 6.3.1 Methods of base functionality testing
+
+#### 6.3.1.1 Check of DSLAM/MSAN equipment functionality
+
+##### 6.3.1.1.1 Check of functions of VLAN tag processing
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_VLAN_01 |
+| Test name | Multi PVC |
+| Test purpose | Check if the DSLAM/MSAN has the possibility to transport the S VLAN (S VID) identifier on Ethernet, which is transferred upstream using the UNI interface Multi PVC model
NOTE – The test is produced in case of use of ATM transport on UNI interface.
|
+| Initial condition | - 1) Prepare in KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, the two customer ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the customer side, the home gateway has to be connected via user network interfaces (HG1 and HG2, accordingly).
- 4) A.1 and A.2 hosts are connected to home gateway HG1.
- 5) B.1 and B.2 hosts are connected to home gateway HG2.
- 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation
- 7) A.1 and B.1 hosts use PPPoE sessions.
- 8) A.2 and B.2 hosts use IPoE sessions.
- 9) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
- 11) For termination of PPPoE sessions from A.1 and B.1 hosts the external router has to be connected to the Ethernet switch.
- 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
- 13) IP-addresses from one IP subnetwork are used on the hosts A.2, B.2 and X.2.
- 14) Two virtual connections are configured on HG1 and HG2 equipment:
- 15) PVC X1/Y1 for PPPoE traffic connected to A.1 and B.1 hosts, accordingly;
- 16) PVC X2/X2 for IPoE traffic connected to A.2 and B.2 hosts, accordingly.
- 17) Multi PVC (X1/Y1 and X2/Y2) on UNI interfaces are configured on the DSLAM/MSAN equipment.
- 18) On the DSLAM/MSAN equipment there is configured the possibility to assign "S VID" =1 for Ethernet frames which are transferred upstream from HG1 equipment on virtual connection PVC X1/Y1.
- 19) On the DSLAM/MSAN equipment there is configured the possibility to assign "S VID" =2 for Ethernet frames which are transferred upstream from HG1 equipment on virtual connection PVC X1/Y1.
|
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 20) On the DSLAM/MSAN equipment there is configured the possibility to assign "S VID" =3 for Ethernet frames which are transferred upstream from any user equipment on virtual connection PVC X2/Y2.
21) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols ICMP ARP.
|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.1.
- 3) Perform traffic exchange between hosts A.2 and X.2.
- 4) Perform traffic exchange between hosts B.2 and X.2.
- 5) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_01.txt) and put the file into the corresponding section of the KB.
- 6) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) The DSLAM/MSAN equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
- 2) The DSLAM/MSAN equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
- 3) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
- 4) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
- 5) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing Host A.1, Host A.2, Host B.1, Host B.2 connected to HG1 and HG2 modems. HG1 and HG2 are connected to a DSLAM via PVCs. The DSLAM is connected to an Ethernet switch via Port 1 and Port 2. Port 1 is connected to a Protocol analyzer and Host X.1. Port 2 is connected to Host X.2 and a Server DHCP. The DSLAM also has three virtual connections labeled S-VID '1' (PPPoEuser 1), S-VID '2' (PPPoEuser 2), and S-VID '3' (IPoEuser 1,2). A PPPoE Termination; DHCP relay agent is also shown.
|
+
+| | |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_VLAN_02 |
+| Test name | Configuration of S-VLAN for Single PVC/Untagged architecture (model N:1+1:1) |
+| Test purpose | Check if the DSLAM/MSAN has the possibility to assign the S VLAN (S-VID) identifier to the Ethernet frames, which are transferred upstream using the Single PVC/Untagged model on UNI interface |
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two customer ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the customer side the home gateway has to be connected via user network interfaces (HG1 and HG2, accordingly).
- 4) A.1 and A.2 hosts are connected to home gateway HG1.
- 5) B.1 and B.2 hosts are connected to home gateway HG2.
- 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
- 7) A.1 and B.1 hosts use PPPoE sessions.
- 8) A.2 and B.2 hosts use IPoE sessions.
- 9) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
- 11) For termination of PPPoE sessions from A.1 and B.1 hosts, the external router has to be connected to the Ethernet switch.
- 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
- 13) IP-addresses from one IP subnetwork are used on the hosts A.2, B.2 and X.2.
- 14) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
- 15) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
- 16) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
- 17) On the DSLAM/MSAN equipment there is configured the possibility to assign "S VID" =1 for Ethernet frames which are transferred upstream depending on value of Ethertype field and user port number. Following options are configured:
- 18) assignment of "S-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1) with the Ethertype value 0x8863 or 0x8864;
- 19) assignment of "S-VID"=2 to Ethernet frames which are transferred from HG2 equipment (user port No. 2) with the Ethertype value 0x8863 or 0x8864;
- 20) assignment of "S-VID"=3 frames to Ethernet transferred from HG1 and HG2 equipment (any user port) with the Ethertype value 0x0800.
- 21) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols ICMP ARP.
|
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.1.
- 3) Perform traffic exchange between hosts A.2 and X.2.
- 4) Perform traffic exchange between hosts B.2 and X.2.
- 5) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_02.txt) and put the file into the corresponding section of the KB.
- 6) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) The DSLAM/MSAN equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
- 2) The DSLAM/MSAN equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
- 3) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
- 4) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
- 5) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme |
|
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_VLAN_03 |
+| Test name | Configuration of S-VLAN for Single PVC/VLAN tagged architecture (model N:1+1:1) |
+| Test purpose | Check if the DSLAM/MSAN has the possibility to assign the S VLAN (S VID) identifier to the Ethernet frames, which are transferred upstream using the Single PVC/VLAN tagged model on UNI interface |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side the home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
- 4) A.1 and A.2 hosts are connected to home getaway HG1.
- 5) B.1 and B.2 hosts are connected to home getaway HG2.
|
+
+- 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
+- 7) A.1 and B.1 hosts use PPPoE sessions.
+- 8) A.2 and B.2 hosts use IPoE sessions.
+- 9) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
+- 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
+- 11) For termination of PPPoE sessions from A.1 and B.1 hosts external router has to be connected to the Ethernet switch.
+- 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
+- 13) IP-addresses from one IP subnetwork are used on the hosts A.2, B.2 and X.2.
+- 14) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
+- 15) HG1 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured as follows: there is assigned VLAN tag "C-VID"=1 for PPPoE sessions connected with host A.1, and VLAN tag "C-VID"=2 for IPoE sessions connected with host A.2.
+- 16) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
+- 17) HG2 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG2 equipment is configured as follows: there is assigned "C-VID"=1 for PPPoE sessions connected with host B.1, and "C-VID"=2 for IPoE sessions connected with host B.2.
+- 18) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
+- 19) The possibility of use VLAN identifiers for users' ports No. 1 and No. 2 is configured on the DSLAM/MSAN equipment. The VLAN Membership List is configured on the DSLAM/MSAN equipment including list of C-VID values resolved for each of users ports. For users ports No. 1 and No. 2 there should be resolved values "C-VID"=1 and "C-VID"=2.
+- 20) On the DSLAM/MSAN equipment there is a possibility to assign S VID identifiers for Ethernet frames which are transferred upstream depending on value of VLAN identifier in initial IEEE 802.1Q tag and user port number. The following configuration of VLAN translation table should be done:
+ - assignment of "S-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1) and have "C-VID"=1 in IEEE 802.1Q tag;
+ - assignment of "S-VID"=2 to Ethernet frames which are transferred from HG2 equipment (user port No. 2) and have "C-VID"=1 in IEEE 802.1Q tag;
+ - assignment of "S-VID"=3 to Ethernet frames which are transferred from HG2 equipment (any user port) and have "C-VID"=2 in IEEE 802.1Q tag.
+- 21) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP || ARP.
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | 1) Perform traffic exchange between hosts A.1 and X.1.
2) Perform traffic exchange between hosts B.1 and X.1.
3) Perform traffic exchange between hosts A.2 and X.2.
4) Perform traffic exchange between hosts B.2 and X.2.
5) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_03.txt) and put the file into the corresponding section of the KB.
6) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) The DSLAM/MSAN equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
2) The DSLAM/MSAN equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
3) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
4) The DSLAM/MSAN equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
5) The DSLAM/MSAN equipment deletes the Ethernet frames which contain C-VID identifiers in IEEE 802.1Q tag not matching VLAN Membership List.
6) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme |
|
+
+| | |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_VLAN_04 |
+| Test name | Configuration of S-VLAN/C-VLAN stack (QinQ) |
+| Test purpose | Check if the DSLAM/MSAN has the possibility to assign the VLAN tag pair (S-Tag/C-Tag) to the Ethernet frame, which are transferred upstream |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side, the home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2. |
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
7) A.1 and B.1 hosts use IPoE sessions.
8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
9) IP-addresses for hosts A.1, B.1, X.1 and X.2 are assigned dynamically with the allocated DHCP server, or are configured manually.
10) IP-addresses from one IP subnetwork are used on the hosts A.1, B.1 and X.2.
11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
13) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
14) On the DSLAM/MSAN equipment there is configured the possibility to assign VLAN tag pair (S-Tag/C-Tag) for Ethernet frames which are transferred upstream. The S-VID value identifies DSLAM/MSAN equipment (i.e., value S VID is identical for all users ports). C-VID value identifies number of user port on which Ethernet frame has arrived. The following configuration should be done:
- – assignment of "S-VID"=1, "C-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1);
- – assignment of "S-VID"=1, "C-VID"=2 to Ethernet frames which are transferred from HG1 equipment (user port No. 2)
15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | 1) Perform traffic exchange between hosts A.1 and X.1.
2) Perform traffic exchange between hosts B.1 and X.2.
3) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_04.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) The DSLAM/MSAN equipment has assigned the identifier "S-VID"=1, "C-VID"=1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
2) The DSLAM/MSAN equipment has assigned the identifier "S-VID"=1, "C-VID"=2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
3) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+| | |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test scheme
| Detailed Diagram Description: The diagram illustrates a network test setup. On the left, Host A.1 and Host B.1 are connected to Home Gateways HG1 and HG2 respectively. HG1 and HG2 are labeled as modemxDSL. The connections between hosts and HGs are labeled 'IP: x.x.x.x (DHCP)'. The HGs connect to a DSLAM via 'PVC 0/35 (IPoE)'. HG1 connects to Port 1 and HG2 connects to Port 2 of the DSLAM. Inside the DSLAM, dashed lines show logical paths to an Ethernet switch. The path from Port 1 is labeled 'S-VID "1", C-VID "1" (user 1)' and the path from Port 2 is labeled 'S-VID "1", C-VID "2" (user 2)'. The Ethernet switch connects to Host X.1 and Host X.2, both labeled 'IP: x.x.x.x (DHCP)'. Additionally, the switch connects to a 'Server DHCP' and a 'DHCP relay agent' (indicated by a red crossed circle icon).
|
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Network diagram for test scheme DSLAM\_VLAN\_05. It shows Host A.1 and Host B.1 connected to HG1 and HG2 (modemxDSL) respectively via IPoE. HG1 and HG2 connect to DSLAM ports 1 and 2 via PVC 0/35 (IPoE). The DSLAM connects to an Ethernet switch. Port 1 traffic is tagged with S-VID '1', C-VID '1' (user 1). Port 2 traffic is tagged with S-VID '1', C-VID '2' (user 2). The Ethernet switch connects to Host X.1 and Host X.2 (both using DHCP), a Server DHCP, and a DHCP relay agent.
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_VLAN_05 |
+| Test name | Configuration of TLS user port |
+| Test purpose | Check if the DSLAM/MSAN has the possibility of TLS user port configuration providing transparent transfer of initial IEEE 802.1Q tags set by users over the network. |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side to the network termination of given user line there should be a connection from home gateway (business) (HG1 equipment).
- 4) Hosts A.1 and A.2 are connected to HG1 equipment.
- 5) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
- 6) Host A.1 uses PPPoE sessions.
- 7) Host A.2 uses IPoE sessions.
- 8) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 9) IP-address for host A.1 is assigned dynamically with allocated PPPoE server or are configured manually.
- 10) For termination of PPPoE sessions from host A.1 external router has to be connected to the Ethernet switch.
- 11) IP-addresses for hosts A.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
- 12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
- 13) HG1 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured as follows: there is assigned VLAN tag "C-VID"=111 for PPPoE sessions connected with host A.1, and VLAN tag "C-VID"=222 for IPoE sessions connected with host A.2.
- 14) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
- 15) User port No. 1 of DSLAM/MSAN equipment is configured as TLS port providing transparent transfer of VLAN tags assigned on user equipment.
|
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 16) VLAN Membership List is configured on the DSLAM/MSAN equipment for user port No. 1. The VLAN Membership List should contain the list of C-VID identifiers which have not been related to TLS traffic transferred through user port No. 1 in an upstream direction. This list should contain "C-VID"=111. All Ethernet frames transferred upstream through user port No. 1 and not having "C-VID"=111, should be processed as TLS traffic.
17) On the DSLAM/MSAN equipment should be configured the VLAN translation table according to which the Ethernet frames transferred upstream and having initial identifier "C-VID"=111 (matching VLAN Membership List) should get "S-VID"=1 identifier. Initial identifier C-VID in this case should be deleted.
18) On the DSLAM/MSAN equipment there is a possibility to assign TLS "S-VID"=100 identifier for Ethernet frames which are transferred upstream through user port No. 1 and having initial IEEE 802.1Q tag, not matching VLAN Membership List. Thus initial IEEE 802.1Q tag, received from the user, remains as enclosed C-Tag.
19) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | 1) Perform traffic exchange between hosts A.1 and X.1.
2) Perform traffic exchange between hosts A.2 and X.2.
3) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_05.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) The DSLAM/MSAN equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1. Thus initial IEEE 802.1Q tag (including "C-VID"=111), received from the user, has been deleted.
2) The DSLAM/MSAN equipment has assigned the identifier "S VID" =100 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2. Thus initial IEEE 802.1Q tag (including "C-VID"=222), received from the user, has remained as an enclosed C-Tag (having "C-VID"=222).
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing the test scheme. On the left, Host A.1 (IP: x.x.x.x PPPoE) and Host A.2 (IP: x.x.x.x DHCP) are connected to an HG1 (modem xDSL). The HG1 is connected to a DSLAM via two PVCs: PVC 0/35 for PPPoE (802.1Q Tag '111') and PVC 0/35 for IPoE (802.1Q Tag '222'). The DSLAM has 'User port#1 - TLS' configured with a VLAN Membership List containing C-VID=111 and a translation table mapping C-VID=111 to S-VID=1. The DSLAM is connected to an Ethernet switch via Port 1. The switch is connected to Host X.1 (IP: x.x.x.x DHCP), Host X.2 (IP: x.x.x.x DHCP), a Server DHCP, and a PPPoE Termination; DHCP relay agent. The switch is configured with S-VID '1' for the PPPoE path and S-VID '100', C-VID '222' for the IPoE path.
|
+
+| | |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_VLAN_06 |
+| Test name | Configuration of admissible list of Ethernet frame types |
+| Test purpose | Check if the DSLAM/MSAN has the possibility of admissible list of Ethernet frame types configuration for certain user port (for the upstream transfer) |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) have to be used. On the user side the home gateway equipment (HG1 equipment) has to be connected to network termination of the given user line.
4) Host A.1 is connected to HG1 equipment.
5) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
6) Host A.1 uses IPoE sessions.
7) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
8) IP-addresses for hosts A.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually.
9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
11) On the DSLAM/MSAN equipment there is a possibility to assign "S-VID"=1 identifiers to any Ethernet frames transferred upstream through user port No. 1.
12) Further adjustment of equipment should be provided according to one of the following configurations:
Configuration 1
On HG1 equipment there should be a disconnected function of VLAN tags assignment for Ethernet frames transferred upstream. Host A.1 also should not assign VLAN tags for Ethernet frames transferred upstream.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "untagged or priority tagged frames" for user port No. 1.
Configuration 2
Configuration of HG1 equipment is the same as in Configuration 1.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "VLAN tagged frames" for user port No. 1.
Configuration 3
Configuration of HG1 equipment is the same as in Configuration 1.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "admit all" for user port No. 1.
|
+
+| | |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | Configuration 4
Activate on HG1 equipment function of VLAN tags assignment to Ethernet frames transferred upstream. HG1 equipment should be configured to assign VLAN "C-VID"=1 identifier for IPoE sessions related with host A.1
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "untagged or priority tagged frames" for user port No. 1.
Configuration 5
Configuration of HG1 equipment is same as in Configuration 4.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "VLAN tagged frames" for user port No. 1.
Configuration 6
Configuration of HG1 equipment is same as in Configuration 4.
On the DSLAM/MSAN equipment during configuration of admissible Ethernet frames types list there should be specified value: "admit all" for user port No. 1.
13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | - 1) Using Configuration 1 perform on host A.1 command ping for host X.1.
- 2) Using Configuration 2 perform on host A.1 command ping for host X.1.
- 3) Using Configuration 3 perform on host A.1 command ping for host X.1.
- 4) Using Configuration 4 perform on host A.1 command ping for host X.1.
- 5) Using Configuration 5 perform on host A.1 command ping for host X.1.
- 6) Using Configuration 6 perform on host A.1 command ping for host X.1.
- 7) Save the captures of traces in separate files ([Vendor]-DSLAM_VLAN_06.txt) and put the file into the corresponding section of the KB.
- 8) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) Successful performance of command ping according to step 1 of test procedure.
- 2) Unsuccessful performance of command ping according to step 2 of test procedure.
- 3) Successful performance of command ping according to step 3 of test procedure.
- 4) Unsuccessful performance of command ping according to step 4 of test procedure.
- 5) Successful performance of command ping according to step 5 of test procedure.
- 6) Successful performance of command ping according to step 6 of test procedure.
- 7) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+| | |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test scheme
| graph LR HostA1[Host A.1
IP: x.x.x.x DHCP] -- IPoE --> HG1[HG1
modem/DSL] HG1 -- "Untagged or VLAN tagged frames, PVC 0/35" --> DSLAM[DSLAM] subgraph DSLAM_Box [DSLAM] Port1[Port 1] Callout[User port#1
The admissible type of
Ethernet frame:
1-st variant Untagged
frames
2-nd variant
VLAN tagged frames
3-rd variant
any frames] end DSLAM -- "S-VID '1'" --> Switch[Ethernet switch] Switch --- HostX1[Host X.1
IP: x.x.x.x DHCP] Switch --- Server[Server
DHCP] Switch -.-> Relay[DHCP relay agent] style Relay stroke:#f00,stroke-width:4px
|
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Network diagram for QoS testing. Host A.1 connects to HG1 (modem/DSL) via IPoE. HG1 connects to DSLAM Port 1 via 'Untagged or VLAN tagged frames, PVC 0/35'. A callout for User port#1 specifies frame variants: 1-st variant Untagged frames, 2-nd variant VLAN tagged frames, 3-rd variant any frames. DSLAM connects to Ethernet switch via S-VID '1'. Host X.1 and a Server DHCP connect to the Ethernet switch. A DHCP relay agent is shown with a red cross over its path.
+
+##### 6.3.1.1.2 Check of QoS functions
+
+| | |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_QOS_01 |
+| Test name | Marks of priority bits during processing of Ethernet frames which are not containing VLAN tags |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of priority bits marking in Ethernet frames which are transferred upstream and not containing IEEE 802.1Q tags, assigned by user equipment |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side the home gateways equipment should be connected to network terminations of user lines (HG1 and HG2, accordingly).
- 4) Host A.1 is connected to home getaway HG1.
- 5) Host B.1 is connected to home getaway HG2.
- 6) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
- 7) A.1 and B.1 hosts use IPoE sessions.
- 8) HG1 and HG2 equipment work in the bridge mode (the function of local DHCP server is disconnected).
- 9) IP-addresses for hosts A.1, B.1 and X.1 are assigned dynamically with the allocated DHCP server, or are configured manually.
- 10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
- 11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
- 12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
- 13) A.1 and B.1 hosts should have possibility of priority assignment to Ethernet frames. A.1 and B.1 hosts should establish priority "6" for all transferred Ethernet frames.
|
+
+| | |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 14) HG1 and HG2 equipment should provide transparent translation of Ethernet frames priorities values configured on A.1 and B.1 hosts, accordingly. On HG1 equipment and HG2 there is disconnected the function of IEEE 802.1Q tags assignment to Ethernet frames transferred upstream.
15) On the DSLAM/MSAN equipment there should be configured possibility of S-Tag assignment, including identifier "S-VID"=1, to Ethernet frames transferred upstream through any of users ports. In this case the general VLAN (N:1) should be configured for all users ports.
16) On the DSLAM/MSAN equipment there should be configured user port No. 1 with the possibility of copying the priority value of Ethernet frame received from HG1 equipment, into the value of S-Tag priority.
17) On the DSLAM/MSAN equipment there should be configured user port No. 2 with the possibility to identify the value of S-Tag priority for Ethernet frames transferred upstream through given port on basis of "Ingress to Egress" policy. In this case as criteria for definition of S-Tag priority the following parameters should be used:
- – value of user port number (physical or logic);
- – value of Ethertype field in the Ethernet frame;
- – value of initial Ethernet frame priority received from HG2 equipment.
18) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.1.
- 3) During traffic exchange between hosts B.1 and X.1 perform transfer of ARP message from host B.1 (for this purpose it is necessary to clear contents of ARP table on host B.1).
- 4) Save the captures of traces in separate files ([Vendor]-DSLAM_QOS_01.txt) and put the file into the corresponding section of the KB.
- 5) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) S-Tag priority for Ethernet frames transferred upstream through user port No. 1 equals to "6".
- 2) S-Tag priority for Ethernet frames transferred upstream through user port No. 2 has been established according to policy defined on the DSLAM/MSAN equipment for the given port.
- 3) Policy for different S-Tag definition criteria has been correctly performed.
- 4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing the test scheme. Host A.1 (IP: x.x.x.x (DHCP)) connects via IPoE to HG1 (modem xDSL). Host B.1 (IP: x.x.x.x (DHCP)) connects via IPoE to HG2 (modem xDSL). Both HGs connect to a DSLAM via links labeled 'Priority tagged frames/No VLAN tag (PVC 0/35)'. The DSLAM has Port 1 (labeled 'Copying of value of priority') and Port 2 (labeled 'Applying of policy: Ingress to Egress'). The DSLAM connects via a link labeled 'S-Tag (S-VID
|
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_QOS_02 |
+| Test name | Marks of priority bits during processing of Ethernet frames containing VLAN tags |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of priority bits marking in Ethernet frames which are transferred upstream and containing IEEE 802.1Q tags, assigned by user equipment |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2.
6) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
7) A.1 and B.1 hosts use IPoE sessions.
8) HG1 and HG2 equipment work in the bridge mode (the function of local DHCP server is disconnected).
9) IP-addresses for hosts A.1, B.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually.
10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
13) HG1 equipment should support the function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured to assign IEEE 802.1Q tag, including "C-VID" =1 and priority value equal to "6" for all frames transferred.
14) HG2 equipment should support the function of VLAN tags assignment according to IEEE 802.1Q standard. HG2 equipment is configured to assign IEEE 802.1Q tag, including "C-VID" =1 and priority value equal to "6" for all frames transferred.
15) On the DSLAM/MSAN equipment should be configured the possibility of IEEE 802.1Q tags usage on users ports No. 1 and No. 2. The VLAN Membership List is configured on the DSLAM/MSAN equipment including list of C-VID values resolved for each of users ports. For users ports No. 1 and No. 2 there should be resolved value "C-VID" =1.
16) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through any of users ports. In this case, the general S-VLAN (N:1) should be configured for all users ports.
17) On the DSLAM/MSAN equipment there should be configured user port No. 1 with the possibility of copying the priority value from IEEE 802.1Q tag, received from HG1 equipment, into the S-Tag priority value.
|
+
+| | |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 18) On the DSLAM/MSAN equipment should be configured user port No. 2 with the possibility to identify the value of S-Tag priority for Ethernet frames transferred upstream through given port on basis of "Ingress to Egress" policy. In this case as criteria for definition of S-Tag priority the following parameters should be used:
- – value of user port number (physical);
- – C-VID value in the initial Ethernet frame;
- – C-Tag priority value in the initial Ethernet frame.
19) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.1.
- 3) Save the captures of traces in separate files ([Vendor]-DSLAM_QOS_02.txt) and put the file into the corresponding section of the KB.
- 4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) S-Tag priority for Ethernet frames transferred upstream through user port No. 1 equals to "6".
- 2) S-Tag priority for Ethernet frames transferred upstream through user port No. 2 has been established according to policy defined on the DSLAM/MSAN equipment for the given port.
- 3) Policy for different S-Tag definition criteria has been correctly performed.
- 4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 (modem xDSL) respectively. These are connected to a DSLAM. Port 1 of the DSLAM is connected to an Ethernet switch, and Port 2 is connected to a DHCP relay agent. Host X.1 is connected to the Ethernet switch. The diagram includes labels for IP addresses (IP: xxx.x (DHCP)), 802.1Q tags (C-VID '1', priority '6'), and policy actions like 'Copying of value of priority 802.1 Q Tag' and 'Applying of policy Ingress to Egress'.
Detailed description of the diagram: - Host A.1 (IP: xxx.x (DHCP)) connects via IPoE to HG1 (modem xDSL). - Host B.1 (IP: xxx.x (DHCP)) connects via IPoE to HG2 (modem xDSL). - HG1 connects to DSLAM Port 1 with label: 802.1Q Tag (C-VID '1', priority '6'), PVC 0/35. - HG2 connects to DSLAM Port 2 with label: 802.1Q Tag (C-VID '1', priority '6'), PVC 0/35. - DSLAM Port 1 has a box: 'Copying of value of priority 802.1 Q Tag'. - DSLAM Port 2 has a box: 'Applying of policy Ingress to Egress'. - DSLAM connects to an Ethernet switch via a link labeled 'S-Tag (S-VID '1'+priority)'. - Host X.1 (IP: xxx.x (DHCP)) connects to the Ethernet switch. - A DHCP relay agent (represented by a server icon with a red 'X' over it) is connected to the Ethernet switch, labeled 'Server DHCP'.
|
+
+##### 6.3.1.1.3 Check of security functions
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_SEC_01 |
+| Test name | Blocking of broadcasting packages |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of blocking upstream and downstream broadcast messages |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect the equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side, the equipment of a home gateway (HG1 equipment) should be connected to network termination of a user line.
- 4) Host A.1 is connected to home gateway HG1.
- 5) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
|
+
+| | |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
7) IP-addresses for hosts A.1 and X.1 are configured manually (statically) and should be from one IP subnetwork.
8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
10) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through user port No. 1.
11) On the DSLAM/MSAN equipment there should be configured blocking of broadcasting packages in an upstream direction for user port No. 1.
12) On the DSLAM/MSAN equipment there should be configured blocking of broadcasting packages in downstream for "S-VID" =1.
13) Before beginning of carrying out of test procedure it is necessary to clear contents of ARP tables on hosts A.1 and X.1.
|
+| Test procedure | 1) Perform on host A.1 command ping for host X.1.
2) Perform on host X.1 command ping for host A.1.
3) Save the captures of traces in separate files ([Vendor]-DSLAM_SEC_01.txt) and put the file into the corresponding section of the KB
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Command ping, performed on host A.1 for host X.1 has not passed (broadcasting ARP message transferred by host A.1 has been blocked on the DSLAM/MSAN equipment).
2) Command ping, performed on host X.1 for host A.1 has not passed (broadcasting ARP message transferred by host X.1 has been blocked on the DSLAM/MSAN equipment).
3) In ARP tables on hosts A.1 and X.1 there are no dynamic records.
4) There is a possibility of broadcasting packages blocking function configuration on the DSLAM/MSAN equipment in a downstream. Configuration of the given function is made on VLAN basis.
5) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme |
graph LR HostA1[Host A.1
IP: xxxxx] --- HG1["HG1
(modemxDSL)"] HG1 --- PVC 0/35 DSLAM subgraph DSLAM [DSLAM] Port1[Port 1] Note[Function of blocking broadcasting packages activated] end Port1 -.-> S-VID "1" EthernetSwitch[Ethernet switch] EthernetSwitch --- HostX1[Host X.1
IP: xxxxx]
|
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_SEC_02 |
+| Test name | Restriction of the MAC-addresses table size |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of restriction of sources MAC-addresses number connected with one user port |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On party of user home gateway equipment (HG1 equipment) should be connected to network termination of a user line.
4) Hosts A.1, A.2 and A.3 are connected to home gateway HG1.
5) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
7) IP-addresses for hosts A.1, A.2, A.3 and X.1 are configured manually (statically) and should be from one IP subnetwork.
8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
10) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through user port No. 1.
11) On the DSLAM/MSAN equipment should be configured the maximum number of MAC-addresses of the sources resolved for user port No. 1 equals to 2. |
+| Test procedure | 1) Perform consecutive connections of hosts A.1, A.2 and A.3.
2) During connection of each host (A.1, A.2, A.3) perform from this host continuous command ping for host X.1.
3) Save the captures of traces in separate files ([Vendor]-DSLAM_SEC_02.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) Successful performance of commands ping from A.1 and A.2 hosts.
2) Unsuccessful performance of commands ping from host A.3.
3) There is a possibility of maximum resolved MAC-addresses number of sources configuration independently for each users ports.
4) The daily report form has been saved in the corresponding section of KB. |
+
+
+
+**Test scheme**
+
+Network diagram showing Host A.1, A.2, and A.3 connected to a central HG1 (modem xDSL) unit. HG1 is connected via a PVC 0/35 line to a DSLAM unit. The DSLAM has a 'User port #1' with a note 'Admissible number of MAC-address of source' and 'Port 1'. The DSLAM is connected via an S-VID '1' line to an Ethernet switch. Host X.1 is connected to the Ethernet switch. All hosts have IP: xxxxx.
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_SEC_03 |
+| Test name | Filtration on MAC-addresses basis |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of Ethernet frames filtration on sources MAC-addresses basis and MAC-addresses of destinations. |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
- 4) A.1 and A.2 hosts are connected to home gateway HG1.
- 5) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
- 6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
- 7) IP-addresses for hosts A.1, A.2, X.1 and X.2 are configured manually (statically) and should be from one IP subnetwork. Hosts A.1/A.2 should have the possibility to exchange traffic with hosts X.1/X.2 without router.
- 8) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
- 9) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
- 10) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including the identifier "S-VID"=1, to Ethernet frames transferred upstream through user port No. 1.
- 11) On the DSLAM/MSAN equipment there should be activated function of Ethernet frames filtration for user port No. 1 MAC-addresses. For the given user port there should be configured barring for access from source with MAC-address of host A.2, and also an barring for access to destination with MAC-address of host X.2.
|
+
+| | |
+|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | 1) Perform on host A.1 command ping for host X.1.
2) Perform on host A.1 command ping for host X.2.
3) Perform on host A.2 command ping for host X.1.
4) Save the captures of traces in separate files ([Vendor]-DSLAM_SEC_03.txt) and put the file into the corresponding section of the KB.
5) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) Successful performance of command ping on host A.1 for host X.1.
2) Unsuccessful performance of command ping on host A.1 for host X.2.
3) Unsuccessful performance of command ping on host A.2 for host X.1.
4) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme | Image: Network diagram showing Host A.1 and Host A.2 connected to HG1 (modem xDSL). HG1 is connected via PVC 0/35 to Port 1 of a DSLAM. Port 1 is connected via S-VID '1' to an Ethernet switch. Host X.1 and Host X.2 are connected to the Ethernet switch via S-VID '1'. The DSLAM has a 'User port #1' with 'Activated function of filtration on MAC-address'.
|
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_SEC_04 |
+| Test name | Determination of duplicated users MAC-addresses |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of detecting the duplicated users MAC-addresses and the subsequent mechanism for resolution of the given situation |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2.
6) Configure for host B.1 MAC-address similar to that is used by host A.1.
7) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation.
8) HG1 and HG2 equipment works in a bridged mode (function of local DHCP server is disconnected).
9) IP-addresses for hosts A.1, B.1 and X.1 are configured manually (statically) and should be from one IP subnetwork.
10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment. |
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
12) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
13) On the DSLAM/MSAN equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through users ports No. 1 and No. 2.
14) Further adjustment of equipment should be provided according to one of the following configurations.
Configuration 1
In case of detection of duplicated MAC-addresses work of all users having identical MAC-addresses is permitted.
Configuration 2
In case of detection of duplicated MAC addresses, one of the users with duplicated MAC addresses is blocked.
Configuration 3
In case of detection of duplicated MAC-addresses refusal of service should be given to both users with the duplicated MAC-addresses.
|
+| Test procedure | 1) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 1).
2) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 2).
3) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 3).
4) Save the captures of traces in separate files ([Vendor]-DSLAM_SEC_04.txt) and put the file into the corresponding section of the KB.
5) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) In case of configuration 1:
- – command ping, performed on host A.1 in direction to host X.1, passes;
- – command ping, performed on host B.1 in direction to host X.1, passes.
2) In case of a configuration 2:
- – command ping, performed on host A.1 in direction to host X.1, passes;
- – command ping, performed on host B.1 in direction to host X.1, does not pass.
3) In case of configuration 3:
- – command ping, performed on host A.1 in direction to host X.1, does not pass;
- – command ping, performed on host B.1 in direction to host X.1, does not pass.
4) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+| | |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test scheme
| graph LR HA1[Host A.1
IP: xxxxx] --- HG1["HG1
(modem xDSL)"] HB1[Host B.1
IP: xxxxx
MAC Address Spoofing] --- HG2["HG2
(modem xDSL)"] HG1 -- "PVC 0/35" --- DSLAM HG2 -- "PVC 0/35" --- DSLAM subgraph DSLAM P1[Port 1] P2[Port 2] end DSLAM -- "S-VID '1'" --- ES[Ethernet switch] HX1[Host X.1
IP: xxxxx] -- "S-VID '1'" --- ES
|
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Test scheme diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 modems respectively. HG1 and HG2 are connected to a DSLAM via PVC 0/35. The DSLAM is connected to an Ethernet switch via S-VID '1'. Host X.1 is connected to the Ethernet switch via S-VID '1'.
+
+##### 6.3.1.1.4 Check of functions of identification of subscriber lines
+
+| | |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_LID_01 |
+| Test name | Support of DHCP Option 82 |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of functioning as DHCP Relay Agent second level and maintenance of DHCP clients identification connection points using an information option (an option 82) |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
- 4) Host A.1 is connected to home gateway HG1.
- 5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
- 6) Host A.1 uses IPoE sessions. IP-address for host A.1 is defined dynamically using allocated DHCP server connected to the Ethernet switch. DHCP server supports option 82.
- 7) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
- 8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
- 9) Router providing functionality (full) of DHCP Relay Agent should be connected to the Ethernet switch equipment.
- 10) DSLAM/MSAN equipment works as DHCP Relay Agent second level.
- 11) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: bootp.
|
+| Test procedure | - 1) Initiate on host A.1 an establishment of IPoE session (provide transfer of broadcasting DHCP request from host A.1).
- 2) Save the captures of traces in separate files ([Vendor]-DSLAM_LID_01.txt) and put the file into the corresponding section of the KB.
- 3) Fill in a daily report form with the testing results and save it in the KB.
|
+
+| | |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expected result | 1) Using information option of DHCP protocol (option 82) DSLAM/MSAN equipment has definitely identified to which client initiating DHCP request user line is connected within network of broadband access.
2) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme |
graph LR HostA1[Host A.1
IP: x.x.x.x
client DHCP] -- IPoE --> HG1[HG1
modem xDSL] HG1 -- "IPoE (PVC 0/35)" --> DSLAM[DSLAM
Layer 2 DHCP Relay Agent
Port 1] DSLAM --- Switch[Ethernet switch] Switch --- Server[Server DHCP] Switch --- Relay[DHCP Relay Agent
full relay agent]
|
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_LID_02 |
+| Test name | PPPoE functions Intermediate Agent support |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of functioning as PPPoE Intermediate Agent for maintenance of user lines identification |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
- 4) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
- 5) One virtual channel (PVC X1/Y1) used for the transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
- 6) Host A.1 is connected to home gateway HG1.
- 7) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
- 8) Host A.1 uses PPPoE sessions. IP-address for host A.1 is defined dynamically using allocated PPPoE server connected to the Ethernet switch.
- 9) Router providing functionality of PPPoE sessions termination is connected to the Ethernet switch equipment.
- 10) DSLAM/MSAN equipment works as PPPoE Intermediate Agent.
- 11) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed.
|
+
+| | |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | 1) Initiate on host A.1 establishment of PPPoE session (to provide PPPoE Discovery message transfer from host A.1).
2) Save the captures of traces in separate files ([Vendor]-DSLAM_LID_02.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) The DSLAM/MSAN equipment adds PPPoE-TAG tag into the PPPoE Discovery packages (PADI, PADR) transferred upstream.
2) The given tag allows to definitely identify user line on which package PPPoE, and also specify user who has transferred the given message: - – "Agent Circuit ID" option should identify definitely DSLAM/MSAN equipment within network of user's access, and also logic port of DSLAM/MSAN equipment through which package PPPoE has been received;
- – "Agent Remote ID" option should identify definitely user connected with corresponding logic port of DSLAM/MSAN equipment through whom PPPoE package has been received.
3) The DSLAM/MSAN equipment has not changed the initial MAC-addresses of source and destination in the PPPoE Discovery packages transferred upstream.
4) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme |
graph LR HostA1[Host A.1
IP: xxxxx
(client PPPoE)] -- PPPoE --> HG1["HG1
(modem xDSL)"] HG1 -- "PPPoE (PVC0/35)" --> DSLAM["DSLAM/MSAN
PPPoE Intermediate Agent
Port 1"] DSLAM --> Switch[Ethernet switch] Switch --> Termination[PPPoE Termination] Switch --> Server["Server PPPoE"]
|
+
+##### 6.3.1.1.5 Check of functions of management, monitoring and statistics gathering
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_MNG_01 |
+| Test name | Equipment monitoring by SNMP protocol |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility for remote monitoring by means of control system using SNMP protocol |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user's ports on the DSLAM/MSAN equipment (two user lines) have to be used. On the user side home gateways equipment should be connected to network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2. |
+
+| | |
+|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 6) HG1 and HG2 equipment work in a bridged mode (function of local DHCP server is disconnected).
7) IP-addresses for A.1 and B.1 hosts are configured manually.
8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
11) Host which functions as remote workstation of the control system is connected to the Ethernet switch. On the given host SNMP software is established. IP-address for specified host should be configured manually and there should be from the same subnetwork, as IP-address of DSLAM/MSAN equipment used for interaction with control system.
12) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: SNMP.
|
+| Test procedure | 1) Initiate remote monitoring of DSLAM/MSAN equipment on host, carrying out functions of workstation of a control system.
2) Provide appearance of emergency and other non-standard situations on the DSLAM/MSAN equipment. Also it is necessary to simulate problems with powering (transition to the reserve block, return to mainframe), problems with interfaces (refusal of physical/channel level), connection of remote users to DSLAM/MSAN equipment on Telnet/SSH/SNMP, change of equipment configuration on Telnet/SSH/SNMP and other events.
3) Save the captures of traces in separate files ([Vendor]-DSLAM_MNG_01.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) During the process of monitoring, DSLAM/MSAN equipment gives the adequate information on condition of interfaces, operative memory and central processor.
2) The DSLAM/MSAN equipment provides transfer of adequate SNMP traps/informs messages in case of emergencies occurrence.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme |
graph LR A1[Host A.1
IP: xxxxx] --- HG1["HG1
(modem xDSL)"] B1[Host B.1
IP: xxxxx] --- HG2["HG2
(modem xDSL)"] HG1 -- "PVC 0/35" --> DSLAM["DSLAM
Port 1"] HG2 -- "PVC 0/35" --> DSLAM["DSLAM
Port 2"] DSLAM --- ES["Ethernet switch"] ES --- RemoteCLI["Remote CLI
IP: xxxxx"] RemoteCLI -.-> SNMP DSLAM
|
+
+##### 6.3.1.1.6 Check of functions of Multicast mode support
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_MC_01 |
+| Test name | Connection of several users to one multicasting group |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility to simultaneously connect several users to one multicasting group without subsequent load increase at network interfaces of DSLAM/MSAN equipment |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, three user ports on the DSLAM/MSAN equipment (three user lines) have to be used. On the user side, home gateway equipment has to be connected to network terminations of user lines (HG1 equipment, HG2 and HG3, accordingly).
- 4) Host A.1 is connected to home gateway HG1.
- 5) Host B.1 is connected to home gateway HG2.
- 6) Host C.1 is connected to home gateway HG3.
- 7) HG1 equipment, HG2 and HG3 work in the bridged mode (function of local DHCP server is disconnected).
- 8) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
- 9) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG2 equipment.
- 10) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG3 equipment.
- 11) On hosts A.1, B.1 and C.1, IP STB software should be used. Hosts A.1, B.1 and C.1 are IGMP hosts. IP-addresses for hosts A.1, B.1 and C.1 are configured manually.
- 12) Hosts A.1, B.1 and C.1 use IPoE sessions.
- 13) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
- 14) Router equipment which functions as an IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM-SSM protocol is used.
- 15) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
- 16) DSLAM/MSAN equipment during processing of IGMP messages, works in the transparent IGMP Snooping mode.
- 17) On the DSLAM/MSAN equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the DSLAM/MSAN equipment should be configured the possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from users IP-STB equipment.
- 18) Perform on the analyser of IP protocols for the corresponding interface, and set the following filter on protocols: IGMP.
|
+
+| | |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | 1) Hosts A.1, B.1 and C.1 should initiate IPoE sessions, transfer IGMP Membership Report messages and, thus, should consistently connect to the same multicasting group (observe one video channel).
2) Save the captures of traces in separate files ([Vendor]-DSLAM_MC_01.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) All users have connections to the same multicasting group (observe one video channel).
2) During consecutive connections of hosts B.1 and C.1, there is no additional load on network interfaces of DSLAM/MSAN equipment.
3) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme | Image: Network diagram for Test scheme. Three hosts (Host A.1, Host B.1, Host C.1) are connected to three separate home gateways (HG1, HG2, HG3). Each host is an IPoE client with an IP address (IP:xxx.x). Each gateway is a modemxDSL unit. Each gateway is connected to a central DSLAM via a PVC035(IPoE) channel. The DSLAM has three ports (Port 1, Port 2, Port 3) corresponding to the three gateways. The DSLAM is configured for IGMP transparent snooping. The DSLAM is connected to an Ethernet switch via a MG-VLAN(S-VID 1) channel. The Ethernet switch is connected to a video server (HostX.1) with IP:xx.xx. The Ethernet switch is also connected to an IGMP router (PIM-SSM).
|
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_MC_02 |
+| Test name | Restriction of channel numbers which are simultaneously observed by the user |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of multicasting groups total number restriction to which one user simultaneously can be connected |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side, home gateway equipment (HG1 equipment) should be connected to network termination of user line.
4) Hosts A.1, A.2 and A.3 are connected to home gateway HG1.
5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected). HG1 equipment should support the IGMP Snooping function.
6) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on HG1 equipment.
7) On hosts A.1, A.2 and A.3 IP STB software should be used. Hosts A.1, A.2 and A.3 are IGMP hosts. IP-addresses for hosts A.1, A.2 and A.3 are configured manually.
8) Hosts A.1, A.2 and A.3 use IPoE sessions. |
+
+| | |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 9) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
10) Router equipment performing functions of an IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM SSM protocol is used.
11) One virtual channel (PVC X1/Y1) used for transfer of all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
12) DSLAM/MSAN equipment during processing of IGMP messages works in the transparent IGMP Snooping mode.
13) On the DSLAM/MSAN equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the DSLAM/MSAN equipment there should be configured a possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from IP-STB equipment of users.
14) On the DSLAM/MSAN equipment there should be configured for user port No. 1 restriction on total number of multicasting groups to which the given user can be connected. Maximum number of multicasting groups for the given user should be equal to 2.
15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.
|
+| Test procedure | 1) Hosts A.1, A.2 and A.3 should consistently initiate IPoE sessions and transfer IGMP Membership Report messages, trying to be connected to various multicasting groups.
2) Save the captures of traces in separate files ([Vendor]-DSLAM_MC_02.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) A.1 and A.2 hosts are successfully connected to various multicasting groups.
2) Host A.3 has no connections to new multicasting group.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram for the test scheme. On the left, three Host IP-STBs (Host A.1, Host A.2, Host A.3) are connected to an HG1 (modem xDSL) unit. Each host is labeled with 'IP: xxxxx (IGMP host)'. The HG1 unit is connected via a 'PVC 0/35 (IPoE)' line to a DSLAM unit. The DSLAM unit has 'User port #1 Max two groups' and 'Port 1'. A dashed line labeled 'MC-VLAN (S/VID 1)' connects Port 1 of the DSLAM to an Ethernet switch. On the right, Host X.1 (video server) with 'IP: xxxxx' is connected to the Ethernet switch. Below the Ethernet switch is an IGMP router labeled 'PIM-SSM'.
|
+
+| | |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSLAM_MC_03 |
+| Test name | Restriction of the multicasting groups list accessible to the user |
+| Test purpose | Check if the DSLAM/MSAN equipment has the possibility of restriction of the multicasting groups list accessible to the specified user |
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side, home gateway equipment (HG1 equipment) should be connected to network termination of user line.
4) Host A.1 is connected to home gateway HG1.
5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
6) On HG1 equipment, one virtual channel (PVC X1/Y1) for carrying out of all traffic types (in case of ATM transport use on UNI interface) is configured.
7) On host A.1, IP-STB software should be used. Host A.1 should be IGMP host. IP-address for host A.1 should be configured manually.
8) Host A.1 uses IPoE sessions.
9) Host X.1 is connected to the Ethernet switch which has implemented functions of the DSLAM/MSAN traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
10) Router equipment performing functions of an IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM-SSM protocol is used.
11) One virtual channel (PVC X1/Y1) used to transfer all types of traffic (in case of ATM transport use on UNI interface) is configured on the DSLAM/MSAN equipment.
12) DSLAM/MSAN equipment during processing of IGMP messages functions in the transparent IGMP Snooping mode.
13) On the DSLAM/MSAN equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the DSLAM/MSAN equipment there should be configured the possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from IP-STB equipment of users.
14) On the DSLAM/MSAN equipment there should be configured for user port No. 1 the multicasting groups list accessible to user.
15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP. |
+| Test procedure | 1) Host A.1 should initiate IPoE session and transfer IGMP Membership Report messages, trying to be consistently connected to various multicasting groups, matching the list of resolved groups, and not matching the given list.
2) Save the captures of traces in separate files ([Vendor]-DSLAM_MC_03.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) Host A.1 has been successfully connected to various multicasting groups matching list of groups, resolved for user port No. 1.
2) Host A.1 has no connections to any of multicasting groups which are not matching the list of groups, resolved for user port No. 1.
3) The daily report form has been saved in the corresponding section of KB. |
+
+
+
+| | |
+|---------------------------|--|
+| Test scheme
| |
+|---------------------------|--|
+
+Network diagram showing Host A.1 (IP-STB) connected to HG1 (modemxDSL), which is connected to DSLAM via PVC 0/35 (IPoE). DSLAM Port 1 is connected via MC-VLAN (S-VID 1) to an Ethernet switch. Host X.1 (video server) is connected to the Ethernet switch. The Ethernet switch is connected to an IGMP router PIM-SSM. IP addresses are indicated for Host A.1 (IP:xxxxx (IGMP host)) and Host X.1 (IP:xxxxx).
+
+#### 6.3.1.2 Check of EAS equipment functionality
+
+##### 6.3.1.2.1 Check of functions of VLAN tags processing
+
+| | |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_VLAN_01 |
+| Test name | Configuration of S-VLAN for Untagged architecture (model N:1+1:1) |
+| Test purpose | Check if the EAS has the possibility to assign the S VLAN (S-VID) identifier to the Ethernet frames,, which are transferred upstream using the Untagged model on UNI interface |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) have to be used. On the user side, the home gateway equipment has to be connected to the network terminations of user lines (HG1 and HG2, accordingly).
- 4) A.1 and A.2 hosts are connected to the home gateway equipment HG1.
- 5) B.1 and B.2 hosts are connected to the home gateway equipment HG2.
- 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
- 7) A.1 and B.1 hosts use PPPoE sessions.
- 8) A.2 and B.2 hosts use IPoE sessions.
- 9) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
- 11) For termination of PPPoE sessions from A.1 and B.1 hosts the external router should be connected to the Ethernet switch equipment.
- 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
- 13) On hosts A.2, B.2 and X.2 used IP-address from one IP subnetwork.
|
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 14) On the EAS equipment possibility of assignment of identifiers S-VID to Ethernet frames transferred upstream, depending on value of field Ethertype and number of port of the user is configured. Following options are configured:
- – assignment of "S-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1) with the Ethertype value 0x8863 or 0x8864;
- – assignment of "S-VID"=2 to Ethernet frames which are transferred from HG2 equipment (user port No. 2) with the Ethertype value 0x8863 or 0x8864;
- – assignment of "S-VID"=3 frames to Ethernet transferred from HG1 and HG2 equipment (any user port) with the Ethertype value 0x0800.
15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.1.
- 3) Perform traffic exchange between hosts A.2 and X.2.
- 4) Perform traffic exchange between hosts B.2 and X.2.
- 5) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_01.txt) and put the file into the corresponding section of the KB.
- 6) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) The EAS equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
- 2) The EAS equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
- 3) The EAS equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
- 4) The EAS equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
- 5) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing the test setup. Hosts A.1, A.2, B.1, and B.2 are connected to HG1 and HG2 (Ethernet WAN) units. HG1 and HG2 are connected to the EAS (Ethernet Aggregation Switch) via Port 1 and Port 2 respectively. The EAS is connected to an Ethernet switch via Port 3. The Ethernet switch is connected to Host X.1, Host X.2, and a Server DHCP. A Protocol analyzer is connected to the EAS. The diagram also shows IP addresses (IP:xxxx) and protocols (PPPoE, IPoE, DHCP) for the hosts and units.
|
+
+| | |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_VLAN_02 |
+| Test name | Configuration of S-VLAN for VLAN tagged architecture (model N:1+1:1) |
+| Test purpose | Check if the EAS has the possibility to assign the S VLAN (S VID) identifier to the Ethernet frames, which are transferred upstream using the VLAN tagged model on UNI interface |
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) have to be used. On the user side the home gateways equipment should be connected to the network terminations of user lines (HG1 and HG2, accordingly).
- 4) A.1 and A.2 hosts are connected to the home gateway equipment HG1.
- 5) B.1 and B.2 hosts are connected to the home gateway equipment HG2.
- 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
- 7) A.1 and B.1 hosts use PPPoE sessions.
- 8) A.2 and B.2 hosts use IPoE sessions.
- 9) HG1 and HG2 equipment works in a bridged mode (function of local DHCP server is disconnected).
- 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually.
- 11) For termination of PPPoE sessions from A.1 and B.1 hosts, the external router should be connected to the Ethernet switch equipment.
- 12) IP-addresses for hosts A.2, B.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
- 13) On hosts A.2, B.2 and X.2 are used IP-addresses from one IP subnetwork.
- 14) HG1 equipment supports the function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured as follows: there is assigned VLAN tag "C-VID"=1 for PPPoE sessions connected with host A.1, and VLAN tag "C-VID"=2 for IPoE sessions connected with host A.2.
- 15) HG2 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG2 equipment is configured as follows: there is assigned "C-VID"=1 for PPPoE sessions connected with host B.1, and "C-VID"=2 for IPoE sessions connected with host B.2.
- 16) The possibility of use VLAN identifiers for users' ports No. 1 and No. 2 is configured on the EAS equipment. The VLAN Membership List is configured on the EAS equipment including list of C-VID values resolved for each of users ports. For users ports No. 1 and No. 2 there should be resolved values "C-VID"=1 and "C-VID"=2.
- 17) On the EAS equipment there is a possibility to assign S VID identifiers for Ethernet frames which are transferred upstream depending on value of VLAN identifier in initial IEEE 802.1Q tag and user port number. The following configuration of VLAN translation table should be done:
- – assignment of "S-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1) and have "C-VID"=1 in IEEE 802.1Q tag;
- – assignment of "S-VID"=2 to Ethernet frames which are transferred from HG2 equipment (user port No. 2) and have "C-VID"=1 in IEEE 802.1Q tag;
- – assignment of "S-VID"=3 to Ethernet frames which are transferred from HG2 equipment (any user port) and have "C-VID"=2 in IEEE 802.1Q tag.
- 18) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.1.
- 3) Perform traffic exchange between hosts A.2 and X.2.
- 4) Perform traffic exchange between hosts B.2 and X.2.
- 5) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_02.txt) and put the file into the corresponding section of the KB.
- 6) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) The EAS equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to the PPPoE session of host A.1.
- 2) The EAS equipment has assigned the identifier "S VID" =2 for Ethernet frames which are transferred upstream and related to the PPPoE session of host B.1.
- 3) The EAS equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2.
- 4) The EAS equipment has assigned the identifier "S VID" =3 for Ethernet frames which are transferred upstream and related to IPoE session of host B.2.
- 5) The EAS equipment deletes the Ethernet frames which contain C-VID identifiers in IEEE 802.1Q tag not matching VLAN Membership List.
- 6) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing the test scheme. Hosts A.1 and A.2 are connected to HG1 (Ethernet WAN). Hosts B.1 and B.2 are connected to HG2 (Ethernet WAN). Both HG1 and HG2 are connected to the EAS (Ethernet Aggregation Switch) via Port 1 and Port 2 respectively. The EAS is connected to a Protocol analyzer and an Ethernet switch. The Ethernet switch is connected to Host X.1 and Host X.2 (both with IP: xxx.x (DHCP)), a Sever DHCP, and a PPPoE Termination/DHCP relay agent. The diagram shows various VLAN tags (C-VID, S-VID) being applied to frames at different points in the network.
|
+| Test number | EAS_VLAN_03 |
+| Test name | Configuration of S-VLAN/C-VLAN stack (QinQ) |
+| Test purpose | Check if the EAS has the possibility to assign the VLAN tag pair (S-Tag/C-Tag) to the Ethernet frame, which are transferred upstream |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) have to be used. On the user side the home gateways equipment should be connected to the network terminations of user lines (HG1 and HG2, accordingly).
- 4) Host A.1 is connected to home gateway HG1.
- 5) Host B.1 is connected to home gateway HG2.
- 6) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
- 7) A.1 and B.1 hosts use IPoE sessions.
|
+
+| | |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
9) IP-addresses for hosts A.1, B.1, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
10) IP-addresses from one IP subnetwork are used on the hosts A.1, B.1 and X.2.
11) On the EAS equipment there is configured the possibility to assign VLAN tag pair (S-Tag/C-Tag) for Ethernet frames which are transferred upstream. The S-VID value identifies EAS equipment (i.e., value S VID is identical for all users ports). C-VID value identifies number of user port on which Ethernet frame has arrived. The following configuration should be done:
- – assignment of "S-VID"=1, "C-VID"=1 to Ethernet frames which are transferred from HG1 equipment (user port No. 1);
- – assignment of "S-VID"=1, "C-VID"=2 to Ethernet frames which are transferred from HG1 equipment (user port No. 2)
12) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | 1) Perform traffic exchange between hosts A.1 and X.1.
2) Perform traffic exchange between hosts B.1 and X.2.
3) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_03.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) The EAS equipment has assigned the identifier "S-VID"=1, "C-VID"=1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1.
2) The EAS equipment has assigned the identifier "S-VID"=1, "C-VID"=2 for Ethernet frames which are transferred upstream and related to PPPoE session of host B.1.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme |
|
+
+| | |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_VLAN_04 |
+| Test name | Configuration of TLS user port |
+| Test purpose | Check if the EAS has the possibility of TLS user port configuration providing transparent transfer of initial IEEE 802.1Q tags set by users over the network. |
+
+| | |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) have to be used. On the user side to the network termination of given user line there should be a connection from home gateway (business) (HG1 equipment).
4) Hosts A.1 and A.2 are connected to HG1 equipment.
5) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
6) Host A.1 uses PPPoE sessions.
7) Host A.2 uses IPoE sessions.
8) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
9) IP-address for host A.1 is assigned dynamically with allocated PPPoE server or are configured manually.
10) For termination of PPPoE sessions from host A.1, the external router should be connected to the Ethernet switch equipment.
11) IP-addresses for hosts A.2, X.1 and X.2 are assigned dynamically with the allocated DHCP server or are configured manually.
12) HG1 equipment supports function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured as follows: there is assigned VLAN tag "C-VID"=111 for PPPoE sessions connected with host A.1, and VLAN tag "C-VID"=222 for IPoE sessions connected with host A.2.
13) User port No. 1 of EAS equipment is configured as TLS port providing transparent transfer of VLAN tags assigned on user equipment.
14) VLAN Membership List is configured on the EAS equipment for user port No. 1. The VLAN Membership List should contain the list of C-VID identifiers which have not been related to TLS traffic transferred through user port No. 1 in an upstream direction. This list should contain "C-VID"=111. All Ethernet frames transferred upstream through user port No. 1 and not having "C-VID"=111, should be processed as TLS traffic.
15) On the EAS equipment should be configured the VLAN translation table according to which the Ethernet frames transferred upstream and having initial identifier "C-VID"=111 (matching VLAN Membership List) should get "S-VID"=1 identifier. Initial identifier C-VID in this case should be deleted.
16) On the EAS equipment there is a possibility to assign TLS "S-VID"=100 identifier for Ethernet frames which are transferred upstream through user port No. 1 and having initial IEEE 802.1Q tag, not matching VLAN Membership List. Thus initial IEEE 802.1Q tag, received from the user, remains as enclosed C-Tag.
17) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP. |
+| Test procedure | 1) Perform traffic exchange between hosts A.1 and X.1.
2) Perform traffic exchange between hosts A.2 and X.2.
3) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_04.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. |
+
+| | |
+|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expected result | 1) The EAS equipment has assigned the identifier "S VID" =1 for Ethernet frames which are transferred upstream and related to PPPoE session of host A.1. Thus initial IEEE 802.1Q tag (including "C-VID"=111), received from the user, has been deleted.
2) The EAS equipment has assigned the identifier "S VID" =100 for Ethernet frames which are transferred upstream and related to IPoE session of host A.2. Thus initial IEEE 802.1Q tag (including "C-VID"=222), received from the user, has remained as an enclosed C-Tag (having "C-VID"=222).
3) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme | Image: Network diagram showing Host A.1 and Host A.2 connected to HG1 (Ethernet WAN). HG1 is connected to EAS via Port 1. EAS has a User port#1 - TLS with VLAN Membership List (C-VID=111) and VLAN translation table (C-VID=111 -> S-VID=1). EAS is connected to an Ethernet switch via Port 2. Host X.1 and Host X.2 are connected to the switch. A PPPoE Termination, DHCP relay agent is connected to the switch. The switch is also connected to a Server DHCP. Labels on the diagram include: Host A.1 (IP: x.x.x.x (PPPoE)), Host A.2 (IP: x.x.x.x (DHCP)), HG1 (Ethernet WAN), 802.1Q Tag '111' (PPPoE), 802.1Q Tag '222' (IPoE), EAS, Port 1, Port 2, TLS, S-VID '1', S-VID '100', C-VID '222', Host X.1 (IP: x.x.x.x (DHCP)), Host X.2 (IP: x.x.x.x (DHCP)), Ethernet switch, Server DHCP, PPPoE Termination, DHCP relay agent.
|
+
+| | |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_VLAN_05 |
+| Test name | Configuration of admissible list of Ethernet frame types |
+| Test purpose | Check if the EAS has the possibility of admissible list of Ethernet frame types configuration for certain user port (for the upstream transfer). |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side the equipment of a home gateway (HG1 equipment) should be connected to the network termination of the given user line.
4) Host A.1 is connected to HG1 equipment.
5) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
6) Host A.1 uses IPoE sessions.
7) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
8) IP-addresses for hosts A.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually.
9) On the EAS equipment there is a possibility to assign "S-VID"=1 identifiers to any Ethernet frames transferred upstream through user port No. 1.
10) Further adjustment of equipment should be provided according to one of the following configurations.
Configuration 1
On HG1 equipment there should be a disconnected function of VLAN tags assignment for Ethernet frames transferred upstream. Host A.1 also should not assign VLAN tags for Ethernet frames transferred upstream. |
+
+| | |
+|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "untagged or priority tagged frames" for user port No. 1.
Configuration 2
Configuration of HG1 equipment is same as in Configuration 1.
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "VLAN tagged frames" for user port No. 1.
Configuration 3
Configuration of HG1 equipment is the same as in Configuration 1.
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "admit all" for user port No. 1.
Configuration 4
Activate on HG1 equipment function of VLAN tags assignment to Ethernet frames transferred upstream. HG1 equipment should be configured to assign VLAN "C-VID"=1 identifier for IPoE sessions related with host A.1
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "untagged or priority tagged frames" for user port No. 1.
Configuration 5
Configuration of HG1 equipment is same as in Configuration 4.
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "VLAN tagged frames" for user port No. 1.
Configuration 6
Configuration of HG1 equipment is the same as in Configuration 4.
On the EAS equipment during configuration of admissible Ethernet frames types list there should be specified value: "admit all" for user port No. 1.
11) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | - 1) Using Configuration 1 perform on host A.1 command ping for host X.1.
- 2) Using Configuration 2 perform on host A.1 command ping for host X.1.
- 3) Using Configuration 3 perform on host A.1 command ping for host X.1.
- 4) Using Configuration 4 perform on host A.1 command ping for host X.1.
- 5) Using Configuration 5 perform on host A.1 command ping for host X.1.
- 6) Using Configuration 6 perform on host A.1 command ping for host X.1.
- 7) Save the captures of traces in separate files ([Vendor]-EAS_VLAN_05.txt) and put the file into the corresponding section of the KB.
- 8) Fill in a daily report form with the testing results and save it in the KB.
|
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expected result | 1) Successful performance of command ping according to step 1 of test procedure.
2) Unsuccessful performance of command ping according to step 2 of test procedure.
3) Successful performance of command ping according to step 3 of test procedure.
4) Unsuccessful performance of command ping according to step 4 of test procedure.
5) Successful performance of command ping according to step 5 of test procedure.
6) Successful performance of command ping according to step 6 of test procedure.
7) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme | Image: Network diagram for the test scheme. Host A.1 (IP: x.xxx (DHCP)) is connected via PoE to HG1 (Ethernet WAN). HG1 is connected to the EAS (Ethernet Aggregation Switch) via Port 1. The EAS is connected to an Ethernet switch via Port 1, labeled s-VID '1'. Host X.1 (IP: x.xxx (DHCP)) is connected to the Ethernet switch. A DHCP relay agent is connected to the Ethernet switch, which is also connected to a Server DHCP.
|
+
+##### 6.3.1.2.2 Check of QoS functions
+
+| | |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_QOS_01 |
+| Test name | Marks of priority bits during processing of Ethernet frames which are not containing VLAN tags |
+| Test purpose | Check if the EAS equipment has the possibility of priority bits marking in Ethernet frames which are transferred upstream and not containing IEEE 802.1Q tags, assigned by user equipment |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user ports on the EAS equipment (two user lines) has to be used. On the user side the home gateway equipment has to be connected to the network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2.
6) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
7) A.1 and B.1 hosts use IPoE sessions.
8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
9) IP-addresses for hosts A.1, B.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually. |
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 10) A.1 and B.1 hosts should have possibility of priority assignment to Ethernet frames. A.1 and B.1 hosts should establish priority "6" for all transferred Ethernet frames.
11) HG1 and HG2 equipment should provide transparent translation of Ethernet frames priorities values configured on A.1 and B.1 hosts, accordingly. On HG1 equipment and HG2 there is disconnected the function of IEEE 802.1Q tags assignment to Ethernet frames transferred upstream.
12) On the EAS equipment there should be configured possibility of S-Tag assignment, including identifier "S-VID"=1, to Ethernet frames transferred upstream through any of users ports. In this case the general VLAN (N:1) should be configured for all users ports.
13) On the EAS equipment there should be configured user port No. 1 with the possibility of copying the priority value of Ethernet frame received from HG1 equipment, into the value of S-Tag priority.
14) On the EAS equipment should be configured user port No. 2 with the possibility to identify the value of S-Tag priority for Ethernet frames transferred upstream through given port on basis of "Ingress to Egress" policy. In this case as criteria for definition of S-Tag priority the following parameters should be used:
- – value of user port number (physical or logic);
- – value of Ethertype field in the Ethernet frame;
- – value of initial Ethernet frame priority received from HG2 equipment.
15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.1.
- 3) During traffic exchange between hosts B.1 and X.1 perform transfer of ARP message from host B.1 (for this purpose it is necessary to clear contents of ARP table on host B.1).
- 4) Save the captures of traces in separate files ([Vendor]-EAS_QOS_01.txt) and put the file into the corresponding section of the KB.
- 5) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) S-Tag priority for Ethernet frames transferred upstream through user port No. 1 equals to "6".
- 2) S-Tag priority for Ethernet frames transferred upstream through user port No. 2 has been established according to policy defined on the EAS equipment for the given port.
- 3) Policy for different S-Tag definition criteria has been correctly performed.
- 4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Test scheme diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 (Ethernet WAN) respectively. HG1 and HG2 are connected to Port 1 and Port 2 of an EAS device. Port 1 is labeled 'Copying of value of priority' and Port 2 is labeled 'Applying of policy Ingress to Egress'. The EAS device is connected to an Ethernet switch via Port 3, labeled 'S-Tag (S-VID 1*priority)'. Host X.1 is connected to the Ethernet switch via Port 4, labeled 'IP: xxxxx (DHCP)'. The Ethernet switch is also connected to a Server DHCP and a DHCP relay agent.
graph LR HA1[Host A.1
IP: xxxxx (DHCP)] -- "IPoE" --> HG1["HG1
(Ethernet WAN)"] HB1[Host B.1
IP: xxxxx (DHCP)] -- "IPoE" --> HG2["HG2
(Ethernet WAN)"] HG1 -- "Priority tagged frames/No VLAN tag" --> EAS["EAS"] HG2 -- "Priority tagged frames/No VLAN tag" --> EAS EAS -- "Port 1: Copying of value of priority" --> ES["Ethernet switch"] EAS -- "Port 2: Applying of policy Ingress to Egress" --> ES EAS -- "Port 3: S-Tag (S-VID 1*priority)" --> ES HX1[Host X.1
IP: xxxxx (DHCP)] -- "IP: xxxxx (DHCP)" --> ES ES --- SDHCP[Server DHCP] ES --- DRA[DHCP relay agent]
|
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_QOS_02 |
+| Test name | Marks of priority bits during processing of Ethernet frames containing VLAN tags |
+| Test purpose | Check if the EAS equipment has the possibility of priority bits marking in Ethernet frames which are transferred upstream and containing IEEE 802.1Q tags, assigned by user equipment |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) has to be used. On the user side the home gateway equipment has to be connected to the network terminations of user lines (HG1 and HG2, accordingly).
- 4) Host A.1 is connected to home gateway HG1.
- 5) Host B.1 is connected to home gateway HG2.
- 6) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
- 7) A.1 and B.1 hosts use IPoE sessions.
- 8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 9) IP-addresses for hosts A.1, B.1 and X.1 are assigned dynamically with the allocated DHCP server or are configured manually.
- 10) HG1 equipment should support the function of VLAN tags assignment according to IEEE 802.1Q standard. HG1 equipment is configured to assign IEEE 802.1Q tag, including "C-VID" =1 and priority value equal to "6" for all frames transferred.
- 11) HG2 equipment should support the function of VLAN tags assignment according to IEEE 802.1Q standard. HG2 equipment is configured to assign IEEE 802.1Q tag, including "C-VID" =1 and priority value equal to "6" for all frames transferred.
- 12) On the EAS equipment should be configured the possibility of IEEE 802.1Q tags usage on users ports No. 1 and No. 2. The VLAN Membership List is configured on the EAS equipment including list of C-VID values resolved for each of users ports. For users ports No. 1 and No. 2 there should be resolved value "C-VID" =1.
- 13) On the EAS equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through any of users ports. In this case, the general S-VLAN (N:1) should be configured for all users ports.
- 14) On the EAS equipment there should be configured user port No. 1 with the possibility of copying the priority value from IEEE 802.1Q tag, received from HG1 equipment, into the S-Tag priority value.
- 15) On the EAS equipment should be configured user port No. 2 with the possibility to identify the value of S-Tag priority for Ethernet frames transferred upstream through given port on basis of "Ingress to Egress" policy. In this case as criteria for definition of S-Tag priority the following parameters should be used:
- – value of user's port number (physical);
- – C-VID value in the initial Ethernet frame;
- – C-Tag priority value in the initial Ethernet frame.
- 16) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ICMP ARP.
|
+
+| | |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.1.
- 3) Save the captures of traces in separate files ([Vendor]-EAS_QOS_02.txt) and put the file into the corresponding section of the KB.
- 4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) S-Tag priority for Ethernet frames transferred upstream through user port No. 1 equals to "6".
- 2) S-Tag priority for Ethernet frames transferred upstream through user port No. 2 has been established according to policy defined on the EAS equipment for the given port.
- 3) Policy for different S-Tag definition criteria has been correctly performed.
- 4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing Host A.1 and Host B.1 connected to HG1 and HG2 respectively. HG1 and HG2 are connected to the EAS equipment. Host X.1 is connected to an Ethernet switch, which is connected to a Server DHCP and a DHCP relay agent. The EAS equipment has Port 1 and Port 2. Port 1 is connected to HG1 and Port 2 is connected to HG2. The diagram shows traffic flow from Host A.1 and Host B.1 through HG1 and HG2 to the EAS equipment, and then from the EAS equipment to Host X.1 via the Ethernet switch. The EAS equipment is configured with S-Tag (S-VID '1'+priority) for Port 1 and Port 2. The DHCP relay agent is connected to the Ethernet switch.
|
+
+##### 6.3.1.2.3 Check of security functions
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_SEC_01 |
+| Test name | Blocking of broadcasting packages |
+| Test purpose | Check if the EAS equipment has the possibility of blocking upstream and downstream broadcast messages |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two user ports on the EAS equipment (one user lines) has to be used. On the user side the home gateway equipment has to be connected to the network terminations of user lines (HG1 equipment).
- 4) Host A.1 is connected to home gateway HG1.
- 5) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
- 6) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 7) IP-addresses for hosts A.1 and X.1 are configured manually (statically) and should be from one IP subnetwork.
- 8) On the EAS equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through user port No. 1.
- 9) On the EAS equipment there should be configured blocking of broadcasting packages in an upstream direction for user port No. 1.
- 10) On the EAS equipment there should be configured blocking of broadcasting packages in downstream for "S-VID" =1.
|
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 11) Before beginning of carrying out of test procedure it is necessary to clear contents of ARP tables on hosts A.1 and X.1. |
+| Test procedure | 1) Perform on host A.1 command ping for host X.1.
2) Perform on host X.1 command ping for host A.1.
3) Save the captures of traces in separate files ([Vendor]-EAS_SEC_01.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) Command ping, performed on host A.1 for host X.1 has not passed (broadcasting ARP message transferred by host A.1 has been blocked on the EAS equipment).
2) Command ping, performed on host X.1 for host A.1 has not passed (broadcasting ARP message transferred by host X.1 has been blocked on the EAS equipment).
3) In ARP tables on hosts A.1 and X.1 there are no dynamic records.
4) There is a possibility of broadcasting packages blocking function configuration on the EAS equipment in a downstream. Configuration of the given function is made on VLAN basis.
5) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme | Image: Network diagram for the test scheme. Host A.1 (IP: xxxxx) is connected to HG1 (Ethernet WAN). HG1 is connected via Ethernet to Port 1 of the EAS equipment. The EAS equipment has a function of blocking broadcasting packages activated. Port 1 is connected via S-VID '1' to an Ethernet switch. Host X.1 (IP: xxxxx) is connected to the Ethernet switch.
|
+
+| | |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_SEC_02 |
+| Test name | Restriction of the MAC-addresses table size |
+| Test purpose | Check if the EAS equipment has the possibility of restriction of sources MAC-addresses number connected with one user port |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side the equipment of a home gateway (HG1 equipment) should be connected to the network termination of a user line.
4) Hosts A.1, A.2 and A.3 are connected to home gateway HG1.
5) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
6) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
7) IP-addresses for hosts A.1, A.2, A.3 and X.1 are configured manually (statically) and should be from one IP subnetwork. |
+
+| | |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 8) On the EAS equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through user port No. 1.
9) On the EAS equipment should be configured the maximum number of MAC-addresses of the sources resolved for user port No. 1 equals to 2.
|
+| Test procedure | 1) Perform consecutive connections of hosts A.1, A.2 and A.3.
2) During connection of each host (A.1, A.2, A.3) perform from this host continuous command ping for host X.1.
3) Save the captures of traces in separate files ([Vendor]-EAS_SEC_02.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Successful performance of commands ping from A.1 and A.2 hosts.
2) Unsuccessful performance of commands ping from host A.3.
3) There is a possibility of maximum resolved MAC-addresses number of sources configuration independently for each users ports.
4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram for Test scheme. On the left, three hosts labeled Host A.1, Host A.2, and Host A.3, each with IP: xxxxx, are connected to a central box labeled HG1 (Ethernet WAN). HG1 is connected via an Ethernet cable to a box labeled EAS. The EAS box has a 'User port#1' with a note 'Admissible number of MAC-address of source' and 'Port 1'. A dashed line labeled 'S-VID '1'' connects Port 1 to an 'Ethernet switch' box. Host X.1, with IP: xxxxx, is connected to the Ethernet switch via a cable labeled 'S-VID '1''.
|
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_SEC_03 |
+| Test name | Filtration on MAC-addresses basis |
+| Test purpose | Check if the EAS equipment has the possibility to filter Ethernet frames based on source and destination MAC-addresses. |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side, the equipment of a home gateway (HG1 equipment) should be connected to the network termination of a user line.
4) A.1 and A.2 hosts are connected to home gateway HG1.
5) X.1 and X.2 hosts are connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
6) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
7) IP-addresses for hosts A.1, A.2, X.1 and X.2 are configured manually (statically) and should be from one IP subnetwork. Hosts A.1/A.2 should have possibility to exchange traffic with hosts X.1/X.2 without router.
|
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 8) On the EAS equipment there should be configured S-Tag assignment possibility, including the identifier "S-VID"=1, to Ethernet frames transferred upstream through user port No. 1.
9) On the EAS equipment there should be activated function of Ethernet frames filtration for user port No. 1 MAC-addresses. For the given user port there should be configured barring for access from source with MAC-address of host A.2, and also barring for access to destination with MAC-address of host X.2.
|
+| Test procedure | - 1) Perform on host A.1 a command ping for host X.1.
- 2) Perform on host A.1 a command ping for host X.2.
- 3) Perform on host A.2 a command ping for host X.1.
- 4) Save the captures of traces in separate files ([Vendor]-EAS_SEC_03.txt) and put the file into the corresponding section of the KB.
- 5) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) Successful performance of command ping on host A.1 for host X.1.
- 2) Unsuccessful performance of command ping on host A.1 for host X.2.
- 3) Unsuccessful performance of command ping on host A.2 for host X.1.
- 4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram for test scheme. Host A.1 and Host A.2 are connected to a home gateway labeled HG1 (Ethernet WAN). HG1 is connected via an Ethernet cable to the EAS equipment. The EAS equipment has a 'User port #1' which is activated for MAC address filtration. This port is connected via an S-VID '1' link to an Ethernet switch. Host X.1 and Host X.2 are connected to this switch. All hosts (A.1, A.2, X.1, X.2) are labeled with IP: xxxxx.
|
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_SEC_04 |
+| Test name | Determination of duplicated users MAC-addresses |
+| Test purpose | Check if the EAS equipment has the possibility of detecting duplicated user MAC-addresses and the subsequent mechanism for resolution of the given situation |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, two user ports on the EAS equipment (two user lines) has to be used. On user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
- 4) Host A.1 is connected to home gateway HG1.
- 5) Host B.1 is connected to home gateway HG2.
- 6) Configure for host B.1 MAC-address similar to that is used by host A.1.
- 7) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation.
|
+
+| | |
+|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 8) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
9) IP-addresses for hosts A.1, B.1 and X.1 are configured manually (statically) and should be from one IP subnetwork.
10) On the EAS equipment there should be configured S-Tag assignment possibility, including identifier "S-VID" =1, to Ethernet frames transferred upstream through users ports No. 1 and No. 2.
11) Further adjustment of equipment should be provided according to one of the following configurations.
Configuration 1
In case of detection of duplicated MAC-addresses work of all users having identical MAC-addresses is permitted.
Configuration 2
In case of detection duplicated MAC addresses one of users with duplicated MAC addresses is blocked.
Configuration 3
In case of detection of duplicated MAC-addresses refusal in service should be given to both users with the duplicated MAC-addresses.
|
+| Test procedure | 1) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 1).
2) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 2).
3) Perform on A.1 and B.1 hosts continuous command ping for host X.1 (configuration 3).
4) Save the captures of traces in separate files ([Vendor]-EAS_SEC_04.txt) and put the file into the corresponding section of the KB.
5) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) In case of configuration 1:
- – command ping, performed on host A.1 in direction to host X.1, passes;
- – command ping, performed on host B.1 in direction to host X.1, passes.
2) In case of a configuration 2:
- – command ping, performed on host A.1 in direction to host X.1, passes;
- – command ping, performed on host B.1 in direction to host X.1, does not pass.
3) In case of configuration 3:
- – command ping, performed on host A.1 in direction to host X.1, does not pass;
- – command ping, performed on host B.1 in direction to host X.1, does not pass.
4) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+| | |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test scheme
| graph LR subgraph " " HA1[Host A.1
IP: x.x.x.x] -- Ethernet --- HG1[HG1
(Ethernet WAN)] HB1[Host B.1
IP: x.x.x.x
MAC Address Spoofing] -- Ethernet --- HG2[HG2
(Ethernet WAN)] end HG1 -- Ethernet --- EAS_P1[Port 1] HG2 -- Ethernet --- EAS_P2[Port 2] subgraph EAS EAS_P1 EAS_P2 end EAS_P1 -.-> EAS_OUT EAS_P2 -.-> EAS_OUT EAS_OUT[ ] -- S-VID '1' --- SW[Ethernet switch] SW -- S-VID '1' --- HX1[Host X.1
IP: x.x.x.x]
|
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Test scheme diagram showing network topology for DHCP Option 82 testing. Host A.1 and Host B.1 connect to HG1 and HG2 respectively. These connect to EAS ports 1 and 2. The EAS connects to an Ethernet switch, which also connects to Host X.1.
+
+##### 6.3.1.2.4 Check of functions of identification of subscriber lines
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_LID_01 |
+| Test name | Support of DHCP Option 82 |
+| Test purpose | Check if the EAS equipment has the possibility of functioning as DHCP Relay Agent second level and maintenance of DHCP clients identification connection points using an information option (option 82) |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, one user port on the DSLAM/MSAN equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
- 4) Host A.1 is connected to home gateway HG1.
- 5) HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 6) Host A.1 uses IPoE sessions. IP-address for host A.1 is defined dynamically using allocated DHCP server connected to the Ethernet switch. DHCP server supports option 82.
- 7) Router providing functionality (full) of DHCP Relay Agent should be connected to the Ethernet switch equipment.
- 8) EAS equipment works as DHCP Relay Agent second level.
- 9) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: bootp.
|
+| Test procedure | - 1) Initiate on host A.1 an establishment of IPoE session (provide transfer of broadcasting DHCP request from host A.1).
- 2) Save the captures of traces in separate files ([Vendor]-EAS_LID_01.txt) and put the file into the corresponding section of the KB.
- 3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) Using information option of DHCP protocol (option 82) EAS equipment has definitely identified to which client initiating DHCP request user line is connected within network of broadband access.
- 2) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+| | |
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test scheme
| graph LR HostA1[Host A.1
IP: xxxxx
(client DHCP)] -- IPoE --> HG1[HG1
(Ethernet WAN)] HG1 -- IPoE --> EAS[EAS
Layer 2 DHCP Relay Agent
Port 1] EAS --- ES[Ethernet switch] ES --- DRA[DHCP Relay Agent
(full relay agent)] DRA --- SDHCP[Server DHCP]
|
+|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Network diagram showing the test scheme. Host A.1 (IP: xxxxx (client DHCP)) is connected via IPoE to HG1 (Ethernet WAN). HG1 is connected via IPoE to the EAS (Layer 2 DHCP Relay Agent, Port 1). The EAS is connected to an Ethernet switch. The Ethernet switch is connected to a DHCP Relay Agent (full relay agent). The DHCP Relay Agent is connected to a Server DHCP.
+
+| | |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_LID_02 |
+| Test name | PPPoE functions Intermediate Agent support |
+| Test purpose | Check if the EAS equipment has the possibility of functioning as PPPoE Intermediate Agent for maintenance of user line identification |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
- 4) Host A.1 is connected to home gateway HG1.
- 5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
- 6) Host A.1 uses PPPoE sessions. IP-address for host A.1 is defined dynamically using allocated PPPoE server connected to the Ethernet switch.
- 7) Router providing functionality of PPPoE sessions termination is connected to the Ethernet switch equipment.
- 8) EAS equipment works as PPPoE Intermediate Agent.
- 9) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed.
|
+| Test procedure | - 1) Initiate on host A.1 an establishment of PPPoE session (perform PPPoE Discovery message transfer from host A.1).
- 2) Save the captures of traces in separate files ([Vendor]-EAS_LID_02.txt) and put the file into the corresponding section of the KB.
- 3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) The EAS equipment adds PPPoE-TAG tag into the PPPoE Discovery packages (PADI, PADR) transferred upstream.
- 2) The given tag allows to definitely identify user line on which package PPPoE, and also specify user who has transferred the given message:
- – "Agent Circuit ID" option should identify definitely EAS equipment within network of user's access, and also logic port of EAS equipment through which package PPPoE has been received;
- – "Agent Remote ID" option should identify definitely user connected with corresponding logic port of EAS equipment through whom PPPoE package has been received.
|
+
+| | |
+|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 3) The EAS equipment has not changed the initial MAC-addresses of source and destination in the PPPoE Discovery packages transferred upstream.
4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme |
graph LR HostA1["Host A.1
IP: x.x.x.x
(client PPPoE)"] -- PPPoE --> HG1["HG1
(Ethernet WAN)"] HG1 -- PPPoE --> EAS["EAS
PPPoE Intermediate Agent
Port 1"] EAS --- Switch[Ethernet switch] Switch --- Server[Server PPPoE] Switch --- Term[PPPoE Termination]
|
+
+##### 6.3.1.2.5 Check of functions of management, monitoring and statistics gathering
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_MNG_01 |
+| Test name | Equipment monitoring by SNMP protocol |
+| Test purpose | Check if the EAS equipment has the possibility for remote monitoring by means of control system using SNMP protocol |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, two user's ports on the EAS equipment (two user lines) has to be used. On the user side home gateways equipment should be connected to network terminations of user lines (HG1 and HG2, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2.
6) HG1 and HG2 equipment work in a bridged mode (function of local DHCP server is disconnected).
7) IP-addresses for A.1 and B.1 hosts are configured manually.
8) Host which performs functions of remote workstation of control system is connected to the Ethernet switch. On the given host SNMP software is established. IP-address for specified host should be configured manually and there should be from the same subnetwork, as IP-address of EAS equipment used for interaction with control system.
9) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: SNMP.
|
+| Test procedure | 1) Initiate remote monitoring of EAS equipment on host, carrying out functions of workstation of a control system.
2) Provide appearance of emergency and other non-standard situations on the EAS equipment. Also it is necessary to simulate problems with powering (transition to the reserve block, return to mainframe), problems with interfaces (refusal of physical / channel level), connection of remote users to EAS equipment on Telnet/SSH/SNMP, change of equipment configuration on Telnet/SSH/SNMP and other events.
|
+
+| | |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 3) Save the captures of traces in separate files ([Vendor]-EAS_MNG_01.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) During the process of monitoring EAS equipment gives the adequate information on condition of interfaces, operative memory and central processor.
2) The EAS equipment provides transfer of adequate SNMP traps/informs messages in case of emergencies occurrence.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Diagram of the test scheme. A central EAS device has two ports, Port 1 and Port 2. Port 1 is connected via Ethernet to an HG1 (Ethernet WAN) unit, which is connected to Host A.1 (IP: xxxxx). Port 2 is connected via Ethernet to an HG2 (Ethernet WAN) unit, which is connected to Host B.1 (IP: xxxxx). Additionally, the EAS device is connected via Ethernet to an Ethernet switch. A Remote CLI (laptop, IP: xxxxx) is connected to the Ethernet switch and has a dashed arrow labeled 'SNMP' pointing to the EAS device's IP: xxxxx.
|
+
+##### 6.3.1.2.6 Check of functions of Multicast mode support
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_MC_01 |
+| Test name | Connection of several users to one multicasting group |
+| Test purpose | Check if the EAS equipment has the possibility of simultaneous connection of several users to one multicasting group without subsequent load increase at network interfaces of EAS equipment |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, three user ports on the EAS equipment (three user lines) has to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 equipment, HG2 and HG3, accordingly).
4) Host A.1 is connected to home gateway HG1.
5) Host B.1 is connected to home gateway HG2.
6) Host C.1 is connected to home gateway HG3.
7) HG1 equipment, HG2 and HG3 work in the bridged mode (function of local DHCP server is disconnected).
8) On hosts A.1, B.1 and C.1 IP STB software should be used. Hosts A.1, B.1 and C.1 are IGMP hosts. IP-addresses for hosts A.1, B.1 and C.1 are configured manually.
9) Hosts A.1, B.1 and C.1 use IPoE sessions.
10) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
|
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 11) Router equipment performing functions of IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM-SSM protocol is used.
12) EAS equipment during processing of IGMP messages works in the transparent IGMP Snooping mode.
13) On the EAS equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the EAS equipment should be configured the possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from users IP-STB equipment.
14) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.
|
+| Test procedure | 1) Hosts A.1, B.1 and C.1 should initiate IPoE sessions, transfer IGMP Membership Report messages and, thus, should consistently connect to the same multicasting group (observe one video channel).
2) Save the captures of traces in separate files ([Vendor]-EAS_MC_01.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) All users have connections to the same multicasting group (observe one video channel).
2) During consecutive connections of hosts B.1 and C.1 there is no additional load on network interfaces of EAS equipment.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram for Test scheme. Three hosts (Host A.1, Host B.1, Host C.1) labeled as IP-STB and IGMP host with IP:xxxx are connected via IPoE to home gateways HG1, HG2, and HG3 (labeled Ethernet WAN). These gateways are connected via Ethernet (IPoE) to the EAS equipment. The EAS equipment has three ports (Port 1, Port 2, Port 3) and is configured for IGMP transparent snooping. Port 3 is connected via MC-VLAN (S-VID 1) to an Ethernet switch. The switch is connected to an IGMP router labeled PIM-SSM. A video server (Host X.1) with IP:xxxx is also connected to the Ethernet switch.
|
+
+| | |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_MC_02 |
+| Test name | Restriction of channels number which are simultaneously observed by the user |
+| Test purpose | Check if the EAS equipment has the possibility of multicasting groups total number restriction to which one user simultaneously can be connected |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
4) Hosts A.1, A.2 and A.3 are connected to home gateway HG1.
|
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected). HG1 equipment should support the IGMP Snooping function.
6) On hosts A.1, A.2 and A.3 IP STB software should be used. Hosts A.1, A.2 and A.3 are IGMP hosts. IP-addresses for hosts A.1, A.2 and A.3 are configured manually.
7) Hosts A.1, A.2 and A.3 use IPoE sessions.
8) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
9) Router equipment which performs functions of IGMP router should be connected to the Ethernet switch equipment. For routing of multicasting traffic PIM SSM protocol is used.
10) EAS equipment during processing of IGMP messages functions in the transparent IGMP Snooping mode.
11) On the EAS equipment should be configured uniform multicasting VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the EAS equipment there should be configured a possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from IP-STB equipment of users.
12) On the EAS equipment there should be configured for user port No. 1 restriction on total number of multicasting groups to which the given user can be connected. Maximum number of multicasting groups for the given user should be equal to 2.
13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.
|
+| Test procedure | 1) Hosts A.1, A.2 and A.3 should consistently initiate IPoE sessions and transfer IGMP Membership Report messages, trying to be connected to various multicasting groups.
2) Save the captures of traces in separate files ([Vendor]-EAS_MC_02.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) A.1 and A.2 hosts are successfully connected to various multicasting groups.
2) Host A.3 has no connections to new multicasting group.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing the test scheme. On the left, three hosts (Host A.1, Host A.2, Host A.3) labeled as IP-STB and IGMP hosts with IP: x.x.x.x are connected to an HG1 (Ethernet WAN) device. The HG1 is connected via an Ethernet (PoE) cable to Port 1 of an EAS (Ethernet Aggregation Switch) device. The EAS device has a 'User port #1' and a 'Multicast VLAN (S-VID 1)'. The EAS is connected via a dashed line labeled 'MC-VLAN(S-VID 1)' to an Ethernet switch. Host X.1 (video server) with IP: x.x.x.x is connected to the Ethernet switch. The Ethernet switch is connected to an IGMP router labeled PIM-SSM.
|
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | EAS_MC_03 |
+| Test name | Restriction of the multicast groups list accessible to the user |
+| Test purpose | Check if the EAS equipment has the possibility of restriction of the multicast groups list accessible to the specified user |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) For carrying out the tests, one user port on the EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
4) Host A.1 is connected to home gateway HG1.
5) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
6) On host A.1 IP-STB software should be used. Host A.1 should be IGMP host. IP-address for host A.1 should be configured manually.
7) Host A.1 uses IPoE sessions.
8) Host X.1 is connected to the Ethernet switch which has implemented functions of the EAS traffic aggregation. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
9) Router equipment which performs functions of IGMP router should be connected to the Ethernet switch equipment. For routing of multicast traffic PIM-SSM protocol is used.
10) EAS equipment during processing of IGMP messages functions in the transparent IGMP Snooping mode.
11) On the EAS equipment should be configured uniform multicast VLAN, intended for carrying out of traffic related with IP-STB equipment of all users. On the EAS equipment there should be configured the possibility of "S-VID"=1 identifiers assignment to the Ethernet frames transferred upstream from IP-STB equipment of users.
12) On the EAS equipment there should be configured for user port No. 1 the multicast groups list accessible to user.
13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.
|
+| Test procedure | 1) Host A.1 should initiate IPoE session and transfer IGMP Membership Report messages, trying to be consistently connected to various multicast groups, matching the list of resolved groups, and not matching the given list.
2) Save the captures of traces in separate files ([Vendor]-EAS_MC_03.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Host A.1 has been successfully connected to various multicast groups matching list of groups, resolved for user port No. 1.
2) Host A.1 has no connections to any of multicast groups which are not matching the list of groups, resolved for user port No. 1.
3) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+**Test scheme**
+
+Network diagram showing the test scheme. Host A.1 (IP-STB) with IP: xxxxx (IGP host) is connected to HG1 (Ethernet WAN). HG1 is connected via Ethernet (IPoE) to Port 1 of the EAS (Ethernet Access Switch). The EAS has a 'User port#1' with a 'List of resolved multiexclusive groups'. Port 1 is connected via MC-VLAN (S-VID '1') to an Ethernet switch. Host X.1 (video server) with IP: xxxxx is connected to the Ethernet switch. The Ethernet switch is connected to an IGMP router PIM-SSM.
+
+#### 6.3.1.3 Check of functionality of BRAS equipment
+
+##### 6.3.1.3.1 Check of functions of VLAN tags processing
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_VLAN_01 |
+| Test name | Assignment of the S-Tag tag to the Ethernet frames transferred downstream |
+| Test purpose | Check if the BRAS equipment can assign the S-Tag to the unmarked Ethernet frames transferred downstream |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet Switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.
- 4) For carrying out the tests, two user's ports on the DSLAM/MSAN/EAS equipment (two user lines) has to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
- 5) HG1 and HG2 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 6) A.1 and A.2 hosts are connected to home gateway HG1.
- 7) B.1 and B.2 hosts are connected to the home gateway equipment HG2.
- 8) A.1 and B.1 hosts use PPPoE sessions.
- 9) A.2 and B.2 hosts use IPoE sessions.
- 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically using PPPoE server or are configured manually. For termination of PPPoE sessions from A.1 and B.1 hosts BRAS equipment is used.
- 11) IP-addresses for A.2 and B.2 hosts are assigned dynamically with the allocated DHCP server or are configured manually. In case of dynamic assignment of IP-addresses for A.2 and B.2 hosts BRAS equipment works as DHCP Relay Agent.
- 12) X.1 and X.2 hosts are connected to the Ethernet switch equipment. IP-addresses for X.1 and X.2 hosts are configured manually.
|
+
+- 13) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
+- 14) Further adjustment of equipment should be provided according to one of the following configurations.
+
+###### *Configuration 1 (1:1 VLAN)*
+
+BRAS equipment should be configured to enable the assignment of S-VLAN tags to unmarked Ethernet frames transferred downstream. Following options should be configured:
+
+- assignment "S-VID"=1 Ethernet frames connected with PPPoE session of host A.1 (user's port No. 1 on the access node equipment);
+- assignment "S-VID"=2 Ethernet frames connected with IPoE session of host A.2 (user's port No. 1 on the access node equipment);
+- assignment "S-VID"=3 Ethernet frames connected with PPPoE session of host B.1 (user's port No. 2 on the access node equipment);
+- assignment "S-VID"=4 Ethernet frames connected with IPoE session of host B.2 (user's port No. 2 on the access node equipment).
+
+S-VLAN options for DSLAM/MSAN/EAS equipment, and also on the Ethernet switch equipment are configured according to S-VLAN options for BRAS equipment.
+
+###### *Configuration 2 (VLAN on the user)*
+
+BRAS equipment should be configured to enable assignment of S-VLAN tags to unmarked Ethernet frames transferred downstream. Following options should be configured:
+
+- assignment "S-VID"=1 Ethernet frames connected with all sessions (PPPoE/IPoE) of HG1 equipment (user port No. 1 on the access node equipment);
+- assignment "S-VID"=2 Ethernet frames connected with all sessions (PPPoE/IPoE) of HG2 equipment (user port No. 2 on the access node equipment).
+
+S-VLAN options for DSLAM/MSAN/EAS equipment, and also on Ethernet switch equipment, are configured according to S-VLAN options for BRAS equipment.
+
+###### *Configuration 3 (VLAN on service)*
+
+BRAS equipment should be configured to enable assignment of S-VLAN tags to unmarked Ethernet frames transferred downstream. Following options should be configured:
+
+- assignment "S-VID"=1 Ethernet frames connected with PPPoE sessions of all users, connected to DSLAM/MSAN/EAS equipment;
+- assignment "S-VID"=2 Ethernet frames connected with IPoE sessions of all users, connected to DSLAM/MSAN/EAS equipment.
+
+S-VLAN options for DSLAM/MSAN/EAS equipment, and also on the Ethernet switch equipment, are configured according to S-VLAN options for BRAS equipment.
+
+- 15) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed || bootp || ICMP.
+
+| | |
+|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure
| - 1) For configuration 1 perform traffic exchange between hosts A.1 and X.1, A.2 and X.2, B.1 and X.1, B.2 and X.2.
- 2) For configuration 2 perform traffic exchange between hosts A.1 and X.1, A.2 and X.2, B.1 and X.1, B.2 and X.2.
- 3) For configuration 3 perform traffic exchange between hosts A.1 and X.1, A.2 and X.2, B.1 and X.1, B.2 and X.2.
- 4) Save the captures of traces in separate files ([Vendor]-BRAS_VLAN_01.txt) and put the file into the corresponding section of the KB.
- 5) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result
| - 1) During use of configuration 1 BRAS equipment performs assignment of S-VLAN identifiers as follows:
- – assignment of identifier "S-VID"=1 Ethernet frames transferred downstream and connected with PPPoE session of host A.1;
- – assignment of identifier "S-VID"=2 Ethernet frames transferred downstream and connected with IPoE session of host A.2;
- – assignment of identifier "S-VID"=3 Ethernet frames transferred downstream and connected with PPPoE session of host B.1;
- – assignment of identifier "S-VID"=4 Ethernet frames transferred downstream and connected with IPoE session of host B.2.
- 2) During use of configuration 2 BRAS equipment performs assignment of S-VLAN identifiers as follows:
- – assignment of identifier "S-VID"=1 Ethernet frames transferred downstream and connected with all PPPoE/IPoE sessions of HG1 equipment (passing through user's port No. 1 DSLAM/MSAN/EAS equipment);
- – assignment of identifier "S-VID"=2 Ethernet frames transferred downstream and connected with all PPPoE/IPoE sessions of HG2 equipment (passing through user's port No. 2 DSLAM/MSAN/EAS equipment).
- 3) BRAS equipment performs assignment of S-VLAN identifiers as follows:
- – assignment of identifier "S-VID"=1 Ethernet frames transferred downstream and connected with PPPoE sessions of all users, connected to DSLAM/MSAN/EAS equipment;
- – assignment of identifier "S-VID"=2 Ethernet frames transferred downstream and connected with IPoE sessions of all users, connected to DSLAM/MSAN/EAS equipment.
- 4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme
| Image: Test scheme diagram showing Host A.1, Host A.2, Host B.1, Host B.2 connected to HG1 and HG2 respectively. HG1 and HG2 are connected to a DSLAM/MSAN/EAS unit. The DSLAM/MSAN/EAS unit is connected to an Ethernet switch, which is connected to a BRAS unit. Host X.1 and Host X.2 are connected to the Ethernet switch. A protocol analyzer is connected to the BRAS unit. The diagram illustrates the network configuration for testing VLAN assignments.
The diagram illustrates the test scheme. On the left, Host A.1 (IP: xxxx (PPPoE)) and Host A.2 (IP: xxxx (IPoE)) are connected to HG1. Host B.1 (IP: xxxx (PPPoE)) and Host B.2 (IP: xxxx (IPoE)) are connected to HG2. HG1 and HG2 are connected to a DSLAM/MSAN/EAS unit via Ethertype PPP, IP. The DSLAM/MSAN/EAS unit has two ports, Port 1 and Port 2, connected to an Ethernet switch. The Ethernet switch is connected to a BRAS unit via an S-VLAN link. Host X.1 (IP: xxxx) and Host X.2 (IP: xxxx) are also connected to the Ethernet switch. A protocol analyzer is connected to the BRAS unit, which performs PPPoE Termination and IPoE. The Ethernet switch contains an S-VLAN bridge and an S-Tag attach point.
|
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_VLAN_02 |
+| Test name | Configuration of S-VLAN/C-VLAN stack (QinQ) |
+| Test purpose | Check if the BRAS has the possibility of assigning the VLAN tag pair (S-Tag/C-Tag) to the Ethernet frame, which is transferred upstream |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet Switch performs aggregation of the traffic from access nodes.
- 4) For carrying out the tests, one access node has to be used. As access node DSLAM/MSAN/EAS equipment can be used.
- 5) For carrying out the tests, two user's ports on the DSLAM/MSAN/EAS equipment (two user lines) has to be used. On the user side the home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
- 6) HG1 and HG2 equipment works in a bridged mode (function of local DHCP server is disconnected).
- 7) Host A.1 is connected to the home gateway equipment HG1.
- 8) Host B.1 is connected to the home gateway equipment HG2.
- 9) A.1 and B.1 hosts use IPoE sessions.
- 10) IP-addresses for A.1 and B.1 hosts are assigned dynamically with the allocated DHCP server or are configured manually. In case of dynamic assignment of IP-addresses for A.2 and B.2 hosts BRAS equipment works as DHCP Relay Agent.
- 11) X.1 and X.2 hosts are connected to the Ethernet switch equipment. IP-addresses for X.1 and X.2 hosts are configured manually.
- 12) In the case when for carrying out of test there is DSLAM/MSAN equipment used, on HG1, HG2 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
- 13) BRAS equipment should be configured S-VLAN/C VLAN pair assignment to unmarked Ethernet frames transferred downstream. Following options should be configured:
- – assignment "S-VID"=1, "C-VID"=1 Ethernet frames connected with all PPPoE sessions/IPoE of HG1 equipment (the identifier "S-VID"=1 is the general for all users connected to DSLAM/MSAN/EAS equipment; identifier "C-VID" =1 characterizes the concrete user – user's port No. 1 on the DSLAM/MSAN/EAS equipment);
- – assignment "S-VID"=1, "C-VID"=2 Ethernet frames connected with all PPPoE sessions/IPoE of HG2 equipment (the identifier "S-VID"=1 is the general for all users connected to DSLAM/MSAN/EAS equipment; identifier "C-VID"=2 characterizes concrete user – user's port No. 2 on the DSLAM/MSAN/EAS equipment).
- 14) S-VLAN/C-VLAN options for DSLAM/MSAN/EAS equipment are configured according to S-VLAN/C-VLAN options for BRAS equipment.
- 15) Ethernet switch S-VLAN options are configured according to S-VLAN options for BRAS equipment and DSLAM/MSAN/EAS equipment.
- 16) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: bootp ICMP.
|
+
+| | |
+|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | - 1) Perform traffic exchange between hosts A.1 and X.1.
- 2) Perform traffic exchange between hosts B.1 and X.2.
- 3) Save the captures of traces in separate files ([Vendor]-BRAS_VLAN_02.txt) and put the file into the corresponding section of the KB.
- 4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | - 1) The BRAS equipment has assigned the identifier "S-VID"=1, "C-VID"=1 for Ethernet frames which are transferred upstream and related to IPoE session of host A.1.
- 2) The BRAS equipment has assigned the identifier "S-VID"=1, "C-VID"=2 for Ethernet frames which are transferred upstream and related to IPoE session of host B.1.
- 3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing Host A.1 connected to HG1, which is connected to DSLAM/MSAN/EAS via IPoE. Host B.1 is connected to HG2, which is also connected to DSLAM/MSAN/EAS via IPoE. The DSLAM/MSAN/EAS is connected to an Ethernet switch via Port 1 and Port 2. The Ethernet switch is connected to a BRAS via S-VLAN-C-VLAN and S-Tag-C-Tag attach. The BRAS is connected to a Protocol analyzer and a Termination IPoE. Host X.1 and Host X.2 are connected to the Ethernet switch via IP:xxxx.
|
+
+##### 6.3.1.3.2 Check of security functions
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_SEC_01 |
+| Test name | Prevention of substitution of user's IP-address |
+| Test purpose | Check if the BRAS equipment has the possibility of prevention of attacks from outside the malicious users connected with substitution of the IP-address of a source (source IP spoofing) |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of the traffic from access nodes.
- 4) For carrying out the tests, one access node has to be used. As access node DSLAM/MSAN/EAS equipment can be used.
- 5) For carrying out the tests, one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used.
- 6) On the user side the equipment of a home gateway (HG1 equipment) should be connected to the network termination of a user line. HG1 equipment work in the bridge mode (function of local DHCP server is disconnected).
- 7) Host A.1 is connected to the home gateway equipment HG1. Host A.1 uses IPoE sessions.
- 8) IP-address for host A.1 is assigned dynamically with allocated DHCP server. BRAS equipment works as DHCP Relay Agent. DHCP server is connected to the Ethernet switch.
|
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 9) Host X.1 is connected to the Ethernet switch equipment. The IP-address for host X.1 should be configured manually.
10) In the case when for carrying out of test there is DSLAM/MSAN equipment used, on HG1, HG2 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
11) On the DSLAM/MSAN/EAS equipment, BRAS equipment and Ethernet switch equipment should be configured S-VLAN with identifier "S-VID"=1.
12) On the DSLAM/MSAN/EAS equipment function of blocking of broadcasting messages should be disconnected.
13) Before beginning of the test host A.1 should establish IPoE session and using DHCP server should receive IP address.
14) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: ARP bootp ICMP.
|
+| Test procedure | 1) Clear contents of ARP table on host A.1.
2) Clear contents of ARP table on BRAS equipment.
3) Perform on host A.1 command ping for host X.1.
4) Check-up records of ARP table on BRAS equipment.
5) Break off IPoE session for host A.1.
6) Perform repeated establishment of IPoE session for host A.1 (allocation of the IP address by means of DHCP).
7) Save the captures of traces in separate files ([Vendor]-BRAS_SEC_01.txt) and put the file into the corresponding section of the KB.
8) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) On termination of command ping passage in ARP table of BRAS equipment there is no record related with MAC-address of host A.1.
2) After repeated establishment of IPoE connection in ARP table of BRAS equipment should be generated new dynamic record related with MAC-address of host A.1
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing the test setup. Host A.1 (IP: x.xxx) is connected to HG1, which is connected to Port 1 of the DSLAM/MSAN/EAS. The DSLAM/MSAN/EAS is connected to an Ethernet switch via a dashed line labeled 'S-VID 1'. The Ethernet switch is connected to a Server DHCP and to a BRAS via a dashed line labeled 'S-VID 1'. The BRAS is connected to a DHCP Relay Agent. Host X.1 (IP: x.xxx) is connected to the Ethernet switch.
graph LR A1[Host A.1
IP: x.xxx] --- HG1[HG1] HG1 --- P1[Port 1] subgraph DSLAM [DSLAM/MSAN/EAS] P1 end P1 -.-> S-VID 1 ES[Ethernet switch] ES --- SDHCP[Server DHCP] ES -.-> S-VID 1 BRAS[BRAS] BRAS --- DRA[DHCP Relay Agent] X1[Host X.1
IP: x.xxx] --- ES
|
+
+##### 6.3.1.3.3 Check of functions of management, monitoring and statistics gathering
+
+| | |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_MNG_01 |
+| Test name | Equipment monitoring by SNMP protocol |
+| Test purpose | Check if the BRAS equipment has the possibility for remote monitoring by means of the control system using SNMP protocol |
+
+| | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes.
4) Host which performs functions of a remote workstation of control system is connected to the Ethernet switch. On the given host SNMP software is established. IP-address for specified host should be configured manually and should be from the same subnetwork, as the IP-address of BRAS equipment used for interaction with the control system.
5) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: report SNMP. |
+| Test procedure | 1) Initiate remote monitoring of BRAS equipment on host, carrying out functions of workstation of a control system.
2) Provide appearance of emergency and other non-standard situations on the BRAS equipment. Also it is necessary to simulate problems with powering (transition to the reserve block, return to mainframe), problems with interfaces (refusal of physical / channel level), connection of remote users to BRAS equipment on Telnet/SSH/SNMP, change of equipment configuration on Telnet/SSH/SNMP and other events.
3) Save the captures of traces in separate files ([Vendor]-BRAS_MNG_01.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) During the process of monitoring BRAS equipment gives the adequate information on condition of interfaces, operative memory and central processor.
2) The BRAS equipment provides transfer of adequate SNMP traps/informs messages in case of emergencies occurrence.
3) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme | Image: Diagram of the test scheme showing a Remote CLI (laptop) connected to an Ethernet switch, which is connected to a DSLAM/MSAN/EAS and a BRAS. The Remote CLI is sending SNMP messages to the BRAS.
graph LR RemoteCLI[Remote CLI
IP:xxxx] --- EthernetSwitch[Ethernet switch] DSLAM[DSLAM/MSAN/EAS] --- EthernetSwitch EthernetSwitch --- BRAS[BRAS
IP:xxxx(MNG)] RemoteCLI -.-> SNMP BRAS
|
+
+##### 6.3.1.3.4 Check of functions of Multicast mode support
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_MC_01 |
+| Test name | Restriction of number of multicasting groups |
+| Test purpose | Check if the BRAS equipment has the possibility of restriction of total number of the multicasting groups transferred within S-VLAN (MC-VLAN) |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme. |
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.
4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected). HG1 equipment should support the IGMP Snooping function.
7) Hosts A.1, A.2 and A.3 are connected to home gateway HG1. On hosts A.1, A.2 and A.3 IP STB software should be used. Hosts A.1, A.2 and A.3 are IGMP hosts (clients). IP-addresses for hosts A.1, A.2 and A.3 are configured manually. Hosts A.1, A.2 and A.3 use IPoE sessions.
8) Host X.1 is connected to the Ethernet switch equipment. Host X.1 performs functionality of video server, being video traffic source. The IP-address for host X.1 should be configured manually.
9) BRAS equipment works as IGMP router. For routing of the multicasting traffic report PIM SSM is used.
10) DSLAM/MSAN/EAS equipment during processing of IGMP messages works in the mode of transparent IGMP Snooping. On the DSLAM/MSAN/EAS equipment function of restriction of number of multicasting groups accessible to users should disconnected.
11) On BRAS equipment, DSLAM/MSAN/EAS equipment and Ethernet switch equipment the S-VLAN (MC-VLAN: "S-VID"=1) should be configured, intended for carrying out of multicasting traffic to all users connected to access node.
12) On BRAS equipment for MC-VLAN ("S-VID"=1) should be configured restriction of total number of the multicasting groups transferred within MC-VLAN. Maximum number of multicasting groups for MC VLAN should equals to 2.
13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: IGMP.
|
+| Test procedure | 1) Hosts A.1, A.2 and A.3 should consistently initiate IPoE sessions, transfer IGMP Membership Report messages and try to connect to various multicasting groups.
2) Save the captures of traces in separate files ([Vendor]-BRAS_MC_01.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) A.1 and A.2 hosts are successfully connected to various multicasting groups.
2) Host A.3 has no connections to new multicasting group.
3) There is a possibility of configuration on BRAS equipment of maximum bandwidth with which it is supposed to occupy within MC-VLAN by transfer of multicasting streams.
4) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+**Test scheme**
+
+Network diagram showing the test scheme. On the left, three hosts (Host A.1, Host A.2, Host A.3) labeled as IP-STB and IGMP hosts are connected to a home gateway (HG1). HG1 is connected to Port 1 of a DSLAM/MSAN/EAS unit. A dashed line labeled 'MC-VLAN (S-VID 11)' connects Port 1 to an Ethernet switch. Host X.1 (video server) is connected to the Ethernet switch. The Ethernet switch is connected to a BRAS unit via another dashed line labeled 'MC-VLAN (S-VID 11)'. The BRAS unit is labeled as an IGMP router PIM-SSM.
+
+| | |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_MC_02 |
+| Test name | Providing statistics of multicasting traffic |
+| Test purpose | Check if the BRAS equipment has the possibility of providing statistics concerning multicasting traffic for each MC-VLAN and each multicasting group |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of the traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.
- 4) For carrying out the tests three user ports on the DSLAM/MSAN/EAS equipment (three user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 equipment, HG2 and HG3, accordingly).
- 5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 and HG3 equipment and DSLAM/MSAN equipment one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
- 6) HG1 equipment, HG2 and HG3 work in the bridge mode (function of local DHCP server is disconnected). HG1 equipment, HG2 and HG3 support function IGMP Snooping.
- 7) Host A.1 is connected to home gateway HG1.
- 8) Host B.1 is connected to home gateway HG2.
- 9) Host C.1 is connected to home gateway HG3.
- 10) On hosts A.1, B.1 and C.1 IP STB software should be used. Hosts A.1, B.1 and C.1 are IGMP hosts (clients). IP-addresses for hosts A.1, B.1 and C.1 are configured manually. Hosts A.1, B.1 and C.1 use IPoE sessions.
- 11) Host X.1 is connected to Ethernet switch equipment. Host X.1 performs functionality of video server, being video traffic source. IP-address for host X.1 should be configured manually.
- 12) BRAS equipment works as IGMP router. For routing of the multicasting traffic report PIM SSM is used.
- 13) DSLAM/MSAN/EAS equipment processing of IGMP messages works in the transparent IGMP Snooping mode.
|
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 14) On the DSLAM/MSAN/EAS equipment, and also on BRAS equipment function of restriction of admissible number of multicasting groups should be disconnected.
15) On BRAS equipment, DSLAM/MSAN/EAS equipment and Ethernet switch equipment the S VLAN (MC-VLAN: "S-VID"=1) should be configured to enable the delivery of multicasting traffic to all users connected to access node.
|
+| Test procedure | 1) Perform consecutive connection of each host (A.1, B.1 and C.1) to various multicasting groups.
2) Perform periodic switching between multicasting groups on everyone each host (A.1, B.1 and C.1).
3) Save the captures of traces in separate files ([Vendor]-BRAS_MC_02.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) During test procedure performance BRAS equipment gives adequate information related with the following statistics:
- – for each MC-VLAN: current number of active multicasting groups; total number of attempts for users joining to multicasting groups (including successful/unsuccessful); total number of messages related with switching-off from multicasting groups; total number of the transferred inquiries – Queries (including general queries/specific queries); total number of received incorrect messages IGMP;
- – for each multicasting group (within defined MC VLAN): present total number of active hosts.
2) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram for the test scheme. On the left, three hosts (Host A.1, Host B.1, Host C.1) are connected to a central DSLAM/MSAN/EAS unit via HG1, HG2, and HG3 respectively. Each host is labeled as an IP-STB and an IGMP host with IP:xxxx. The DSLAM/MSAN/EAS unit has three ports (Port 1, Port 2, Port 3) connected to the hosts and a dashed line representing an MC-VLAN (S-VID 1) connection to an Ethernet switch on the right. The Ethernet switch is connected to a BRAS unit, which is further connected to an IGMP router (PIM-SSM). A video server (Host X.1) is also connected to the Ethernet switch.
|
+
+##### 6.3.1.3.5 Accounting and management of access policy
+
+| | |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_ACC_01 |
+| Test name | Establishment of PPPoE session |
+| Test purpose | Check if the BRAS equipment has the possibility of PPPoE user sessions establishment |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
|
+
+| | |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.
4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side the equipment of a home gateway (HG1 equipment) should be connected to network termination of a user line.
5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1 equipment and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
7) Host A.1 is connected to the home gateway equipment HG1.
8) Host A.1 uses PPPoE sessions. The IP-address for host A.1 is assigned dynamically.
9) Host X.1 is connected to the Ethernet switch equipment. The IP-address for host X.1 should be configured manually.
10) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server. BRAS equipment contain IP-addresses pool for dynamic assignment during establishment of users' sessions.
11) Subscribers authentication performed on allocated AAA server.
12) AAA Server (RADIUS server) is connected to the Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on host A.1.
13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed bootp PPP ICMP RADIUS.
|
+| Test procedure | 1) Initiate an establishment of PPPoE session on host A.1 (enter correct values of username and password).
2) Perform data exchange between hosts A.1 and X.1.
3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_01.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Successful user authentication on host A.1 and subsequent establishment of PPPoE session. Host A.1 has received the IP-address from pool of addresses located on BRAS equipment.
2) Correctness of PPPoE messages transferred by BRAS equipment in direction to host A.1.
3) Correctness of RADIUS messages transferred by BRAS equipment in direction to AAA server.
4) There is a data exchange possibility between hosts A.1 and X.1.
5) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+| | |
+|--------------------|--|
+| Test scheme | |
+|--------------------|--|
+
+Network diagram for the test scheme. Host A.1 (IP: xxxxx (client PPPoE)) is connected to HG1 (bridged mode). HG1 is connected to DSLAM/MSAN/EAS via PPPoE. DSLAM/MSAN/EAS has Port 1 connected to an Ethernet switch via S-VID '1'. Host X.1 (IP: xxxxx) is also connected to the Ethernet switch. The Ethernet switch is connected to a Server AAA and a BRAS (PPPoE Server) via S-VID '1-1'. The BRAS is connected to the Server AAA via RADIUS.
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_ACC_02 |
+| Test name | Establishment of IPoE session |
+| Test purpose | Check if the BRAS equipment has the possibility of establishment of user IPoE (DHCP) sessions |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node has to be used. As access node, DSLAM/MSAN/EAS equipment can be used.
- 4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
- 5) If there is DSLAM/MSAN equipment used on HG1 equipment and DSLAM/MSAN, one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
- 6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
- 7) Host A.1 is connected to home gateway HG1.
- 8) Host A.1 uses IPoE sessions. The IP-address for host A.1 is defined dynamically using allocated DHCP server connected to the Ethernet switch. DHCP server supports an option 82.
- 9) DSLAM/MSAN/EAS equipment works as Layer 2 DHCP Relay Agent. DSLAM/MSAN/EAS equipment supports an option 82 during transfer of broadcasting DHCP messages from users.
- 10) Host X.1 is connected to the Ethernet switch equipment. The IP-address for host X.1 should be configured manually.
- 11) BRAS equipment is configured for termination of IPoE sessions. BRAS equipment works as quality (full) DHCP Relay Agent. BRAS equipment comprises IP-addresses pool for dynamic assignment during establishment of users sessions.
- 12) On DHCP server should be configured new user profile where for user identification port number of access node (contains in DHCP option 82) is used.
- 13) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed bootp PPP ICMP RADIUS.
|
+
+| | |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test procedure | 1) Initiate establishment of IPoE session on host A.1 (perform transfer of DHCP broadcasting messages from host A.1).
2) Perform data exchange between hosts A.1 and X.1.
3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_02.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB. |
+| Expected result | 1) Successful establishment of IPoE session. Host A.1 has received IP-address from pool of addresses located on BRAS equipment.
2) BRAS equipment correctly processes DHCP messages containing option 82 which are transferred from user side, and from DHCP server side.
3) During reception of broadcasting DHCP messages from users BRAS equipment directs them to DHCP server in a unicast mode.
4) There is a data exchange possibility between hosts A.1 and X.1.
5) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme | Image: Network diagram for Test scheme. Host A.1 (IP: xxxxx client DHCP) is connected via IPoE to HG1 (bridged mode). HG1 is connected via IPoE to DSLAM/MSAN/EAS (Layer 2 DHCP Relay Agent, DHCP opt82 insertion, Port 1). DSLAM/MSAN/EAS is connected via S-VID '1' to an Ethernet switch. Host X.1 (IP: xxxxx) is also connected to the Ethernet switch. The Ethernet switch is connected to a Server DHCP (option 82) and a BRAS (IDHCP Relay Agent). Arrows show DHCP opt82 broadcast from Host A.1 to the switch, and DHCP opt82 unicast from the switch to the Server DHCP and BRAS.
|
+
+| | |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_ACC_03 |
+| Test name | Establishment of L2TP tunnels |
+| Test purpose | Check if the BRAS equipment has the possibility of functioning as LNS server during termination of L2TP tunnels of users |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests, one access node has to be used. As access node DSLAM/MSAN/EAS equipment can be used.
4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side equipment of a home gateway (HG1 equipment) should be connected to network termination of a user line.
5) If there is DSLAM/MSAN equipment used on HG1 equipment and DSLAM/MSAN, one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
7) Host A.1 is connected to home gateway HG1. |
+
+| | |
+|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 8) Host A.1 uses PPPoE sessions. IP-address for host A.1 is assigned dynamically.
9) Host A.1 uses L2TP tunnel during interaction with BRAS equipment and transport of PPPoE messages.
10) Host X.1 is connected to the Ethernet switch equipment. IP-address for host X.1 should be configured manually.
11) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server.
12) BRAS equipment works as LNS server during establishment of L2TP tunnels between BRAS and users.
13) AAA Server (RADIUS server) is connected to the Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on host A.1.
14) Perform on the analyser of punctures IP the interface with filter on bootp PPP ICMP L2TP.
|
+| Test procedure | 1) Initiate an establishment of PPPoE session on host A.1 (enter correct values of username and password).
2) Perform data exchange between hosts A.1 and X.1.
3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_03.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Successful user authentication on host A.1 and subsequent establishment of PPPoE session.
2) There is data exchange between hosts A.1 and X.1.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Network diagram showing Host A.1 connected to HG1 (bridged mode), which is connected to DSLAM/MSAN/EAS (Port 1). Host A.1 is labeled with 'IP:xxxx client PPPoE client L2TP'. A dashed line labeled 'L2TP tunnel' connects Host A.1 to BRAS (LNS PPPoE Server). DSLAM/MSAN/EAS is connected to an Ethernet switch via a link labeled 'S/VID 1'. The Ethernet switch is connected to Server AAA and to BRAS (LNS PPPoE Server) via a link labeled 'G 0/0/1'. Host X.1 is connected to the Ethernet switch and labeled with 'IP:xxxx'.
|
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_ACC_04 |
+| Test name | Accounting of rendered services volume for PPPoE sessions |
+| Test purpose | Check if the BRAS equipment has the possibility of rendered broadband services volume accounting for users initiating PPPoE sessions |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. DSLAM/MSAN/EAS can be used as access node.
|
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 4) For carrying out the tests one user port on the DSLAM/MSAN/EAS equipment (one user line) has to be used. On the user side home gateway equipment (HG1 equipment) should be connected to network termination of user line.
5) If there is DSLAM/MSAN equipment used on HG1 equipment and DSLAM/MSAN, one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
6) HG1 equipment works in a bridged mode (function of local DHCP server is disconnected).
7) Host A.1 is connected to home gateway HG1.
8) Host A.1 uses PPPoE sessions. IP-address for host A.1 is assigned dynamically.
9) Host X.1 is connected to the Ethernet switch equipment. IP-address for host X.1 should be configured manually. Host X.1 is configured as FTP-server. There are several files of various volume on the FTP-server.
10) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server.
11) Subscribers authentication performed on allocated AAA server.
12) AAA server (RADIUS server) is connected to the Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on host A.1.
13) There should be configured on BRAS equipment periodical data transmission about volume of rendered services in direction to AAA server.
14) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: RADIUS.
|
+| Test procedure | 1) Initiate an establishment of PPPoE session on host A.1 (enter correct values of username and password).
2) On host A.1 perform download of several files from FTP server.
3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_04.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Correctness of RADIUS messages transferred by BRAS equipment in direction to AAA server. These messages should contain information about the volume of transferred data and should be transferred in beginning and in end of session, and also during all session through certain interval of time configured on BRAS equipment.
2) Correctness of CDR records formed on AAA server.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Test scheme diagram showing the network topology for the test. Host A.1 (client PPPoE) is connected to HG1 (bridged mode), which is connected to Port 1 of the DSLAM/MSAN/EAS. The DSLAM/MSAN/EAS is connected via S-VID '1' to an Ethernet switch. Host X.1 (FTP server) is also connected to the Ethernet switch. The Ethernet switch is connected to a BRAS (PPPoE Server), which is connected to a Server AAA via RADIUS. The BRAS is also connected to the Server AAA via RADIUS.
graph LR HostA1[Host A.1
IP:xxxxx
(client PPPoE)] -- PPPoE --> HG1[HG1
(bridged mode)] HG1 -- PPPoE --> Port1[Port 1] subgraph DSLAM_MSAN_EAS [DSLAM/MSAN/EAS] Port1 end Port1 -.-> S-VID "1" EthernetSwitch[Ethernet switch] HostX1[Host X.1
IP:xxxxx
(FTP server)] --> EthernetSwitch EthernetSwitch --> BRAS[BRAS
(PPPoE Server)] BRAS -- RADIUS --> ServerAAA[Server AAA] EthernetSwitch -- RADIUS --> ServerAAA
|
+
+| | |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_ACC_05 |
+| Test name | Switching-off of the user after the quota reached |
+| Test purpose | Check if the BRAS equipment has the possibility of switching-off the user after achievement of the configured quota of the received data volume |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node has to be used. DSLAM/MSAN/EAS equipment can be used as access node.
- 4) For carrying out the tests two user ports on the DSLAM/MSAN/EAS equipment (two user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
- 5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
- 6) HG1 and HG2 equipment work in a bridged mode (function of local DHCP server is disconnected).
- 7) Host A.1 is connected to home gateway HG1.
- 8) Host B.1 is connected to home gateway HG2.
- 9) A.1 and B.1 hosts use PPPoE sessions. The IP-address for A.1 and B.1 hosts are assigned dynamically.
- 10) Host X.1 is connected to the Ethernet switch equipment. IP-address for host X.1 should be configured manually. Host X.1 is configured as FTP-server. There are several files of various volume on the FTP-server.
- 11) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server.
- 12) Subscribers authentication performed on allocated AAA server.
- 13) AAA server (RADIUS server) is connected to the Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on A.1 and B.1 hosts.
- 14) On AAA server for user of host A.1 there should be configured quota for as much as possible admissible volume of the received data. Establish the given quota equal to 10 Mb.
- 15) On AAA server for user of host B.1 there should be configured possibility of unlimited volume data reception.
- 16) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: RADIUS.
|
+| Test procedure | - 1) Initiate an establishment of PPPoE sessions on A.1 and B.1 hosts.
- 2) On host A.1 and B.1 perform download of several files from FTP server.
- 3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_05.txt) and put the file into the corresponding section of the KB.
- 4) Fill in a daily report form with the testing results and save it in the KB.
|
+
+| | |
+|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expected result | 1) User of host B.1 has possibility of reception of unlimited volume of data while session of user of host A.1 is broken off after reaching of configured quota.
2) Correctness of RADIUS messages transferred by BRAS equipment in direction to AAA server and also PPPoE messages transferred by BRAS equipment in direction to host A.1 during interruption of the established session.
3) The daily report form has been saved in the corresponding section of KB. |
+| Test scheme |
|
+
+| | |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | BRAS_ACC_06 |
+| Test name | Restriction of bandwidth accessible to user |
+| Test purpose | Check if the BRAS equipment has the possibility of user accessible bandwidth restriction for data reception/transmission |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) BRAS equipment is connected to the Ethernet switch equipment. Ethernet switch performs aggregation of traffic from access nodes. For carrying out of tests one access node have to be used. As access node DSLAM/MSAN/EAS equipment can be used.
4) For carrying out the tests two user ports on the DSLAM/MSAN/EAS equipment (two user lines) have to be used. On the user side home gateway equipment has to be connected to network terminations of user lines (HG1 and HG2, accordingly).
5) In the case when for carrying out of test there is DSLAM/MSAN equipment used on HG1, HG2 and DSLAM/MSAN one virtual channel (PVC X1/Y1) is configured for transfer of all types of the traffic.
6) HG1 and HG2 equipment work in a bridged mode (function of DHCP local server is disconnected).
7) Host A.1 is connected to home gateway HG1.
8) Host B.1 is connected to home gateway HG2.
9) A.1 and B.1 hosts use PPPoE sessions. IP-address for A.1 and B.1 hosts are assigned dynamically.
10) Host X.1 is connected to the Ethernet switch equipment. IP-address for host X.1 should be configured manually. Host X.1 is configured as FTP-server. There are several files of various volume on the FTP-server.
11) BRAS equipment is configured for termination of PPPoE sessions. BRAS equipment works as PPPoE server. |
+
+| | |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 12) Subscribers authentication performed on allocated AAA server.
13) Server AAA (server RADIUS) is connected to Ethernet switch equipment. On AAA server should be configured new user profile containing pair "user name"/"password". Given profile will be used during establishment of sessions on A.1 and B.1 hosts.
14) On AAA server for user of host A.1 there should be configured restrictions on an accessible bandwidth: 500 Kbit/with – DL, 100 Kbit/with – UL.
15) On AAA server for user of host B.1 there should be configured restrictions on an accessible bandwidth: 5 Mbit/with – DL, 1 Mbit/with – UL.
16) On the DSLAM/MSAN/EAS equipment should be configured for both users greatest possible bandwidth in both directions DL and UL.
17) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: RADIUS.
|
+| Test procedure | 1) Initiate establishment of PPPoE sessions on A.1 and B.1 hosts.
2) On host A.1 and B.1 perform download of several files from FTP server.
3) Save the captures of traces in separate files ([Vendor]-BRAS_ACC_06.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Real downloading speed of files on A.1 and B.1 hosts corresponds to the values configured on BRAS equipment.
2) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Test scheme diagram showing Host A.1 and Host B.1 connected via HG1 and HG2 (bridged mode) to a DSLAM/MSAN/EAS unit. The DSLAM/MSAN/EAS is connected to an Ethernet switch via S-VID 1 and S-VID 2. The Ethernet switch is connected to a Server AAA and a BRAS (PPPoE Server). Host X.1 (FTP server) is also connected to the Ethernet switch.
graph LR A1[Host A.1
IP:xxxx
(client PPPoE)] -- PPPoE --> HG1[HG1
(bridged mode)] B1[Host B.1
IP:xxxx
(client PPPoE)] -- PPPoE --> HG2[HG2
(bridged mode)] HG1 -- PPPoE --> DSLAM[DSLAM/MSAN/EAS
Port 1] HG2 -- PPPoE --> DSLAM DSLAM -- S-VID 1 --> SW[Ethernet switch] DSLAM -- S-VID 2 --> SW SW --> AAA[Server AAA] SW --> BRAS[BRAS
(PPPoE Server)] SW --> X1[Host X.1
(FTP server)
IP:xxxx]
|
+
+### 6.3.2 Methods of BBA TM interoperability testing
+
+#### 6.3.2.1 Check of compatibility of the access node and BRAS equipment of various vendors
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | AN-BRAS_COMP_01 |
+| Test name | User's line identification on basis of DHCP option 82 |
+| Test purpose | Check if there is compatibility of access node equipment (DSLAM/MSAN/EAS/OLT) and BRAS equipment of various vendors considering maintenance of user line identification procedure on basis of information presented in DHCP messages (option 82) |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) Vendor "X" represent access node equipment (e.g., DSLAM, MSAN, EAS and OLT PON).
|
+
+| | |
+|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 4) In the case when access node equipment is presented by DSLAM, MSAN or OLT PON, Vendor "X" should represent the home gateway equipment HG1.
5) Vendor "Y" represent BRAS equipment and DHCP server equipment. DHCP server is external in relation to BRAS equipment and is connected by Ethernet interface (electric). DHCP server supports an option 82.
6) For connection establishment between access node equipment of Vendor "X" and BRAS equipment of Vendor "Y" Ethernet interface (electric) is used. Mirroring of traffic from given interface is provided by Vendor "X".
7) Vendor "Y" provides mirroring of traffic from Ethernet interface between BRAS equipment and DHCP server equipment.
8) Host A.1 is DHCP client. Host A.1 is connected to home gateway HG1 (by Ethernet interface) if technology of access is xDSL or PON, or directly to access node if technology of access is Ethernet. HG1 equipment works in a bridged mode.
9) Access node equipment works as Layer 2 DHCP relay agent, providing addition of an option 82 in all DHCP messages transferred by clients in direction to BRAS equipment. Function Layer 2 DHCP relay agent should be activated for that user's port of access node to which HG1 equipment/host A.1 is connected.
10) BRAS equipment works as quality (full) DHCP relay agent.
11) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: bootp RADIUS.
|
+| Test procedure | 1) Initiate establishment of IPoE session from host A.1.
2) Save the captures of traces in separate files ([Vendor]-AN-BRAS_COMP_01.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Access node equipment during processing of DHCP messages provides additions of options 82 into these messages.
2) BRAS equipment, having received within DHCP option 82 information related with user line identification, correctly broadcasts given information in direction to DHCP server.
3) Successful establishment of IPoE session for host A.1.
4) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Test scheme diagram showing the network architecture for DHCP testing. Host A.1 (Client DHCP) is connected to HG1 (bridged mode) which is connected to an Access Node (Vendor 'X') via IPoE. The Access Node contains a Layer 2 DHCP Relay Agent and is connected to a DSLAM/MSAN/EAS. The Access Node is connected via Ethernet to a BRAS (Vendor 'Y') which contains a DHCP Relay Agent. The BRAS is connected to a Server DHCP. A Protocol analyzer is connected to the BRAS and Server DHCP interfaces with a 'filter: bootp'.
graph LR subgraph Vendor_X [Vendor "X"] subgraph AN [Access Node] L2RA[Layer 2 DHCP Relay Agent] end HG1[HG1
(bridged mode)] DSLAM[DSLAM/MSAN/EAS] HostA1[Host A.1
Client DHCP] HG1 --- IPoE((IPoE)) --- L2RA L2RA --- port1[port 1] --- DSLAM HostA1 --- HG1 end subgraph Vendor_Y [Vendor "Y"] BRAS[BRAS
DHCP Relay Agent] ServerDHCP[Server DHCP] end L2RA --- Ethernet((Ethernet)) --- BRAS BRAS --- ServerDHCP BRAS --- PA[Protocol analyzer
filter: bootp] ServerDHCP --- PA HostA1 -.-> DHCP > L2RA L2RA -.-> DHCPoption82 > BRAS BRAS -.-> DHCPoption82 > ServerDHCP
|
+
+| | |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | AN-BRAS_COMP_02 |
+| Test name | User line identification on basis of PPPoE tag |
+| Test purpose | Check if there is compatibility of access node equipment (DSLAM/MSAN/EAS/OLT) and BRAS equipment of various vendors, considering maintenance of user line identification procedure on basis of information presented in PPPoE tag |
+| Initial condition | 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
2) Connect equipment under test and measurement equipment in accordance with testing scheme.
3) Vendor "X" represent access node equipment (e.g., DSLAM, MSAN, OLT PON and home gateway equipment HG1).
4) Vendor "Y" represent BRAS equipment and equipment of AAA server. AAA server is external in relation to BRAS equipment and is connected on Ethernet interface (electric). AAA server is RADIUS server.
5) For connection establishment between access node equipment of Vendor "X" and BRAS equipment of Vendor "Y" Ethernet interface (electric) is used. Mirroring of traffic from given interface is provided by Vendor "X".
6) Vendor "Y" provides mirroring of traffic from Ethernet interface between BRAS equipment and equipment of AAA server.
7) Host A.1 is PPPoE client. Host A.1 is connected to home gateway HG1 (by Ethernet interface). HG1 equipment works in a bridged mode.
8) Access node equipment works as PPPoE intermediate agent, providing addition PPPoE tag (0x0105 Vendor-Specific) in all PPPoE messages transferred by clients in direction to BRAS equipment during phase of connection establishment (discovery stage).
9) BRAS equipment works as PPPoE server, terminating corresponding client sessions. BRAS equipment hands over information on user line identification received within PPPoE tag framework from access node, in direction to AAA server using RADIUS protocol.
10) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoe RADIUS.
|
+| Test procedure | 1) Initiate establishment of PPPoE session from host A.1.
2) Save the captures of traces in separate files ([Vendor]-AN-BRAS_COMP_02.txt) and put the file into the corresponding section of the KB.
3) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) On phase of connection establishment (discovery stage) access node equipment during processing of PPPoE discovery messages provides addition of PPPoE tag (0x0105 Vendor-Specific) into these messages.
2) BRAS equipment, having received in PPPoE tag framework information related with user line identification, correctly broadcasts given information in direction to AAA server inside attribute of RADIUS Access-Request message.
3) Successful establishment of PPPoE session for host A.1.
4) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+**Test scheme**
+
+Diagram of the test scheme showing the network architecture. On the left, Host A.1 (Client PPPoE) is connected to HG1 (bridged mode) which is part of AT&RONT. HG1 is connected to an Access Node (Vendor 'X') containing a PPPoE Intermediate Agent and a DSLAM/MSAN/VOLT. The Access Node is connected via Ethernet to a BRAS (Vendor 'Y') which contains a Server PPPoE. The BRAS is connected to a Server AAA. A Protocol analyzer is connected to the BRAS and Server AAA via RADIUS and PPPoE filters. The diagram shows the flow of PPPoE discovery stage packets from Host A.1 through the Access Node to the BRAS, and the subsequent RADIUS authentication process.
+
+| | |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | AN-BRAS_COMP_03 |
+| Test name | Information transfer about characteristics of DSL user lines |
+| Test purpose | Check if there is compatibility of access node equipment (DSLAM/MSAN/EAS/OLT) and BRAS equipment of various vendors, considering maintenance of DSL user lines characteristics information transfer procedure |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) Vendor "X" represents the access node equipment (e.g., DSLAM/MSAN and also the home gateways equipment HG1 and HG). Vendor "X" provides two user lines ADSL/ADSL2/ADSL2 +/VDSL2 for connection of the home gateway equipment to access node equipment.
- 4) Vendor "Y" provides BRAS equipment and the equipment of AAA server. AAA server is external in relation to BRAS equipment and is connected on Ethernet interface (electric). AAA server is RADIUS server. BRAS equipment supports functionality of PPPoE server, DHCP server (possibility of use of external DHCP server is supposed) and functionality of RADIUS client.
- 5) For connection establishment between access node equipment of vendor "X" and BRAS equipment of vendor "Y" Ethernet interface (electric) is used. Mirroring of the traffic from the given interface is provided with vendor "X".
- 6) Vendor "Y" provides mirroring of traffic from Ethernet interface between BRAS equipment and equipment of AAA server.
- 7) Host A.1 is DHCP client. Host A.1 is connected to home gateway HG1 (by Ethernet interface). HG1 equipment works in a bridged mode.
- 8) Host B.1 is PPPoE client. Host B.1 is connected to home gateway HG2 (by Ethernet interface). HG2 equipment works in a bridged mode.
- 9) Access node equipment works as Layer 2 DHCP relay agent, providing addition of option 82 in all DHCP messages transferred by clients in direction to BRAS equipment. Function Layer 2 DHCP relay agent should be activated for that user's port of access node to which HG1 equipment/host A.1 is connected.
|
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 10) During functioning as Layer 2 DHCP relay agent access node equipment should provide an information transfer about characteristics of user line, including actual speed of data transmission in user line (upstream/downstream actual data rate) and minimum speed of data transmission in user line (upstream/downstream minimum data rate). Information on characteristics of user line should be transferred in option 82 inside field vendor-specific sub-option.
11) Access node equipment works as PPPoE intermediate agent, providing addition of PPPoE tag (0x0105 Vendor-Specific) in all PPPoE messages transferred by clients in direction to BRAS equipment during phase of connection establishment (discovery stage).
12) During functioning as PPPoE intermediate agent, the access node equipment should provide information about characteristics of user line, including actual speed of data transmission in user line (upstream/downstream actual data rate) and minimum speed of data transmission in user line (upstream/downstream minimum data rate). Information on characteristics of user line should be transferred in additional fields of PPPoE tag expansion (Vendor-Specific).
13) BRAS equipment performs reception of information on characteristics of user line transferred from access node inside DHCP option 82 or PPPoE tag, and provides transfer of given information to direction of AAA server inside Access-Request RADIUS message. Information transfer about characteristics of user line is performed inside RADIUS attributes 'Vendor Specific Attributes'.
14) Perform on the analyser of IP protocols for the corresponding interface and set the following filter on protocols: pppoed bootp RADIUS.
|
+| Test procedure | 1) Initiate establishment of IPoE session from host A.1.
2) Initiate establishment of PPPoE session from host B.1.
3) Save the captures of traces in separate files ([Vendor]-AN-BRAS_COMP_03.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Access node equipment provides information transfer about characteristics of user line within limits of option 82 DHCP.
2) Access node equipment provides information transfer about characteristics of user line in frameworks PPPoE tag (Vendor-Specific).
3) BRAS equipment, having received information on characteristics of user line inside DHCP option 82 or PPPoE tag, correctly broadcasts given information in direction to AAA server inside Access-Request RADIUS message.
4) Successful establishment of IPoE and PPPoE sessions for A.1 and B.1 hosts, accordingly.
5) The daily report form has been saved in the corresponding section of KB.
|
+
+
+
+**Test scheme**
+
+The diagram illustrates a network test scheme. On the left, under 'Vendor "X"', Host A.1 (Client DHCP) is connected to HG1 (bridged mode, AT&RVTUR), which is connected to the DSLAM/MSAN via iPoE. Host B.1 (Client PPPoE) is connected to HG2 (bridged mode, AT&RVTUR), which is connected to the DSLAM/MSAN via PPPoE. The DSLAM/MSAN contains a Layer 2 DHCP Relay Agent on port 1 and a PPPoE Intermediate Agent on port 2. An Ethernet connection links the DSLAM/MSAN to the BRAS under 'Vendor "Y"'. The BRAS contains a Server PPPoE and a Server DHCP. The BRAS is also connected to a Server AAA (RADIUS). A Protocol analyzer is connected to the BRAS. Dashed lines indicate traffic paths: DHCP/PPPoE (discovery) from Host A.1 and Host B.1 through the DSLAM/MSAN to the BRAS; DHCPoption82 || PPPoE(discovery)+TAG from the BRAS to the Server AAA (RADIUS); and RADIUS traffic between the BRAS and the Server AAA (RADIUS). Filters are applied: 'filter: bootp || pppoe' on the path to the protocol analyzer, and 'filter: radius' on the path from the protocol analyzer to the Server AAA (RADIUS).
+
+Test scheme diagram showing network architecture with Vendor 'X' and Vendor 'Y' equipment. Vendor 'X' includes Host A.1 (Client DHCP), Host B.1 (Client PPPoE), HG1 (bridged mode), HG2 (bridged mode), and DSLAM/MSAN. Vendor 'Y' includes BRAS and Server AAA (RADIUS). A protocol analyzer is connected to the BRAS. Dashed lines show DHCP/PPPoE discovery and RADIUS traffic paths.
+
+#### 6.3.2.2 Check of compatibility of the access node and home gateway equipment of various vendors
+
+| | |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test number | DSL_COMP_01 |
+| Test name | Check of compatibility of home gateway equipment and DSLAM/MSAN equipment |
+| Test purpose | Check if there is a compatibility of home gateway DSL equipment (ATU R/VTU R) and access node equipment (DSLAM/MSAN) from various vendors |
+| Initial condition | - 1) Prepare in the KB the specified form to be filled-in (template of daily report) which should include the date, list of tests and achieved results.
- 2) Connect equipment under test and measurement equipment in accordance with testing scheme.
- 3) Vendor "X" provides access node equipment DSLAM/MSAN with support of cards ADSL2/ADSL2 +/VDSL2/SHDSL. Vendor "X" provides user line (twisted pair) for connection of home gateway DSL equipment to access node equipment.
- 4) Vendor "Y" provides home gateway DSL equipment (ADSL2/ADSL2 +/VDSL2/SHDSL) – HG1.
- 5) Vendor "X" provides specification of DSLAM/MSAN access node equipment in the following style:
|
+
+| | | |
+|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|
+| | | |
+| | General information on DSLAM/MSAN access node equipment | |
+| | Name and product updating | _____ |
+| | Version of hardware maintenance | _____ |
+| | Software version | _____ |
+| | Types of supported linear cards | _____ |
+| | Supported standards DSL | _____ |
+| | Characteristics ADSL2/ADSL2+ | |
+| | Maximum supporting speed – downstream (Net Data Rate) | _____ |
+| | Maximum supporting speed – upstream (Net Data Rate) | _____ |
+| | Characteristics VDSL2 | |
+| | Maximum supporting speed – downstream (Net Data Rate) | _____ |
+| | Maximum supporting speed – upstream (Net Data Rate) | _____ |
+| | Characteristics SHDSL | |
+| | Maximum supporting speed – downstream (Net Data Rate) | _____ |
+| | Maximum supporting speed – upstream (Net Data Rate) | _____ |
+| | 6) Vendor "Y" provides specification of home gateway DSL equipment in the following style: | |
+| | General information on home gateway DSL equipment | |
+| | Name and product updating | _____ |
+| | Supported standards DSL | _____ |
+| | Version of hardware maintenance | _____ |
+| | Software version | _____ |
+| | Serial number | _____ |
+| | Characteristics ADSL2/ADSL2+/VDSL2/SHDSL | |
+| | Maximum supporting speed – downstream (Net Data Rate) | _____ |
+| | Maximum supporting speed – upstream (Net Data Rate) | _____ |
+| | 7) Home gateway equipment HG1 is connected to DSLAM/MSAN access node equipment on DSL interface taking into account specifications of equipment, provided by vendor "X" and vendor "Y".
8) Host A.1 is connected to home gateway HG1 on Ethernet interface.
9) Home gateway HG1 functions in the bridged mode.
10) Host X.1 is connected on Ethernet interface directly to (uplink) DSLAM/MSAN equipment. Possibility of connection of host X.1 to DSLAM/MSAN equipment through Ethernet switch is assumed. In the last case Ethernet switch is given by vendor "X". | |
+
+| | |
+|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | 11) IP addresses of hosts A.1 and X.1 are from the same IP subnetwork.
12) Establish on hosts A.1 and X.1 IPerf utility, allowing testing of accessible throughput of data link. Further during start of IPerf utility as client part it is necessary to use host A.1, and as server part – host X.1.
|
+| Test procedure | 1) Initiate establishment of DSL connection between home gateway equipment HG1 and access DSLAM/MSAN equipment.
2) Perform traffic transfer by means of IPerf utility between hosts A.1 and X.1 in both directions (upstream/downstream) within 15 minutes.
3) Save the captures of traces in separate files ([Vendor]-DSL_COMP_01.txt) and put the file into the corresponding section of the KB.
4) Fill in a daily report form with the testing results and save it in the KB.
|
+| Expected result | 1) Interval of time from moment of initiation of DSL connection on HG1 equipment till the moment of showtime condition does not exceed 60 seconds (train time s).
2) There is possibility of successful establishment of connection and data exchange between HG1 equipment and DSLAM/MSAN according to standards declared in specifications.
3) The daily report form has been saved in the corresponding section of KB.
|
+| Test scheme | Image: Test scheme diagram showing Host A.1 connected to HG1 (bridged mode) via Ethernet. HG1 is connected to DSLAM/MSAN via DSL. DSLAM/MSAN is connected to a Switch Ethernet via Ethernet. Switch Ethernet is connected to Host X.1 via Ethernet. A Simulator/Analyzer of traffic is connected to both Host A.1 and Host X.1 via dotted lines. The diagram is divided into two vendor regions: Vendor 'Y' (containing Host A.1 and HG1) and Vendor 'X' (containing DSLAM/MSAN, Switch Ethernet, and Host X.1).
graph LR subgraph Vendor_Y [Vendor "Y"] HA1[Host A.1] -- Ethernet --> HG1["HG1
(bridged mode)
ATU-R/VTU-R"] end subgraph Vendor_X [Vendor "X"] DSLAM["DSLAM/MSAN"] -- DSL --> HG1 subgraph DSLAM内部 [ ] direction LR ATU["ATU-C/VTU-O"] --- FE["FE/GE"] end FE -- Ethernet --> SE["Switch Ethernet"] SE -- Ethernet --> HX1[Host X.1] end HA1 -.-> SAT["Simulator/Analyzer of traffic"] HX1 -.-> SAT style Vendor_Y fill:none,stroke-dasharray: 5 5 style Vendor_X fill:none,stroke-dasharray: 5 5 style DSLAM内部 fill:none,stroke:none
|
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6641455ab8f6a4aa2368db84ad8e90ad33caf0e5
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e36e623674d0ffee33dcd5083f81bb72e0ef4be4933d253c01b0f7584ed88ebd
+size 65898
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e48e11052ae36b8779f9acd5a057ae1cfc08570
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/28d75f39a24203712ee907b32cf0bbe5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ed480ce68f2b323d263a1939fd64efab9c43ef1a27a73667ccb061048d93e7e
+size 45269
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2f60a12dcbd226f5596a6902aeb5604d611cd67
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70024c6cfe1f8a121a77e0e800372eed6ba1c125ae63b274991f6dfa86c59b04
+size 19881
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d857c32bd6c9ddc1bf5d24181449cb9d3c29029e
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:725fcd6cbc19a7776a7236501c3c830a3d24458a8824622abd1e031cd305e39f
+size 72937
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aedf1151177b786a92754a3222427d097592ffc8
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/802707b774f2d2973b49cea2020e8453_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d281360d4faf6d13114cc31a9e721b94380ff8a3f7770ed8725a6161500be610
+size 46759
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3eaa33367045c22e385853b196d878900a468583
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:705e15d71a71e303be7961ea9a92b79ce156fa01726c3614ae3dbdc78e1452bc
+size 24973
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..71494113597c55a39dbef7a3273fdb5be00315e2
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:651ab44cd96087a99b4e8aba0d6d95cd480d9a1e47081229a4a17f5e2b8e8bf3
+size 31977
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef
+size 3635
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..485df638c6e101fe0a63d3ac94cf9c0805994b26
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b2cc37ae1974ec7b87b91f54963b855d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9cbd37aa093f5bf50e9dde45930b5228355ab3179aecfed33427bff13141e3be
+size 35672
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08ae2ed4691a6ce36ebaa3fe83ac7c7835920730
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d6122a3fe6934bd1f3fbb111d5d1606ac29e08053f16420bb24440981cc2140f
+size 44421
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4c5f48730703273a1fe46e2aab0b4cf74fa64e9
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fc1240177a17e3e16ecb3da95722da62298ce3b6039683f8dbab2cdda061012
+size 23036
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..864b316940d8761c5ff25f3d42ca26546cabe474
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:833da5cb93a5c0a2fa5c7d8f8e333fb82e2c77997af9aef399b0c8318a604dea
+size 65595
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3164d908ad57995d1060010a86af560e961b11df
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c05eda72f36938f00f176341b4701c03bbc6841d583a5b28a1a8c32671fce9da
+size 72988
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8416bfafaec02edcacf4798507305c60684b764a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:234ef729d9b0f5252889c6c33cd628abbc0d3eea310cf42a5babff0aef71827a
+size 14278
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66116619a68b4db80e001dfa686109fef54fcf98
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f2fe814dc80d404ca201e14f61304109b6f019609f7f3ea1c71aaeab4906851
+size 29495
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b4c65b053dd5dd9f65975ab5b2d63fc18883798
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfd0f7cd638deed8e323fbe6f90f2da50dc87bdfffc6a46e103325450ee21f76
+size 73027
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..edd87c25a36d596417b4920bfcc50201790f0e25
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/ccf6853c7291703cb04568057fef5849_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:721bb98a21d866057b5d9e8a1962df42a5c1cd0435593bef533ec7f9aca64be4
+size 56278
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eb54f687029bb6633886fd8467eeb70d7a4d2cd8
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d3b5eac55166fc428a223bba5c46961b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce9b41174749c17e436407be34c7ac2d4f306944c02101b0e1e82a6b4659e219
+size 44564
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d9c034cd43309288cb109b76ffb7418d_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d9c034cd43309288cb109b76ffb7418d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5cb1d6723fbc96d993357b79a87a98c72f3f9732
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/d9c034cd43309288cb109b76ffb7418d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a1563b7077f901cb7237aeb45ad0e34e8a2ba185161bcc483c115bc97f42f99
+size 39219
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..894b6cb4248564c648344c33f02f5fe09b7f7dfa
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75ca705154495937eef1bbff36f65791c16c4bcb3614e747594ffe6eba65a66d
+size 69872
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c4557efdd9e1614e3715b39b7c2e91e3b9718e1
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fbfa653853daf5541118a9ddecb92284_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63a0b50fc56e2ad5563c656cba72514d17cdf3ee0d2aa51396414d4ff9cd4559
+size 27783
diff --git a/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..43ee8bdd1942ab816e28a7b301a7c2090c9e2204
--- /dev/null
+++ b/marked/Q/T-REC-Q.3930-201208-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9c11a5e7e87d2a0da76d2372de6d0e10624e16a755f537166b54056678813e9
+size 34892
diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2db69df27dc6c6e9cde82b6d11cc060266ee8e7c
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/raw.md
@@ -0,0 +1,622 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3932.1**
+
+(06/2015)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for next generation networks
+
+---
+
+**IMS/NGN performance benchmark – Part 1: Core concept**
+
+Recommendation ITU-T Q.3932.1
+
+ITU-T
+
+
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in a blue, sans-serif font.
+
+ITU logo: A globe with a red lightning bolt, next to the text 'International Telecommunication Union'.
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.3932.1
+
+### IMS/NGN performance benchmark – Part 1: Core concept
+
+## Summary
+
+Recommendation ITU-T Q.3932.1 provides the first part of a multi-part deliverable covering the IP multimedia subsystem (IMS)/next generation networks (NGN) performance benchmark, as identified below:
+
+### **Part 1: Core concepts;**
+
+Part 2: Subsystem configurations and benchmarks;
+
+Part 3: Traffic sets and traffic profiles;
+
+Part 4: Reference load network quality parameters.
+
+This Recommendation describes the performance benchmark methodology for the IMS based services multimedia telephony (MMTel), video telephony and IMS/PES. The terminology and concepts are described in Recommendation ITU-T Q.3930.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3932.1 | 2015-06-13 | 11 | 11.1002/1000/12495 |
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-----------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 2 |
+| 3.1 Terms defined elsewhere ..... | 2 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 3 |
+| 5 Conventions ..... | 4 |
+| 6 Benchmark information model ..... | 4 |
+| 6.1 Use case ..... | 5 |
+| 6.2 Benchmark test ..... | 7 |
+| 6.3 Benchmark report ..... | 9 |
+| 7 System under test (SUT)..... | 9 |
+| 8 Test system ..... | 13 |
+| 9 Benchmark metrics examples ..... | 13 |
+
+
+
+## Recommendation ITU-T Q.3932.1
+
+## IMS/NGN Performance benchmark – Part 1: Core concept
+
+# 1 Scope
+
+Recommendation ITU-T Q.3932.1 provides the first part of a multi-part deliverable covering the IMS/NGN performance benchmark, as identified below:
+
+### **Part 1: Core concepts;**
+
+Part 2: Subsystem configurations and benchmarks;
+
+Part 3: Traffic sets and traffic profiles;
+
+Part 4: Reference load network quality parameters.
+
+The present Recommendation describes the performance benchmark methodology for the IMS based services MMTel, video telephony and IMS/PSTN emulation solution (PES). The terminology and concepts are described in [ITU-T Q.3930].
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T P.56] Recommendation ITU-T P.56 (2011), *Objective measurement of active speech level*.
+- [ITU-T P.862] Recommendation ITU-T P.862 (2001), *Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs*.
+- [ITU-T P.862.1] Recommendation ITU-T P.862.1 (2003), *Mapping function for transforming P.862 raw result scores to MOS-LQO*.
+- [ITU-T P.863] Recommendation ITU-T P.863 (2014), *Perceptual objective listening quality assessment*.
+- [ITU-T Q.3930] Recommendation ITU-T Q.3930 (2012), *Performance testing of distributed systems – Concepts and terminology*.
+- [ITU-T Q.3932.2] Recommendation ITU-T Q.3932.2 (2015), *IMS/NGN performance benchmark – Part 2: Subsystem configurations and benchmarks*.
+- [TS 101 563] ETSI TS 101 563 V.1.3.1 (2014), *Speech and multimedia Transmission Quality (STQ); IMS/PES/VoLTE exchange performance requirements*.
+- [TS 123 002] ETSI TS 123 002 (V11.6.0) (2013), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 11.6.0 Release 11)*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+The IMS benchmarking definitions are described in [ITU-T Q.3930].
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 background load:** Workload applied to a system under test (SUT) during a benchmark test, for the purpose of consuming SUT resources during a benchmark test and changing the traffic intensity at which the capacity of the SUT is reached.
+
+**3.2.2 benchmark report:** Document generated at the conclusion of a test procedure containing the metrics measured during the execution of the test and/or computed from the data collected in the benchmark log.
+
+**3.2.3 benchmark test:** Procedure by which a test system interacts with a system under test (SUT) to measure its behaviour and produce a benchmark report.
+
+**3.2.4 configuration:** Specification of a subset of IMS/PES architectural elements and metrics for which collection of benchmark tests can be defined.
+
+**3.2.5 design objective (DO):** Probabilistic model of delay and failure requirements for SUT, associated with a use case, specified by threshold values and probabilities for delay and scenario failure.
+
+**3.2.6 design objective capacity (DOC):** Largest load a SUT can sustain while not exceeding design objectives (DOs) defined for a use case.
+
+**3.2.7 idle load:** Load that is not dependent on the traffic or other external activities.
+
+**3.2.8 maximum capacity:** maximum processor load that a processor can handle without rejecting new calls.
+
+**3.2.9 metric:** Performance measurement of a system under test (SUT) reported in a benchmark report.
+
+**3.2.10 parameter:** Attribute of a SUT, test system, system load, or traffic set whose value is set externally and prior to a benchmark test, and whose value affects the behaviour of the benchmark test.
+
+**3.2.11 processor load:** Amount of time the processor executes work. It is normally expressed in percent.
+
+NOTE – The processor load consists of idle load, traffic load and usage load.
+
+**3.2.12 reference call (RC):** Basic ISDN user part (ISUP) to ISUP call connected through two media gateways (MGWs) in the same media gateway controller (MGC) domain.
+
+**3.2.13 session attempts per second (SAPS) increase amount:** Increment by which the average SAPS changes between steps of a profile.
+
+**3.2.14 test parameters:** Parameters whose values determine the behaviour of a benchmark test.
+
+**3.2.15 test procedure:** Specification of the steps to be performed by a benchmark test.
+
+**3.2.16 test scenario:** Specific path through a use case, whose implementation by a test system creates a system load.
+
+**3.2.17 test system:** Collection of hardware and software which presents a system load to a system under test (SUT) and collects data on the SUT's performance, from which metrics can be computed.
+
+**3.2.18 traffic load:** Load that results from handling traffic events that are directly related to calls.
+
+NOTE – This load varies with the traffic intensity.
+
+**3.2.19 traffic-time profile:** Evolution of the average scenario over a time interval.
+
+**3.2.20 traffic set:** Mixture of traffic scenarios.
+
+**3.2.21 usage load:** Load that is reserved for the administration's operation and maintenance activities during busy hour.
+
+**3.2.22 workload:** Number of reference calls per second (RC/s).
+
+NOTE – It is calculated by multiplying calls per second by its corresponding workload factor (WLF).
+
+**3.2.23 workload factor (WLF):** Traffic load for different types of calls in relation to the traffic load of the reference call (ISUP call).
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|-----------------------------------------|
+| AGCF | Access Gateway Control Function |
+| BGCF | Breakout Gateway Control Function |
+| BYE | BYE message |
+| CN | Core Network |
+| CPU | Central Processor Unit |
+| CS | Circuit Switched |
+| CSCF | Call Server Control Function |
+| DO | Design Objective |
+| DOC | Design Objective Capacity |
+| ETH | Ethernet |
+| HSS | Home Subscriber Server |
+| FM | Fault Management |
+| IBCF | Interconnection Border Control Function |
+| II-NNI | Inter-IMS Network to Network Interface |
+| IM | IP Multimedia |
+| IMS | IP Multimedia Subsystem |
+| IP | Internet Protocol |
+| ISC | IP multimedia Service Control |
+| ISDN | Integrated Service Digital Network |
+| ISUP | ISDN User Part |
+| LCS | Location Services |
+| LRF | Location Retrieval Function |
+| MCS | Modulation and Coding Scheme |
+| MGC | Media Gateway Controller |
+| MGW | Media Gateway |
+| MHT | Mean Holding Time |
+
+| | |
+|---------|---------------------------------------------------------------|
+| MME | Mobile Management Entity |
+| MMTel | Multimedia Telephony |
+| MRB | Media Resource Broker |
+| MRF | Media Resource Function |
+| MRFP | Media Resource Function Processor |
+| NGN | Next Generation Networks |
+| NNI | Network-to-Network Interface |
+| PES | PSTN Emulation Solution |
+| PESQ | Perceptual Evaluation of Speech Quality |
+| POLQA | Perceptual Objective Listening Quality Assessment |
+| POTS | Plain old telephone service |
+| RC | Reference Call |
+| RTP | Real-Time Protocol |
+| SAPS | Session Attempts Per Second |
+| S-CSCF | Serving CSCF |
+| SIGTRAN | Stream Control Transmission Protocol |
+| SIP | Session Initiation Protocol |
+| SIP-I | a mapping from SIP to ISUP |
+| SLF | Subscription Locator Function |
+| SUA | SCCP-User Adaptation Layer |
+| SUT | System Under Test |
+| TA | Tones and Announcement |
+| TDM | Time-division multiplexing |
+| UDI | Unrestricted Digital Information |
+| UDI/TA | Unrestricted Digital Information with tones and announcements |
+| UE | User Equipment |
+| VGW | Voice Gateway |
+| WLF | Workload factor |
+
+# 5 Conventions
+
+None.
+
+# 6 Benchmark information model
+
+In this clause, "benchmark information model" refers to the structure of the information elements that define the benchmark. This **information** model is depicted in Figure 1.
+
+The information model consists of three primary elements: use cases, which describe the behaviour of an individual user, and which in turn define scenarios; benchmark tests, which generate a workload by aggregating the behaviour of individual scenarios in a controlled manner, and collect log files of measurements during the test; and benchmark test reports, which report metrics interpreted from the benchmark test log files.
+
+
+
+The diagram illustrates the IP multimedia subsystem (IMS) benchmark information model, organized into three main columns: Use case, Benchmark test, and Test report.
+
+- Use case 1: MMTel - (registration)**
+ - Scenario 1.1: e.g., user not registered**
+ - Call flows
+ - Load profiles
+ - Design objectives
+ - Metrics
+ - SUT parameters
+ - Scenario 1.2: (e.g., user already registered)**
+- Use case 2: MMTel - Session setup**
+ - Scenario 2.1: call successful**
+ - Call flows
+ - Load profiles
+ - Design objectives
+ - Metrics
+ - SUT parameters
+ - Scenario 2.2: user not found**
+- Benchmark test**
+ - Traffic set**
+ - X % of scenario 1.1
+ - X % of scenario 1.2
+ - X % of scenario 2.1
+ - X % of scenario 2.2
+ - Traffic time profile
+ - SUT characteristic
+ - Background load
+- Test report**
+ - Metrics and graphics with design objective capacity
+ - Call detail report
+ - Voice quality summary report
+ - Voice quality detail report
+ - Error summary report
+ - Error detail report
+ - Voice quality error summary report
+ - Voice quality error detail report
+
+Arrows indicate the flow from Use cases to Benchmark tests and from Benchmark tests to Test reports. Specifically, arrows from the scenarios in Use cases point to the Traffic set in the Benchmark test, and an arrow from the Benchmark test points to the Test report.
+
+Diagram of the IP multimedia subsystem (IMS) benchmark information model showing the relationship between Use cases, Benchmark tests, and Test reports.
+
+Q.3932.1(15)\_F01
+
+**Figure 1 – IP multimedia subsystem (IMS) benchmark information model**
+
+## 6.1 Use case
+
+The top level of the individual behavioural model is the use case. A use case describes: The goal that a user has in interacting with a system, the various actors (e.g., other users, network elements) that participate in the use case, the basic course of events that are carried out by the user and the SUT, the design objective (DO) of the use case, the possible outcomes that apply to the use case, and the metrics to be collected. The goal and actors of a use case are documented in narrative text and diagrams; the other elements are complex information elements, which are described in their respective clauses.
+
+### **6.1.1 Call flow**
+
+The calls flows define the characteristic message flows, the tones and announcements (TAs) for a specific interface.
+
+### **6.1.2 Load profile**
+
+To facilitate the calculation of processing capacity and the appropriate load profile, the concept of workload factor (WLF) has been defined based on the reference call (RC) for each combination of traffic case and traffic signalling interface. The RC is defined as a basic ISDN user part (ISUP) to ISUP call connected through two media gateways (MGWs) in the same domain.
+
+Based on the WLFs for all different types of calls, the call intensities and the services used, one can express the total traffic load in an equivalent number of RCs per second.
+
+The dimensioning of any type of network depends on a number of different parameters such as utilization per channel, calls per second, mean holding time (MHT), type of accesses being involved and type of services being requested.
+
+#### **6.1.3 Metrics**
+
+The metrics of a use case describe the measurements collected from the execution of a scenario attempt. Typical metrics include response times and message rates. If a scenario is selected for execution in a benchmark test, its metrics are collected. See clause 8 for more detail.
+
+#### **6.1.4 Use case outcomes**
+
+A use case outcome is a set of possible outcomes of the scenarios of a use case. An outcome may be simply "correct", it may reflect an error or failure condition, or it may reflect a correct behaviour that took an excessive amount of time to occur. An instance of a scenario that experiences an error, failure, or timeout outcome is referred to as an inadequately handled scenario attempt.
+
+#### **6.1.5 Scenarios and scenario attempts**
+
+A scenario is a trace of a path through a use case. It is analogous to "call attempt", but applies to all interactions within an IMS/PES network, different bearer and application interactions.
+
+A scenario may succeed, fail, or succeed functionally.
+
+The terms "scenario attempt" and "scenario attempts per second" are used in the present document in place of "call attempt" and "call attempts per second" because IMS is a transaction-oriented system with transactions of a variety of types traffic sets, and in the real world do not operate according to only one transaction type, so the more generalized term is necessary. It would be incorrect and misleading to attempt to report the capacity of a system in "call attempts per second", "registration attempts per second", etc., for system loads that were other than purely call attempts, registration attempts, etc.
+
+#### **6.1.6 Design objective (DO)**
+
+The DO describes the maximal acceptable rate handled scenario attempts for a use case.
+
+#### **6.1.7 Scenario**
+
+A scenario describes a single interaction sequence among the actors of a use case. It is documented by a set of preconditions on its actors (typically specified by parameter values). In the case of IMS/PES the scenario is defined as a set of different bearer capabilities (e.g., speech, 3.1 kHz audio, unrestricted digital information (UDI), unrestricted digital information with tones and announcements (UDI/TA)), services (fax, modem), or dial modes.
+
+## 6.2 Benchmark test
+
+A benchmark by definition measures the behaviour of a population of users. To accomplish this, the behaviours of individual users shall be aggregated into input traffic to the SUT. The input traffic shall be realistic, in the sense that a population of users would perform such actions in the real world, and in the sense that statistical variation in user behaviour is similar to statistical variation that would occur in the real world.
+
+### 6.2.1 Traffic set
+
+The traffic set is a collection of scenarios which are determined to be likely to co-occur in a real-world scenario. The scenarios do not need to come from the same use case. Within a traffic set, each scenario has an associated relative occurrence frequency, interpreted as the probability with which it would occur in the course of the test procedure.
+
+### 6.2.2 Background load
+
+Background load is a workload presented to the SUT in order to consume its resources. It may consist of a stream of traffic presented to the SUT by an external system apart from the test system; or it may be a workload presented to the processing elements, network, or storage subsystem of the SUT.
+
+The purpose of background traffic is to make possible the measurement of a DOC in SUT when the capacity of the test system is insufficient to reach the DOC.
+
+If a benchmark test is published in which background load is used, then the following requirements apply:
+
+- the hardware used to generate the background load shall be fully specified. If the background load is generated by software running directly on the SUT, then the components of the SUT on which the background load is executed shall be fully specified;
+- the software used to generate the background load shall be provided in source form, including makefiles and any other configuration files required to compile the software.
+
+#### 6.2.3 Traffic-time profile
+
+The traffic-time profile is a function describing the average scenario attempt arrival rate as a function of elapsed time during a benchmark test. A traffic-time profile should be chosen in such a manner so that, for a given scenario attempt arrival rate, sufficient samples are generated that metrics can be collected with an appropriate confidence bound. The following call profiler traffic patterns are used today: saw tooth, blast, ramp, steady call rate, rolling blast and Poisson distribution. To get a realistic scenario, a combination of at least two scenarios is needed.
+
+### 6.2.4 Test parameters
+
+The benchmark test parameters are used to control the behaviour of the test script. The data elements required to configure the test system are listed in Table 1.
+
+Table 1 is a non-exhaustive list of test parameters defined for the benchmark standard. The list is expected to grow over time, as additional subsystems and system configurations are developed.
+
+**Table 1 – Test parameters**
+
+| Parameter | Description |
+|------------|--------------------------------------------------------------------------------|
+| Start time | Amount of time that a system load is presented to a SUT at the start of a test |
+| Stop time | Amount of time that a system load is presented to a SUT at the end of a test |
+
+**Table 1 – Test parameters**
+
+| Parameter | Description |
+|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TotalProvisionedSubscribers | The number of simulated subscribers provisioned in the network |
+| PercentSimulatedSubscriber | The average percentage of simulated subscribers |
+| Simulated maximum simultaneous call legs | The number of simulated maximum simultaneous call legs |
+| Traffic per subscriber | Traffic per subscriber; default value 0.1 Erlang |
+| PX_PercentRegisteredSubscribers | The average percentage of simulated subscribers that are registered simultaneously |
+| PX_PercentRoamingSubscribers | The average percentage of simulated subscribers that are roaming (i.e., registered in a non-local network) |
+| PX_Simulated Subscriber Registration Parameters | Parameters and distributions of the probabilistic model of simulated subscriber operation |
+| MHT | Mean holding time of a call; default value 110 seconds |
+| Ringing time | Duration between (180 ringing and 200 OK INVITE )
Default value 1-5 s |
+| NoS | Number of subscribers originating traffic per subscriber |
+| CAPS/BHCA | Call attempts per second/busy hour call attempts |
+| WLF for call controller | The WLF for call controller for a specific configuration. Default value 1-3 |
+| WLF for gateway controller | The WLF for gateway controller for a specific configuration. Default value 1-3 |
+| WLF for MGW | The WLF for MGs for a specific configuration. Default value 1-3 |
+| Time-division multiplexing TDM trunks | Number of TDM trunks |
+| Ethernet (ETH) | Number of ETH connections |
+| Type of call | MMTel fixed access to MMTel fixed access
Video telephony
IMS/PES to IMS/PES
MMTel fixed access to IMS/PES |
+| Protocol call type and interfaces | SIP-I
ISUP
Steam control transmission protocol (SIGTRAN) (M2PA; M2UA; M3UA; SCCP-user adaptation layer (SUA))
Session initiation protocol (SIP) inter-IMS network to network interface (II NNI) (Ici,Izi)
SIP NNI (Mx Interface)
Gm interface |
+| MGCF/MGW/I-BCF/TrMGW performance tests | SIP-I to SIP-I
SIP-I to ISUP
SIP-I to network-to-network interface (NNI)
NNI to NNI |
+
+**Table 1 – Test parameters**
+
+| Parameter | Description |
+|----------------------|-------------------------------------------------------------------------------------------------|
+| | SIGTRAN to SIGTRAN (M2PA; M2UA; M3UA; SUA) |
+| | ISUP (SIGTRAN) to NNI |
+| Transport interfaces | Voice over LTE (VoLTE) (LTE-Uu, S1-U, S-11, S6a, S11, S5/S8, Rx, Gx, Mw, ISC and Ut interfaces) |
+| | ETH |
+| | xDSL |
+| | Integrated services digital network (ISDN) |
+| | Plain old telephone service (POTS) (Z) |
+
+## 6.3 Benchmark report
+
+A test report is a document, with accompanying data files, that provides a full description of an execution of a benchmark test on a test system. The SUT and test system, as well as their parameters, are described in sufficient detail that an independent test site can replicate the test. The results of the test include: Data, represented as charts and data sets, depicting the behaviour of the SUT over the elapsed time of the test; reports of the relevant metrics that are conventionally used to compare benchmark results of differing SUTs; and a full description of other observations and exceptions noted during the test.
+
+## 7 System under test (SUT)
+
+The IMS performance benchmark covers benchmark tests for the video telephony and multimedia telephony (MMTel) fixed access – IMS/PES.
+
+Figure 2 depicts the IMS reference architecture. The components of the architecture are the primary building blocks, which are either defined by the IMS standard, or defined by external standards and referenced by the IMS. The links between the primary building blocks represent reference points over which the building blocks communicate with each other.
+
+The reference architecture is a logical architecture; no mapping of functional elements to hardware or software components is mandated. And conversely, IMS products as deployed in the real world do not factor neatly into the elements of the reference architecture, which complicates the process of comparing similar products with a benchmark.
+
+The problem can be simplified by observing that there are classes of products which have common subsets of reference architecture elements. For classes defined in this manner, common sets of benchmarks can be defined. The classes defined in this manner are called IMSs, or simply subsystems, and are expected to grow over time, as the IMS marketplace becomes richer.
+
+[ITU-T Q.3932.2], which is part of this multi-part deliverable, maintains a list and description of subsystems.
+
+In order to proceed from a subsystem description to a benchmark test, a complete description of all aspects of the subsystem relevant to the performance of the benchmark shall be present; this is referred to as the system configuration, or SUT configuration. This description starts with an enumeration of the elements of the reference architecture and an enumeration of all reference points that are external to the subsystem (i.e., reference points between elements within the subsystem are "internal"). However, the configuration requires a specification of the hardware elements (e.g., servers, central processor units (CPUs), network configuration and bandwidth) and software elements (e.g., operating system, database system), because even though the metrics reported by the benchmark tests are
+
+measured with respect to such metrics as total round-trip delay of messages and system capacity, the behaviour of IMSs is still an area of study and a thorough understanding of how CPU and network bandwidth utilization behaves during operation is of interest.
+
+Figure 3 depicts the II NNI between two IP multimedia (IM) core network (CN) subsystem networks.
+
+Figure 4 depicts the IMS/LTE basic configuration.
+
+Figure 5 depicts the LTE end-to-end configuration.
+
+Figure 6 depicts the access gateway control function (AGCF)/voice gateway (VGW) session processing model for IMS PES.
+
+![Figure 2 – Overview of IMS functional entities [ETSI TS 123 002]. This diagram illustrates the architecture of an IP Multimedia Subsystem (IMS). At the top, a box labeled 'IP multimedia networks' spans across the top of the diagram. Below this, several functional entities are shown in boxes: CS network, IMS-MGW, MRFP, BGCF (two instances), MGCF, MRFC, P-CSCF, I-CSCF, S-CSCF, HSS, SLF, MRB, AS, E-CSCF, LRF, EATF, IBCF, and TrGW. At the bottom, a UE (User Equipment) is connected to the TrGW. On the right, an LCS client is connected to the LRF. Interfaces are represented by lines: solid lines for user traffic (e.g., Mb, CS, Mp, Gm, Ix, Izi, Ut) and dashed lines for signaling (e.g., Mg, Mk, Mj, Mn, Mr, Mw, Mm, Ma, Cx, C, D, Gc, Gr, Dh, ISC, RC, Cr, I4, Mi, Le, Mm, Ix, Izi). A legend at the bottom left clarifies the line types. A note on the right indicates the source as Q.3932.1(15)_F02.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg)
+
+Figure 2 – Overview of IMS functional entities [ETSI TS 123 002]. This diagram illustrates the architecture of an IP Multimedia Subsystem (IMS). At the top, a box labeled 'IP multimedia networks' spans across the top of the diagram. Below this, several functional entities are shown in boxes: CS network, IMS-MGW, MRFP, BGCF (two instances), MGCF, MRFC, P-CSCF, I-CSCF, S-CSCF, HSS, SLF, MRB, AS, E-CSCF, LRF, EATF, IBCF, and TrGW. At the bottom, a UE (User Equipment) is connected to the TrGW. On the right, an LCS client is connected to the LRF. Interfaces are represented by lines: solid lines for user traffic (e.g., Mb, CS, Mp, Gm, Ix, Izi, Ut) and dashed lines for signaling (e.g., Mg, Mk, Mj, Mn, Mr, Mw, Mm, Ma, Cx, C, D, Gc, Gr, Dh, ISC, RC, Cr, I4, Mi, Le, Mm, Ix, Izi). A legend at the bottom left clarifies the line types. A note on the right indicates the source as Q.3932.1(15)\_F02.
+
+NOTE 1: The reference point CS (Circuit Switched) is not specified in the present document.
+ NOTE 2: The reference point I5 is not shown in this figure.
+
+**Figure 2 – Overview of IMS functional entities [ETSI TS 123 002]**
+
+
+
+This diagram illustrates the Interconnection of two IM CN subsystem networks, labeled 'IM CN subsystem network A' and 'IM CN subsystem network B'. The networks are connected via an 'II-NNI' (Interconnection Interface), which is highlighted with a red oval and contains the interfaces 'Ici' (signalling) and 'Izi' (bearer).
+ On the left side (Network A), the components include: S-CSCF, I-CSCF, BGCF, ATCF, P-CSCF, IBCF, TrGW, and an MSC server enhanced for ICS or SRVCC. Signalling paths (dashed lines) are shown between S-CSCF, I-CSCF, BGCF, ATCF, P-CSCF, and IBCF. Bearer paths (solid lines) connect the MSC server to TrGW and IBCF to TrGW. Interfaces 'Mx' and 'Ix' are indicated between various components.
+ The right side (Network B) has a similar architecture. The connection between the two networks' TrGWs is a solid line representing the bearer interface 'Izi'.
+
+----- Signalling
+ ————— Bearer
+
+Q.3932.1(15)\_F03
+
+Diagram of II-NNI between two IM CN subsystem networks (A and B).
+
+NOTE: Interface (II-NNI) between two IM CN subsystem networks.
+
+**Figure 3 – II NNI between two IM CN subsystem networks**
+
+
+
+This diagram shows the basic configuration of an IMS/LTE network. A UE (User Equipment) with an IMS UA is connected to an eNodeB via an 'LTE-Uu' interface. The eNodeB is connected to an MME via 'S1-MME' (signalling) and 'S1-U' (bearer) interfaces. The MME is connected to an S-GW via an 'S11' interface. The S-GW is connected to a P-GW via an 'S5' interface. The P-GW is connected to a PCRF via a 'Gx' interface and to the IMS core via an 'SGi' interface. The PCRF is also connected to the MME via an 'Rx' interface.
+ The IMS core contains the following components: HSS, P-CSCF (which includes IMS-ALG and IMS-AGW), I/S-CSCF, and MMTel AS. The HSS is connected to the MME via an 'S6a' interface. The P-CSCF is connected to the HSS via a 'Gm' interface and to the I/S-CSCF via an 'Mw' interface. The I/S-CSCF is connected to the MMTel AS via an 'ISC' interface. The MMTel AS is connected to the HSS via a 'Sh' interface and to the P-CSCF via a 'Cx' interface. Additionally, the UE is connected to the IMS core via 'Ut' interfaces.
+
+Q.3932.1(15)\_F04
+
+Diagram of IMS/LTE basic configuration showing UE, eNodeB, MME, S-GW, P-GW, and IMS core components.
+
+**Figure 4 – IMS/LTE basic configuration**
+
+
+
+This diagram illustrates the LTE end-to-end configuration for IMS services. It is divided into two main sections: HPLMN (Home PLMN) and VPLMN (Visited PLMN), separated by a dashed line.
+ In the HPLMN section, a UE (User Equipment) with an IMS UA (User Agent) connects via LTE-Uu to an eNodeB, which is connected to a Sec-GW. The Sec-GW connects to an MME via S1-MME and S1-U interfaces. The MME connects to an H-PCRF via S6a and to a Diameter agent via S11. The H-PCRF connects to the Diameter agent via Rx. The Diameter agent connects to the IMS core via S6a, S9, and SGI interfaces. The IMS core contains various components: MMTel/RCS Application servers, MRF, HSS, P-CSCF/IMS-ALG/IMS-AGW, I/S-CSCF, IBCF/TrGW, and MRFP. The Diameter agent also connects to an ENUM server, which in turn connects to an IPX.
+ In the VPLMN section, a similar setup exists but with a V-PCRF instead of an H-PCRF. The V-PCRF connects to the Diameter agent via Rx. The Diameter agent in the VPLMN connects to the IMS core via S6a, S9, and SGI interfaces. The IMS core in the VPLMN contains P-CSCF/IMS-ALG/IMS-AGW, IBCF/TrGW, and MRFP. The Diameter agent in the VPLMN also connects to an ENUM server, which connects to an IPX.
+ The diagram shows various interfaces: Ut (orange), S6a (blue), S9 (blue), Rx (blue), Gx (blue), S11 (blue), S1-MME (blue), S1-U (blue), S5 (blue), SGI (blue), Diameter App ID=0 (red), ENUM (red), Ici/Izi (red), and Gm (red).
+
+Figure 5 – LTE end-to-end configuration diagram showing two network paths (HPLMN and VPLMN) with various components like UE, eNodeB, Sec-GW, MME, H-PCRF, Diameter agent, S-GW, P-GW, IMS core, ENUM server, and IPX. The diagram illustrates the flow of signaling and data between these elements across different network domains.
+
+Figure 5 – LTE end-to-end configuration
+
+
+
+This diagram illustrates the AGCF/VGW session processing models. It shows two models: VGW and AGCF. Both models are connected to an RTP cloud.
+ In the VGW model, a UE connects to a P-CSCF, which is connected to an S-CSCF, which is connected to an AS. The P-CSCF is also connected to a VGW, which contains MGC, FM, and SIP UA. The VGW is connected to an MGF, which is connected to the RTP cloud.
+ In the AGCF model, a UE connects to an AGCF, which contains SIP UA, FM, and MGC. The AGCF is connected to an S-CSCF, which is connected to an AS. The AGCF is also connected to an MGF, which is connected to the RTP cloud.
+ The diagram shows various components: AS (Application Server), S-CSCF (Serving CSCF), P-CSCF (PDN CSCF), MGC (Media Gateway Controller), FM (Function Module), SIP UA (SIP User Agent), VGW (VGW), AGCF (AGCF), and MGF (Media Gateway Function).
+
+Figure 6 – AGCF/VGW session processing models diagram showing two models (VGW and AGCF) connected to an RTP cloud. Each model includes components like AS, S-CSCF, P-CSCF, MGC, FM, SIP UA, and MGF. The diagram illustrates the flow of signaling and data between these elements.
+
+Figure 6 – AGCF/VGW session processing models
+
+### Creation of subscriber database
+
+The subscriber database is the data set required to configure the SUT in order to execute a benchmark test. Using the same data, the test system should be able to generate correct traffic.
+
+The present document does not try to specify a complete set, but rather just the subset that will ensure comparable results. All other provisioning information required for correct configuration of a SUT is to be set at the discretion of the SUT provider.
+
+One requirement for a fair benchmark is that the input data is similar for all test-runs. In order for this to happen we have two choices:
+
+- a) provide a database for the subscriber base. However, because we have to ensure scalability for the benchmark, this solution is not feasible;
+- b) provide rules to generate this data and data generators. Algorithms using random generators will be avoided for data that could possibly influence the results.
+
+# **8 Test system**
+
+The test system is used to generate the appropriate load on the SUT. The present document does not mandate any specific test system to be used, although the details of the test system shall be reported in the benchmark report.
+
+The test system should have two main functions:
+
+- traffic generation: the test system shall be able to execute use cases' scenarios following the traffic-time profile. It shall also be able to reproduce the appropriate traffic set (a mix of scenarios with a weight for each of them);
+- network emulation: optionally, network characteristics on the different interfaces should be emulated by the test system.
+
+## **9 Benchmark metrics examples**
+
+The metrics reported by a benchmark test are measured in real time during the execution of the test, or may be computed after completion of the test from event logs collected during the execution. Enclosed is a benchmark matrix based on [ETSI TS 101 563].
+
+**Table 2 – Benchmark metrics examples**
+
+| Delay parameters | Description |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Call request delay | Call request delay is defined as the interval from the instant at which the INVITE message has been received from the SIP subscriber until the 100 Trying from the SBC/P-CSCF is passed back to the subscriber |
+| Alerting sending | Call request delay is defined as the interval from the instant at which the 180 Ringing is received from the terminating subscriber until the 180 Ringing is passed back to the originating subscriber |
+| Call set up delay | The time interval starts when the digit collection function determines that the address information received in the INFO or subsequent INVITE message is sufficient for session initiation, and ends when the INVITE message on the Ic or terminating Gm interface has been sent |
+| Through connection delay | The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating Gm interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating Gm interface |
+| Connection release delay | Connection release delay is defined as the interval from the instant when a BYE message (BYE) is received at the originating or terminating Gm interface until the instant when 200 OK is sent and a corresponding BYE is sent at the terminating or originating Gm interface respectively |
+| Speech quality analysis | |
+| Speech quality | [ITU-T P.862] and [ITU-T P.862.1] |
+| | [ITU-T P.863] |
+| Speech level – active level | [ITU-T P.56] |
+| Speech level – peak | |
+| Speech level – noise | |
+| Speech level – signal to interval noise | |
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fbc06bf97d4bf33e26b453a1602ce986a75a31ba
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:47399445e06db02d12c7c715d5acd09300ee2344a71be75d327ab150fa0d7462
+size 75577
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..525691cea0ea5ac3264b008fa5d7a582e11fe6dc
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454b98c591f24d851c93db0d49f8c19420534cad8210ace800342f2024492fa0
+size 23650
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c8f8c15b3f366b7d4080f7244c83b3f33d204ea
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:116e5017225839bb7324c06a74650855e6093dfeecdb090432eca9ee787510ba
+size 57450
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dad02182b30e94f721c7f50726f60641c96df521
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45bf920a7798c0111eed0c87f3f277105f8935167814eaedd42f96a3f983bba0
+size 4024
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..711545244bf9e5f9abddcd42f24ff2130d5c4f6a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e6f14d9b6e5fd033b82eb4f9ec1b608d9942cfedfc34779383a119b5fcf7233
+size 100294
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d994add8213c96fc4e54a3010645088694f21b26
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03762a50edd3a30af722b42b7244105f31743106ef8988f7ea04c0e24d74ed98
+size 36390
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4022393e79d76198e8a379c4e80941692d562031
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e72a19206801ef55016d12cef4bc6c9e827c7bf8e2ee9ba5e66c9b9f3cf902c8
+size 182035
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..459d9fa4e72114fa7a9206b9e431e929f2097f26
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ccc435d3890d26bb8eb664ec64f3008c752a9afa9644e6ad5177cb07aaa5f72e
+size 11494
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0ecdbad50db7844551dd0afccc92d489e073a6f
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d7cf346f94150790035a6c6944c212ef993b890c2a428b4badbc10cf2b66b95
+size 50921
diff --git a/marked/Q/T-REC-Q.3949-201208-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bffc0c0116b562d041b8849c4c8e8642160bc19d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3949-201208-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7b7700e52e56cca92d58a243bf7837450ea392b8efa328287ac3d21efb93e2b
+size 15537
diff --git a/marked/Q/T-REC-Q.3957-202504-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3957-202504-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..243b3dd39541bdaa7869ecb9b678b3f32103ce51
--- /dev/null
+++ b/marked/Q/T-REC-Q.3957-202504-I_PDF-E/raw.md
@@ -0,0 +1,899 @@
+
+
+# Recommendation**ITU-T Q.3957 (04/2025)**
+
+SERIES Q: Switching and signalling, and associated measurements and tests
+
+Testing specifications – Testing specifications for next generation networks
+
+---
+
+### **Interoperability testing suite for cloud-based control plane and pooled user plane of virtualized broadband network gateway**
+
+
+
+The logo of the International Telecommunication Union (ITU), featuring the letters 'ITU' in blue inside a circle with a globe-like design.
+
+ITU logo
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## **Switching and signalling, and associated measurements and tests**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS NO. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM NO. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900-Q.4099 |
+| Testing specifications for next generation networks | Q.3900-Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000-Q.4039 |
+| Testing specifications for Cloud computing | Q.4040-Q.4059 |
+| Testing specifications for IMT-2020 and IoT | Q.4060-Q.4099 |
+| PROTOCOLS AND SIGNALLING FOR PEER-TO-PEER COMMUNICATIONS | Q.4100-Q.4139 |
+| PROTOCOLS AND SIGNALLING FOR COMPUTING POWER NETWORKS | Q.4140-Q.4159 |
+| PROTOCOLS AND SIGNALLING FOR QUANTUM KEY DISTRIBUTION NETWORKS | Q.4160-Q.4179 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000-Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050-Q.5069 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T Q.3957
+
+# Interoperability testing suite for cloud-based control plane and pooled user plane of virtualized broadband network gateway
+
+## Summary
+
+Recommendation ITU-T Q.3957 aims to specify the interoperability testing suite for cloud-based control plane and pooled user plane (UP) of virtualized broadband network gateway (vBNG), which is based on the signalling requirements of vBNG in Recommendation ITU-T Q.4143. As a background, this Recommendation gives an overview of interoperability testing between the vBNG control plane (vBNG-CP) and vBNG pooled user plane (vBNG-PUP). This Recommendation also deals with interoperability testing of two target areas, including the interoperability testing between vBNG-CP and vBNG-PUP, interoperability testing between vBNG-PUPs, and all the test cases are designed around these two target areas.
+
+## History\*
+
+| Edition | Recommendation | Approval | Study Group | Unique ID |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0 | ITU-T Q.3957 | 2025-04-13 | 11 | 11.1002/1000/16291 |
+
+## Keywords
+
+Cloud-based control plane, interoperability testing, pooled user plane, virtualized broadband network gateway.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2025
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------------------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Overview of IOPT framework for vBNG-CP and vBNG-PUP..... | 2 |
+| 7 Interoperability testing cases between vBNG-CP and vBNG-PUP ..... | 4 |
+| 7.1 Test case: Establish the management channel..... | 4 |
+| 7.2 Test case: Establish the control channel..... | 4 |
+| 7.3 Test case: Establish the service channel..... | 5 |
+| 7.4 Test case: PPPoE ..... | 5 |
+| 7.5 Test case: IPoE ..... | 6 |
+| 7.6 Test case: vBNG-CP (1+1 hot standby deployment) switching between master vBNG-CP and backup vBNG-CP ..... | 7 |
+| 7.7 Test case: vBNG-CP (1:1 cold standby deployment) switching between master vBNG-CP and backup vBNG-CP ..... | 9 |
+| 8 Interoperability testing cases between different vBNG-PUPs..... | 10 |
+| 8.1 Test case: vBNG-PUP joins the warm standby group..... | 10 |
+| 8.2 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch over during the user accessing process) ..... | 11 |
+| 8.3 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch over during the forwarding process) ..... | 12 |
+| 8.4 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch back during the user accessing process) ..... | 13 |
+| 8.5 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch back during the forwarding process)..... | 13 |
+| 8.6 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch over during the user accessing process) ..... | 14 |
+| 8.7 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch over during the forwarding process) ..... | 15 |
+| 8.8 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch back during the user accessing process) ..... | 16 |
+| 8.9 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch back during the forwarding process)..... | 17 |
+| 8.10 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch over during the user accessing process) ..... | 18 |
+| 8.11 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch over during the forwarding process) ..... | 19 |
+
+| | Page |
+|---------------------------------------------------------------------------------------------------------------------------------|-------------|
+| 8.12 Test case: Interface switching in vBNG-PUP N:1 cold standby group
(Switch back during the user accessing process) ..... | 20 |
+| 8.13 Test case: Interface switching in vBNG-PUP N:1 cold standby group
(Switch back during the forwarding process)..... | 21 |
+| 8.14 Test case: CGN switching (cold standby) ..... | 22 |
+| 8.15 Test case: CGN switching (warm standby) ..... | 23 |
+
+# Recommendation ITU-T Q.3957
+
+# Interoperability testing suite for cloud-based control plane and pooled user plane of virtualized broadband network gateway
+
+# 1 Scope
+
+This Recommendation specifies the interoperability testing suite for cloud-based virtualized broadband network gateway control plane (vBNG-CP) and pooled user plane (vBNG-PUP). The following aspects are addressed in this Recommendation:
+
+- Overview of interoperability testing (IOPT) framework for vBNG-CP and vBNG-PUP.
+- Interoperability testing cases between vBNG-CP and vBNG-PUP.
+- Interoperability testing cases between different vBNG-PUPs.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.3315] Recommendation ITU-T Q.3315 (2015), *Signalling requirements for flexible network service combination on broadband network gateway*.
+- [ITU-T Q.3719] Recommendation ITU-T Q.3719 (2019), *Signalling requirements for the separation of control plane and user plane in a virtualized broadband network gateway (vBNG)*.
+- [ITU-T Q.4064] Recommendation ITU-T Q.4064 (2020), *Interoperability testing requirements for a virtualized broadband network gateway*.
+- [ITU-T Q.4143] Recommendation ITU-T Q.4143 (2024), *Signalling requirements for cloud-based control plane and pooled user plane of virtualized broadband network gateway (vBNG)*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 broadband network gateway (BNG)** [ITU-T Q.3315]: The access point to the provider's IP network for wireline broadband services.
+
+**3.1.2 virtualized broadband network gateway (vBNG)** [ITU-T Q.4064]: A virtualized solution of a broadband network gateway, attained by using virtualization technologies. vBNG is responsible for user access and traffic forwarding to realize broadband services and is also called virtualized broadband remote access server (vBRAS).
+
+**3.1.3 vBNG control plane** [ITU-T Q.3719]: The vBNG control plane is in charge of the control functions, including authentication, authorization and accounting (AAA) management function, Internet protocol (IP) address management function, user management function, access protocol processing function, and vBNG user plane management function, etc. The vBNG control plane is implemented using the virtualization technologies and deployed in the mode of centralization.
+
+**3.1.4 vBNG user plane** [ITU-T Q.3719]: The vBNG user plane mainly provides user packets switching under the instruction of the vBNG control plane. The vBNG user plane (UP) can be implemented in different types of forwarding hardware, including NP-based dedicated equipment, ASIC-based dedicated equipment, or X86-based commercial equipment.
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-------|-------------------------------------------------|
+| AAA | Authentication, Authorization and Accounting |
+| ACL | Access Control List |
+| CGN | Carrier Grade NAT |
+| CP | Control Plane |
+| CPU | Central Processing Unit |
+| CU | Control plane and User plane |
+| CUSP | Control plane and User plane Separated Protocol |
+| IOPT | Interoperability Testing |
+| IP | Internet Protocol |
+| IPoE | IP over Ethernet |
+| IS-IS | Intermediate System-Intermediate System |
+| NAT | Network Address Translation |
+| PPP | Point-to-Point Protocol |
+| PPPoE | Point-to-Point Protocol over Ethernet |
+| UP | User Plane |
+| vBIT | vBNG Interoperability Tester |
+| vBNG | Virtual Broadband Network Gateway |
+
+## **5 Conventions**
+
+None.
+
+# **6 Overview of IOPT framework for vBNG-CP and vBNG-PUP**
+
+Virtual broadband network gateway (vBNG) serves as the access point to the provider's broadband network. Compared with the traditional vBNG architecture defined in [ITU-T Q.3719], the cloud-based control plane (CP) and pooled user plane vBNG concentrates on the reliability between vBNG-CP and vBNG-PUP. Hence, except for the basic layer 2 and layer 3 functions, the interoperability should include failure detection as well as switching of vBNG-CP and vBNG-PUP.
+
+Since [ITU-T Q.4143] defines the signalling requirements between vBNG-CP and vBNG-PUP, this Recommendation aims to verify whether the interactions are as expected as those described in [ITU-T Q.4143].
+
+There are two target areas that should be considered during interoperability testing (IOPT), as shown in Figure 6-1:
+
+- target area 1: IOPT between vBNG-CP and vBNG-PUP.
+- target area 2: IOPT between vBNG-PUPs.
+
+
+
+Diagram of vBNG architecture showing the Control Plane (CP) connected to multiple User Plane (PUP) units (PUP1, PUP2, PUPn) within a pooled user plane. Red lines with circled numbers 1 and 2 indicate interoperability test areas: 1 between CP and PUP2, and 2 between PUP2 and PUPn. A legend at the bottom right indicates red lines represent 'Interoperability test'. The diagram is labeled Q.3957(25).
+
+**Figure 6-1 – Interoperability testing areas for vBNG-CP and vBNG-PUP of vBNG**
+
+For the target area 1, the IOPT includes user accessing, failure detection and user switching under the instruction of vBNG-CP.
+
+For the target area 2, the IOPT between vBNG-PUPs include standby group switching as well as carrier grade NAT (CGN) backup switching.
+
+The test entities include vBNG-CP and vBNG-PUP, and the IOPT between the entities includes the IOPT of vBNG-CP and vBNG-PUP, vBNG-PUP and vBNG-PUP.
+
+For each target area, specific relevant test cases need to be provided to verify different capabilities in different functions. Noted that the basic test cases are described in [ITU-T Q.4064]. The test cases in this Recommendation concentrate on the new characteristics or different operation steps introduced by the pooling of vBNG-UPs. At the same time, this Recommendation follows the signalling requirements of [ITU-T Q.4143] and provides vBNG-CP and vBNG-PUP IOPT related test cases, as shown in Table 6-1.
+
+**Table 6-1 – Interoperability testing suite overview for cloud-based control plane and pooled user plane of vBNG**
+
+| Target area | Specific relevant test cases |
+|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| Area 1: IOPT between vBNG-CP and vBNG-PUP | Establishing a management channel |
+| | Establishing a control channel |
+| | Establishing a service channel |
+| | Point-to-point protocol over ethernet (PPPoE) |
+| | IP over ethernet (IPoE) |
+| | vBNG-CP switching (hot standby and cold standby) |
+| Area 2: IOPT between vBNG-PUPs | Interface switching over or switching back during the process of the user accessing or forwarding in the warm/cold standby group |
+
+# 7 Interoperability testing cases between vBNG-CP and vBNG-PUP
+
+## 7.1 Test case: Establish the management channel
+
+Table 7-1 shows the test case for establishing the management channel in order to transmit configuration from vBNG-CP to vBNG-PUP.
+
+**Table 7-1 – Test case: Establish the management channel**
+
+| Test description | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test purpose | | To verify that vBNG supports establishing the management channel. | | |
+| Reference | | [ITU-T Q.4143] clause 7.4 | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login to the configuration interface of vBNG-CP. | |
+| | 2 | Stimulus | Configure the loopback addresses of vBNG-CP and vBNG-PUP for underlying Internet protocol (IP) interoperability between vBNG-CP and vBNG-PUP with intermediate system-intermediate system (IS-IS) or static routing. | |
+| | 3 | Stimulus | Enable Netconf function on vBNG-PUP and vBNG-CP respectively and configure SSH connection policy and Netconf connection policy. | |
+| | 4 | Stimulus | Enter the vBNG-PUP view. Create a control plane and user plane separated protocol (CUSP) agent, configure the IP address of the CUSP agent at vBNG-PUP and bind the CUSP agent, as well as the Netconf connection policy. There is the expected result 1. | |
+| | 5 | Stimulus | vBNG-CP delivers the configuration to vBNG-PUP. There is the expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The management channel has been successfully established between vBNG-CP and vBNG-PUP. | |
+| | 2 | Check | vBNG-PUP can receive the command. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+## 7.2 Test case: Establish the control channel
+
+Table 7-2 shows the test case for establishing the control channel in order to transmit the user table entry and report interface/board/device information.
+
+**Table 7-2 – Test case: Establish the control channel**
+
+| Test description | |
+|-------------------------|----------------------------------------------------------------|
+| Test purpose | To verify that vBNG supports establishing the control channel. |
+| Reference | [ITU-T Q.4143] clause 7.4 |
+
+**Table 7-2 – Test case: Establish the control channel**
+
+| | | | | |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP. | |
+| | 2 | Stimulus | Configure the loopback addresses of vBNG-CP and vBNG-PUP for underlying IP interoperability between vBNG-CP and vBNG-PUP with intermediate system-intermediate system (IS-IS) or static route. | |
+| | Step | Type | Description | |
+| Expected results | 3 | Stimulus | Configure CUSP agent on vBNG-PUP and vBNG-CP, configure the IP address of the CUSP agent at the vBNG-PUP side, and bind the CUSP agent. There is expected result 1. | |
+| | Step | Type | Description | Result |
+| | 1 | Check | The control channel has been successfully established between vBNG-CP and vBNG-PUP. | |
+| Notes | | | | |
+| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | |
+
+## 7.3 Test case: Establish the service channel
+
+Table 7-3 shows the test case for establishing the service channel in order to transmit accessing packet from users.
+
+**Table 7-3 – Test case: Establish the service channel**
+
+| | | | | |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test description | | | | |
+| Test purpose | To verify that vBNG supports establishing the service channel. | | | |
+| Reference | [ITU-T Q.4143] clause 7.2 | | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP. | |
+| | 2 | Stimulus | Configure the vBNG-CP and vBNG-PUP loopback addresses for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | Create and bind VxLAN channels on vBNG-PUP and vBNG-CP, configure the source and destination IP addresses. There is expected result 1. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The service channel has been successfully established between vBNG-CP and vBNG-PUP. | |
+| Notes | | | | |
+| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | |
+
+### 7.4 Test case: PPPoE
+
+Table 7-4 shows the test case for the PPPoE access function.
+
+**Table 7-4 – Test case: PPPoE**
+
+| Test description | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test purpose | | To verify that vBNG provides PPPoE access function, which includes providing point-to-point protocol (PPP) connection with vBNG-CPE/vvBNG-CPE and allocating an IP address for the user to access the Internet. | | |
+| Reference | | [ITU-T Q.4064] clause 8.2 | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG. | |
+| | 2 | Stimulus | Configure user access domain name "pppoe" in vBNG-CP. Create a PPPoE user account "test1@pppoe". | |
+| | 3 | Stimulus | Configure the authentication mode as local and configure the address allocation method as local assignment. | |
+| | 4 | Stimulus | vBNG interoperability tester (vBIT) simulates as PPPoE user "test1" dialing in through vBNG-CPE/vvBNG-CPE.
NOTE – vBIT refers to the test tool which can simulate as a user or network equipment to help complete the IOPT of vBNG. | |
+| | 5 | Stimulus | Capture the packets on vBNG-CP. There is expected result 1. | |
+| | 6 | Stimulus | Check the user entry on vBNG-CP. Check whether user "test1" can obtain an IP address. There is expected result 2. | |
+| | 7 | Stimulus | Check the forwarding table on vBNG-PUP. There is expected result 3. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | There are N PPPoE packets uploaded by vBNG-PUP (N depends on the number of vBNG-PUPs). | |
+| | 2 | Check | User "test1" can obtain an IP address and access the Internet. | |
+| | 3 | Check | Only the selected vBNG-PUP has the specific forwarding entry of user "test1". | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+## 7.5 Test case: IPoE
+
+Table 7-5 shows the test case for the IPoE access function.
+
+**Table 7-5 – Test case: IPoE**
+
+| IPoE test description | | | | |
+|------------------------------|-------------|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|--|
+| Test purpose | | To verify that vBNG supports IPoE service, including providing related access and control functions. | | |
+| Reference | | [ITU-T Q.4064] clause 8.1 | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG. | |
+| | 2 | Stimulus | Configure user access domain name "ipoe" in vBNG. Create an IP over ethernet (IPOE) user account "test2@ipoe". | |
+
+**Table 7-5 – Test case: IPoE**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------|
+| | Step | Type | Description | |
+| | 3 | Stimulus | Configure the authentication mode as local and configure the address allocation method as local assignment. | |
+| | 4 | Stimulus | vBIT simulates as IPoE user "test2" dialing in through vBNG-CPE/vvBNG-CPE. | |
+| | 5 | Stimulus | Capture the packets on vBNG-CP. There is expected result 1. | |
+| | 6 | Stimulus | Check the user entry on vBNG-CP. Check whether user "test2" can obtain an IP address. There is expected result 2. | |
+| | 7 | Stimulus | Check the forwarding table on vBNG-PUP. There exists result 3. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | There are N IPoE packets uploaded by vBNG-PUP (N depends on the number of vBNG-PUPs). | |
+| | 2 | Check | User "test2" can obtain an IP address and access the Internet. | |
+| | 3 | Check | Only the selected vBNG-PUP has the specific forwarding entry of user "test2". | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+## **7.6 Test case: vBNG-CP (1+1 hot standby deployment) switching between master vBNG-CP and backup vBNG-CP**
+
+Table 7-6 shows the vBNG-CP switching between the master vBNG-CP and backup vBNG-CP.
+
+**Table 7-6 – Test case: vBNG-CP (1+1 hot standby deployment) switching between master vBNG-CP and backup vBNG-CP**
+
+| | | | | |
+|-------------------------|-------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| Test description | | | | |
+| Test purpose | To verify that vBNG supports vBNG-CP switching. | | | |
+| Reference | [ITU-T Q.4143] clause 7.5 | | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup vBNG-PUP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route; Configure CU channel: service interface, control interface, and management interface. | |
+| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. | |
+
+**Table 7-6 – Test case: vBNG-CP (1+1 hot standby deployment) switching between master vBNG-CP and backup vBNG-CP**
+
+| | | | | |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| | Step | Type | Description | |
+| | 4 | Stimulus | Cut off the CU channel between vBNG-CP and UP (both service/control/management interfaces are cut off), observe the switching between the master and backup vBNG-CP, there is expected result 1; Check the user's accessing status and there is expected result 2. | |
+| | 5 | Stimulus | After all users are accessing successfully, boot them offline and repeat step 3. | |
+| | 6 | Stimulus | Cut off the heartbeat channel between the master and backup vBNG-CP, observe the switching situation of the master and backup vBNG-CP, there is expected result 3; Check the user's accessing status and there is expected result 4. | |
+| | 7 | Stimulus | After all users are accessing successfully, boot them offline and repeat step 3. | |
+| | 8 | Stimulus | Reboot the master vBNG-CP and observe the switching between the master and backup vBNG-CP, there is expected result 5; Check the user's accessing status and there is expected result 6. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The master vBNG-CP changes to backup vBNG-CP, the original backup vBNG-CP upgrades to master vBNG-CP. | |
+| | 2 | Check | Newly accessing users will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP), there is no effect on the former users which have been authenticated and are online. | |
+| | 3 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | |
+| | 4 | Check | Newly accessing users will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP), there is no effect of the former users which have been authenticated and are online. | |
+| | 5 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | |
+| | 6 | Check | Newly accessing users will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP), there is no effect of the former users which have been authenticated and are online. | |
+| Notes | | | | |
+| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | |
+
+## 7.7 Test case: vBNG-CP (1:1 cold standby deployment) switching between master vBNG-CP and backup vBNG-CP
+
+Table 7-7 shows the vBNG-CP switching between master vBNG-CP and backup vBNG-CP.
+
+**Table 7-7 – Test case: vBNG-CP (1:1 cold standby deployment) switching between master vBNG-CP and backup vBNG-CP**
+
+| Test description | | | | |
+|-------------------------|-------------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test purpose | | To verify that vBNG supports vBNG-CP switching. | | |
+| Reference | | [ITU-T Q.4143] clause 7.5 | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route; Configure CU channel: service interface, control interface, and management interface. | |
+| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. | |
+| | 4 | Stimulus | Cut off the CU channel between vBNG-CP and UP (both service/control/management interfaces are cut off), check the switching between the master and backup vBNG-CP, there is expected result 1; Check the user's accessing status and there is expected result 2. | |
+| | 5 | Stimulus | After all users are accessing successfully, boot them offline and repeat step 3. | |
+| | 6 | Stimulus | Cut off the heartbeat channel between the master and backup vBNG-CP, check the switching situation of the master and backup vBNG-CP, there is expected result 3; Check the user's accessing status and obtaining the result. | |
+| | 7 | Stimulus | After all users are accessing successfully, boot them offline and repeat step 3. | |
+| | 8 | Stimulus | Reboot the master vBNG-CP and observe the switching between the master and backup vBNG-CP, there is expected result 5; Check the user's accessing status and there is expected result 6. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | |
+| | 2 | Check | Newly accessing users will not be online during the switching process. The original users will be booted offline. All the users have to redial and will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP). | |
+| | 3 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | |
+
+**Table 7-7 – Test case: vBNG-CP (1:1 cold standby deployment) switching between master vBNG-CP and backup vBNG-CP**
+
+| | Step | Type | Description | Result |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| | 4 | Check | Newly accessing users will not be online during the switching process. The original users will be booted offline. All the users have to redial and will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP). | |
+| | 5 | Check | The master vBNG-CP changes to backup, the original backup vBNG-CP upgrades to master. | |
+| | 6 | Check | Newly accessing users will not be online during the switching process. The original users will be booted offline. All the users have to redial and will be authenticated and be online on the master vBNG-CP (the original backup vBNG-CP). | |
+| Notes | | | | |
+| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | |
+
+# 8 Interoperability testing cases between different vBNG-PUPs
+
+Here, the "warm standby group" of vBNG-PUP means a group of accessing interfaces from different vBNG-PUP with a warm standby mechanism defined in [ITU-T Q.4143].
+
+The mechanism "warm standby" of vBNG-PUP means that users' entries will be synchronized after the interface within the warm standby group is fault. The mechanism "cold standby" of vBNG-PUP means the user entries will not be synchronized, and users have to redial to be online [ITU-T Q.4143].
+
+The mechanism "warm standby" of the CGN card in vBNG-PUP means that the user entries will be synchronized to the other CGN cards within the device after the CGN card is at fault. The mechanism "cold standby" means the user entries will not be synchronized and have to be regenerated between different devices [ITU-T Q.4143].
+
+The action "switch over" means that switching after the device is at fault, "switch back" means that switching after the fault device is recovered.
+
+### 8.1 Test case: vBNG-PUP joins the warm standby group
+
+Table 8-1 shows the test case for joining the warm standby group.
+
+**Table 8-1 – Test case: vBNG-PUP joins the warm standby group**
+
+| Test description | | | | |
+|------------------------|------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------|--|
+| Test purpose | To verify that vBNG-PUP supports joining the warm standby group. | | | |
+| Reference | [ITU-T Q.4143] clause 8.2 | | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | There are four vBNG-PUPs, namely vBNG-PUP1~vBNG-PUP4. Enter the vBNG-CP configuration interface. | |
+
+**Table 8-1 – Test case: vBNG-PUP joins the warm standby group**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| | Step | Type | Description | |
+| | 2 | Stimulus | Configure the number of vMAC (virtual MAC) addresses for interfaces within the warm standby group, vMAC address can be configured, or by default, vMAC address is automatically assigned if by default. | |
+| | 3 | Stimulus | Add the interfaces of vBNG-PUP1~vBNG-PUP4 to the warm standby group in the vBNG-CP command window and check the vMAC address. There is expected result 1. | |
+| | 4 | Stimulus | The vBIT sends a broadcast stream to the vBNG-PUPs and observes whether the interfaces in the warm standby group achieves load balancing. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The interface of vBNG-PUP1-vBNG-PUP4 have been joined to the same standby group. | |
+| | 2 | Check | Load balancing of traffic in the standby group. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+## **8.2 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch over during the user accessing process)**
+
+Table 8-2 shows the interface switching in the vBNG-PUP warm standby group.
+
+**Table 8-2 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | | | | |
+|-------------------------|--------------------------------------------------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| Test description | | | | |
+| Test purpose | To verify that vBNG supports interface switching in the vBNG-PUP warm standby group. | | | |
+| Reference | [ITU-T Q.4143] clause 8.2 | | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join warm standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. | |
+| | 4 | Stimulus | Shutdown interface 1 of vBNG-PUP1 during the user's dialling process, observe the user's status. There is expected result 1. | |
+| | 5 | Stimulus | Check the load balancing of traffic on other interfaces within the warm standby group. There is expected result 2. | |
+
+**Table 8-2 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| Expected results | Step | Type | Description | Result |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------------------------------------------------|--------|
+| | 1 | Check | A small number of users dialling packet loss and retransmission. Finally, all users were able to go online normally. | |
+| | 2 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | |
+| Notes | | | | |
+| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | |
+
+## **8.3 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch over during the forwarding process)**
+
+Table 8-3 shows the test case for interface switching in vBNG-PUP warm standby group.
+
+**Table 8-3 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| Test description | | | | |
+|-------------------------|----------------------------------------------------------------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | | | |
+| Reference | [ITU-T Q.4143] clause 8.2 | | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup user plane (UP)). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. | |
+| | 4 | Stimulus | During the traffic forwarding process, shutdown interface 1 of vBNG-PUP1, observe the packet loss situation. There is expected result 1. | |
+| | 5 | Stimulus | Check the load balancing of traffic between other interfaces within the warm standby group. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | Some packet loss in the traffic when the status is switching. After finishing the switching, the traffic forwards normally. | |
+| | 2 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | |
+
+**Table 8-3 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | |
+|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Notes | |
+| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. |
+
+### 8.4 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch back during the user accessing process)
+
+Table 8-4 shows the test case for interface switching in vBNG-PUP warm standby group.
+
+**Table 8-4 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | | | | |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test description | | | | |
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | | | |
+| Reference | [ITU-T Q.4143] clause 8.2 | | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | |
+| | 4 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. | |
+| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the user's accessing process, check the user's status on vBNG-CP. There is expected result 1. | |
+| | 6 | Stimulus | Check the load balancing of traffic between other interfaces within the warm standby group. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | There is packet loss during accessing progress which affects new users. Old users will stay online. Finally, all users will be online. | |
+| | 2 | Check | Load balancing of traffic in the standby group. | |
+| Notes | | | | |
+| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | |
+
+### 8.5 Test case: Interface switching in vBNG-PUP N+1 warm standby group (Switch back during the forwarding process)
+
+Table 8-5 shows the test case for interface switching in vBNG-PUP warm standby group.
+
+**Table 8-5 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| Test description | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test purpose | | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. | | |
+| Reference | | [ITU-T Q.4143] clause 8.2 | | |
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | |
+| | 4 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. There is expected result 1. | |
+| | 5 | Stimulus | Reopen interface 1 of vBNG-PUP1. | |
+| | 6 | Stimulus | Check the user accessing status on vBNG-CP. There is expected result 2. | |
+| | 7 | Stimulus | Check the load balancing of the interface within the warm standby group. There is expected result 3. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | There is no packet loss in traffic and keeping normal forwarding on vBNG-PUP2~vBNG-PUP4. | |
+| | 2 | Check | All users will be kept online. | |
+| | 3 | Check | Load balancing of traffic in the standby group. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+### **8.6 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch over during the user accessing process)**
+
+Table 8-6 shows the interface switching in vBNG-PUP warm standby group.
+
+**Table 8-6 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| Test description | |
+|-------------------------|----------------------------------------------------------------------------------|
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-6 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | |
+| | 4 | Stimulus | Shutdown interface 1 of vBNG-PUP1 during the user's dialling process, observe the user's status. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP1~vBNG-PUP3. The backup vBNG-PUP4 does not forward the packet. | |
+| | 2 | Check | A small number of users dialling packet loss and retransmission. Finally, all users were able to go online normally. | |
+| | 3 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+### 8.7 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch over during the forwarding process)
+
+Table 8-7 shows the test case for interface switching in vBNG-PUP warm standby group.
+
+**Table 8-7 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | |
+|-------------------------|----------------------------------------------------------------------------------|
+| Test description | |
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-7 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | | | | |
+|-------------------------|-------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | |
+| | 4 | Stimulus | During the traffic forwarding process, shutdown interface 1 of vBNG-PUP1, observe the packet loss situation. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP1~vBNG-PUP3. The backup vBNG-PUP4 does not forward the packet. | |
+| | 2 | Check | Some packet loss in the traffic when the status is switching. After finishing the switching, the traffic forwards normally. | |
+| | 3 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | |
+| Notes | | | | |
+| Test verdict | | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | |
+
+### 8.8 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch back during the user accessing process)
+
+Table 8-8 shows the test case for interface switching in vBNG-PUP warm standby group.
+
+**Table 8-8 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | |
+|-------------------------|----------------------------------------------------------------------------------|
+| Test description | |
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-8 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | | | | |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying Internet protocol (IP) interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | |
+| | 4 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | |
+| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the user's accessing process, check the user's status on vBNG-CP. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the interface of vBNG-PUP1 has been shut down. | |
+| | 2 | Check | There is packet loss during accessing progress. All users will stay online. | |
+| | 3 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3 while the interface of vBNG-PUP1 has recovered. | |
+| Notes | | | | |
+| Test verdict | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | | |
+
+### 8.9 Test case: Interface switching in vBNG-PUP N:1 warm standby group (Switch back during the forwarding process)
+
+Table 8-9 shows the test case for interface switching in vBNG-PUP warm standby group.
+
+**Table 8-9 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | |
+|-------------------------|----------------------------------------------------------------------------------|
+| Test description | |
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP warm standby group. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-9 – Test case: Interface switching in vBNG-PUP warm standby group**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | |
+| | 4 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | |
+| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the packet forwarding process, check the user's status on vBNG-CP. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the interface of vBNG-PUP1 has been shut down. | |
+| | 2 | Check | All users will stay online. | |
+| | 3 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3 while the interface of vBNG-PUP1 has recovered. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+### **8.10 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch over during the user accessing process)**
+
+Table 8-10 shows the interface switching in vBNG-PUP warm standby group.
+
+**Table 8-10 – Test case: Interface switching in vBNG-PUP cold standby group**
+
+| | |
+|-------------------------|-----------------------------------------------------------------------------|
+| Test description | |
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP standby group. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-10 – Test case: Interface switching in vBNG-PUP cold standby group**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | |
+| | 4 | Stimulus | Shutdown interface 1 of vBNG-PUP1 during the user's dialling process, observe the user's status and forwarding table on vBNG-PUP4. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3. The backup vBNG-PUP4 does not forward the packet. | |
+| | 2 | Check | When vBNG-PUP1 first switches to vBNG-PUP4, the forwarding table is empty and retrieves from vBNG-CP. A small number of users dialling packet loss and retransmission. Finally, all users were able to go online normally. | |
+| | 3 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+### 8.11 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch over during the forwarding process)
+
+Table 8-11 shows the test case for interface switching in vBNG-PUP cold standby group.
+
+**Table 8-11 – Test case: Interface switching in vBNG-PUP cold standby group**
+
+| | |
+|-------------------------|-----------------------------------------------------------------------------|
+| Test description | |
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP standby group. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-11 – Test case: Interface switching in vBNG-PUP cold standby group**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP warm standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Check the forwarding table on vBNG-PUP4. Check the load balancing of traffic. There is expected result 1. | |
+| | 4 | Stimulus | During the traffic forwarding process, shutdown interface 1 of vBNG-PUP1, observe the packet loss situation and observe the forwarding table on vBNG-PUP4. There is expected result 2. | |
+| Expected results | 5 | Stimulus | Check the load balancing of traffic between other interfaces within the warm standby group. There is expected result 3. | |
+| | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3. The backup vBNG-PUP4 does not forward the packet. There is no forwarding table on vBNG-PUP4. | |
+| | 2 | Check | When vBNG-PUP1 first switches to vBNG-PUP4, the forwarding table is empty then it retrieves from vBNG-CP. All traffic is interrupted then gradually recovers. | |
+| | 3 | Check | Load balancing of traffic between interface 2 of vBNG-PUP2, interface 3 of vBNG-PUP3, and interface 4 of vBNG-PUP4. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+## **8.12 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch back during the user accessing process)**
+
+Table 8-12 shows the test case for interface switching in vBNG-PUP cold standby group.
+
+**Table 8-12 – Test case: Interface switching in vBNG-PUP cold standby group**
+
+| | |
+|-------------------------|-----------------------------------------------------------------------------|
+| Test description | |
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP standby group. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-12 – Test case: Interface switching in vBNG-PUP cold standby group**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | |
+| | 4 | Stimulus | The vBIT simulates user PPPoE/IPoE packets and continuously sends these packets to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. Check the forwarding table on vBNG-PUP4. There is expected result 1. | |
+| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the user's accessing process, check the user's status on vBNG-CP. There is expected result 2. | |
+| | 6 | Stimulus | Check the load balancing of traffic between other interfaces within the standby group. Check the forwarding table on vBNG-PUP4. There is expected result 3. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the interface of vBNG-PUP1 has been shut down. There is a forwarding table on vBNG-PUP4. | |
+| | 2 | Check | There is packet loss during accessing progress. All users will stay online. | |
+| | 3 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3 while the interface of vBNG-PUP1 has recovered. The forwarding table will expire on vBNG-PUP4. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+### 8.13 Test case: Interface switching in vBNG-PUP N:1 cold standby group (Switch back during the forwarding process)
+
+Table 8-13 shows the test case for interface switching in vBNG-PUP cold standby group.
+
+**Table 8-13 – Test case: Interface switching in vBNG-PUP cold standby group**
+
+| | |
+|-------------------------|-----------------------------------------------------------------------------|
+| Test description | |
+| Test purpose | To verify that vBNG supports interface switching in vBNG-PUP standby group. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-13 – Test case: Interface switching in vBNG-PUP cold standby group**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the configuration interface of vBNG-CP and configure the vBNG-PUP standby group. For example, vBNG-PUP1 selects interface 1 to join standby group A, vBNG-PUP2 selects interface 2 to join standby group A, and so on. (vBNG-PUP4 is selected as the backup UP). | |
+| | 2 | Stimulus | Configure the vBNG-PUP loopback address for underlying IP interoperability between vBNG-CP and vBNG-PUP with IS-IS or static route. | |
+| | 3 | Stimulus | Shutdown interface 1 of vBNG-PUP1. | |
+| | 4 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Check the load balancing of traffic. Check the forwarding table on vBNG-PUP4. There is expected result 1. | |
+| | 5 | Stimulus | Reopen the interface 1 of vBNG-PUP1 during the packet forwarding process, check the user's status on vBNG-CP. There is expected result 2. | |
+| Expected results | 6 | Stimulus | Check the load balancing of traffic between other interfaces within the warm standby group. There is expected result 3. | |
+| | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the interface of vBNG-PUP1 has been shut down. There is a forwarding table on vBNG-PUP4. | |
+| | 2 | Check | All users will stay online. | |
+| | 3 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP3 while the interface of vBNG-PUP1 has recovered. The forwarding table will expire on vBNG-PUP4. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+## 8.14 Test case: CGN switching (cold standby)
+
+Table 8-14 shows the test case for CGN switching.
+
+**Table 8-14 – Test case: CGN switching (cold standby)**
+
+| | |
+|-------------------------|---------------------------------------------|
+| Test description | |
+| Test purpose | To verify that vBNG supports CGN switching. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-14 – Test case: CGN switching (cold standby)**
+
+| Test procedures | Step | Type | Description | |
+|------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| | 1 | Stimulus | >Login the vBNG-PUP. Config network address translation (NAT) service location (instruct load balance on vBNG-central processing unit (CPU) of CGN card), service instance group (binding the service location) and create NAT instance. Then config warm standby group on vBNG-PUP1~vBNG-PUP4. | |
+| | 2 | Stimulus | Config the basic function of CGN, such as network segment, port block, traffic steering policy based on access control list (ACL) and NAT translation policy. The users on CGN cards of vBNG-PUP1~vBNG-PUP4 load balanced and normally access the Internet. | |
+| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1~vBNG-PUP4. Record the CGN table of vBNG-PUP1. | |
+| | 4 | Stimulus | Shutdown the CGN cards on vBNG-PUP1. | |
+| | 5 | Stimulus | Check the user traffic. There is expected result 1. | |
+| | 6 | Stimulus | Check the CGN table on vBNG-PUP2~vBNG-PUP4. There is expected result 2. | |
+| | 7 | Stimulus | Check the user entries including mapping the relationship between public network address and private network address, as well as the corresponding port blocks. There is expected result 3. | |
+| Expected results | Step | Type | Description | |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP2-vBNG-PUP4 while the CGN cards of vBNG-PUP1 has been shut down. | |
+| | 2 | Check | vBNG-PUP2~vBNG-PUP4 regenerates CGN tables (Reassign private and public network mapping relationships and port blocks) of the original users carried by vBNG-PUP1, which means that the public network addresses have been reallocated. | |
+| | 3 | Check | vBNG-CP has refreshed the mapping relationship between public network address and private network address, as well as the corresponding port blocks of user entries on vBNG-PUP2~vBNG-PUP4. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+## 8.15 Test case: CGN switching (warm standby)
+
+Table 8-15 shows the test case for carrier grade NAT (CGN) switching (warm standby).
+
+**Table 8-15 – Test case: CGN switching (warm standby)**
+
+| Test description | |
+|------------------|----------------------------------------------------------------------------|
+| Test purpose | To verify that vBNG supports CGN warm-standby switching within the device. |
+| Reference | [ITU-T Q.4143] clause 8.2 |
+
+**Table 8-15 – Test case: CGN switching (warm standby)**
+
+| | | | | |
+|-------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Test procedures | Step | Type | Description | |
+| | 1 | Stimulus | Login the vBNG-PUP. Config NAT service location (instruct load balance on vBNG-CPU of CGN card), service instance group (binding the service location) and create NAT instance. Then config warm standby group on vBNG-PUP1~vBNG-PUP4. | |
+| | 2 | Stimulus | Config the basic function of CGN, such as network segment, port block, backup mode, traffic steering policy based on ACL and NAT translation policy. The users on CGN cards of vBNG-PUP1~vBNG-PUP4 load balanced and normally access the Internet. | |
+| | 3 | Stimulus | The vBIT simulates the user's traffic that accesses the Internet and continuously sends traffic to vBNG-PUP1. Record the CGN table of vBNG-PUP1. | |
+| | 4 | Stimulus | Shutdown one of the CGN cards on vBNG-PUP1. | |
+| | 5 | Stimulus | Check the user traffic and resource utilization such as vBNG-CPU utilization or memory utilization. There is expected result 1. | |
+| | 6 | Stimulus | Check the CGN table on vBNG-PUP2~vBNG-PUP4. There is expected result 2. | |
+| Expected results | Step | Type | Description | Result |
+| | 1 | Check | The traffic loads balancing between vBNG-PUP1-vBNG-PUP4, the vBNG-CPU utilization increases in vBNG-PUP1. | |
+| | 2 | Check | There is no change to the CGN table on vBNG-PUP2~vBNG-PUP4. | |
+| | 3 | Check | There is no change of user entries on vBNG-PUP2~vBNG-PUP4, including the mapping relationship between public network address and private network address, as well as the corresponding port blocks. | |
+| Notes | | | | |
+| Test verdict | | If all checks described in the test case are successful, it is deemed successfully terminated. If at least one check is successful but at least one check fails, the test is deemed partially passed. If no checks are successful, the test is deemed failed. | | |
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4e668942e77f263cb9c1d080314402337405f43
--- /dev/null
+++ b/marked/Q/T-REC-Q.4-198811-I_PDF-E/raw.md
@@ -0,0 +1,384 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.4**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**GENERAL RECOMMENDATIONS ON TELEPHONE
+SWITCHING AND SIGNALLING**
+
+**INTERNATIONAL AUTOMATIC AND
+SEMI-AUTOMATIC WORKING**
+
+---
+
+**AUTOMATIC SWITCHING FUNCTIONS FOR
+USE IN NATIONAL NETWORKS**
+
+**ITU-T Recommendation Q.4**
+
+(Extract from the *Blue Book*)
+
+---
+
+## NOTES
+
+1 ITU-T Recommendation Q.4 was published in Fascicle VI.1 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## Recommendation Q.4
+
+# AUTOMATIC SWITCHING FUNCTIONS FOR USE IN NATIONAL NETWORKS
+
+## 1 Preamble
+
+The CCITT,
+
+*considering*
+
+(1) that a large amount of switching equipment will be installed in the next few years, especially in areas of low subscriber density;
+
+(2) the continuous rapid development of new switching techniques results in different generations of equipment having to co-exist;
+
+(3) that some degree of compatibility in the installed switching equipment is required in the world-wide automatic network;
+
+(4) that the introduction of newly developed switching systems presents Administrations with an ever increasing number of engineering, staff training, maintenance and other operational considerations,
+
+*and also considering*
+
+(5) that Recommendations originally intended for international application only are increasingly being applied to national networks, or could be so applied;
+
+(6) that many current studies are aimed at producing Recommendations primarily applicable to national networks,
+
+*recommends*
+
+the following guidelines for use by Administrations establishing national switching standards or, if desired, for updating existing standards. Each Administration may select those guidelines it deems applicable to its own situation.
+
+## 2 Automatic switching functions for use in national networks
+
+Table 1/Q.4 lists the functional switching capabilities of an exchange which will, or may in some instances, according to the role of the exchange in a network, need to be technically specified in order that the Administration concerned can be assured that the exchange will satisfy existing and foreseen future needs of the network. For the required capabilities, references are given to CCITT texts which should be taken into account when decisions on national standards are taken; some make positive recommendations, others give guidelines or background information. Table 2/Q.4 provides full titles for those referenced texts, and for others applicable to national switching, in order to provide more specific information about the subject matter.
+
+Some of the functions listed are required in all types of exchanges. Others may or may not be, according to the role of the exchange, e.g. local, combined local/transit, transit, international, etc.
+
+It is not always necessary that a precise technical specification be given, e.g., in a tender specification, for each switching function. In some instances, it may be sufficient to state the requirements broadly, possibly including desired ranges of parameter values, and to invite a tenderer to make his own specific proposals for evaluation.
+
+## 3 Requirements for ISDN
+
+As Recommendations for the ISDN are being developed concurrently, it is difficult to reference them in this Recommendation. All Recommendations relevant to the ISDN will be published in a single volume at the end of this Study Period 1981-1984 (Fascicle III.5).
+
+## **4 Requirements other than automatic switching functions**
+
+The technical specifications of the required automatic switching functions of an exchange do not, in themselves, constitute a complete specification. Other aspects possibly needing to be covered, which are particular to an exchange or to a group of exchanges and not included within the scope of automatic switching functions are:
+
+- traffic (dimensioning and service performance);
+- specifications dictated by the equipment environment (building constraints, power supplies, climatic conditions, etc.);
+- installation, including testing, acceptance, post-acceptance technical support, etc.;
+- training and documentation;
+- support of system design and software, e.g., CCITT Recommendation Z.100 (SDL) series and CCITT Recommendation Z.200 (CHILL) series.
+
+## **5 Technical cooperation possibilities**
+
+The CCITT Recommendations already established so far do not themselves suffice to cover all the points of a specification dealing with the functions to be performed by switching equipment. It is unavoidable, if national standards are to match the requirements and circumstances of a particular network, that the responsible Administration itself exercise a number of choices.
+
+An Administration seeking advice or guidance beyond that indicated in CCITT texts may, by approaching the ITU Secretariat, obtain information on the standards adopted by other Administrations.
+
+## **6 Definition of requirements in terms of services and facilities**
+
+6.1 Fundamental decisions as to range of service(s) and facilities to be provided must be made by the Administration. Descriptions and other information on the various services normally provided by a switching system may be found as indicated in the following:
+
+- types of services (GAS 6, Chapter II, § 3; Chapter III, § 3.2),
+- basic services (GAS 6, Chapter IV, § 1.2),
+- supplementary services (GAS 6, Chapter IV, § 1.4); Recommendations E.130, E.132, E.151; Supplement No. 1 to Series E Recommendations.
+
+6.2 A list of possible telephony subscriber services and facilities has been extracted from the GAS 6 Handbook, Chapter IX, § 1.3.2 and is shown in Annex A.
+
+TABLE 1/Q.4
+
+## **CCITT texts (Recommendations and GAS Handbooks) relevant to the technical specification of automatic switching functions of exchanges in national networks**
+
+| Item | Reference |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| A. Switching | |
+| Type of switch: analogue (2- or 4-wire)/digital, space or time division | GAS 6 II 1, VI 1.1
GAS 3 III, Annex 1
Recs. Q.501, Q.511 |
+| Type of control: distributed/centralized | GAS 6 VI 1.2 |
+| Subscriber classification | GAS 6 VI 1.2.1 |
+| B. Routing and selection | |
+| Classification of exchange inlets and outlets: according to types of inter-exchange circuits to be connected: taking into account the line, inter-register, etc., signalling arrangements and the transmission, operating, testing, network management, etc., requirements | GAS 6 IV 5.6-7
VI 1.4.1 and 4
Recs. E.543
Q.7, Q.48, Q.49, Q.108, Q.110,
Q.251-Q.300, Q.310-Q.331, Q.400-Q.480,
Q.501-Q.507, Q.511-Q.517 |
+| Number analysis functions: required capacity and depth of analysis for routing, determination of number length, barring, digit insertion/deletion, charging, echo control, etc. | GAS 6 IV 6, VI 1.4.6
Recs. E.160, E.161, E.163
Q.103, Q.105, Q.106, Q.107, Q.107 bis,
Q.115 |
+| Choice of outgoing circuit: search procedure, dual seizures, alternative routing, repeat attempts, etc. | GAS 6 VI 1.4.2, 3 and 5
Recs. E.170, E.171
Q.12, Q.263 |
+| Network management functions: circuit group denial, alternative routing cancellation, exchange load control, etc. | GAS 6 VI 1.4.7
Recs. E.170, E.410, E.411, E.412, E.413
Q.506, Q.516 |
+| C. Charging | |
+| Methods: local, long-distance, international, non-chargeable, payphone, etc., calls | GAS 6 IV 7.1-2, VI 1.5.1
Recs. E.230-E.232 |
+| Charge determination: principles and parameters | GAS 6 IV 7.3, VI 1.5.2 |
+| D. Transmission characteristics | |
+| Interfaces: specification of the transmission characteristics of the interfaces, or the identification of the standard interfaces, at which the exchange is to interconnect with external facilities and systems | GAS 3 III
Recs. G.703, G.704, G.705, G.731-G.739,
G.741-G.746,
Q.502, Q.512 |
+| Exchange transmission performance: Limits for the levels of transmission impairments attributable to the exchange and for characteristics affecting performance, taking account of all possible types of connection through the exchange | GAS 6 VI 1.8
Recs. G.121, G.122, G.123
Q.45, Q.507, Q.517 |
+| E. Synchronization and timing | Recs. G.811, G.822
Q.502, Q.503, Q.512, Q.513 |
+| F. Tones and recorded announcements | |
+| Scope and applications; tones; announcements | GAS 6 VI 1.7
Recs. E.180 (Q.35), E.181 (Q.36), E.182
Supplement No. 2 to
Series E Recommendations
Rec. Q.24 |
+
+TABLE 1/Q.4 (cont.)
+
+| Item | Reference |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| G. Subscriber line characteristics | |
+| 1. Analogue subscriber line | |
+| Subscriber line standards: limits for loop resistance, loop insulation, overall line attenuation, etc. | GAS 2 V 3.2, 3.3
GAS 6 VI 1.3.1
GAS 3 II 3.1
Recs. G.120-G.123 |
+| Subscriber line signals.. supervision address information, ringing, metering, tones, etc. | GAS 2 V 6.2
GAS 6 IV 8, VI 1.3.2
Recs. E. 131
Q.16, Q.23, Q.35 (E.180), Q.118 |
+| 2. Digital subscriber line | |
+| Exchange interfaces signalling for digital access | Recs. I.412
Q.512, Q.920, Q.921, Q.930, Q.931 |
+| H. Inter-exchange signalling | |
+| Specification of required exchange functions by identification of existing and planned inter-exchange signalling arrangements
Signalling philosophies and types of signalling | GAS 6 II 2, IV 8, VI 1.6
GAS 3 II 3.2
Recs. Q.7, Q.21
Supplement No. 3 to
Series Q Recommendations
Recs. Q.101-Q.103, Q.105-Q.118 bis ,
Q.251-Q.300, Q.310-Q.331, Q.400-Q.490,
Q.701-Q.795 |
+| Signalling system specifications (channel associated and common channel, as appropriate) | |
+| Interworking of signalling systems | Recs. Q.601 -Q.685 |
+| I. Operation | |
+| The specification of exchange features designed to facilitate the operation of the exchange with respect to the administrations of: | GAS 6 IV 7.4-7, 9.1-2
VI 1.5.3-4, 1.9 |
+| - subscribers | Recs. E.500 |
+| - routing | Q.505, Q.506, Q.515, Q.516 |
+| - traffic | Z.331-Z.333 |
+| - tariffs and charging | |
+| - recording and billing | |
+| - system control | |
+| taking into account remote control possibilities | |
+| J. Maintenance | |
+| The specification, with respect to maintenance, of: | GAS 6 IV 9.1, 9.3, VI 1.10
Recs. G.231 |
+| - subscriber lines | M.565 |
+| - inter-exchange circuits | O.22 (Q.49) |
+| - switching network | Q.506, Q.516 |
+| - control system | Z.301, Z.331-Z.333 |
+| the specification of testing and maintenance features, taking into account the objectives of: | |
+| - minimization of the fault rate | |
+| - simplification of maintenance activities | |
+| - adequate equipment repair facilities | |
+| - maximization of immunity to failures | |
+| - optimizing maintenance centralization | |
+| L. Input/output devices for operation and maintenance | GAS 6 VI 1.11
Recs. E.220, E.221
Z.301-Z.302, Z.311-Z.317, Z.321-Z.323 |
+
+TABLE 2/Q.4
+
+### **Titles of CCITT texts (Recommendations and GAS Handbooks) relevant to national switching applications**
+
+CCITT Manual *Local telephone networks*, ITU, Geneva, 1968 (Gas 2 Handbook).
+
+CCITT Manual *Transmission planning of switched telephone networks*, ITU, Geneva, 1976 (Gas 3 Handbook).
+
+CCITT Manual *Economic and technical aspects of the choice of telephone switching systems*, ITU, Geneva, 1981 (GAS 6 Handbook).
+
+CCITT Manual *Economic and technical aspects of the transition from analogue to digital telecommunication networks*, ITU, Geneva, 1984 (GAS 9 Handbook).
+
+CCITT Rec. E.130 *Choice of the most useful and desirable supplementary telephone services*.
+
+CCITT Rec. E.131 *Subscriber control procedures for supplementary services*.
+
+CCITT Rec. E.132 *Standardization of elements of control procedures for supplementary telephone services*.
+
+CCITT Rec. E.151 *Conference calls*.
+
+CCITT Rec. E.160 *Definitions relating to national and international numbering plans*.
+
+CCITT Rec. E.161 *Arrangement of figures, letters and symbols on rotary dials and pushbutton telephone sets*.
+
+CCITT Rec. E.163 *Numbering plan for the international telephone service*.
+
+CCITT Rec. E.170 *Overflow - alternative routing - rerouting - automatic repeat attempt*.
+
+CCITT Rec. E.171 *International routing plan*.
+
+CCITT Rec. E.180 *Characteristics of the dial tone, ringing tone, busy tone, congestion tone, special information tone and warning tone*.
+
+CCITT Rec. E.181 *Customer recognition of foreign tones*.
+
+CCITT Rec. E.182 *Application of tones and recorded announcements in telephone services*.
+
+CCITT Rec. E.211 *Numbering and dialling procedures for VHF/UHF and maritime mobile satellite services*.
+
+CCITT Rec. E.220 *Ergonomic aspects of visual display terminals*.
+
+CCITT Rec. E.221 *Human interface to visual display terminals*.
+
+CCITT Recs. E.230-E.232 *Charging (determination of collection charges) in the international telephone service*.
+
+CCITT Rec. E.500 *Measurement and recording of traffic*.
+
+CCITT Rec. E.521 *Calculation of the number of circuits in a group carrying overflow traffic*.
+
+CCITT Rec. E.543 *Grades of service in analogue/digital international telephone exchanges*.
+
+CCITT Rec. E.410, E.411, E.412 and E.413 *Network management*.
+
+CCITT Series E. Recommendations Supplement No. 1 *List of possible supplementary telephone services which may be offered to subscribers*.
+
+CCITT Series E. Recommendations Supplement No. 2 *Various tones used in national networks*.
+
+CCITT Recs. G.120-G. 123 *General characteristics of national systems forming part of international connections.*
+
+CCITT Rec. G.121 *Corrected reference equivalents (CREs) of national systems.*
+
+CCITT Rec. G.122 *Influence of national networks on stability and echo losses in national systems.*
+
+CCITT Rec. G.123 *Circuit noise in national networks.*
+
+CCITT Rec. G.231 (2) *Use of standard components in transmission equipment.*
+
+CCITT Rec. G.703 *General aspects of interfaces.*
+
+CCITT Rec. G.704 *Functional characteristics of interfaces associated with network nodes.*
+
+CCITT Rec. G.705 *Characteristics required to terminate digital paths on a digital exchange.*
+
+CCITT Recs. G.731-G.739 *Principal characteristics of primary multiplex equipment.*
+
+CCITT Recs. G.741-G.746 *Principal characteristics of second order multiplex equipments.*
+
+CCITT Rec. G.811 *Performance of clocks suitable for plesiochronous operation of international digital links.*
+
+CCITT Rec. G.822 *Controlled slip rate objectives on an international digital connection.*
+
+CCITT Rec. I.412 *ISDN user-network interfaces-channel structures and access capabilities.*
+
+CCITT Rec. M.565 *Access point for international telephone circuits.*
+
+CCITT Rec. O.22 *Specification for the CCITT automatic transmission measuring and signalling testing equipment ATME No. 2.*
+
+CCITT Rec. Q.7 *Signalling systems to be used for international automatic and semi-automatic telephone working*
+
+CCITT Rec. Q.12 *Overflow-alternative routing - rerouting - automatic repeat attempt.*
+
+CCITT Rec. Q.14 *Means to control the number of satellite links in an international telephone connection.*
+
+CCITT Rec. Q.15 *Nominal mean power during the busy hour.*
+
+CCITT Rec. Q.16 *Maximum permissible value for the absolute power level of a signalling pulse.*
+
+CCITT Rec. Q.21 *Systems recommended for out-band signalling.*
+
+CCITT Rec. Q.23 *Technical features of push-button telephone sets.*
+
+CCITT Rec. Q.24 *Multi-frequency push-button signal reception.*
+
+CCITT Rec. Q.33 *Protection against the effects of faulty transmission on groups of circuits.*
+
+CCITT Rec. Q.35 *Characteristics of the dial tone, ringing tone, busy tone, congestion tone, special information tone and warning tone.*
+
+CCITT Rec. Q.45 *Transmission characteristics of an international exchange.*
+
+CCITT Rec. Q.48 *Demand assignment signalling systems.*
+
+CCITT Rec. Q.49 *Specification for the CCITT automatic transmission measuring and signalling testing equipment ATME No. 2.*
+
+CCITT Recs. Q.101-Q.103, Q.105-Q.118 bis *Clauses applicable to CCITT standard systems.*
+
+CCITT Rec. Q.103 *Numbering used.*
+
+CCITT Rec. Q.105 *National (significant) number.*
+
+CCITT Rec. Q.106 *The sending-finished signal*
+
+CCITT Rec. Q.107 *Standard sending sequence of forward address information.*
+
+CCITT Rec. Q.107 bis *Analysis of forward address information for routing.*
+
+CCITT Rec. Q.108 *One-way or both-way operation of international circuits.*
+
+CCITT Rec. Q.110 *General aspects of the utilization of standardized CCITT signalling systems on PCM links.*
+
+CCITT Rec. Q.115 *Control of echo suppressors.*
+
+CCITT Recs. Q.118 *Special release arrangements.*
+
+CCITT Recs. Q.251-Q.300 *Specifications of Signalling System No. 6.*
+
+CCITT Rec. Q.263 *Double seizing with both-way operation.*
+
+CCITT Recs. Q.310-Q.331 *Specifications of Signalling System R1.*
+
+CCITT Recs. Q.400-Q.490 *Specifications of Signalling System R2.*
+
+CCITT Recs. Q.500-Q.554 *Digital local, transit, combined and international exchanges in integrated digital networks and mixed analogue-digital networks.*
+
+CCITT Recs. Q.601-Q.685 *Interworking of signalling systems.*
+
+CCITT Recs. Q.701-Q.795 *Specifications of Signalling System No. 7.*
+
+CCITT Rec. Q.920 *ISDN user-network interface data link layer - General aspects.*
+
+CCITT Rec. Q.921 *ISDN user-network interface data link layer specification.*
+
+CCITT Rec. Q.930 *ISDN user-network interface layer 3 - General aspects.*
+
+CCITT Rec. Q.931 *ISDN user-network interface layer 3 specification for basic call control*
+
+CCITT Series Q. Recommendations Supplement No. 3 *Information received on national voice-frequency signalling systems.*
+
+CCITT Rec. Z.100 Series *Functional specification and description language (SDL).*
+
+CCITT Rec. Z.200 Series *CCITT high level language (CHILL).*
+
+CCITT Rec. Z.300 Series *Man-machine language (MML).*
+
+CCITT Recs. Z.301-Z.302 *General principles.*
+
+CCITT Rec. Z.301 *Introduction to the CCITT man-machine language.*
+
+CCITT Recs. Z.311-Z.317 *Basic syntax and dialogue procedures.*
+
+CCITT Recs. Z.321-Z.323 *Extended MML for visual display terminals.*
+
+CCITT Recs. Z.331-Z.333 *Specification of man-machine interface.*
+
+## ANNEX A
+
+(to Recommendation Q.4)
+
+### **List of possible subscriber services and facilities**
+
+#### Subscriber services
+
+#### *Basic services*
+
+- subscriber dialled local, long distance, and international calling with automatic charging
+- PBX line hunting, night service, and direct dialling-in
+- payphone
+- access to operators for assistance and information
+- access to community services (police, fire brigade, etc.)
+- access to recorded announcements
+- call barring
+- malicious call trace
+- interception of calls
+- absent subscriber
+- line observation
+
+#### *Supplementary services*
+
+- abbreviated dialling
+- alarm call
+- hot line
+- outgoing service restriction
+- call diversion
+- call waiting
+- do not disturb
+- call completion to busy subscribers
+- switching-in not permitted
+- call charge indicator at subscriber's premises
+- immediate call charge announcement
+- priority line
+- two party line
+- multiparty line
+- multifrequency push-button (MFPB) dialling
+- mobile subscriber
+- conference service
+- Centrex services
+- other services
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4001.1-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4001.1-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a308271fb239928318c461337c31936dd84fe604
--- /dev/null
+++ b/marked/Q/T-REC-Q.4001.1-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6a0f146a2a7abe73d858cf87904646fa5525273febbbbb82a1db78580ee044a
+size 3757
diff --git a/marked/Q/T-REC-Q.4010.1-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4010.1-201608-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..52f4934bd91bd8371b70738d632bdcb36f6b8825
--- /dev/null
+++ b/marked/Q/T-REC-Q.4010.1-201608-I_PDF-E/raw.md
@@ -0,0 +1,491 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4010.1**
+
+(08/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**Message waiting indication using IP multimedia
+core network subsystem – Part 1: Protocol
+implementation conformance statement**
+
+Recommendation ITU-T Q.4010.1
+
+ITU-T
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking across it. To the right of the globe, the text "International Telecommunication Union" is written in blue, with "ITU" in a larger, bold font above it.
+
+ITU logo
+
+International
+Telecommunication
+Union
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900-Q.4099 |
+| Testing specifications for next generation networks | Q.3900-Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000-Q.4039 |
+| Testing specifications for Cloud computing | Q.4040-Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T Q.4010.1
+
+## Message waiting indication using IP multimedia core network subsystem – Part 1: Protocol implementation conformance statement
+
+## Summary
+
+Recommendation ITU-T Q.4010.1 v.1 (2016) provides the testing requirements for message waiting indication (MWI) using IP multimedia (IM) core network (CN) subsystem – Part 1: Protocol implementation conformance statement (PICS) (based on Recommendation ITU-T Q.3626 v.1).
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4010.1, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|--------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4010.1 v.1 | 2016-08-29 | 11 | 11.1002/1000/13001 |
+
+## Keywords
+
+IMS, IP multimedia subsystem, message waiting indication, MWI, testing, test suite structure and test purposes, TSS&TP
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|---------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Guidance for completing the ICS proforma ..... | 2 |
+| 6.1 General overview of ICS proforma ..... | 2 |
+| 6.2 Identification of the implementation ..... | 4 |
+| 6.3 Identification of the MWI specification ..... | 6 |
+| 6.4 Global statement of conformance..... | 6 |
+| 6.5 Roles ..... | 6 |
+| 6.6 User role ..... | 6 |
+| 6.7 Network role..... | 7 |
+
+
+
+## Recommendation ITU-T Q.4010.1
+
+## Message waiting indication using IP multimedia core network subsystem – Part 1: Protocol implementation conformance statement
+
+# 1 Scope
+
+This Recommendation is part 1 of a multi-part deliverable covering message waiting indication (MWI) using IP multimedia (IM) core network (CN) subsystem – Part 1: Protocol implementation conformance statement (PICS), as identified below:
+
+**Part 1: "Protocol implementation conformance statement (PICS)";**
+
+Part 2: "Test suite structure and test purposes; Network side";
+
+Part 3: "Test suite structure and test purposes (TSS&TP); User side".
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.3626 v.1] Recommendation ITU-T Q.3626 v.1 (2016), *Message waiting indication using IP multimedia core network subsystem – Protocol specification*.
+- [IETF RFC 3842] IETF RFC 3842 (2004), *A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)*.
+- [ITU-T X.290] Recommendation ITU-T X.290 (1994), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*.
+- [ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+For the purposes of this Recommendation, the terms and definitions given in [ITU-T Q.3626 v.1], [ITU-T X.290], [ITU-T X.296] and the following apply:
+
+**3.1.1 PICS proforma:** Document, in the form of a questionnaire, which when completed for an implementation or system becomes a PICS.
+
+**3.1.2 Protocol ICS (PICS):** ICS for an implementation or system claimed to conform to a given protocol specification.
+
+NOTE – This may contain additional information.
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|-----------------------------------------------|
+| ICS | Implementation Conformance Statement |
+| IUT | Implementation Under Test |
+| MA | Message Account |
+| MIME | Multipurpose Internet Mail Extensions |
+| MNUA | MWI Notifier User Agent |
+| MSUA | MWI Subscriber User Agent |
+| MWI | Message Waiting Indication |
+| PDU | Protocol Data Unit |
+| PICS | Protocol Implementation Conformance Statement |
+| SCS | System Conformance Statement |
+| SUT | System Under Test |
+
+# **5 Conventions**
+
+None.
+
+# **6 Guidance for completing the ICS proforma**
+
+## **6.1 General overview of ICS proforma**
+
+### **6.1.1 Purposes and structure**
+
+The purpose of this protocol implementation conformance statement (PICS) proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in [ITU-T Q.3626 v.1] may provide information about the implementation in a standardized manner.
+
+The implementation conformance statement (ICS) proforma is subdivided into clauses for the following categories of information:
+
+- guidance for completing the ICS proforma;
+- identification of the implementation;
+- identification of the ;
+- global statement of conformance;
+- roles;
+- user role;
+- network role.
+
+### **6.1.2 Abbreviations and conventions**
+
+The PICS proforma contained in this Recommendation is comprised of information in tabular form in accordance with the guidelines presented in [ITU-T X.296].
+
+#### Item column
+
+The item column contains a number which identifies the item in the table.
+
+#### Item description column
+
+The item description column describes in free text each respective item (e.g., parameters, timers, etc.). It implicitly means "is - supported by the implementation?".
+
+#### Status column
+
+The following notations, defined in [ITU-T X.296], are used for the status column:
+
+- m mandatory – the capability is required to be supported.
+- o optional – the capability may be supported or not.
+- n/a not applicable – in the given context, it is impossible to use the capability.
+- x prohibited (excluded) – there is a requirement not to use this capability in the given context.
+- 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", "x" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression which is defined immediately following the table.
+
+##### Reference column
+
+The reference column makes reference to [ITU-T Q.3626 v.1], except where explicitly stated otherwise.
+
+#### Support column
+
+The support column shall be filled in by the supplier of the implementation. The following common notations, defined in [ITU-T X.296], are used for the support column:
+
+- Y or y supported by the implementation.
+- N or n not supported by the implementation.
+- N/A, n/a or no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status).
+
+If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able to answer that a capability is supported for one profile and not supported for another. In that case, the supplier shall enter the unique reference to a conditional expression, preceded by "?:" (e.g., ?3). This expression shall be given in the space for comments provided at the bottom of the table. It uses predicates defined in the system conformance statement (SCS), each of which refers to a single profile and which takes the value TRUE if and only if that profile is to be used.
+
+EXAMPLE 1: ?3: IF prof1 THEN Y ELSE N
+
+*In case of protocol, the following text should be added:*
+
+NOTE – As stated in [ITU-T X.296], support for a received protocol data unit (PDU) requires the ability to parse all valid parameters of that PDU. Supporting a PDU while having no ability to parse a valid parameter is non-conformant. Support for a parameter on a PDU means that the semantics of that parameter are supported.
+
+##### Prerequisite line
+
+A prerequisite line takes the form: Prerequisite: .
+
+A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be completed if the predicate is FALSE.
+
+### **6.1.3 Instructions for completing the PICS proforma**
+
+The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in clause 6.1.2.
+
+However, the tables containing in "user role" clause shall only be completed for user implementations, and the tables containing in "network role" clause shall only be completed for network implementations.
+
+If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately.
+
+More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
+
+## **6.2 Identification of the implementation**
+
+Identification of the implementation under test (IUT) and the system in which it resides (the system under test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options.
+
+The product supplier information and client information should both be filled in if they are different.
+
+A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
+
+### **6.2.1 Date of the statement**
+
+.....
+
+### **6.2.2 Implementation Under Test (IUT) identification**
+
+IUT name:
+
+.....
+
+.....
+
+IUT version:
+
+.....
+
+### **6.2.3 System Under Test (SUT) identification**
+
+SUT name:
+
+.....
+
+.....
+
+Hardware configuration:
+
+.....
+
+.....
+
+.....
+
+Operating system:
+
+.....
+
+### **6.2.4 Product supplier**
+
+Name:
+
+.....
+
+Address:
+
+.....
+
+.....
+
+.....
+
+Telephone number:
+
+.....
+
+Facsimile number:
+
+.....
+
+E-mail address:
+
+.....
+
+Additional information:
+
+.....
+
+.....
+
+.....
+
+### **6.2.5 Client (if different from product supplier)**
+
+Name:
+
+.....
+
+Address:
+
+.....
+
+.....
+
+.....
+
+Telephone number:
+
+.....
+
+Facsimile number:
+
+.....
+
+E-mail address:
+
+.....
+
+Additional information:
+
+.....
+
+.....
+
+.....
+
+### 6.2.6 PICS contact person
+
+(A person to contact if there are any queries concerning the content of the ICS)
+
+Name:
+
+Telephone number:
+
+Facsimile number:
+
+E-mail address:
+
+Additional information:
+
+## 6.3 Identification of the MWI specification
+
+This PICS proforma applies to the following standard: [ITU-T Q.3626 v.1].
+
+## 6.4 Global statement of conformance
+
+Are all mandatory capabilities implemented? (Yes/No).....
+
+NOTE – Answering "No" to this question indicates non-conformance to the message waiting indication (MWI) specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma.
+
+## 6.5 Roles
+
+**Table 6-1 – Roles**
+
+| Item | Role | Reference | Status | Support |
+|------|----------------------------------|------------------------------------|--------|---------|
+| 1 | MWI subscriber user agent (MSUA) | Clause 4.4.1 of [ITU-T Q.3626 v.1] | o | |
+| 2 | MWI notifier user agent (MNUA) | Clause 4.4.2 of [ITU-T Q.3626 v.1] | m | |
+| 3 | Message account (MA) | Clause 4.4.3 of [ITU-T Q.3626 v.1] | m | |
+
+Comments:
+
+## 6.6 User role
+
+This clause contains the PICS proforma tables related to the user role. They need to be completed only for user equipment implementations:
+
+Prerequisite: 6.1/1 -- user role
+
+### 6.6.1 Major capabilities
+
+**Table 6-2 – MWI subscriber user agent capabilities**
+
+| Item | Item description | Reference | Status | Support |
+|------|---------------------------------------------------------------------------------------------|--------------------------------------|--------|---------|
+| 1 | The user equipment is able to address the message account using the public service identity | Clause 4.4.3.2 of [ITU-T Q.3626 v.1] | o.1 | |
+| 2 | The user equipment is able to address the message account using the public user identity | Clause 4.4.3.2 of [ITU-T Q.3626 v.1] | o.1 | |
+
+o.1: It is mandatory to support at least one of these items.
+
+Comments:
+
+## 6.7 Network role
+
+This clause contains the PICS proforma tables related to the network role. They need to be completed only for network implementations:
+
+Prerequisite: 6.1/2 network role
+
+**Table 6.3 – MWI Notifier User Agent (MNUA) capabilities**
+
+| Item | Item description | Reference | Status | Support |
+|------|---------------------------------------------------------------------------------------------------|-------------------------------|--------|---------|
+| 1 | The MNUA includes the message account in the MIME body to identify the served user | Clause 3.5 of [IETF RFC 3842] | o | |
+| 2 | The MNUA includes the message summary line in the MIME body to identify the served user | Clause 3.5 of [IETF RFC 3842] | o | |
+| 3 | The MNUA append message headers, which further describe newly added messages as "opt-msg-headers" | Clause 3.5 of [IETF RFC 3842] | o | |
+
+
+
+
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4011.2-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4011.2-201608-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d848fb44b4c22bf227b2774bc666c11c1507b6e4
--- /dev/null
+++ b/marked/Q/T-REC-Q.4011.2-201608-I_PDF-E/raw.md
@@ -0,0 +1,1397 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4011.2**
+
+(08/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**Closed user group using IP multimedia core
+network subsystem; Conformance test
+specification – Part 2: Test suite structure and
+test purposes; Network side**
+
+Recommendation ITU-T Q.4011.2
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T Q.4011.2
+
+## Closed user group using IP multimedia core network subsystem; Conformance test specification – Part 2: Test suite structure and test purposes; Network side
+
+## Summary
+
+Recommendation ITU-T Q.4011.2 provides the testing requirements for the supplementary service "Closed user group (CUG) using IP multimedia (IM) core network (CN) subsystem; Conformance Test Specification – Part 2: Test suite structure and test purposes (TSS&TP); Network side" (based on Recommendation ITU-T Q.3627 v.1).
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4011.2, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|--------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4011.2 v.1 | 2016-08-29 | 11 | 11.1002/1000/13005 |
+
+## Keywords
+
+IMS, IP multimedia subsystem , malicious communication identification, MCID, testing, test suite structure and test purposes, TSS&TP.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2017
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-----------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 1 |
+| 5 Conventions ..... | 2 |
+| 6 Test suite structure..... | 3 |
+| 7 Test purposes ..... | 4 |
+| 7.1 Introduction ..... | 4 |
+| 7.2 Test purposes for closed user group ..... | 5 |
+| 7.3 Interaction with other services..... | 49 |
+
+
+
+## Recommendation ITU-T Q.4011.2
+
+## Closed user group using IP multimedia core network subsystem; Conformance test specification – Part 2: Test suite structure and test purposes; Network side
+
+# 1 Scope
+
+This Recommendation is Part 2 of a multi-part deliverable covering closed user group (CUG) using IP multimedia (IM) core network (CN) subsystem; Conformance test specification, as identified below:
+
+Part 1: "Protocol implementation conformance statement (PICS)";
+
+**Part 2: "Test suite structure and test purposes (TSS&TP); Network side";**
+
+Part 3: "Test suite structure and test purposes (TSS&TP); User side".
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ITU-T Q.3627 v.1] Recommendation ITU-T Q.3627 v.1 (2016): *Closed user group using IP multimedia core network subsystem – Protocol Specification.*
+
+[ITU-T Q.4011.1 v.1] Recommendation ITU-T Q.4011.1 v.1 (2016): *Closed user group using IP multimedia core network subsystem; Conformance test specification – Part 1: Protocol implementation conformance statement.*
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+None.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|-------------------------------------------|
+| AS | Application Server |
+| CD | Communication Deflection |
+| CDIV | Communication Diversion service |
+| CFB | Communication Forwarding on Busy |
+| CFNL | Communication Forwarding on Not Logged-in |
+| CFNR | Communication Forwarding on no Reply |
+
+CFU Communication Forwarding Unconditional
+CONF Conference calling
+CSCF Call Session Control Function
+CUG Closed User Group
+ECT Explicit Communication Transfer
+IA Incoming Access
+ICB Incoming Communication Barring within a CUG
+IMS IP Multimedia Subsystem
+IP Internet Protocol
+ISC Reference point between Serving CSCF and Application Server
+IUT Implementation Under Test
+NNI Network-to-Network Interface
+OA Outgoing Access
+OAE Outgoing Access, explicit request required
+OAI Outgoing Access, implicit outgoing access for all communications
+OCB Outgoing Communication Barring within a CUG
+PIXIT Protocol Implementation extra Information for Testing
+SIP Session Initiation Protocol
+SUT System Under Test
+TP Test Purposes
+TSS Test Suite Structure
+UE User Equipment
+
+# **5 Conventions**
+
+None.
+
+# 6 Test suite structure
+
+**Table 6-1 – Test suite structure**
+
+| | | | |
+|-----|----------------|------------------------------|-------------|
+| CUG | originating_AS | CUG without preference | CUG_N01_xxx |
+| | | CUG without preference + OAE | CUG_N02_xxx |
+| | | CUG without preference + OAI | CUG_N03_xxx |
+| | | CUG with preference | CUG_N04_xxx |
+| | | CUG with preference + OAE | CUG_N05_xxx |
+| | | CUG with preference + OAI | CUG_N06_xxx |
+| | | No CUG | CUG_N07_xxx |
+| | | | |
+| | terminating_AS | CUG with OA not allowed | CUG_N08_xxx |
+| | | CUG with OA allowed | CUG_N09_xxx |
+| | | No CUG | CUG_N10_xxx |
+| | Services | | |
+| | | CONF | CUG_N11_xxx |
+| | | CDIV | CUG_N12_xxx |
+| | | ECT | CUG_N13_xxx |
+
+### 6.1.1 Testing of the application server
+
+The application server (AS) entity is responsible for performing and managing services. The reference point between serving call session control function (CSCF) and application server (ISC) interface is the appropriate access point for testing, see Figure 6.1.1-1.
+
+
+
+The diagram shows a central green rectangular block labeled "Application server" and "Implementation under test". To its left and right are cyan rectangular blocks labeled "Test system". Each "Test system" is connected to the central block via a horizontal line labeled "ISC" with a vertical tick mark on the line.
+
+Diagram showing the applicable interface to test AS functionalities. A central green box labeled 'Application server' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system' via ISC interfaces.
+
+Q.4011.2v1(16)\_F6.1.1-1
+
+**Figure 6.1.1-1 – Applicable interface to test AS functionalities**
+
+If the ISC interface is not accessible it is also possible to perform the test of the AS using any network-to-network interface (NNI) (i.e., Mw, Mg, Mx) (see Figure 6.1.1-2). In case only the Gm interface is accessible this interface can be used instead for testing, but the verification of all requirements may not be possible.
+
+
+
+The diagram shows a central green rectangular block labeled "CSCF (and/or AS)" and "Implementation under test". To its left and right are cyan rectangular blocks labeled "Test system". Each "Test system" is connected to the central block via a horizontal line labeled "Mw, Mg, Mx" with a vertical tick mark on the line.
+
+Diagram showing the applicable interfaces for tests using a (generic) NNI. A central green box labeled 'CSCF (and/or AS)' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system' via Mw, Mg, Mx interfaces.
+
+Q.4011.2v1(16)\_F6.1.1-2
+
+**Figure 6.1.1-2 – Applicable interfaces for tests using a (generic) NNI**
+
+# 7 Test purposes
+
+## 7.1 Introduction
+
+For each test requirement a test purpose (TP) is defined.
+
+### 7.1.1 TP naming convention
+
+Test purposes (TPs) are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see Table 1).
+
+**Table 1 – TP identifier naming convention scheme**
+
+| | | |
+|-------------------------------------|--------------------------|-------------------------------------------------------------|
+| Identifier: __ | | |
+| | = supplementary service: | e.g. "CUG" |
+| | = type of IUT: | U User equipment
N Network entity |
+| | = group | 2 digit field representing group reference according to TSS |
+| | = sequential number | (001-999) |
+
+### 7.1.2 Test strategy
+
+As the base standard [ITU-T Q.3627 v.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 [ITU-T Q.4011.1 v.1]. The criteria applied include the following:
+
+- Whether or not a test case can be built from the TP is not considered.
+
+### 7.2 Test purposes for closed user group
+
+#### 7.2.1 Actions at the AS of the originating user
+
+##### 7.2.1.1 CUG without preference
+
+| | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|--|--|---|---------|
+| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_001 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/1 [ITU-T Q.4011.1 v.1] | | | | | | | | | |
+| Test purpose
CUG without preference: INVITE with CUG index, successful.
Ensure that the system under test (SUT) on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
INVITE2:
Content-Disposition: ...;handling=required
[PIXIT] networkIndicator>
[related to registered CUG index]
11
| | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | ➔ | |
| ➔ | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ | | | ➔ | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | |
+| INVITE1 | ➔ | | | | | | | | | | | |
+| | ➔ | INVITE2 | | | | | | | | | | |
+
+Rec. ITU-T Q.4011.2 (08/2016) 5
+
+| | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|-------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_002 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/1 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG without preference + OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring (OCB). | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | → | |
| 603 Decline | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | | AS | INVITE | → | | 603 Decline | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 603 Decline | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_003 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG without preference: INVITE with unallocated CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
FALSE
[unregistered CUG]
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+6 **Rec. ITU-T Q.4011.2 (08/2016)**
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|-----------|
+| CUG/originating_AS/CUG without preference | CUG_N01_004 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG without preference: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG index]
INVITE2:
Content-Disposition: ...;handling=required
[registered CUG index]
[related to registered CUG index]
11
| | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | ➔ | ➔ INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ | ➔ INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|-------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/1 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG without preference +OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
[registered CUG index]
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | → | |
| 603 Decline | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | | AS | INVITE | → | | 603 Decline | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 603 Decline | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG without preference | TP
CUG_N01_006 | CUG reference
clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG without preference: INVITE with unallocated CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
[unregistered CUG]
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+8 **Rec. ITU-T Q.4011.2 (08/2016)**
+
+| TSS | TP | CUG reference | Selection expression |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|----------------------------------------------------------|
+| CUG/originating_AS/CUG without preference | CUG_N01_007 | Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG without preference: INVITE without CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
rejects the INVITE request by sending a 403 Forbidden due to missing CUGindex. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | |
+| SIP header values:
INVITE:
FALSE
| | | |
+| Comments:
Test equipment (Gm) | | | |
+| INVITE | AS | | |
+| 403 Forbidden | ← | | |
+| ACK | → | | |
+
+| TSS | TP | CUG reference | Selection expression |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|----------------------------------------------------------|
+| CUG/originating_AS/CUG without preference | CUG_N01_008 | Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/1
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG without preference: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
rejects the INVITE request by sending a 403 Forbidden due to missing CUGindex. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | |
+| SIP header values:
INVITE:
TRUE
| | | |
+| Comments:
Test equipment (Gm) | | | |
+| INVITE | AS | | |
+| 403 Forbidden | ← | | |
+| ACK | → | | |
+
+| | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG without preference | | TP
CUG_N01_009 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/1 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG without preference: INVITE for non-CUG communication, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden due to missing cug XML element. | | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
No xml element | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | | |
+
+### 7.2.1.2 CUG without preference + OAE
+
+| | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|--|--|---|---------|
+| TSS
CUG/originating_AS/CUG without preference + OAE | | TP
CUG_N02_001 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | |
+| Test purpose
CUG without preference + OAE: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
INVITE2:
Content-Disposition: ...;handling=required
[PIXIT]
[related to registered CUG index]
11
| | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → | |
| → | INVITE2 |
| | | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | | | → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | | |
+| INVITE1 | → | | | | | | | | | | | | |
+| | → | INVITE2 | | | | | | | | | | | |
+
+10 Rec. ITU-T Q.4011.2 (08/2016)
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG without preference + OAE | TP
CUG_N02_002 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/2 AND
PICS 4.7.1/10
[ITU-T Q.4011.111 v.1] |
+| Test purpose
CUG without preference + OAE + OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE:
FALSE
[registered CUG index]
| | | |
+| Comments:
Test equipment (Gm) → AS
INVITE →
603 Decline ←
ACK → | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG without preference + OAE | TP
CUG_N02_003 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/2
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG without preference + OAE: INVITE with unallocated CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE:
FALSE
[unregistered CUG]
403 Forbidden
Reason: ... | | | |
+| Comments:
Test equipment (Gm) → AS
INVITE →
403 Forbidden ←
ACK → | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------|
+| CUG/originating_AS/CUG without preference + OAE | CUG_N02_004 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG without preference + OAE: INVITE with CUG index and outgoingAccessRequest = true, successful non CUG communication.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG index]
INVITE2:
[PIXIT] networkIndicator>
[related to registered CUG index]
10
| | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → | INVITE2 | | | | | | | |
+
+| TSS
CUG/originating_AS/CUG without preference + OAE | TP
CUG_N02_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|----------------------|---------|
+| Test purpose
CUG without preference + OAE + OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards the INVITE request containing no xml element cug. | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG index]
INVITE2:
No xml element | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | ➔ ➔ | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ ➔ | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | ➔ ➔ | INVITE2 | | | | | | | |
+
+| TSS
CUG/originating_AS/CUG without preference + OAE | TP
CUG_N02_006 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|--|--------|---|--|---------------|---|--|-----|---|--|
+| Test purpose
CUG without preference + OAE: INVITE with unallocated CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
[unregistered CUG]
403 Forbidden
Reason: ... | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | |
| INVITE | ➔ | |
| 403 Forbidden | ⬅ | |
| ACK | ➔ | |
| | | | Test equipment (Gm) | AS | | INVITE | ➔ | | 403 Forbidden | ⬅ | | ACK | ➔ | |
+| Test equipment (Gm) | AS | | | | | | | | | | | | | | |
+| INVITE | ➔ | | | | | | | | | | | | | | |
+| 403 Forbidden | ⬅ | | | | | | | | | | | | | | |
+| ACK | ➔ | | | | | | | | | | | | | | |
+
+Rec. ITU-T Q.4011.2 (08/2016) 13
+
+| TSS | TP | CUG reference | Selection expression |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------|
+| CUG/originating_AS/CUG without preference + OAE | CUG_N02_007 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG without preference + OAE: INVITE without CUG index, unsuccessful outgoing access not allowed.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = false, rejects the INVITE request by sending a 403 Forbidden due to outgoing access not allowed. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE:
FALSE
403 Forbidden
Reason: ... | | | |
+| Comments:
Test equipment (Gm) | | | |
+| INVITE | AS | | |
+| 403 Forbidden | ← | | |
+| ACK | → | | |
+
+| TSS | TP | CUG reference | Selection expression |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------|
+| CUG/originating_AS/CUG without preference + OAE | CUG_N02_008 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/2 [ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG without preference + OAE: INVITE without CUG index and with outgoingAccessRequest = true, successful outgoing access allowed.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, forwards the INVITE request containing no xml element cug due to outgoing access allowed. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE1:
TRUE
INVITE2:
No xml element | | | |
+| Comments:
Test equipment (Gm) | | | |
+| INVITE1 | AS | | Test equipment (ISC, Mw) |
+| | → | | INVITE2 |
+
+| TSS | TP | CUG reference | Selection expression |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|----------------------------------------------------------|
+| CUG/originating_AS/CUG without preference + OAE | CUG_N02_009 | Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/2
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG without preference + OAE: INVITE for non-CUG communication, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE:
No xml element
403 Forbidden
Reason: ... | | | |
+| Comments:
Test equipment (ISC) | | | |
+| INVITE | → | AS | |
+| 403 Forbidden | ← | | |
+| ACK | → | | |
+
+#### 7.2.1.3 CUG without preference + OAI
+
+| TSS | TP | CUG reference | Selection expression |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|----------------------------------------------------------|
+| CUG/originating_AS/CUG without preference + OAI | CUG_N03_001 | Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/3
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG without preference + OAI: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
INVITE2:
[PIXIT]
[related to registered CUG index]
10
| | | |
+| Comments:
Test equipment (Gm) | | | |
+| INVITE1 | → | AS | Test equipment (ISC, Mw) |
+| | | → | INVITE2 |
+
+| | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|----------------------|---------|
+| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_002 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/3 [ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG without preference + OAI and OCB within CUG: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing no xml element cug. | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
INVITE2:
No xml element | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → → | INVITE2 | | | | | | | |
+
+| | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|--------|---|---------------|---|-----|---|
+| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_003 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/3 [ITU-T Q.4011.1 v.1] | | | | | | | | |
+| Test purpose
CUG without preference + OAI: INVITE with unregistered CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | | | |
+| SIP header values:
INVITE:
FALSE
[unregistered CUG]
403 Forbidden
Reason: ... | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS |
| INVITE | → |
| 403 Forbidden | ← |
| ACK | → |
| | | | Test equipment (Gm) | AS | INVITE | → | 403 Forbidden | ← | ACK | → |
+| Test equipment (Gm) | AS | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | |
+| ACK | → | | | | | | | | | | |
+
+16 Rec. ITU-T Q.4011.2 (08/2016)
+
+
+
+| | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|----------------------|---------|
+| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/3 [ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG without preference + OAI and OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing no xml element cug. | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG index]
INVITE2:
No xml element | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → → | INVITE2 | | | | | | | |
+
+| | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|--------|---|---------------|---|-----|---|
+| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_006 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/3 [ITU-T Q.4011.1 v.1] | | | | | | | | |
+| Test purpose
CUG without preference + OAI: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
[unregistered CUG]
403 Forbidden
Reason: ... | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS |
| INVITE | → |
| 403 Forbidden | ← |
| ACK | → |
| | | | Test equipment (Gm) | AS | INVITE | → | 403 Forbidden | ← | ACK | → |
+| Test equipment (Gm) | AS | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | |
+| ACK | → | | | | | | | | | | |
+
+18 Rec. ITU-T Q.4011.2 (08/2016)
+
+| | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|--------------|---------|
+| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_007 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/3
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG without preference + OAI: INVITE without CUG index, successful outgoing access allowed.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
forwards an INVITE request containing no xml element cug. | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
INVITE2:
No xml element | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → → | INVITE2 | | | | | | | |
+
+| | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|--------------|---------|
+| TSS
CUG/originating_AS/CUG without preference + OAI | TP
CUG_N03_008 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/3
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG without preference + OAI: INVITE without CUG index and with outgoingAccessRequest = true, successful outgoing access allowed.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
forwards an INVITE request containing no xml element cug. | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: allowed permanent | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
INVITE2:
No xml element | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → → | INVITE2 | | | | | | | |
+
+**Rec. ITU-T Q.4011.2 (08/2016)** 19
+
+
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_002 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/4 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference + OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | |
+| SIP header values:
INVITE:
FALSE
[registered CUG index]
| | | |
+| Comments:
Test equipment (Gm) → AS
INVITE →
603 Decline ←
ACK → | | | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_003 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference: INVITE with unregistered CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | |
+| SIP header values:
INVITE:
FALSE
[unregistered CUG]
403 Forbidden
Reason: ... | | | |
+| Comments:
Test equipment (Gm) → AS
INVITE →
403 Forbidden ←
ACK → | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|-----------|
+| CUG/originating_AS/CUG with preference | CUG_N04_004 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG with preference: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG index]
INVITE2:
Content-Disposition: ...;handling=required
[registered CUG index] networkIndicator>
[related to registered CUG index]
11
| | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | ➔ | ➔ INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ | ➔ INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|-------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/4 AND PICS 4.7.1/10 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with preference +OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
[registered CUG index]
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | → | |
| 603 Decline | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | | AS | INVITE | → | | 603 Decline | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 603 Decline | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_006 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/4 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with preference: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
[unregistered CUG]
403 Forbidden
Reason: ... | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+Rec. ITU-T Q.4011.2 (08/2016) 23
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------|
+| CUG/originating_AS/CUG with preference | CUG_N04_007 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG with preference: INVITE without CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
INVITE2:
Content-Disposition: ...;handling=required
[registered CUG index] networkIndicator>
[related to preferred CUG index]
11
| | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → | INVITE2 | | | | | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_008 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
rejects the INVITE request by sending a 403 Forbidden due to outgoing access not allowed. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | |
+| SIP header values:
INVITE:
TRUE
403 Forbidden
Reason: ... | | | |
+| Comments: | | | |
+| Test equipment (Gm) | AS | | |
+| INVITE | → | | |
+| 403 Forbidden | ← | | |
+| ACK | → | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG with preference | TP
CUG_N04_009 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/4
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference: INVITE for non-CUG communication, successful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: not allowed | | | |
+| SIP header values:
INVITE1:
No xml element
INVITE2:
Content-Disposition: ...;handling=required
[registered CUG index]
[related to preferred CUG index]
11
| | | |
+| Comments: | | | |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | |
+| INVITE1 | → | → | INVITE2 |
+
+Rec. ITU-T Q.4011.2 (08/2016) 25
+
+#### 7.2.1.5 CUG with preference + OAE
+
+| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_001 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/5
[ITU-T Q.4011.1 v.1] | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------|
+| Test purpose
CUG with preference + OAE: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
INVITE2:
Content-Disposition: ...;handling=required
[PIXIT] networkIndicator>
[related to registered CUG index]
11
| | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → | INVITE2 | | | | | | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_002 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/5 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference + OAE + OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline to Outgoing Communication Barring. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE:
FALSE
[registered CUG index]
| | | |
+| Comments:
Test equipment (Gm) → AS
INVITE →
603 Decline ←
ACK → | | | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_003 | CUG reference
Clause 4.5.2.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/5
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference + OAE: INVITE with unregistered CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE:
FALSE
[unregistered CUG]
403 Forbidden
Reason: ... | | | |
+| Comments:
Test equipment (Gm) → AS
INVITE →
403 Forbidden ←
ACK → | | | |
+
+
+
+| | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|----------------------|---------|
+| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_005 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/5 [ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG with preference + OAE + OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing no xml element cug. | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG index]
INVITE2:
No xml element | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → → | INVITE2 | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|--|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG with preference + OAE | TP
CUG_N05_006 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/5 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with preference + OAE: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
[unregistered CUG]
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | AS | | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (Gm) | AS | | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+Rec. ITU-T Q.4011.2 (08/2016) 29
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------|
+| CUG/originating_AS/CUG with preference + OAE | CUG_N05_007 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/5
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG with preference + OAE: INVITE without CUG index and with outgoingAccessRequest = false, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
INVITE2:
Content-Disposition: ...;handling=required
[PIXIT] networkIndicator>
[related to preferred CUG index]
11
| | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → | INVITE2 | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------|
+| CUG/originating_AS/CUG with preference + OAE | CUG_N05_008 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/5 [ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference + OAE: INVITE without CUG index and with outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
forwards an INVITE request containing no xml element cug. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE1:
TRUE
INVITE2:
No xml element | | | |
+| Comments:
Test equipment (Gm) → AS → Test equipment (ISC, Mw)
INVITE1 → → INVITE2 | | | |
+
+| TSS | TP | CUG reference | Selection expression |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------|
+| CUG/originating_AS/CUG with preference + OAE | CUG_N05_009 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND PICS 4.7.1/5 [ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference + OAE: INVITE for non-CUG communication, successful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug,
returns an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access). | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed per communication | | | |
+| SIP header values:
INVITE1:
No xml element
INVITE2:
Content-Disposition: ...;handling=required
[PIXIT] networkIndicator>
[related to preferred CUG index]
11
| | | |
+| Comments:
Test equipment (Gm) → AS → Test equipment (ISC, Mw)
INVITE1 → → INVITE2 | | | |
+
+**7.2.1.6 CUG with preference + OAI**
+
+| | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|--|--|---|---------|
+| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_001 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/6 [ITU-T Q.4011.1 v.1] | | | | | | | | | |
+| Test purpose
CUG with preference + OAI: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
INVITE2:
[PIXIT] networkIndicator>
[related to registered CUG index]
10
| | | | | | | | | | | | |
+| Comments: | | | | | | | | | | | | |
+| | Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | ➠ | |
| ➠ | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➠ | | | ➠ | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | |
+| INVITE1 | ➠ | | | | | | | | | | | |
+| | ➠ | INVITE2 | | | | | | | | | | |
+
+32 Rec. ITU-T Q.4011.2 (08/2016)
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_002 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/6 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference + OAI and OCB: INVITE with CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | |
+| SIP header values:
INVITE:
FALSE
[registered CUG index]
| | | |
+| Comments:
Test equipment (Gm) → AS
INVITE →
603 Decline ←
ACK → | | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_003 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/6
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with preference + OAI and OCB within CUG: INVITE with CUG index, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing no xml element cug is present | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
INVITE2:
No xml element | | | |
+| Comments:
Test equipment (Gm) → AS → INVITE2
INVITE1 → | | | |
+
+| | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_004 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/6 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with preference + OAI: INVITE with unregistered CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
FALSE
[unregistered CUG]
403 Forbidden
Reason: ... | | | | | | | | | | | | | | | |
+| Comments: | | | | | | | | | | | | | | | |
+| | Test equipment (Gm) | | AS |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+34 Rec. ITU-T Q.4011.2 (08/2016)
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|---------|
+| CUG/originating_AS/CUG with preference + OAI | CUG_N06_005 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/6
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG with preference + OAI: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG]
INVITE2:
[PIXIT]
[related to registered CUG index]
10
| | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → | INVITE2 | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|-------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|--------|---|--|-------------|---|--|-----|---|--|
+| CUG/originating_AS/CUG with preference + OAI | CUG_N06_006 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/6 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with preference + OAI and OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG]
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE | → | |
| 603 Decline | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE | → | | 603 Decline | ← | | ACK | → | |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 603 Decline | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------|----------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|-----------|
+| CUG/originating_AS/CUG with preference + OAI | CUG_N06_007 | Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | PICS 4.5.1/2 AND
PICS 4.7.1/6
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose
CUG with preference + OAI and OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
registered CUGIndex,
forwards an INVITE request containing no xml element cug is present | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB within CUG
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
[registered CUG]
INVITE2:
No xml element | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | → | → INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | → | → INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | |
+| INVITE1 | → | → INVITE2 | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_008 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND PICS 4.7.1/6 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with preference + OAI: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true and
unregistered CUGIndex,
rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
[unregistered CUG]
403 Forbidden
Reason: ... | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+ Rec. ITU-T Q.4011.2 (08/2016) 37
+
+| | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------|-----------|---------------------------------|---------|---|--|--|---|---------|
+| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_009 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/6
[ITU-T Q.4011.1 v.1] | | | | | | | | | |
+| Test purpose
CUG with preference + OAI: INVITE without CUG index and with outgoingAccessRequest = true, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
forwards an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to preferred CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access). | | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
TRUE
INVITE2:
[PIXIT]
[related to preferred CUG index]
10
| | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (ISC, Mw) |
| INVITE1 | ➔ | |
| ➔ | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (ISC, Mw) | INVITE1 | ➔ | | | ➔ | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (ISC, Mw) | | | | | | | | | | |
+| INVITE1 | ➔ | | | | | | | | | | | |
+| | ➔ | INVITE2 | | | | | | | | | | |
+
+| | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------|-----------|--------|---|-------------|---|-----|---|
+| TSS
CUG/originating_AS/CUG with preference + OAI | TP
CUG_N06_010 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 AND
PICS 4.7.1/6 AND
PICS 4.7.1/10
[ITU-T Q.4011.1 v.1] | | | | | | | | |
+| Test purpose
CUG with preference + OAI and OCB: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
rejects the INVITE request by sending a 603 Decline due to outgoing communication barring. | | | | | | | | | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: OCB
Options for public identity in use:
Preferential CUG: registered CUG
Outgoing access: allowed permanent | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
| | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS |
| INVITE | ➔ |
| 603 Decline | ⬅ |
| ACK | ➔ |
| | | | Test equipment (Gm) | AS | INVITE | ➔ | 603 Decline | ⬅ | ACK | ➔ |
+| Test equipment (Gm) | AS | | | | | | | | | | |
+| INVITE | ➔ | | | | | | | | | | |
+| 603 Decline | ⬅ | | | | | | | | | | |
+| ACK | ➔ | | | | | | | | | | |
+
+38 Rec. ITU-T Q.4011.2 (08/2016)
+
+
+
+| | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/No CUG | TP
CUG_N07_003 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
No CUG: INVITE without CUG index, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = false,
rejects the INVITE request by sending a 403 Forbidden. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has not subscribed to CUG | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
FALSE
403 Forbidden
Reason: ... | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | ➠ | |
| 403 Forbidden | ⬅ | |
| ACK | ➠ | |
| | | | Test equipment (Gm) | | AS | INVITE | ➠ | | 403 Forbidden | ⬅ | | ACK | ➠ | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | ➠ | | | | | | | | | | | | | | |
+| 403 Forbidden | ⬅ | | | | | | | | | | | | | | |
+| ACK | ➠ | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/originating_AS/No CUG | TP
CUG_N07_004 | CUG reference
Clause 4.5.2.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
No CUG: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
outgoingAccessRequest = true,
rejects the INVITE request by sending a 403 Forbidden. | | | | | | | | | | | | | | | |
+| Preconditions: Originating user has not subscribed to CUG | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
TRUE
403 Forbidden
Reason: ... | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE | ➠ | |
| 403 Forbidden | ⬅ | |
| ACK | ➠ | |
| | | | Test equipment (Gm) | | AS | INVITE | ➠ | | 403 Forbidden | ⬅ | | ACK | ➠ | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | |
+| INVITE | ➠ | | | | | | | | | | | | | | |
+| 403 Forbidden | ⬅ | | | | | | | | | | | | | | |
+| ACK | ➠ | | | | | | | | | | | | | | |
+
+40 Rec. ITU-T Q.4011.2 (08/2016)
+
+### 7.2.2 Actions at the AS of the terminating user
+
+#### 7.2.2.1 CUG with outgoing access (OA) not allowed
+
+| | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|-----------|----------------------------|---------|---|--|--|---|---------|
+| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_001 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | |
+| Test purpose
CUG with IA not allowed: INVITE with interlock code matching registered CUG index and without outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
forwards an INVITE request containing no xml element cug. | | | | | | | | | | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-ICB)
Options for public identity in use:
Incoming access: not allowed | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
<cug>
<networkIndicator>[PIXIT]</networkIndicator>
<cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode>
<cugCommunicationIndicator>11</cugCommunicationIndicator>
</cug>
INVITE2:
No XML element | | | | | | | | | | | | |
+| Comments:
| Test equipment (ISC, Mw) | AS | Test equipment (Gm) |
| INVITE1 | → | |
| → | INVITE2 |
| | | | Test equipment (ISC, Mw) | AS | Test equipment (Gm) | INVITE1 | → | | | → | INVITE2 |
+| Test equipment (ISC, Mw) | AS | Test equipment (Gm) | | | | | | | | | | |
+| INVITE1 | → | | | | | | | | | | | |
+| | → | INVITE2 | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|-----------|--|--------|---|--|-------------|---|--|-----|---|--|
+| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_002 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with IA not allowed and ICB: INVITE with interlock code matching registered CUG index and without outgoing access, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
rejects the INVITE request by sending a 603 Decline due to incoming calls barred. | | | | | | | | | | | | | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: ICB
Options for public identity in use:
Incoming access: not allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
<cug>
<networkIndicator>[PIXIT]</networkIndicator>
<cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode>
<cugCommunicationIndicator>11</cugCommunicationIndicator>
</cug> | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (ISC, Mw) | AS | |
| INVITE | → | |
| 603 Decline | ← | |
| ACK | → | |
| | | | Test equipment (ISC, Mw) | AS | | INVITE | → | | 603 Decline | ← | | ACK | → | |
+| Test equipment (ISC, Mw) | AS | | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 603 Decline | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+**Rec. ITU-T Q.4011.2 (08/2016)** 41
+
+| | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|-----------|--|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_003 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with IA not allowed: INVITE with interlock code not matching registered CUG index and without outgoing access, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode not related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
rejects the INVITE request by sending a 403 Forbidden due to not matched CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
[PIXIT]
[not related to registered CUG index]
11
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (ISC, Mw) | AS | |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (ISC, Mw) | AS | | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (ISC, Mw) | AS | | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|-----------|----------------------------|---------|---|--|--|---|---------|
+| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_004 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | |
+| Test purpose
CUG with IA allowed: INVITE with interlock code matching registered CUG index and without outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
forwards an INVITE request containing no xml element cug. | | | | | | | | | | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-ICB)
Options for public identity in use:
Incoming access: allowed | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
[PIXIT]
[related to registered CUG index]
11
INVITE2:
No XML element | | | | | | | | | | | | |
+| Comments:
| Test equipment (ISC, Mw) | AS | Test equipment (Gm) |
| INVITE1 | → | |
| → | INVITE2 |
| | | | Test equipment (ISC, Mw) | AS | Test equipment (Gm) | INVITE1 | → | | | → | INVITE2 |
+| Test equipment (ISC, Mw) | AS | Test equipment (Gm) | | | | | | | | | | |
+| INVITE1 | → | | | | | | | | | | | |
+| | → | INVITE2 | | | | | | | | | | |
+
+42 Rec. ITU-T Q.4011.2 (08/2016)
+
+| | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|--|-----------|--------|---|--|-------------|---|--|-----|---|--|
+| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_005 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with IA allowed and ICB: INVITE with interlock code matching registered CUG index and without outgoing access, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
rejects the INVITE request by sending a 603 Decline due to incoming calls barred. | | | | | | | | | | | | | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: ICB
Options for public identity in use:
Incoming access: allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
[PIXIT]
[related to registered CUG index]
11
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (ISC, Mw) | | AS |
| INVITE | → | |
| 603 Decline | ← | |
| ACK | → | |
| | | | Test equipment (ISC, Mw) | | AS | INVITE | → | | 603 Decline | ← | | ACK | → | |
+| Test equipment (ISC, Mw) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 603 Decline | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|---------------------------------|--|-----------|--------|---|--|---------------|---|--|-----|---|--|
+| TSS
CUG/ terminating _AS/CUG with OA not allowed | TP
CUG_N08_006 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with IA allowed: INVITE with interlock code not matching registered CUG index and without outgoing access, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode not related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "11" (CUG without outgoing access),
rejects the INVITE request by sending a 403 Forbidden due to not matched CUG index. | | | | | | | | | | | | | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: allowed | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
[PIXIT]
[not related to registered CUG index]
11
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (ISC, Mw) | | AS |
| INVITE | → | |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (ISC, Mw) | | AS | INVITE | → | | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (ISC, Mw) | | AS | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | |
+
+ Rec. ITU-T Q.4011.2 (08/2016) 43
+
+
+
+
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------------|---------------------------------------------------------------------|
+| TSS
CUG/ terminating _AS/CUG with OA allowed | TP
CUG_N09_004 | CUG reference
Clause 4.5.2.10 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with IA allowed: INVITE with interlock code matching registered CUG index and with outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access),
forwards an INVITE request containing no xml element cug. | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: None designated (-ICB)
Options for public identity in use:
Incoming access: allowed | | | |
+| SIP header values:
INVITE1:
[PIXIT]
[related to registered CUG index]
10
INVITE2:
No XML element | | | |
+| Comments:
Test equipment (ISC, Mw) → AS → Test equipment (Gm)
INVITE1 → INVITE2 | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------------|---------------------------------------------------------------------|
+| TSS
CUG/ terminating _AS/CUG with OA allowed | TP
CUG_N09_005 | CUG reference
Clause 4.5.2.10 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with IA allowed and ICB: INVITE with interlock code matching registered CUG index and with outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access),
forwards an INVITE request containing no xml element cug. | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for registered CUG index:
Intra CUG restrictions: ICB
Options for public identity in use:
Incoming access: allowed | | | |
+| SIP header values:
INVITE1:
[PIXIT]
[related to registered CUG index]
10
INVITE2:
No XML element | | | |
+| Comments:
Test equipment (ISC, Mw) → AS → Test equipment (Gm)
INVITE1 → INVITE2 | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|
+| TSS
CUG/ terminating _AS/CUG with OA allowed | TP
CUG_N09_006 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with IA allowed: INVITE with interlock code not matching registered CUG index and with outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode not related to registered CUG index,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access),
forwards an INVITE request containing no xml element cug. | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: allowed | | | |
+| SIP header values:
INVITE1:
[PIXIT]
[not related to registered CUG index]
10
INVITE2:
No XML element | | | |
+| Comments:
Test equipment (ISC, Mw) AS Test equipment (Gm)
INVITE1 → → INVITE2 | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|------------------------------------------------------------------|
+| TSS
CUG/ terminating _AS/CUG with OA allowed | TP
CUG_N09_007 | CUG reference
Clause 4.5.2.10 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.5.1/2 [ITU-T Q.4011.1 v.1] |
+| Test purpose
No CUG: INVITE with interlock code and with outgoing access, successful.
Ensure that the SUT on receipt of an INVITE request containing an xml element cug with
cugInterlockBinaryCode,
networkIndicator (PIXIT) and
cugCommunicationIndicator set to "10" (CUG with outgoing access),
forwards an INVITE request containing no xml element cug. | | | |
+| Preconditions: Terminating user has not subscribed to CUG | | | |
+| SIP header values:
INVITE1:
[PIXIT]
[related to any CUG index]
10
INVITE2:
No XML element | | | |
+| Comments:
Test equipment (ISC, Mw) AS Test equipment (Gm)
INVITE1 → → INVITE2 | | | |
+
+Rec. ITU-T Q.4011.2 (08/2016) 47
+
+#### 7.2.2.3 No CUG
+
+| TSS | TP | CUG reference | Selection expression |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------|--------------------------------------|
+| CUG/ terminating _AS/No CUG | CUG_N10_001 | Clause 4.5.2.10 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with IA not allowed: INVITE without xml element cug, unsuccessful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden. | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed | | | |
+| SIP header values:
INVITE:
No xml element | | | |
+| Comments: | | | |
+| Test equipment (ISC) | AS | | |
+| INVITE | → | | |
+| 403 Forbidden | ← | | |
+| ACK | → | | |
+
+| TSS | TP | CUG reference | Selection expression |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------|--------------------------------------|
+| CUG/ terminating _AS/No CUG | CUG_N10_002 | Clause 4.5.2.10 of
[ITU-T Q.3627 v.1] | PICS 4.5.1/2
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with IA allowed: INVITE without xml element cug, successful.
Ensure that the SUT on receipt of an INVITE request containing no xml element cug, forwards an INVITE request containing no xml element cug. | | | |
+| Preconditions: Terminating user has subscribed to CUG
Options for public identity in use:
Incoming access: allowed | | | |
+| SIP header values:
INVITE1:
No xml element
INVITE2:
No XML element | | | |
+| Comments: | | | |
+| Test equipment (ISC, Mw) | AS | | Test equipment (Gm) |
+| INVITE1 | → | | → INVITE2 |
+
+## 7.3 Interaction with other services
+
+### 7.3.1 Conference calling (CONF)
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|---------------------------------------------------------------------|
+| TSS
CUG/Services/CONF | TP
CUG_N11_001 | CUG reference
Clause 4.6.6 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/7
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with OA not allowed: First added conferee join the conference, successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the conference focus allows to join the created conference as the first conferee. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | |
+| SIP header values:
INVITE:
Request Line
FALSE
[registered CUG index]
| | | |
+| Comments:
Test equipment (Gm) AS
A conference is already created
INVITE →
200 OK ← | | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------------------|---------------------------------------------------------------------|
+| TSS
CUG/Services/CONF | TP
CUG_N11_002 | CUG reference
Clause 4.6.6 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/7
[ITU-T Q.4011.1 v.1] |
+| Test purpose
CUG with OA not allowed: Subsequent conferee added to the conference, successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the conference focus allows to join the created conference as a subsequent conferee and belongs to the same closed user group. | | | |
+| Preconditions: Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed | | | |
+| SIP header values:
INVITE:
Request Line
FALSE
[registered CUG index]
| | | |
+| Comments:
Test equipment (ISC, Mw) AS
A conference is already created
A CUG user is already added to the conference
INVITE →
200 OK ← | | | |
+
+### 7.3.2 Communication Diversion Services (CDIV)
+
+| | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------|--|-----------|--|---------------------------------|---------|---|--|---|---------|
+| TSS
CUG/Services/CDIV | TP
CUG_N12_001 | CUG reference
Clause 4.6.7.1 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, communication forwarding unconditional (CFU) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFU. | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding Unconditional (CFU)
Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS | | Test equipment (ISC, Mw) |
| INVITE1 | → | | → | INVITE2 |
| | | | Test equipment (Gm) | | AS | | Test equipment (ISC, Mw) | INVITE1 | → | | → | INVITE2 |
+| Test equipment (Gm) | | AS | | Test equipment (ISC, Mw) | | | | | | | | | |
+| INVITE1 | → | | → | INVITE2 | | | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------|---|-----------|
+| CUG/Services/CDIV | CUG_N12_002 | Clause 4.6.7.1 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose | | | | | | | | | |
+| CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFU successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFU) and the communication to the forwarded-to party is successful.
| | | | | | | | | |
+| Preconditions: | | | | | | | | | |
+| Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding Unconditional (CFU)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in the same CUG
| | | | | | | | | |
+| SIP header values: | | | | | | | | | |
+| INVITE1:
<cug>
<cugCallOperation>
<outgoingAccessRequest>FALSE</outgoingAccessRequest>
<cugIndex>[registered CUG index]</cugIndex>
</cugCallOperation>
</cug>
| | | | | | | | | |
+| Comments: | | | | | | | | | |
+| | Test equipment (Gm) | AS | Test equipment (Gm) |
| INVITE1 | ➔ | ➔ INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE1 | ➔ | ➔ INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | |
+| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|--|-----------|---------|---|--|--|--|--|---------------|---|--|-----|---|--|
+| TSS
CUG/Services/CDIV | TP
CUG_N12_003 | CUG reference
Clause 4.6.7.1 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFU unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFU) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding Unconditional (CFU)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE1 | ➠ | |
| | |
| 403 Forbidden | ⬅ | |
| ACK | ➠ | |
| | | | Test equipment (Gm) | | AS | INVITE1 | ➠ | | | | | 403 Forbidden | ⬅ | | ACK | ➠ | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | | | | |
+| INVITE1 | ➠ | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | |
+| 403 Forbidden | ⬅ | | | | | | | | | | | | | | | | | |
+| ACK | ➠ | | | | | | | | | | | | | | | | | |
+
+52 Rec. ITU-T Q.4011.2 (08/2016)
+
+| | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|---------|---|-----------|--|--|--|-----------------|--|--|--|-------|--|--|--|---|-----------|
+| TSS
CUG/Services/CDIV | TP
CUG_N12_004 | CUG reference
Clause 4.6.7.2 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, communication forwarding on busy (CFB) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the communication diversion service CFB. | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Busy user (CFB)
Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) |
| INVITE1 | → | → INVITE2 | |
| | ← 486 Busy Here | |
| | → ACK | |
| | → | → INVITE3 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | INVITE1 | → | → INVITE2 | | | | ← 486 Busy Here | | | | → ACK | | | | → | → INVITE3 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | |
+| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 486 Busy Here | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | |
+| | | → | → INVITE3 | | | | | | | | | | | | | | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|-----------|--|--|--|-----------------|--|--|--|-------|--|--|--|--|-----------|
+| CUG/Services/CDIV | CUG_N12_005 | Clause 4.6.7.2 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | |
+| Test purpose | | | | | | | | | | | | | | | | | | | | | | | |
+| CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFB successful. | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFB) and the communication to the forwarded-to party is successful. | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions: | | | | | | | | | | | | | | | | | | | | | | | |
+| Originating user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | | | | |
+| Options for registered and preferred CUG index: | | | | | | | | | | | | | | | | | | | | | | | |
+| Intra CUG restrictions: None designated (-OCB) | | | | | | | | | | | | | | | | | | | | | | | |
+| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | | | | |
+| Preferential CUG: None designated | | | | | | | | | | | | | | | | | | | | | | | |
+| Outgoing access: not allowed | | | | | | | | | | | | | | | | | | | | | | | |
+| Forwarding user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | | | | |
+| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | | | | |
+| Incoming access: not allowed | | | | | | | | | | | | | | | | | | | | | | | |
+| Forwarding user has subscribed to CDIV | | | | | | | | | | | | | | | | | | | | | | | |
+| Communication Forwarding on Busy user (CFB) | | | | | | | | | | | | | | | | | | | | | | | |
+| Forwarded-to user has subscribed to CUG | | | | | | | | | | | | | | | | | | | | | | | |
+| Options for public identity in use: | | | | | | | | | | | | | | | | | | | | | | | |
+| Incoming access: not allowed | | | | | | | | | | | | | | | | | | | | | | | |
+| Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | |
+| Originating party and forwarded-to party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values: | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE1: | | | | | | | | | | | | | | | | | | | | | | | |
+| <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug>
| | | | | | | | | | | | | | | | | | | | | | | |
+| Comments: | | | | | | | | | | | | | | | | | | | | | | | |
+| | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) |
| INVITE1 | → | → INVITE2 | |
| | ← 486 Busy Here | |
| | → ACK | |
| | | → INVITE3 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | → | → INVITE2 | | | | ← 486 Busy Here | | | | → ACK | | | | | → INVITE3 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | |
+| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 486 Busy Here | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | |
+| | | | → INVITE3 | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-----------|----------------------------|---------|---|-----------|--|--|-----------------|--|--|-------|---------------|---|--|-----|---|--|
+| TSS
CUG/Services/CDIV | TP
CUG_N12_006 | CUG reference
Clause 4.6.7.2 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFB unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFB) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Busy user (CFB)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) |
| INVITE1 | → | → INVITE2 |
| | ← 486 Busy Here |
| | → ACK |
| 403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE1 | → | → INVITE2 | | | ← 486 Busy Here | | | → ACK | 403 Forbidden | ← | | ACK | → | |
+| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | |
+| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | |
+| | | ← 486 Busy Here | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|------------------------------------------------------|---|--------------------------------------------|--------|------------------------------------------------------|---|--------------------------------------------|
+| CUG/Services/CDIV | CUG_N12_007 | Clause 4.6.7.3 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, communication forwarding on no reply (CFNR) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNR. | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on no Reply (CFNR)
Originating party and forwarding party are in the same CUG | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | |
+| Comments:
Test equipment (Gm) INVITE1 | ➔ | AS | ➔ ← | Test equipment (Gm) INVITE2 180 Ringing | ➔ | Test equipment (ISC, Mw) INVITE3 |
| | | | Test equipment (Gm)
INVITE1 | ➔ | AS | ➔
← | Test equipment (Gm)
INVITE2
180 Ringing | ➔ | Test equipment (ISC, Mw)
INVITE3 |
+| Test equipment (Gm)
INVITE1 | ➔ | AS | ➔
← | Test equipment (Gm)
INVITE2
180 Ringing | ➔ | Test equipment (ISC, Mw)
INVITE3 | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|-----------|--|--|--|---------------|--|--|--|--|-----------|
+| CUG/Services/CDIV | CUG_N12_008 | Clause 4.6.7.3 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | |
+| Test purpose | | | | | | | | | | | | | | | | | | | |
+| CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNR successful. | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNR) and the communication to the forwarded-to party is successful. | | | | | | | | | | | | | | | | | | | |
+| Preconditions: | | | | | | | | | | | | | | | | | | | |
+| Originating user has subscribed to CUG | | | | | | | | | | | | | | | | | | | |
+| Options for registered and preferred CUG index: | | | | | | | | | | | | | | | | | | | |
+| Intra CUG restrictions: None designated (-OCB) | | | | | | | | | | | | | | | | | | | |
+| Options for public identity in use: | | | | | | | | | | | | | | | | | | | |
+| Preferential CUG: None designated | | | | | | | | | | | | | | | | | | | |
+| Outgoing access: not allowed | | | | | | | | | | | | | | | | | | | |
+| Forwarding user has subscribed to CUG | | | | | | | | | | | | | | | | | | | |
+| Options for public identity in use: | | | | | | | | | | | | | | | | | | | |
+| Incoming access: not allowed | | | | | | | | | | | | | | | | | | | |
+| Forwarding user has subscribed to CDIV | | | | | | | | | | | | | | | | | | | |
+| Communication Forwarding on no Reply (CFNR) | | | | | | | | | | | | | | | | | | | |
+| Forwarded-to user has subscribed to CUG | | | | | | | | | | | | | | | | | | | |
+| Options for public identity in use: | | | | | | | | | | | | | | | | | | | |
+| Incoming access: not allowed | | | | | | | | | | | | | | | | | | | |
+| Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | | | | | | |
+| Originating party and forwarded-to party are in the same CUG | | | | | | | | | | | | | | | | | | | |
+| SIP header values: | | | | | | | | | | | | | | | | | | | |
+| INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | |
+| Comments: | | | | | | | | | | | | | | | | | | | |
+| | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) |
| INVITE1 | → | → INVITE2 | |
| | ← 180 Ringing | |
| | | → INVITE3 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | → | → INVITE2 | | | | ← 180 Ringing | | | | | → INVITE3 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | | | | |
+| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | |
+| | | ← 180 Ringing | | | | | | | | | | | | | | | | | |
+| | | | → INVITE3 | | | | | | | | | | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|--|-----------|--|----------------------------|---------|---|--|---|---------|--|--|--|---|-------------|---------------|---|--|--|--|-----|---|--|--|--|
+| CUG/Services/CDIV | CUG_N12_009 | Clause 4.6.7.3 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNR unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNR) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on no Reply (CFNR)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS | | Test equipment (Gm) |
| INVITE1 | → | | → | INVITE2 |
| | | ← | 180 Ringing |
| 403 Forbidden | ← | | | |
| ACK | → | | | |
| | | | Test equipment (Gm) | | AS | | Test equipment (Gm) | INVITE1 | → | | → | INVITE2 | | | | ← | 180 Ringing | 403 Forbidden | ← | | | | ACK | → | | | |
+| Test equipment (Gm) | | AS | | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE1 | → | | → | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------|---|-----------|---|--------------------------------------------|
+| TSS
CUG/Services/CDIV | TP
CUG_N12_010 | CUG reference
Clause 4.6.7.4 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, communication forwarding on not logged-in (CFNL) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNL. | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Not Logged-in (CFNL)
Originating party and forwarding party are in the same CUG | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | |
+| Comments:
Test equipment (Gm) INVITE1 | ➔ | AS | ➔ | Test equipment (ISC, Mw) INVITE2 |
| | | | Test equipment (Gm)
INVITE1 | ➔ | AS | ➔ | Test equipment (ISC, Mw)
INVITE2 |
+| Test equipment (Gm)
INVITE1 | ➔ | AS | ➔ | Test equipment (ISC, Mw)
INVITE2 | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------|---|-----------|
+| CUG/Services/CDIV | CUG_N12_011 | Clause 4.6.7.4 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | |
+| Test purpose | | | | | | | | | |
+| CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNL successful. | | | | | | | | | |
+| Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNL) and the communication to the forwarded-to party is successful. | | | | | | | | | |
+| Preconditions: | | | | | | | | | |
+| Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Not Logged-in (CFNL)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in the same CUG | | | | | | | | | |
+| SIP header values: | | | | | | | | | |
+| INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | |
+| Comments: | | | | | | | | | |
+| | Test equipment (Gm) | AS | Test equipment (Gm) |
| INVITE1 | ➔ | ➔ INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE1 | ➔ | ➔ INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | |
+| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|--|-----------|---------|---|--|--|--|--|---------------|---|--|-----|---|--|
+| TSS
CUG/Services/CDIV | TP
CUG_N12_012 | CUG reference
Clause 4.6.7.4 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNL unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNL) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Not Logged-in (CFNL)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | | AS |
| INVITE1 | ➔ | |
| | |
| 403 Forbidden | ← | |
| ACK | ➔ | |
| | | | Test equipment (Gm) | | AS | INVITE1 | ➔ | | | | | 403 Forbidden | ← | | ACK | ➔ | |
+| Test equipment (Gm) | | AS | | | | | | | | | | | | | | | | |
+| INVITE1 | ➔ | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | | | | |
+| ACK | ➔ | | | | | | | | | | | | | | | | | |
+
+Rec. ITU-T Q.4011.2 (08/2016) 61
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|---------------------------------------|---------------------------------|-----------|---|---------------------------------------|---------------------------------|--|--|--|--|--|-----------|
+| CUG/Services/CDIV | CUG_N12_013 | Clause 4.6.7.5 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarding party, CNRc successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNRc. | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Subscriber Not Reachable (CFNRc)
Originating party and forwarding party are in the same CUG | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | |
+| Comments:
Test equipment (Gm) INVITE1 | ➔ | AS | ➔ | Test equipment (Gm) INVITE2 | Test equipment (ISC, Mw) |
| ➔ INVITE3 |
| | | | Test equipment (Gm)
INVITE1 | ➔ | AS | ➔ | Test equipment (Gm)
INVITE2 | Test equipment (ISC, Mw) | | | | | | ➔ INVITE3 |
+| Test equipment (Gm)
INVITE1 | ➔ | AS | ➔ | Test equipment (Gm)
INVITE2 | Test equipment (ISC, Mw) | | | | | | | | | | |
+| | | | | | ➔ INVITE3 | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------|------------------------------------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|---------|--|--|--|---|---------|
+| TSS
CUG/Services/CDIV | TP
CUG_N12_014 | CUG reference
Clause 4.6.7.5 of [ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8 [ITU-T Q.4011.1 v.1] | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNRc successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNRc) and the communication to the forwarded-to party is successful. | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Subscriber Not Reachable (CFNRc)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in the same CUG | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) |
| INVITE1 | → | INVITE2 | |
| | → | INVITE3 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | → | INVITE2 | | | | → | INVITE3 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | |
+| INVITE1 | → | INVITE2 | | | | | | | | | | | | | |
+| | | → | INVITE3 | | | | | | | | | | | | |
+
+Rec. ITU-T Q.4011.2 (08/2016) 63
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|---------|--|---------------|---|--|--|-----|---|--|--|
+| CUG/Services/CDIV | CUG_N12_015 | Clause 4.6.7.5 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNRc unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNRc) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matching CUG data. | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Forwarding user has subscribed to CDIV
Communication Forwarding on Subscriber Not Reachable (CFNRc)
Forwarded-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and forwarding party are in the same CUG
Originating party and forwarded-to party are in different CUG | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) |
| INVITE1 | → | INVITE2 | |
| 403 Forbidden | ← | | |
| ACK | → | | |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | → | INVITE2 | | 403 Forbidden | ← | | | ACK | → | | |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | | | | |
+| INVITE1 | → | INVITE2 | | | | | | | | | | | | | | | | | |
+| 403 Forbidden | ← | | | | | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|---------|---|-----------|--|--|--|---------------|--|--|--|-------------------------|--|--|--|-------|--|--|--|--|-----------|
+| CUG/Services/CDIV | CUG_N12_016 | Clause 4.6.7.6 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call setup between originating party and deflecting party, communication deflection (CD) successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party and the deflecting party and performs the communication diversion service CD. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Forwarding user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Deflecting user has subscribed to CDIV
Communication Deflection (CD)
Originating party and deflecting party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) |
| INVITE1 | → | → INVITE2 | |
| | ← 180 Ringing | |
| | ← 302 Moved Temporarily | |
| | → ACK | |
| | | → INVITE3 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | INVITE1 | → | → INVITE2 | | | | ← 180 Ringing | | | | ← 302 Moved Temporarily | | | | → ACK | | | | | → INVITE3 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
CUG/Services/CDIV | TP
CUG_N12_017 | CUG reference
Clause 4.6.7.6 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|--------------------------------------------------------------|----------------------------|-----------|----------------------------|----------------------------|---------|---|-----------|--|--|--|---------------|--|--|--|-------------------------|--|--|--|-------|--|--|--|--|-----------|
+| Test purpose
CUG with OA not allowed: Call setup between originating party and forwarded-to party, CD successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the deflecting party and the deflected-to party (CD) and the communication to the deflected-to party is successful. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Deflecting user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Deflected-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and deflecting party are in the same CUG
Originating party and deflected-to party are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) |
| INVITE1 | ➔ | ➔ INVITE2 | |
| | ← 180 Ringing | |
| | ← 302 Moved Temporarily | |
| | ➔ ACK | |
| | | ➔ INVITE3 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | INVITE1 | ➔ | ➔ INVITE2 | | | | ← 180 Ringing | | | | ← 302 Moved Temporarily | | | | ➔ ACK | | | | | ➔ INVITE3 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE1 | ➔ | ➔ INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
CUG/Services/CDIV | TP
CUG_N12_018 | CUG reference
Clause 4.6.7.6 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/8
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-----------|----------------------------|---------|---|-----------|--|--|---------------|--|--|-------------------------|--|--|-------|-------------------|-------|--|-----|---|--|
+| Test purpose
CUG with OA not allowed: Call setup between originating party and deflected-to party, CD unsuccessful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the originating party, the deflecting party and the deflected-to party (CD) and the communication to the deflected-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. | | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Originating user has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Deflecting user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
deflected-to user has subscribed to CUG
Options for public identity in use:
Incoming access: not allowed
Originating party and deflecting party are in the same CUG
Originating party and deflected-to party are in different CUG | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) |
| INVITE1 | → | → INVITE2 |
| | ← 180 Ringing |
| | ← 302 Moved Temporarily |
| | → ACK |
403 Forbidden | ← | |
| ACK | → | |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE1 | → | → INVITE2 | | | ← 180 Ringing | | | ← 302 Moved Temporarily | | | → ACK |
403 Forbidden |
← | | ACK | → | |
+| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE1 | → | → INVITE2 | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | |
+|
403 Forbidden |
← | | | | | | | | | | | | | | | | | | | | | | | |
+| ACK | → | | | | | | | | | | | | | | | | | | | | | | | |
+
+### 7.3.3 Explicit communication transfer (ECT)
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|--------|---|----------|-------------|---|---------------|--------|---|----------|-----|---|-------|
+| CUG/Services/ECT | CUG_N13_001 | Clause 4.6.10 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/9
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Communication transfer - transferor and transferee in the same CUG, successful.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the transferor and the transferee. The communication is successful | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Transferor has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferee has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferor and transferee are in the same CUG | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE:
Request Line
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) |
| INVITE | ➔ | ➔ INVITE |
| 180 Ringing | ⬅ | ⬅ 180 Ringing |
| 200 OK | ⬅ | ⬅ 200 OK |
| ACK | ➔ | ➔ ACK |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | INVITE | ➔ | ➔ INVITE | 180 Ringing | ⬅ | ⬅ 180 Ringing | 200 OK | ⬅ | ⬅ 200 OK | ACK | ➔ | ➔ ACK |
+| Test equipment (Gm) | AS | Test equipment (Gm) | | | | | | | | | | | | | | | | |
+| INVITE | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | |
+| 180 Ringing | ⬅ | ⬅ 180 Ringing | | | | | | | | | | | | | | | | |
+| 200 OK | ⬅ | ⬅ 200 OK | | | | | | | | | | | | | | | | |
+| ACK | ➔ | ➔ ACK | | | | | | | | | | | | | | | | |
+
+| TSS
CUG/Services/ECT | TP
CUG_N13_001 | CUG reference
Clause 4.6.10 of
[ITU-T Q.3627 v.1] | Selection expression
PICS 4.7.1/9
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|----------------------------------------------------------------|---------------------------------------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|------------------------------------------------------------------------|--|--|--|-------|---|--|--|--------------|---|--|--|-----|---|--|--|--------------|---|--|--|--|--|-----------|---------|
+| Test purpose
CUG with OA not allowed: Call communication transfer transferee and transfer target in the same CUG, successful blind transfer.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the transferee and the transfer target and performs the communication transfer service (Blind transfer). | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Transferor has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferee has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferor and transferee are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
Request Line
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) |
| A communication between transferor and transferee already exits |
| REFER | ➔ | | |
| 202 Accepted | ⬅ | | |
| BYE | ➔ | | |
| 200 OK (BYE) | ⬅ | | |
| | INVITE1 ➔ | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | A communication between transferor and transferee already exits | | | | REFER | ➔ | | | 202 Accepted | ⬅ | | | BYE | ➔ | | | 200 OK (BYE) | ⬅ | | | | | INVITE1 ➔ | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| A communication between transferor and transferee already exits | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| REFER | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 202 Accepted | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| BYE | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 200 OK (BYE) | ⬅ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | INVITE1 ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|-------------------------------------------------------------------------|--|--|--|-------|---|--|--|--------------|---|--|--|--|--|-----------|---------|
+| CUG/Services/ECT | CUG_N13_001 | Clause 4.6.10 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/9
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call communication transfer transferee and transfer target in the same CUG, successful assured transfer.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the transferee and the transfer target and performs the communication transfer service (assured transfer). | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Transferor has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferee has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferor and transferee are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
Request Line
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) |
| A communication between transferor and transferee already exists |
| REFER | ➔ | | |
| 202 Accepted | ⬅ | | |
| | INVITE1 ➔ | INVITE2 |
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | A communication between transferor and transferee already exists | | | | REFER | ➔ | | | 202 Accepted | ⬅ | | | | | INVITE1 ➔ | INVITE2 |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | |
+| A communication between transferor and transferee already exists | | | | | | | | | | | | | | | | | | | | | | | |
+| REFER | ➔ | | | | | | | | | | | | | | | | | | | | | | |
+| 202 Accepted | ⬅ | | | | | | | | | | | | | | | | | | | | | | |
+| | | INVITE1 ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | |
+
+| TSS | TP | CUG reference | Selection expression | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|----------------------------------------|--------------------------------------|----------------------------|-----------|----------------------------|---------------------------------|--|------------------------------------------------------------------------|--|--|--|-----------------------------------------------------------------------------|--|--|-------|---|--|--|--------------|---|--|--|
+| CUG/Services/ECT | CUG_N13_001 | Clause 4.6.10 of
[ITU-T Q.3627 v.1] | PICS 4.7.1/9
[ITU-T Q.4011.1 v.1] | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
CUG with OA not allowed: Call Communication transfer transferee and transfer target in the same CUG, successful consultative transfer.
Ensure that on receipt of an INVITE request containing an xml element cug with
cugCallOperation containing
registered CUGIndex,
the SUT checks the CUG restrictions for the transferee and the transfer target and performs the communication transfer service (assured transfer). | | | | | | | | | | | | | | | | | | | | | | | |
+| Preconditions:
Transferor has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferee has subscribed to CUG
Options for registered and preferred CUG index:
Intra CUG restrictions: None designated (-OCB)
Options for public identity in use:
Preferential CUG: None designated
Outgoing access: not allowed
Transferor and transferee are in the same CUG | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE1:
Request Line
FALSE
[registered CUG index]
| | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) |
| A communication between transferor and transferee already exits |
| A communication between transferor and transfer target already exits |
| REFER | ➔ | | |
| 202 Accepted | ⬅ | | |
INVITE1 ➔ INVITE2
| | | | Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | A communication between transferor and transferee already exits | | | | A communication between transferor and transfer target already exits | | | REFER | ➔ | | | 202 Accepted | ⬅ | | |
+| Test equipment (Gm) | AS | Test equipment (Gm) | Test equipment (ISC, Mw) | | | | | | | | | | | | | | | | | | | | |
+| | A communication between transferor and transferee already exits | | | | | | | | | | | | | | | | | | | | | | |
+| | A communication between transferor and transfer target already exits | | | | | | | | | | | | | | | | | | | | | | |
+| REFER | ➔ | | | | | | | | | | | | | | | | | | | | | | |
+| 202 Accepted | ⬅ | | | | | | | | | | | | | | | | | | | | | | |
+
+
+
+
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426
--- /dev/null
+++ b/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d
+size 3828
diff --git a/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0159f17f74c345c265ea824e976fe9eb8fab9e6d
--- /dev/null
+++ b/marked/Q/T-REC-Q.4011.3-201608-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f2d01f3d5c249e393eb2533eb660bacb3b30eccf94d1201834adfe4005e4fec
+size 15510
diff --git a/marked/Q/T-REC-Q.4014.2-201904-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4014.2-201904-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..36e3400d2ee8b59eb3a05f9dbbf771b4f5fc587f
--- /dev/null
+++ b/marked/Q/T-REC-Q.4014.2-201904-I_PDF-E/raw.md
@@ -0,0 +1,14879 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4014.2**
+
+(04/2019)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**PSTN/ISDN terminal equipment using IP
+multimedia core network subsystem;
+Conformance testing – Part 2: Test suite
+structure and test purposes**
+
+Recommendation ITU-T Q.4014.2
+
+ITU-T
+
+
+
+The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters 'ITU' are prominently displayed in blue and white within the globe.
+
+ITU logo
+
+International
+Telecommunication
+Union
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+# SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+| Testing specifications for IMT-2020 and IoT | Q.4060–Q.4099 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.4014.2
+
+# PSTN/ISDN terminal equipment using IP multimedia core network subsystem; Conformance testing – Part 2: Test suite structure and test purposes
+
+## Summary
+
+Recommendation ITU-T Q.4014.2 is part 2 of the testing specifications of the terminal equipment used in the IMS-based public switched telephone network/integrated services digital network (PSTN/ISDN) emulation subsystem based on the media gateway control protocol, the session initiation protocol and the associated session description protocol.
+
+The Recommendation specifies the test suite structure and test purposes (TSS and TP) to test PSTN/ISDN terminal equipment using Internet protocol (IP) multimedia core network subsystem.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4014.2 | 2019-04-29 | 11 | 11.1002/1000/13886 |
+
+## Keywords
+
+IAD, IMS, PES, SDP, SIP, testing, TP, TSS, user side
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2019
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 3 |
+| 3.1 Terms defined elsewhere ..... | 3 |
+| 4 Abbreviations and acronyms ..... | 3 |
+| 5 Conventions ..... | 5 |
+| 6 Test suite structure..... | 5 |
+| 7 Test purposes ..... | 6 |
+| 7.1 Introduction ..... | 6 |
+| 7.2 Procedures at the user equipment..... | 6 |
+
+
+
+## Recommendation ITU-T Q.4014.2
+
+# PSTN/ISDN terminal equipment using IP Multimedia core network subsystem; Conformance testing – Part 2: Test suite structure and test purposes
+
+# 1 Scope
+
+This Recommendation specifies the test suite structure and test purposes to test PSTN/ISDN terminal equipment using IP multimedia core network subsystem.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3*.
+- [ITU-T Q.4014.1] Recommendation ITU-T Q.4014.1 (2019), *PSTN/ISDN terminal equipment using IP Multimedia core network subsystem; Conformance testing – Part 1: PICS*.
+- [ISO/IEC 9646-1] Recommendation ISO/IEC 9646-1, *Information technology – Open systems interconnection – Conformance testing methodology and framework – Part 1: General concepts*.
+- [ETSI TS 124 147] Recommendation ETSI TS 124 147 (2015-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3*.
+- [ETSI TS 124 229] Recommendation ETSI TS 124 229 (2019), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 Release 10)*.
+- [ETSI TS 124 605] Recommendation ETSI TS 124 605 (2013-01), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 version 10.1.0 Release 10)*.
+- [ETSI TS 124 608] Recommendation ETSI TS 124 608 (2013-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 version 10.1.0 Release 10)*.
+
+- [ETSI TS 124 628] Recommendation ETSI TS 124 628 (2013), *Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.628 version 10.4.0 Release 10).*
+- [ETSI TS 129 163] Recommendation ETSI TS 129 163 (2019), *Digital cellular telecommunications system (Phase 2+) (GSM);Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks.*
+- [ETSI TS 183 036] Recommendation ETSI TS 183 036 (2012), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification.*
+- [ETSI TS 183 043] Recommendation ETSI TS 183 043 (2011), *Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification.*
+- [IETF RFC 768] Recommendation IETF RFC 768 (1980), *User Datagram Protocol.*
+- [IETF RFC 793] Recommendation IETF RFC 793 (1981), *Transmission Control Protocol.*
+- [IETF RFC 2327] Recommendation IETF RFC 2327 (1998), *SDP: Session Description Protocol.*
+- [IETF RFC 2805] Recommendation IETF RFC 2805 (2000), *Media Gateway Control Protocol Architecture and Requirements.*
+- [IETF RFC 3261] Recommendation IETF RFC 3261 (2002), *SIP: Session Initiation Protocol.*
+- [IETF RFC 3262] Recommendation IETF RFC 3262 (2002), *Integration of Resource Management and Session Initiation Protocol (SIP).*
+- [IETF RFC 3312] Recommendation IETF RFC 3312 (2002), *Reliability of Provisional Responses in the Session Initiation Protocol (SIP).*
+- [IETF RFC 3323] Recommendation IETF RFC 3323 (2002), *A Privacy Mechanism for the Session Initiation Protocol (SIP).*
+- [IETF RFC 3325] Recommendation IETF RFC 3325 (2002), *Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks.*
+- [IETF RFC 5009] Recommendation IETF RFC 5009 (2007), *Private Header (P-Header) Extension to Session Initiation Protocol (SIP) for Authorization of Early Media.*
+- [IETF RFC 6080] Recommendation IETF RFC 3312 (2011), *A Framework for Session Initiation Protocol User Agent Profile Delivery.*
+- [IETF RFC 6140] Recommendation IETF RFC 6140 (2011), *Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP).*
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 access gateway** [ETSI TS 183 043]: Gateway device that interworks a significant number of analogue lines/ISDN accesses (directly or via an V5 Access Network) to a packet network and is located at the operator's premises.
+
+**3.1.2 loose coupling** [ETSI TS 183 043]: On-hook and flash-hook are analyzed in the AGCF/VGW; much like a simulation endpoint would operate.
+
+**3.1.3 media gateway (MGW)** [ETSI TS 183 043]: Gateway device acting at the media/transport plane, providing the functions of an MGF.
+
+**3.1.4 media gateway controller (MGC)** [ITU-T H.248.1]: Controls the parts of the call state that pertain to connection control for media channels in an MG.
+
+**3.1.5 residential gateway** [ETSI TS 183 043]: Gateway device that interworks a small number of analogue lines/ISDN accesses.
+
+**3.1.6 tight coupling** [ETSI TS 183 043]: On-hook and flash-hook are interpreted by the AS.
+
+**3.1.7 voice over IP gateway (VGW)** [ETSI TS 183 043]: SIP-based gateway device that implements both a media gateway function and a media gateway controller function as defined in IETF RFC 2805 and supports the provision of voice based services to analogue lines/ISDN accesses.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-------|--------------------------------------------|
+| 3PTY | Three-Party Service |
+| ACR | Anonymous Communication Rejection |
+| AGCF | Access Gateway Control Function |
+| AGW | Access Gateway |
+| AOC-D | Advice of Charge During the call |
+| AOC-E | Advice of Charge at the End of the call |
+| AOC-S | Advice of Charge at call Set-up time |
+| AS | Application Server |
+| BC | Bearer Capability information element |
+| BRI | Basic Rate Interface |
+| CCBS | Call Completion on Busy Subscriber |
+| CCNR | Call Completion on No Reply |
+| CD | Call Deflection |
+| CFB | Call Forwarding on Busy |
+| CFU | Call Forwarding Unconditional |
+| CLIP | Calling Line Identification Presentation |
+| COLP | Connected Line identification Presentation |
+| CSCF | Call Session Control Function |
+
+| | |
+|--------|-----------------------------------------------|
+| CUG | Closed User Group |
+| CW | Communication Waiting |
+| FQDN | Fully Qualified Domain Name |
+| HLC | High Layer Compatibility |
+| HOLD | call HOLD |
+| IAD | Integrated Access Device |
+| IMS | IP Multimedia Subsystem |
+| IP | Internet Protocol |
+| ISDN | Integrated Services Digital Network |
+| IUT | Implementation Under Test |
+| MCID | Malicious Communication Identification |
+| MGC | Media Gateway Controller |
+| MGF | Media Gateway Function |
+| MIME | Multimodal Internet Mail Extensions |
+| MWI | Message Waiting Indication |
+| OIP | Originating Identification Presentation |
+| OIR | Originating Identification |
+| PICS | Protocol Implementation Conformance Statement |
+| POTS | Plain Old Telephone Service |
+| PSTN | Public Switched Telephone Network |
+| S-CSCF | Serving CSCF |
+| SDP | Session Description Protocol |
+| SIP | Session Initiation Protocol |
+| SOC | Switching Order Command |
+| SUT | System Under Test |
+| TIP | Terminating Identification Presentation |
+| TIR | Terminating Identification Restriction |
+| TP | Test Purposes |
+| TSS | Test Suite Structure |
+| UA | User Agent |
+| UE | User Equipment |
+| URI | Uniform Resource Identifier |
+| URN | User Requirements Notation |
+| VGW | Voice over IP Gate Way |
+| XML | Extensible Markup Language |
+
+# 5 Conventions
+
+- is "protocol";
+- is "ETSI TS 183 043";
+- is "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification";
+- is "IMS-based PSTN/ISDN Emulation; Stage 3 specification".
+
+# 6 Test suite structure
+
+**Table 6-1 – Test suite structure**
+
+| | | |
+|-------------------------------------|------------------------------------------------|------------|
+| Registration | Initial_registration | TP_101_xxx |
+| | User-initiated_re-registration | TP_102_xxx |
+| | User-initiated_deregistration | TP_103_xxx |
+| | Network-initiated_deregistration | TP_104_xxx |
+| | Subscription_and_notification | TP_105_xxx |
+| Call initiation_UE-originating_case | Orig_Establishment_of_an_early_dialogue | TP_201_xxx |
+| | Orig_Establishment_of_a_confirmed_dialogue | TP_202_xxx |
+| | Orig_Release_initiated_by_the_terminating_user | TP_203_xxx |
+| | Orig_Release_initiated_by_the_terminating_user | TP_204_xxx |
+| | Orig_Timers | TP_205_xxx |
+| | Orig_Abnormal_situations | TP_206_xxx |
+| Call initiation_UE_terminating_case | Term_Establishment_of_an_early_dialogue | TP_301_xxx |
+| | Term_Establishment_of_a_confirmed_dialogue | TP_302_xxx |
+| | Term_Release_initiated_by_the_originating_user | TP_303_xxx |
+| | Term_Release_initiated_by_the_terminating_user | TP_304_xxx |
+| | Term_Timers | TP_305_xxx |
+| | Term_Abnormal_situations | TP_306_xxx |
+| Emergency_service | | TP_401_xxx |
+| Supplementary_Service_control | OIP_OIR | TP_501_xxx |
+| | TIP_TIR | TP_502_xxx |
+| | HOLD | TP_503_xxx |
+| | CDIV | TP_504_xxx |
+| | 3PTY | TP_505_xxx |
+| | CUG | TP_506_xxx |
+| | CW | TP_507_xxx |
+| | TP | TP_508_xxx |
+| | ECT | TP_509_xxx |
+| | UUS | TP_510_xxx |
+| | SUB | TP_511_xxx |
+| | MCID | TP_512_xxx |
+| | MWI | TP_513_xxx |
+| | CCBS_CCNR | TP_514_xxx |
+
+# 7 Test purposes
+
+## 7.1 Introduction
+
+For each test requirement, a test purpose (TP) is defined.
+
+All protocol implementation conformance statement (PICS) items referred to in this clause are as specified in [ITU-T Q.4014.1] unless indicated otherwise by another numbered reference.
+
+### 7.1.1 TP naming convention
+
+TPs are numbered, starting at 001, within each group. Groups are organized according to the test suite structure (TSS). Additional references are added to identify the actual test suite and whether or not it applies to the network (see Table 7.1.1).
+
+**Table 7.1.1 – TP identifier naming convention scheme**
+
+| |
+|-------------------------------------------------------------------------------|
+| - Identifier: TP__ |
+| - = group 3 digit field representing group reference according to TSS |
+| - = sequential number (001-999) |
+
+### 7.1.2 Test strategy
+
+As the base standards [ETSI TS 124 229] and [ETSI TS 183 036] contain no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification [ITU-T Q.4014.1]. The criteria applied include the following:
+
+- Whether or not a test case can be built from the TP is not considered.
+
+## 7.2 Procedures at the user equipment
+
+### 7.2.1 Registration and authentication
+
+#### 7.2.1.1 Initial registration
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|-------------------|--|-----------------------|---------------------------|--|--|--|---|------------|--|---|------------------|--|---|------------|--|---|-------------------|-------------------------|--|--|
+| TSS
Initial_registration | TP_101_001 | Reference
clause 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
REGISTER request have to be authorized receipt of 401
Ensure that the SUT sends a REGISTER request, receives a 401 Unauthorized and the WWW- Authenticate header is present. The SUT repeats the REGISTER request. The Authorization header is present including 'username', 'realm', 'nonce', 'digest-uri' and 'response' HTTP parameters. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
401
WWW-Authenticate:
REGISTER 2
Authorization: username[proper value];realm=[proper value];nonce=[proper value];digest-uri=[proper value] | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Make end device available | | |
| ➔ | REGISTER 1 |
| ⬅ | 401 Unauthorized |
| ➔ | REGISTER 2 |
| ⬅ | 200 OK (REGISTER) |
| Apply post test routine | | |
| | | | End device | | Test equipment | Make end device available | | | | ➔ | REGISTER 1 | | ⬅ | 401 Unauthorized | | ➔ | REGISTER 2 | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|-------------------|--|-----------------------|----------------------------------|--|--|--|---|------------|--|---|-----------------------------------|--|---|------------|--|---|-------------------|--------------------------------|--|--|
+| TSS
Initial_registration | TP_101_002 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
REGISTER request have to be authorized, receipt of 407 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the SUT sends a REGISTER request, receives a 407 Proxy Authentication Required and the Proxy-Authenticate header is present. The SUT repeats the REGISTER request. The Proxy-Authorization header is present including 'username', 'realm', 'nonce', 'digest-uri' and 'response' HTTP parameters. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
407
Proxy-Authenticate:
REGISTER 2
Proxy-Authorization: username=[proper value];realm=[proper value];nonce=[proper value];digest-uri=[proper value] | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Make end device available | | |
| ➔ | REGISTER 1 |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | REGISTER 2 |
| ⬅ | 200 OK (REGISTER) |
| Apply post test routine | | |
| | | | End device | | Test equipment | Make end device available | | | | ➔ | REGISTER 1 | | ⬅ | 407 Proxy Authentication Required | | ➔ | REGISTER 2 | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|-------------------|--|-----------------------|----------------------------------|--|--|--|---|------------|--|---|-----------------------------------|--|---|------------|--|---|-------------------|--------------------------------|--|--|
+| TSS
Initial_registration | TP_101_003 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
REGISTER request have to be authorized, receipt of 407 the Cseq is incremented | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the SUT sends a REGISTER request, receives a 407 Proxy Authentication Required and the Proxy-Authenticate header is present. The SUT repeats the REGISTER request. The Proxy-Authorization header is present and the Cseq header value is incremented. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
REGISTER 1
Call-ID [any value]
Cseq x REGISTER
REGISTER 2
Call-ID [same value as in REGISTER 1]
Cseq x+1 REGISTER | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Make end device available | | |
| ➔ | REGISTER 1 |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | REGISTER 2 |
| ⬅ | 200 OK (REGISTER) |
| Apply post test routine | | |
| | | | End device | | Test equipment | Make end device available | | | | ➔ | REGISTER 1 | | ⬅ | 407 Proxy Authentication Required | | ➔ | REGISTER 2 | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------------------------------|----------------------|-------------------|--|-----------------------|----------------------------------|--|--|--|--------------|--|--|--------------------|--|--|--------------|--|--|---------------------|--|--------------------------------|--|--|
+| TSS
Initial_registration | TP_101_004 | Reference
section 10.2 and 22 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Request line in the REGISTER request
Ensure that the SUT sends a REGISTER request to its registrar and there is no 'userpart' in the SIP-URI of the Request-line. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
REGISTER
Request-line: sip:[hostpart=domain of location service] | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Make end device available | | |
| ➔ REGISTER 1 | |
| ⬅ 401 Unauthorized | |
| ➔ REGISTER 2 | |
| ⬅ 200 OK (REGISTER) | |
| Apply post test routine |
| | | | End device | | Test equipment | Make end device available | | | | ➔ REGISTER 1 | | | ⬅ 401 Unauthorized | | | ➔ REGISTER 2 | | | ⬅ 200 OK (REGISTER) | | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------------------------------|----------------------|-------------------|--|-----------------------|----------------------------------|--|--|--|--------------|--|--|--------------------|--|--|--------------|--|--|---------------------|--|--------------------------------|--|--|
+| TSS
Initial_registration | TP_101_005 | Reference
section 10.3 and 22 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Successful final response to the REGISTER request
Ensure that the SUT receives a 200 OK Final response to the REGISTER request sent to its registrar and the Contact header and an 'expires' parameter in the Contact header. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (REGISTER)
Contact: sip:[any registered URI];expires=[any value] | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Make end device available | | |
| ➔ REGISTER 1 | |
| ⬅ 401 Unauthorized | |
| ➔ REGISTER 2 | |
| ⬅ 200 OK (REGISTER) | |
| Apply post test routine |
| | | | End device | | Test equipment | Make end device available | | | | ➔ REGISTER 1 | | | ⬅ 401 Unauthorized | | | ➔ REGISTER 2 | | | ⬅ 200 OK (REGISTER) | | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| Make end device available | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ REGISTER 1 | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ REGISTER 2 | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|------------------------------------|
+| TSS
Initial_registration | TP_101_006 | Reference
section 10.2.6 of
[IETF RFC 3261] | Selection expression
PICS 5.2/1 |
+| Test purpose
Successful registration using a preconfigured registrar address
Ensure that the SUT sends a REGISTER request addressed to a pre-configured registrar without a 'userpart' in the Request URI. | | | |
+
+| | |
+|-------------------------------------------------------------------------------------------------------------|-----------------------|
+| SIP header values
REGISTER
Request-line: sip:[hostpart=preconfigured registrar address] | |
+| Message flow | |
+| End device
Make end device available | Test equipment |
+| → REGISTER 1
← 401 Unauthorized
→ REGISTER 2
← 200 OK (REGISTER)
Apply post test routine | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|------------------------------------|
+| TSS
Initial_registration | TP_101_007 | Reference
section 10.2.6 of
[IETF RFC 3261] | Selection expression
PICS 5.2/2 |
+| Test purpose
Successful registration using the 'multicast' mechanism | | | |
+| Ensure that the SUT sends a REGISTER request to the "all SIP servers" multicast address "sip:mcast.net" without a 'userpart'. | | | |
+| SIP header values
REGISTER
Request-line: sip:
OR
Request-line: sip: <224.0.1.75> | | | |
+| Message flow | | | |
+| End device
Make end device available. | Test equipment | | |
+| → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER)
Apply post test routine | | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_008 | Reference
section 10.2 of [IETF RFC 3261] | Selection expression |
+| Test purpose
Successful registration To header | | | |
+| Ensure that the SUT sends a REGISTER request to the registrar and the To header with the address of the registrant and the type of the To header is 'sip' | | | |
+| SIP header values
REGISTER
To: sip:[address of registrant] | | | |
+
+| | |
+|-----------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| Make end device available. | |
+| ➔ | REGISTER |
+| ⬅ | 401 Unauthorized |
+| ➔ | REGISTER |
+| ⬅ | 200 OK (REGISTER) |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|-------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_009 | Reference
section 10.2 of
[IETF RFC 3261] | Selection expression |
+|-----------------------------|------------|-------------------------------------------------|----------------------|
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Successful registration From header |
+| Ensure that the SUT sends a REGISTER request to the registrar and the 'From' header is set to the same value as the To header. |
+
+| |
+|----------------------------------------------------------------------|
+| SIP header values
REGISTER |
+| To: sip:[address of registrant]
From: sip:[address of registrant] |
+
+| | |
+|-----------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| Make end device available. | |
+| ➔ | REGISTER |
+| ⬅ | 401 Unauthorized |
+| ➔ | REGISTER |
+| ⬅ | 200 OK (REGISTER) |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|----------------------------------------------------------|------------------------------------|
+| TSS
Initial_registration | TP_101_010 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/1 |
+|-----------------------------|------------|----------------------------------------------------------|------------------------------------|
+
+| |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Successful registration Via header for UDP |
+| Ensure that the SUT sends a REGISTER request to the registrar and the 'Via' header contains a sent-by field containing the IP address or fully qualified domain name (FQDN) of the UE and the port number where the UE expects to receive the response to this request when UDP is used. |
+
+| |
+|--------------------------------------------------------------------------------------------------------|
+| SIP header values
REGISTER |
+| Via: SIP/2.0/UDP [IP Address]:[Port number];branch=z9hG4bK[branch]; sent-by=[IP Address]:[Port number] |
+
+| | |
+|-----------------------------------------------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| Make end device available. | |
+| → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER) | |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|----------------------------------------------------------|------------------------------------|
+| TSS
Initial_registration | TP_101_011 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/2 |
+|-----------------------------|------------|----------------------------------------------------------|------------------------------------|
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Successful registration Via header for TCP |
+| Ensure that the SUT sends a REGISTER request to the registrar and the 'Via' header contains a "rport" header field parameter with no value in the Via header field when TCP is used. |
+
+| |
+|-------------------------------------------------------------------------------------------------------------------------|
+| SIP header values
REGISTER
Via: SIP/2.0/UDP [IP Address]:[Port number];branch=z9hG4bK[branch];rport |
+|-------------------------------------------------------------------------------------------------------------------------|
+
+| | |
+|-----------------------------------------------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| Make end device available. | |
+| → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER) | |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|----------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_012 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression |
+|-----------------------------|------------|----------------------------------------------------------|----------------------|
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Successful registration option-tag 'path' in the Supported header |
+| Ensure that the SUT sends a REGISTER request to the registrar and the 'Supported' header contains the option-tag "path". |
+
+| |
+|----------------------------------------------------------------|
+| SIP header values
REGISTER
Supported: path |
+|----------------------------------------------------------------|
+
+| | |
+|-----------------------------------------------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| Make end device available. | |
+| → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER) | |
+| Apply post test routine | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------|-------------------|--|-----------------------|----------------------------|--|--|--|---|----------|--|---|------------------|--|---|----------|--|---|-------------------|--------------------------------|--|--|
+| TSS
Initial_registration | TP_101_013 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/3 | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Successful registration option-tag 'gruu' in the Supported header
Ensure that the SUT sends a REGISTER request to the registrar and the 'Supported' header contains the option-tag "gruu" if the SUT supports GRUU. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
REGISTER
Supported: gruu | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Make end device available. | | |
| ➔ | REGISTER |
| ⬅ | 401 Unauthorized |
| ➔ | REGISTER |
| ⬅ | 200 OK (REGISTER) |
| Apply post test routine |
| | | | End device | | Test equipment | Make end device available. | | | | ➔ | REGISTER | | ⬅ | 401 Unauthorized | | ➔ | REGISTER | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| Make end device available. | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|--------------------------------------------|-------------------|--|-----------------------|----------------------------|--|--|--|---|----------|--|---|------------------|--|---|----------|--|---|-------------------|--------------------------------|--|--|
+| TSS
Initial_registration | TP_101_014 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/4 and 5.2 | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Successful registration option-tag 'gin' in the Require header
Ensure that the SUT sends a REGISTER request to the registrar and the 'Require' header contains the option-tag "gin" if the SUT performs the functions of an external attached network. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
REGISTER
Require: gin | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Make end device available. | | |
| ➔ | REGISTER |
| ⬅ | 401 Unauthorized |
| ➔ | REGISTER |
| ⬅ | 200 OK (REGISTER) |
| Apply post test routine |
| | | | End device | | Test equipment | Make end device available. | | | | ➔ | REGISTER | | ⬅ | 401 Unauthorized | | ➔ | REGISTER | | ⬅ | 200 OK (REGISTER) | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| Make end device available. | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|--------------------------------------------|
+| TSS
Initial_registration | TP_101_015 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.2/4 and 5.2 |
+| Test purpose
Successful registration option-tag 'gin' in the Proxy-Require header
Ensure that the SUT sends a REGISTER request to the registrar and the 'Proxy-Require' header contains the option-tag "gin" if the SUT performs the functions of an external attached network. | | | |
+
+| | |
+|-------------------------------------------------------------------|-----------------------------------------------------------------------|
+| SIP header values
REGISTER
Proxy-Require: gin | |
+| Message flow | |
+| End device | Test equipment |
+| Make end device available. | |
+| | → REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK (REGISTER) |
+| Apply post test routine | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|-------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_016 | Reference
section 10.2 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
Successful registration. No new registration before successful final response | | | |
+| Ensure that the SUT does not send a new REGISTER request before it has received a successful final response to its previous REGISTER request or before expiration of the re-attempt timeout. | | | |
+| SIP header values
REGISTER | | | |
+| Message flow | | | |
+| End device | Test equipment | | |
+| Make end device available. | | | |
+| | → REGISTER
← 401 Unauthorized
→ REGISTER | | |
+| | Timeout initial request
→ REGISTER
← 200 OK (REGISTER) | | |
+| Apply post test routine | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_017 | Reference
section 10.2 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
Successful registration increments the Cseq in a new request | | | |
+| Ensure that the SUT sends a new REGISTER request and increments the Cseq header and uses the same Call-ID value as in the initial REGISTER request. | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------|-----------------------|---------------------------|--|--|--|---|------------|--|---|------------------|--|---|------------|--|---|-------------------|-------------------------|--|--|
+| SIP header values
REGISTER 1
Call-ID [any value]
Cseq x REGISTER
REGISTER 2
Call-ID [same value as in REGISTER 1]
Cseq x+1 REGISTER | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SUT is already registered |
| → | REGISTER 1 |
| ← | 401 Unauthorized |
| → | REGISTER 2 |
| ← | 200 OK (REGISTER) |
| Apply post test routine |
| End device | | Test equipment | SUT is already registered | | | | → | REGISTER 1 | | ← | 401 Unauthorized | | → | REGISTER 2 | | ← | 200 OK (REGISTER) | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SUT is already registered | | | | | | | | | | | | | | | | | | | | | |
+| | → | REGISTER 1 | | | | | | | | | | | | | | | | | | | |
+| | ← | 401 Unauthorized | | | | | | | | | | | | | | | | | | | |
+| | → | REGISTER 2 | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-----------------------------|------------|------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_018 | Reference
section 10.2.4 of [IETF RFC 3261] | Selection expression |
+|-----------------------------|------------|------------------------------------------------|----------------------|
+
+| |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Successful registration. Refreshing of registration
Ensure that the SUT refreshes each Binding given in the expires parameter of the Contact header received in the previous 200 OK REGISTER final response. The Call-ID is the same as in the previous REGISTER request and the Cseq header value is incremented. |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------|-----------------------|---------------------------|--|--|--|---|----------|--|---|------------------|--|---|------------|--|---|-------------------|-------------------------|--|--|
+| SIP header values
REGISTER 1
Call-ID [any value]
Cseq x REGISTER
REGISTER 2
Call-ID [same value as in REGISTER 1]
Cseq x+1 REGISTER | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SUT is already registered |
| → | REGISTER |
| ← | 401 Unauthorized |
| → | REGISTER 2 |
| ← | 200 OK (REGISTER) |
| Apply post test routine |
| End device | | Test equipment | SUT is already registered | | | | → | REGISTER | | ← | 401 Unauthorized | | → | REGISTER 2 | | ← | 200 OK (REGISTER) | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SUT is already registered | | | | | | | | | | | | | | | | | | | | | |
+| | → | REGISTER | | | | | | | | | | | | | | | | | | | |
+| | ← | 401 Unauthorized | | | | | | | | | | | | | | | | | | | |
+| | → | REGISTER 2 | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|------------------------------------|-------------------|-----------------------|---------------------------|--|---|----------|---|------------------|---|----------|---|-------------------|-------------------------|--|
+| TSS
Initial_registration | TP_101_019 | Reference
section 10.2.2 of [IETF
RFC 3261] | Selection expression
PICS 5.2/6 | | | | | | | | | | | | | | |
+| Test purpose
Successful registration removing a Binding
Ensure that the SUT is able to deregister a particular Binding by sending a REGISTER request and the expires parameter for that Binding is set to '0' or the Expires header is set to '0'. | | | | | | | | | | | | | | | | | |
+| SIP header values
REGISTER
Contact: sip:[any registered URI];expires=0
OR
Contact: *
Expires: 0 | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| SUT is already registered |
| ➔ | REGISTER |
| ⬅ | 401 Unauthorized |
| ➔ | REGISTER |
| ⬅ | 200 OK (REGISTER) |
| Apply post test routine |
| | | | End device | Test equipment | SUT is already registered | | ➔ | REGISTER | ⬅ | 401 Unauthorized | ➔ | REGISTER | ⬅ | 200 OK (REGISTER) | Apply post test routine | |
+| End device | Test equipment | | | | | | | | | | | | | | | | |
+| SUT is already registered | | | | | | | | | | | | | | | | | |
+| ➔ | REGISTER | | | | | | | | | | | | | | | | |
+| ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | |
+| ➔ | REGISTER | | | | | | | | | | | | | | | | |
+| ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------|------------------------------------|-------------------|-----------------------|---------------------------|--|---|----------|---|-------------------|-------------------------|--|
+| TSS
Initial_registration | TP_101_020 | Reference
section 10.2.1 of [IETF
RFC 3261] | Selection expression
PICS 5.2/7 | | | | | | | | | | |
+| Test purpose
The SUT gets its registered contacts
Ensure that the SUT, in order to get its registered contacts, sends a REGISTER request to its registrar without Contact header. | | | | | | | | | | | | | |
+| SIP header values
REGISTER
[without Contact header] | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| Make end device available |
| ➔ | REGISTER |
| ⬅ | 200 OK (REGISTER) |
| Apply post test routine |
| | | | End device | Test equipment | Make end device available | | ➔ | REGISTER | ⬅ | 200 OK (REGISTER) | Apply post test routine | |
+| End device | Test equipment | | | | | | | | | | | | |
+| Make end device available | | | | | | | | | | | | | |
+| ➔ | REGISTER | | | | | | | | | | | | |
+| ⬅ | 200 OK (REGISTER) | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------|------------------------------------|
+| TSS
Initial_registration | TP_101_021 | Reference
Annex A and section 17.1.2.2 of [IETF RFC 3261] | Selection expression
PICS 5.2/1 |
+| Test purpose
REGISTER request is repeated if no response is received
Ensure that the SUT or the IUT, having sent a REGISTER request, repeats its request after timer E set to T1 value expires, if an unreliable transport is used. | | | |
+| SIP header values | | | |
+| Message flow
sequenceDiagram participant End device participant Test equipment Note over End device: Start timer E End device->>Test equipment: REGISTER Note over End device: Timeout timer E End device->>Test equipment: REGISTER
Apply post test routine
| | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------|
+| TSS
Initial_registration | TP_101_022 | Reference
Annex A and section 17.1.3 of [IETF RFC 3261] | Selection expression
PICS 5.2/1 |
+| Test purpose
REGISTER request is repeated if no response is received
Ensure that the SUT, having sent a REGISTER request twice, repeats its request after timer E set to the $MIN(2*T1,T2)$ value expires, if an unreliable transport is used. | | | |
+| SIP header values | | | |
+| Message flow
sequenceDiagram participant End device participant Test equipment Note over End device: Start timer E=T1 End device->>Test equipment: REGISTER Note over End device: Timeout timer E End device->>Test equipment: REGISTER Note over End device: Start timer E=2*T1 Note over End device: Timeout timer E End device->>Test equipment: REGISTER
Apply post test routine
| | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------|
+| TSS
Initial_registration | TP_101_023 | Reference
Annex A and section 17.1.3 of [IETF RFC 3261] | Selection expression
PICS 5.2/1 |
+| Test purpose
REGISTER request is repeated if no response is received
Ensure that the SUT, having sent a REGISTER request three times, repeats its request after timer E set to the $MIN(4*T1,T2)$ value expires, If an unreliable transport is used. | | | |
+| SIP header values | | | |
+
+| | |
+|--------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| | → REGISTER |
+| Start timer E= $T1$ | |
+| Timeout timer E | |
+| | → REGISTER |
+| Start timer E= $2*T1$ | |
+| Timeout timer E | |
+| | → REGISTER |
+| Start timer E= $4*T1$ | |
+| Timeout timer E | |
+| | → REGISTER |
+| Apply post test routine | |
+
+| | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------------------|-----------------------------------------------|-------------------|-----------------------|--|------------|------------------------|--|--|------------|--|------------|--|------------|-----------------|--|--------------------------------|--|
+| TSS
Initial_registration | TP_101_024 | Reference
Annex A and
section 17.1.3 of
[IETF RFC 3261] | Selection expression
PICS 5.2/2 and 5.2/12 | | | | | | | | | | | | | | | | |
+| Test purpose
The REGISTER is not repeated after timer F expires
Ensure that the SUT does not repeat a REGISTER request, after timer F set to expires, If an unreliable transport is used.
| | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| → REGISTER |
| Start timer F= | |
| → REGISTER |
| → REGISTER |
| → REGISTER |
| Timeout timer F | |
| Apply post test routine |
| | | | End device | Test equipment | | → REGISTER | Start timer F= $64*T1$ | | | → REGISTER | | → REGISTER | | → REGISTER | Timeout timer F | | Apply post test routine | |
+| End device | Test equipment | | | | | | | | | | | | | | | | | | |
+| | → REGISTER | | | | | | | | | | | | | | | | | | |
+| Start timer F= $64*T1$ | | | | | | | | | | | | | | | | | | | |
+| | → REGISTER | | | | | | | | | | | | | | | | | | |
+| | → REGISTER | | | | | | | | | | | | | | | | | | |
+| | → REGISTER | | | | | | | | | | | | | | | | | | |
+| Timeout timer F | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_025 | Reference
Annex A and
section 17.1.3 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
REGISTER request in the Proceeding state is repeated if no response is received
Ensure that the SUT, when a REGISTER client transaction is in the Proceeding state, repeats its REGISTER request after timer E set to value expires.
| | | |
+| SIP header values | | | |
+
+
+
+| | |
+|--------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| | → REGISTER |
+| | ← 100 Trying |
+| Start timer E=T1 | |
+| Timeout timer E | |
+| | → REGISTER |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|------------------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_026 | Reference
Annex A and
section 17.1.3 of [IETF
RFC 3261] | Selection expression |
+|-----------------------------|------------|------------------------------------------------------------------|----------------------|
+
+**Test purpose**
+*REGISTER request in the Proceeding state is repeated if no response is received*
+
+Ensure that the SUT, when a REGISTER client transaction is in the Proceeding state, repeats its REGISTER request after timer E set to T1 value expires.
+
+**SIP header values**
+
+
+
+| | |
+|--------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| | → REGISTER |
+| | ← 100 Trying |
+| Start timer E=T1 | |
+| Timeout timer E | |
+| | → REGISTER |
+| | ← 100 Trying |
+| Start timer E=T2 | |
+| Timeout timer E | |
+| | → REGISTER |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|------------------------------------------------------------------|-------------------------------------|
+| TSS
Initial_registration | TP_101_027 | Reference
Annex A and
section 17.1.3 of
[IETF RFC 3261] | Selection expression
PICS 5.2/12 |
+|-----------------------------|------------|------------------------------------------------------------------|-------------------------------------|
+
+**Test purpose**
+*REGISTER request in the Proceeding state is not repeated if no response is received*
+
+Ensure that the SUT, when a REGISTER client transaction is in the Proceeding state and REGISTER request have already been repeated in this state, repeats its REGISTER request after timer E set to T2 value expires.
+
+**SIP header values**
+
+
+
+| | |
+|--------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| | → REGISTER |
+| | ← 100 Trying |
+| Start timer F=64*T1 | |
+| | → REGISTER |
+| | ← 100 Trying |
+| | |
+| | → REGISTER |
+| | ← 100 Trying |
+| Timeout timer F | |
+| Apply post test routine | |
+
+| | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------|----------------------|-------------------|-----------------------|--|------------|--|-----------------|--|------------|--------------------------------|--|
+| TSS
Initial_registration | TP_101_028 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression | | | | | | | | | | |
+| Test purpose
Receipt of a 305 (Use Proxy) response to the unprotected REGISTER request | | | | | | | | | | | | | |
+| Ensure that the SUT, on receipt of a 305 (Use Proxy) response to the unprotected REGISTER request, select a P-CSCF address from the address list, which is different from the previously used address, and perform the procedures for initial registration. | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| → REGISTER |
| ← 305 Use Proxy |
| → REGISTER |
| Apply post test routine |
| | | | End device | Test equipment | | → REGISTER | | ← 305 Use Proxy | | → REGISTER | Apply post test routine | |
+| End device | Test equipment | | | | | | | | | | | | |
+| | → REGISTER | | | | | | | | | | | | |
+| | ← 305 Use Proxy | | | | | | | | | | | | |
+| | → REGISTER | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_029 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression |
+| Test purpose
Receipt of a 423 (Interval Too Brief) response to the unprotected REGISTER request | | | |
+| Ensure that the SUT, on receipt of a 423 (Interval Too Brief) response to the unprotected REGISTER request, send another REGISTER request populating the registration expiration interval value with an expiration timer of at least the value received in the Min-Expires header field of the 423 (Interval Too Brief) response. | | | |
+| SIP header values | | | |
+| 423:
Min-Expires:
INVITE2
Expires: | | | |
+
+| | |
+|--------------------------------|------------------------|
+| Message flow | |
+| End device | Test equipment |
+| → | REGISTER |
+| ← | 423 Interval Too Brief |
+| → | REGISTER2 |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|---------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_030 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression |
+|-----------------------------|------------|---------------------------------------------------------|----------------------|
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Test purpose | |
+| Receipt of a 408 (Request Timeout) response to the unprotected REGISTER request | |
+| Ensure that the SUT, on receipt of a 408 (Request Timeout) response to the unprotected REGISTER request attempt to perform initial registration again. | |
+| SIP header values | |
+| Message flow | |
+| End device | Test equipment |
+| → | REGISTER |
+| ← | 408 Request Timeout |
+| → | REGISTER |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|---------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_031 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression |
+|-----------------------------|------------|---------------------------------------------------------|----------------------|
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Test purpose | |
+| Receipt of a 500 (Server Internal Error) response to the unprotected REGISTER request | |
+| Ensure that the SUT, on receipt of a 500 (Server Internal Error) response to the unprotected REGISTER request attempt to perform initial registration again. | |
+| SIP header values | |
+| Message flow | |
+| End device | Test equipment |
+| → | REGISTER |
+| ← | 500 Server Internal Error |
+| → | REGISTER2 |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------|------------|---------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_032 | Reference
subclause 5.1.1.2.1 of
[ETSI TS124 229] | Selection expression |
+|-----------------------------|------------|---------------------------------------------------------|----------------------|
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| Test purpose | |
+| Receipt of a 504 (Server Time-Out) response to the unprotected REGISTER request | |
+| Ensure that the SUT, on receipt of a 504 (Server Time-Out) response to the unprotected REGISTER request attempt to perform initial registration again. | |
+| SIP header values | |
+
+| | |
+|--------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| ➔ | REGISTER |
+| ⬅ | 504 Server Time-Out |
+| ➔ | REGISTER |
+| Apply post test routine | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_033 | Reference
Annex A and
section 17.1.3 of
[IETF RFC 3261] | Selection expression |
+| Test purpose | | | |
+| Receipt of a 600 (Busy Everywhere) response to the unprotected REGISTER request | | | |
+| Ensure that the SUT, on receipt of a 600 (Busy Everywhere) response to the unprotected REGISTER request attempt to perform initial registration again. | | | |
+| SIP header values | | | |
+| Message flow | | | |
+| End device | Test equipment | | |
+| ➔ | REGISTER | | |
+| ⬅ | 600 Busy Everywhere | | |
+| ➔ | REGISTER | | |
+| Apply post test routine | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------------------------------|----------------------|
+| TSS | TP_101_034 | Reference
Annex A and
section 17.1.3 of [IETF
RFC 3261] | Selection expression |
+| Test purpose | | | |
+| Receipt of a 403 (Forbidden) response to the unprotected REGISTER request | | | |
+| Ensure that the SUT, on receipt of a 403 (Forbidden) response to the unprotected REGISTER request, considers the registration to have failed. | | | |
+| SIP header values | | | |
+| Message flow | | | |
+| End device | Test equipment | | |
+| ➔ | REGISTER | | |
+| ⬅ | 403 Forbidden | | |
+| Apply post test routine | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|-----------------------------------|--|-------------------|--|-----------------------|--|--|---|----------|--|--|---|------------------|--|--|---|----------|--|--|---|-----------------|-------------------|--|-------|---------------|--|--|---|------------------|--|--|---|--------|--|--|---|---------------|-------------------|--|-------|---------------|--|--|---|-----------------------------------|--|--|---|-----------|--|--|---|------------------|--|--|---|--------|--|--|---|---------------|
+| TSS
Initial_registration | TP_101_035 | Reference
subclause 5.1.1.3 of
[ETSI TS 124 229] | Selection expression
PICS VGW | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Subscription to the registration-state event package
Ensure that the SUT, on receipt of a 200 OK REGISTER response, subscribes to the 'reg' event package. The SUT sends a SUBSCRIBE request to the resource to which the UE wants to be subscribed to.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIPheader values
SUBSCRIBE
Request URI: SIP URI which is the default public user identity used for subscription
From: [default public user identity used for subscription]
To: [default public user identity used for subscription]
Event: reg
Expires: 600000
200 OK SUBSCRIBE
Expires: [any value <=600000]
NOTIFY
Event: reg
Subscription-State: active; expires=<any value>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| | ➔ | REGISTER |
| | ⬅ | 401 Unauthorized |
| | ➔ | REGISTER |
| | ⬅ | 200 OK REGISTER |
CASE A | | ➔ | SUBSCRIBE |
| | ⬅ | 2xx OK SUBSCRIBE |
| | ⬅ | NOTIFY |
| | ➔ | 200 OK NOTIFY |
CASE B | | ➔ | SUBSCRIBE |
| | ⬅ | 407 Proxy Authentication Required |
| | ➔ | SUBSCRIBE |
| | ⬅ | 2xx OK SUBSCRIBE |
| | ⬅ | NOTIFY |
| | ➔ | 200 OK NOTIFY |
Apply post test routine
| | | | | End device | | Test equipment | | | ➔ | REGISTER | | | ⬅ | 401 Unauthorized | | | ➔ | REGISTER | | | ⬅ | 200 OK REGISTER |
CASE A | |
➔ |
SUBSCRIBE | | | ⬅ | 2xx OK SUBSCRIBE | | | ⬅ | NOTIFY | | | ➔ | 200 OK NOTIFY |
CASE B | |
➔ |
SUBSCRIBE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | SUBSCRIBE | | | ⬅ | 2xx OK SUBSCRIBE | | | ⬅ | NOTIFY | | | ➔ | 200 OK NOTIFY |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 200 OK REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE A | |
➔ |
SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 2xx OK SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE B | |
➔ |
SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 2xx OK SUBSCRIBE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|----------------------|-------------------|--|-----------------------|--|----------------------------------|--|---------------|------------------------------------------------------------------|--|---------------|------------------------------------------------------------------------------------------------------------------------|--|--|--------------------------------|--|
+| TSS
Initial_registration | TP_101_036 | Reference
subclause 5.1.1.3 of
[ETSI TS124 229] | Selection expression | | | | | | | | | | | | | | | |
+| Test purpose
Re-subscription to the registration-state event package | | | | | | | | | | | | | | | | | | |
+| Ensure that the SUT, after the registration state event is subscribed and the expires time is reached, starts the re-subscription procedure. The SUT sends a new SUBSCRIPTION request to re-subscribe the registration state event. | | | | | | | | | | | | | | | | | | |
+| SIPheader values
SUBSCRIBE
Request URI: SIP URI which is the default public user identity used for subscription
From: [default public user identity used for subscription]
To: [default public user identity used for subscription]
Event: reg
Expires: 600000
200 OK SUBSCRIBE
Expires: [any value <=600000] | | | | | | | | | | | | | | | | | | |
+| NOTIFY
Event: reg
Subscription-State : active; expires= | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SUT is already registered | |
| CASE A | → SUBSCRIBE ← 2xx OK SUBSCRIBE ← NOTIFY → 200 OK NOTIFY | |
| CASE B | → SUBSCRIBE ← 407 Proxy Authentication Required → SUBSCRIBE ← 2xx OK SUBSCRIBE ← NOTIFY → 200 OK NOTIFY | |
| Apply post test routine | |
| | | | End device | | Test equipment | | SUT is already registered | | CASE A | → SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY | | CASE B | → SUBSCRIBE
← 407 Proxy Authentication Required
→ SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY | | | Apply post test routine | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | |
+| | SUT is already registered | | | | | | | | | | | | | | | | | |
+| CASE A | → SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY | | | | | | | | | | | | | | | | | |
+| CASE B | → SUBSCRIBE
← 407 Proxy Authentication Required
→ SUBSCRIBE
← 2xx OK SUBSCRIBE
← NOTIFY
→ 200 OK NOTIFY | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------|----------------------|
+| TSS
Initial_registration | TP_101_037 | Reference
subclause 5.1.1.5A and
5.1.1.4.1of
[ETSI TS124 229] | Selection expression |
+| Test purpose
Network-initiated re-authentication | | | |
+| Ensure that the SUT, upon receipt of a NOTIFY to a subscribed registration state event, starts the re-authentication procedures. | | | |
+
+| | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|----------------------------------|--|---|--------|---|---------------|--|--|---|----------|---|------------------|---|----------|---|-------------------|--------------------------------|--|
+| SIPheader values
NOTIFY
Event: reg
Subscription-State : active
Contact: ;event= shortened;expires=[any value] | | | | | | | | | | | | | | | | | | | | |
+| REGISTER
Request-line: sip:[hostpart=domain of location service]
Call-ID [any value]
Cseq x REGISTER
From: sip:[address of registrant]
To: sip:[address of registrant]
Expires: 600000 | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| SUT is already registered |
| ← | NOTIFY |
| → | 200 OK NOTIFY |
| |
| → | REGISTER |
| ← | 401 Unauthorized |
| → | REGISTER |
| ← | 200 OK (REGISTER) |
| Apply post test routine |
| End device | Test equipment | SUT is already registered | | ← | NOTIFY | → | 200 OK NOTIFY | | | → | REGISTER | ← | 401 Unauthorized | → | REGISTER | ← | 200 OK (REGISTER) | Apply post test routine | |
+| End device | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SUT is already registered | | | | | | | | | | | | | | | | | | | | |
+| ← | NOTIFY | | | | | | | | | | | | | | | | | | | |
+| → | 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | |
+| → | REGISTER | | | | | | | | | | | | | | | | | | | |
+| ← | 401 Unauthorized | | | | | | | | | | | | | | | | | | | |
+| → | REGISTER | | | | | | | | | | | | | | | | | | | |
+| ← | 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | |
+
+#### 7.2.1.2 User-initiated re-registration and registration of an additional public user identity
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------|
+| TSS
User-initiated_re-registration | TP_102_001 | Reference
subclause 5.1.1.4.1 of
[ETSI TS124 229] | Selection expression |
+| Test purpose
User initiated reregistration
Ensure that the SUT, after the SUT is registered, starts the reregistration procedure of a previously registered public user identity. | | | |
+| SIP: Header values
REGISTER 1
Request-line: sip:[hostpart=domain of location service]
Call-ID [any value]
Cseq x REGISTER
From: sip:[address of registrant]
To: sip:[address of registrant]
Expires: 600000 | | | |
+
+
+
+| | |
+|----------------------------------------------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| SUT is already registered | |
+| The SUT has determined that a continued registration is not required | |
+| ➔ REGISTER | |
+| ⬅ 401 Unauthorized | |
+| ➔ REGISTER | |
+| ⬅ 200 OK REGISTER | |
+| Apply post test routine | |
+
+| | | | |
+|---------------------------------------|------------|---------------------------------------------------------|------------------------------------|
+| TSS
User-initiated_re-registration | TP_102_002 | Reference
subclause 5.1.1.4.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/3 |
+|---------------------------------------|------------|---------------------------------------------------------|------------------------------------|
+
+**Test purpose**
+*User initiated reregistration – GRUU supported*
+
+Ensure that the SUT, after the SUT is registered, starts the reregistration procedure of a previously registered public user identity.
+
+**SIPheader values**
+**REGISTER 1**
+ Supported: path,gruu
+
+
+
+| | |
+|----------------------------------------------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| SUT is already registered | |
+| The SUT has determined that a continued registration is not required | |
+| ➔ REGISTER | |
+| ⬅ 401 Unauthorized | |
+| ➔ REGISTER | |
+| ⬅ 200 OK REGISTER | |
+| Apply post test routine | |
+
+| | | | |
+|---------------------------------------|------------|---------------------------------------------------------|------------------------------------|
+| TSS
User-initiated_re-registration | TP_102_003 | Reference
subclause 5.1.1.4.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/4 |
+|---------------------------------------|------------|---------------------------------------------------------|------------------------------------|
+
+**Test purpose**
+*User initiated reregistration - multiple registrations is supported*
+
+Ensure that the SUT, after the SUT is registered, starts the reregistration procedure of a previously registered public user identity.
+
+**SIPheader values**
+**REGISTER 1**
+ Supported: path,outbound
+
+
+
+| | |
+|----------------------------------------------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| SUT is already registered | |
+| The SUT has determined that a continued registration is not required | |
+| ➔ REGISTER | |
+| ⬅ 401 Unauthorized | |
+| ➔ REGISTER | |
+| ⬅ 200 OK REGISTER | |
+| Apply post test routine | |
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------|----------------------------------------------|---------------------|--|-------------------|-----------------------|----------------------------------|--|----------------------------------------------------------------------|--|------------|--|--------------------|--|------------|--|-------------------|--|--------------------------------|--|
+| TSS
User-initiated_re-registration | TP_102_004 | Reference
subclause 5.1.1.4.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/4 and 5.2/5 | | | | | | | | | | | | | | | | | | |
+| Test purpose
User initiated reregistration - functions of an external attached network is supported | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the SUT, after the SUT is registered, starts the reregistration procedure of a previously registered public user identity. | | | | | | | | | | | | | | | | | | | | | |
+| SIPheader values
REGISTER 1
Require: gin | | | | | | | | | | | | | | | | | | | | | |
+| | Message flow |
| End device | Test equipment |
| SUT is already registered |
| The SUT has determined that a continued registration is not required |
| ➔ REGISTER | |
| ⬅ 401 Unauthorized | |
| ➔ REGISTER | |
| ⬅ 200 OK REGISTER | |
| Apply post test routine |
| | | | Message flow | | End device | Test equipment | SUT is already registered | | The SUT has determined that a continued registration is not required | | ➔ REGISTER | | ⬅ 401 Unauthorized | | ➔ REGISTER | | ⬅ 200 OK REGISTER | | Apply post test routine | |
+| Message flow | | | | | | | | | | | | | | | | | | | | | |
+| End device | Test equipment | | | | | | | | | | | | | | | | | | | | |
+| SUT is already registered | | | | | | | | | | | | | | | | | | | | | |
+| The SUT has determined that a continued registration is not required | | | | | | | | | | | | | | | | | | | | | |
+| ➔ REGISTER | | | | | | | | | | | | | | | | | | | | | |
+| ⬅ 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | |
+| ➔ REGISTER | | | | | | | | | | | | | | | | | | | | | |
+| ⬅ 200 OK REGISTER | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | |
+
+#### 7.2.1.3 User-initiated deregistration
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------|
+| TSS
User-initiated_deregistration | TP_103_001 | Reference
subclause 5.1.1.6.1 of
[ETSI TS124 229] | Selection expression |
+| Test purpose
User initiated deregistration – general procedure | | | |
+| Ensure that the SUT, after the SUT is registered, starts the deregistration procedure of a previously registered public user identity. | | | |
+
+| | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| SIPheader values
REGISTER 1
Request-line: sip:[hostpart=domain of location service]
From: sip:[address of registrant]
To: sip:[address of registrant]
Expires: 0 | |
+| Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a deregistration is required
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK REGISTER
Apply post test routine
| |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------|
+| TSS
User-initiated_deregistration | TP_103_002 | Reference
subclause 5.1.1.6.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/3 |
+| Test purpose
User initiated deregistration – GRUU supported
Ensure that the SUT, after the UE is registered, starts the deregistration procedure of a previously registered public user identity when GRUU is supported. | | | |
+| SIPheader values
REGISTER 1
Supported: path,gruu
Expires: 0 | | | |
+| Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a deregistration is required
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK REGISTER
Apply post test routine
| | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------|
+| TSS
User-initiated_deregistration | TP_103_003 | Reference
subclause 5.1.1.6.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/4 |
+| Test purpose
User initiated deregistration - multiple registrations is supported
Ensure that the SUT, after the UE is registered, starts the deregistration procedure of a previously registered public user identity when multiple registration is supported. | | | |
+| SIPheader values
REGISTER 1
Supported: path,outbound
Expires: 0 | | | |
+| Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a deregistration is required
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK REGISTER
Apply post test routine
| | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|----------------------------------------------|
+| TSS
User-initiated_deregistration | TP_103_004 | Reference
subclause 5.1.1.6.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/4 and 5.2/5 |
+| Test purpose
User initiated deregistration - functions of an external attached network is supported
Ensure that the SUT, after the UE is registered, starts the deregistration procedure of a previously registered public user identity when external attached network is performed. | | | |
+| SIPheader values
REGISTER 1
Require: gin
Expires: 0 | | | |
+| Message flow
End device Test equipment
SUT is already registered
The SUT has determined that a deregistration is required
→ REGISTER
← 401 Unauthorized
→ REGISTER
← 200 OK REGISTER
Apply post test routine
| | | |
+
+#### 7.2.1.4 Network-initiated deregistration
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------|----------------------|-------------------|--|-----------------------|--|----------------------------------|--|--|----------|--|--|-----------------|--|--|----------------|--|--|--------------------|--|--|------------|--|--|---------------------|--|--|--------------------------------|--|
+| TSS
Network-initiated_deregistration | TP_104_001 | Reference
subclause 5.1.1.7 of
[ETSI TS124 229] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Network-initiated deregistration
Ensure that the SUT, upon receipt of a NOTIFY to a subscribed registration state event, starts the deregistration procedures. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIPheader values
NOTIFY
Event: reg
Subscription-State: terminated
Contact: ;event= shortened;expires=[any value] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| REGISTER 1
Request-line: sip:[hostpart=domain of location service]
Call-ID [any value]
Cseq x REGISTER
From: sip:[address of registrant]
To: sip:[address of registrant]
Expires: 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SUT is already registered | |
| ← NOTIFY | |
| → 200 OK NOTIFY | |
| → REGISTER | |
| ← 401 Unauthorized | |
| → REGISTER | |
| ← 200 OK (REGISTER) | |
| Apply post test routine | |
| | | | End device | | Test equipment | | SUT is already registered | | | ← NOTIFY | | | → 200 OK NOTIFY | | |
→ REGISTER | | | ← 401 Unauthorized | | | → REGISTER | | | ← 200 OK (REGISTER) | | | Apply post test routine | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | SUT is already registered | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → 200 OK NOTIFY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| |
→ REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → REGISTER | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 200 OK (REGISTER) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+#### 7.2.1.5 Subscription and notification
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|------------------------------------|
+| TSS
Subscription_and_notification | TP_105_001 | Reference
subclause 5.3.1 of
[ETSI TS183 043] | Selection expression
PICS 5.3/1 |
+| Test purpose
Subscription to the User Agent Profile Delivery
Ensure that the SUT sends a SUBSCRIBE to the network to subscribe to the User Agent Profile Delivery. The SUT receives a dial-tone-management XML element. | | | |
+| | | | |
+
+| | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|----------------------------------|--|---|-----------|---|--------------------|--|--|---|--------|---|-----------------|--------------------------------|--|
+| SIPheader values
SUBSCRIBE
Event: ua-profile;profile-type=user ; vendor="[any reasonable value]";model="[any reasonable value]";version="[any reasonable value]" | | | | | | | | | | | | | | | | |
+| NOTIFY
Event: ua-profile;profile-type=user ; vendor="[any reasonable value]";model="[any reasonable value]";version="[any reasonable value]"
standard-dial-tone (optional)
special-condition-tone (optional)
message-waiting-tone (optional)
| | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| SUT is already registered |
| → | SUBSCRIBE |
| ← | 200 OK (SUBSCRIBE) |
| |
| ← | NOTIFY |
| → | 200 OK (NOTIFY) |
| Apply post test routine |
| End device | Test equipment | SUT is already registered | | → | SUBSCRIBE | ← | 200 OK (SUBSCRIBE) | | | ← | NOTIFY | → | 200 OK (NOTIFY) | Apply post test routine | |
+| End device | Test equipment | | | | | | | | | | | | | | | |
+| SUT is already registered | | | | | | | | | | | | | | | | |
+| → | SUBSCRIBE | | | | | | | | | | | | | | | |
+| ← | 200 OK (SUBSCRIBE) | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | |
+| ← | NOTIFY | | | | | | | | | | | | | | | |
+| → | 200 OK (NOTIFY) | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|------------------------------------|
+| TSS
Subscription_and_notification | TP_105_002 | Reference
subclause 5.3.1 of
[ETSI TS183 043] | Selection expression
PICS 5.3/1 |
+| Test purpose
Subscription to the Message waiting indication
Ensure that the SUT sends a SUBSCRIBE to the network to subscribe to the Message Waiting indication service. The SUT receives in a NOTIFY request a MIME body with new reports about waiting messages. | | | |
+| SIPheader values
SUBSCRIBE
Accept: application/simple-message-summary
Expires:
Event: message-summary | | | |
+| NOTIFY
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
MIME body:
Messages-Waiting: yes
Message-Account: sip:served_user@Server
Voice-Message: 4/1 (2/0)
Video-Message: 3/1 (1/0)
Fax-Message: 2/1 (0/1) | | | |
+
+
+
+| | |
+|--------------------------------|-----------------------|
+| Message flow | |
+| End device | Test equipment |
+| SUT is already registered | |
+| → | SUBSCRIBE |
+| ← | 200 OK (SUBSCRIBE) |
+| ← | NOTIFY |
+| → | 200 OK (NOTIFY) |
+| Apply post test routine | |
+
+| | | | |
+|--------------------------------------|------------|-----------------------------------------------------|------------------------------------|
+| TSS
Subscription_and_notification | TP_105_003 | Reference
subclause 5.3.1 of
[ETSI TS183 043] | Selection expression
PICS 5.3/1 |
+|--------------------------------------|------------|-----------------------------------------------------|------------------------------------|
+
+**Test purpose**
+*Subscription to the Message waiting indication rejected with 503*
+
+Ensure that the SUT sends a SUBSCRIBE to the network to subscribe to the Message Waiting indication service. The SUT receives a 503 (Service Unavailable) response to a SUBSCRIBE request containing a Retry-After header. The SUT does not automatically reattempt the request until after the period indicated by the Retry-After header contents
+
+**SIPheader values**
+**SUBSCRIBE**
+ Accept: application/simple-message-summary
+ Expires:
+ Event: message-summary
+
+**503**
+ Retry-After: 20
+
+
+
+| | |
+|-------------------------------------------------------|-------------------------|
+| Message flow | |
+| End device | Test equipment |
+| SUT is already registered | |
+| → | SUBSCRIBE |
+| ← | 200 OK (SUBSCRIBE) |
+| ← | 503 Service Unavailable |
+| Wait for the time indicated in the Retry-After header | |
+| → | SUBSCRIBE |
+| ← | 200 OK (SUBSCRIBE) |
+| Apply post test routine | |
+
+### 7.2.2 Call initiation – UE-originating case
+
+#### 7.2.2.1 Establishment of an early dialogue
+
+##### 7.2.2.1.1 SIP basic procedures
+
+| | | | |
+|------------------------------------------------|------------|--------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_001 | Reference
section 8.1.1 of
[IETF RFC 3261] | Selection expression |
+|------------------------------------------------|------------|--------------------------------------------------|----------------------|
+
+**Test purpose**
+*Sending of INVITE request containing all mandatory headers*
+
+Ensure that the SUT is able to send an INVITE request containing all mandatory SIP headers:
+
+| | |
+|-------------------------------------------------------------------------------------------------------|--------------------------|
+| SIP Header values
INVITE
To
From
CSeq
Call-ID
Max-Forwards
Contact
Via | |
+| Message flow | |
+| End device | Test equipment |
+| Interworking POTS
Off hook
Dial number | |
+| | → INVITE
← 100 Trying |
+| ISDN interworking
SETUP | |
+| | → INVITE
← 100 Trying |
+| Apply post test routine | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------|--------------------------|---------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_002 | Reference
section 8.1.1. of
[IETF RFC 3261] | Selection expression |
+| Test purpose
The Request line is set to the same URI value of the To header | | | |
+| Ensure that the IUT is able to establish a session and the Request line URI is set to the same value as the To header URI | | | |
+| SIP header values
INVITE sip: [Request URI] SIP/2.0
To: < sip: [Request URI]> | | | |
+| Message flow | | | |
+| End device | Test equipment | | |
+| Interworking POTS
Off hook
Dial number | | | |
+| | → INVITE
← 100 Trying | | |
+| ISDN interworking
SETUP | | | |
+| | → INVITE
← 100 Trying | | |
+| Apply post test routine | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|------------|------------------------------|--|--|--|-------|--|---|--------|--|--|---|------------|--------------------------------|--|--|--|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_003 | Reference
section 8.1.1.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
The To header does not contain a 'tag' parameter
Ensure that the IUT is able to establish a session and the 'To' header in the INVITE request does not contain the 'tag' parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
To: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS | | | |
| Off hook | | | |
| Dial number | | ➔ | INVITE |
| | ⬅ | 100 Trying |
ISDN interworking | | | |
| SETUP | | ➔ | INVITE |
| | ⬅ | 100 Trying |
| Apply post test routine |
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 100 Trying |
ISDN interworking | | | | SETUP | | ➔ | INVITE | | | ⬅ | 100 Trying | Apply post test routine | | | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|------------|------------------------------|--|--|--|-------|--|---|--------|--|--|---|------------|--------------------------------|--|--|--|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_004 | Reference
section 8.1.1.3 of [IETF RFC
3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
The From header contains a 'tag' parameter
Ensure that the IUT is able to establish a session and the 'From' header in the INVITE request contains the 'tag' parameter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
From: ;tag=[any value] | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS | | | |
| Off hook | | | |
| Dial number | | ➔ | INVITE |
| | ⬅ | 100 Trying |
ISDN interworking | | | |
| SETUP | | ➔ | INVITE |
| | ⬅ | 100 Trying |
| Apply post test routine |
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 100 Trying |
ISDN interworking | | | | SETUP | | ➔ | INVITE | | | ⬅ | 100 Trying | Apply post test routine | | | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_005 | Reference
section 8.1.1.5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|------------------------------|--|--|-------|---|--------|--|---|------------|
+| Test purpose
The CSeq header contains the method INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE includes a CSeq header and the method parameter is set to 'INVITE'. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
CSeq: INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 100 Trying |
ISDN interworking |
| SETUP | ➔ | INVITE |
| ⬅ | 100 Trying |
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying |
ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_006 | Reference
section 8.1.1.6 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|------------------------------|--|--|-------|---|--------|--|---|------------|
+| Test purpose
Max-Forwards initial value | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE contains a Max-Forwards header set to the initial value '70' | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
Max-Forwards: 70 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 100 Trying |
ISDN interworking |
| SETUP | ➔ | INVITE |
| ⬅ | 100 Trying |
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying |
ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_007 | Reference
section 8.1.1.7 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Coding of Via header in the INVITE
Ensure that the IUT is able to establish a session and the INVITE contains a Via header with a protocol name set to SIP, a protocol version set to 2.0 and a branch parameter set to a value beginning with "z9hG4bK". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
Via:SIP 2.0 ;branch= z9hG4bK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 100 Trying |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| ⬅ | 100 Trying |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_008 | Reference
section 13.2.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Allow and Supported header in the INVITE
Ensure that the IUT is able to establish a session and the INVITE contains the Allow and Supported header | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
Allow:
Supported: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 100 Trying |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| ⬅ | 100 Trying |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|-------------------|---|------------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_009 | Reference
sections 8, 8.1.3.2, 13.2.2.1
and Figure 5 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
100 received, the client enters the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Calling state, on receipt of a Trying (100 Trying) response enters in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 100 Trying |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 100 Trying |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|----------------------|--------------------------|--|--|-------|---|--------|-----------------|---|----------------------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_010 | Reference
sections 8, 8.1.3.2, 13.2.2.1
and Figure 5 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
183 received, the client enters the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Calling state, on receipt of a Session Progress (183 Session Progress) response enters in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 183 Session Progress |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| CALL PROCEEDING | ⬅ | 183 Session Progress |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 183 Session Progress | ISDN interworking | | | SETUP | ➔ | INVITE | CALL PROCEEDING | ⬅ | 183 Session Progress | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CALL PROCEEDING | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|--------------------------|--|--|-------|---|--------|----------|---|-------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_011 | Reference
sections 8, 8.1.3.2, 13.2.2.1,
and Figure 5 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
180 received, the client enters the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Calling state, on receipt of a Ringing (180 Ringing) response enters in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 180 Ringing |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| ALERTING | ⬅ | 180 Ringing |
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 180 Ringing | ISDN interworking | | | SETUP | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|--------------------------|--|--|-------|---|--------|-------------------|---|-------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_012 | Reference
sections 8, 8.1.3.2, 13.2.2.1
and Figure 5 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
198 received, the client enters the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Calling state, on receipt of a Unknown (198 Unknown) response enters in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 198 Unknown |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 198 Unknown |
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 198 Unknown | ISDN interworking | | | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 198 Unknown |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 198 Unknown | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 198 Unknown | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|------------------------------|--|--|-------|---|--------|-------------------|---|------------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_013 | Reference
sections 8, 8.1.3.2, 13.2.2.1 and Figure 5 [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
100 received, the client remains the Proceeding state | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE client transaction is in the Proceeding state, on receipt of a Trying (100 Trying) response stays in the Proceeding state. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 100 Trying |
ISDN interworking |
| SETUP | → | INVITE |
| SETUP ACKNOWLEDGE | ← | 100 Trying |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 100 Trying |
ISDN interworking | | | SETUP | → | INVITE | SETUP ACKNOWLEDGE | ← | 100 Trying | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|------------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_014 | Reference
section 20.14 and 13.2.1 of [IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Content-Length header and SDP in the initial INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE request contains the Content-Length header set to the size of the body in the message that contains the session description. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE
Content-Length: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SDP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 100 Trying |
ISDN interworking |
| SETUP | → | INVITE |
| ← | 100 Trying |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 100 Trying |
ISDN interworking | | | SETUP | → | INVITE | | ← | 100 Trying | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_015 | Reference
section 20.15 and 13.2.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Content-Type header and SDP in the initial INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE request contains the Content-Type header in the message that contains the session description. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
Content-Type: application/sdp
SDP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 100 Trying |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| ⬅ | 100 Trying |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|--------------------------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|--------------------------|--|--|-------|---|--------|--|---|------------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_016 | Reference
section 20.14 and 13.2.1 of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Content-Length header and SDP in the initial INVITE and TCP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE request contains the Content-Length header set to the size of the body in the message that contains the session description and a reliable transport (TCP) is used. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
Content-Type: application/sdp
SDP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 100 Trying |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| ⬅ | 100 Trying |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | ISDN interworking | | | SETUP | ➔ | INVITE | | ⬅ | 100 Trying | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------|-------------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|----------|--|--|---|------------------|--|--|---|-----|--|--|---|----------|------------------------------|--|--|--|-------|--|---|----------|--|--|---|------------------|--|--|---|-----|--|--|---|----------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_017 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression on | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
The CSeq in the repeated INVITE is incremented | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE request, on receipt of an Unauthorized (401 Unauthorized) response including a WWW-Authenticate header, repeats its INVITE request with an Authorization header and with an incremented Cseq value.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE1:
CSeq: INVITE
INVITE2:
Authorization:
CSeq: INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | | |
| Dial number | | ➔ | INVITE 1 |
| | ⬅ | 401 Unauthorized |
| | ➔ | ACK |
| | ➔ | INVITE 2 |
ISDN interworking |
| SETUP | | ➔ | INVITE 1 |
| | ⬅ | 401 Unauthorized |
| | ➔ | ACK |
| | ➔ | INVITE 2 |
Apply post test routine
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE 1 | | | ⬅ | 401 Unauthorized | | | ➔ | ACK | | | ➔ | INVITE 2 |
ISDN interworking | | | | SETUP | | ➔ | INVITE 1 | | | ⬅ | 401 Unauthorized | | | ➔ | ACK | | | ➔ | INVITE 2 |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | | ➔ | INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | ➔ | INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 401 Unauthorized | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | INVITE 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_018 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
Authorization header present in the repeated INVITE | | | |
+| Ensure that the IUT is able to establish a session and the INVITE request, on receipt of a 401 Unauthorized response including a WWW-Authenticate header, repeats its INVITE request with an Authorization header including proper values for username, realm nonce, digest-uri and response HTTP parameters.
| | | |
+| SIP header values
INVITE2:
Authorization: Digest username="", realm="",nonce="",uri="", qop=auth, cnonce="",response="",algorithm= | | | |
+
+| Message flow | | |
+|--------------------------------|-------------------|-----------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | ➔ | INVITE1 |
+| | ⬅ | 401 Unauthorized |
+| | ➔ | ACK |
+| | ➔ | INVITE2 |
+|
ISDN interworking | | |
+| SETUP | ➔ | INVITE |
+| | ⬅ | 401 Unauthorized |
+| | ➔ | ACK |
+| | ➔ | INVITE2 |
+| Apply post test routine | | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_019 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression |
+| Test purpose | | | |
+| The CSeq in the repeated INVITE is incremented | | | |
+| Ensure that the IUT is able to establish a session and the INVITE request, on receipt of a 407 Proxy Authentication Required response including a Proxy-Authenticate header, repeats its INVITE request with an Proxy-Authorization header and with an incremented Cseq value. | | | |
+| SIP header values | | | |
+| INVITE1:
CSeq: INVITE | | | |
+| INVITE2:
Proxy-Authenticate:
CSeq: INVITE | | | |
+| Message flow | | | |
+| | End device | Test equipment | |
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | ➔ | INVITE | |
+| | ⬅ | 407 Proxy Authentication Required | |
+| | ➔ | ACK | |
+| | ➔ | INVITE2 | |
+|
ISDN interworking | | | |
+| SETUP | ➔ | INVITE | |
+| | ⬅ | 407 Proxy Authentication Required | |
+| | ➔ | ACK | |
+| | ➔ | INVITE2 | |
+| Apply post test routine | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|-----------------------------------|-------------------|--|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|---------|--------------------------|--|--|--|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|---------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_020 | Reference
section 8.1.3.5 and 22.2 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Proxy-Authorization header present in the repeated INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT is able to establish a session and the INVITE request, on receipt of an 407 Proxy Authentication Required response including a Proxy-Authenticate header, repeats its INVITE request with an Proxy-Authorization header including proper values for username, realm nonce, digest-uri and response HTTP parameters. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE2:
Proxy-Authorization: Digest username=""=" , realm=""=",nonce=""=",uri=""=", qop=auth, cnonce=""=",response=""=",algorithm= | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | | Test equipment |
| Interworking POTS |
| Off hook | | | |
| Dial number | | ➔ | INVITE |
| | ⬅ | 407 Proxy Authentication Required |
| | ➔ | ACK |
| | ➔ | INVITE2 |
| ISDN interworking |
| SETUP | | ➔ | INVITE |
| | ⬅ | 407 Proxy Authentication Required |
| | ➔ | ACK |
| | ➔ | INVITE2 |
Apply post test routine
| | | | End device | | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE2 | ISDN interworking | | | | SETUP | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE2 |
+| End device | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_021 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression |
+| Test purpose
Accept header with support of SDP in the initial INVITE | | | |
+| Ensure that the IUT is able to generate an initial INVITE request, the UE shall include the Accept header field with "application/sdp". | | | |
+| SIP header values
INVITE2:
Accept: < application/sdp > | | | |
+
+| Message flow | |
+|--------------------------------|-----------------------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 |
+| ISDN interworking | |
+| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 |
+| Apply post test routine | |
+
+| | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------------------------|-------------------------------------|--|--|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_022 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/14 | | |
+| Test purpose
Precondition support in the initial INVITE | | | | | |
+| Ensure that the IUT is able to generating an initial INVITE request with indication of support of resource reservation, the SUT shall include the Support header field with "precondition" and "100rel". | | | | | |
+| SIP header values | | | | | |
+| INVITE2:
Supported: precondition,100rel | | | | | |
+| SDP
.
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory/optional local sendrecv
a=des:qos mandatory/optional remote sendrecv | | | | | |
+| Message flow | | | | | |
+| End device | | Test equipment | | | |
+| Interworking POTS | | | | | |
+| Off hook | | | | | |
+| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | | | | |
+| ISDN interworking | | | | | |
+| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 | | | | |
+| Apply post test routine | | | | | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|-------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_023 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/14 |
+| Test purpose
Successful resource reservation procedure
Ensure that the IUT is able to complete the resource reservation procedure. The (reliable) 183 contains in the SDP the instruction to reserve the quality of service on the SUT side. The SUT indicates that resource is reserved in the UPDATE request and the remote side confirms the resource reservation in the 200 OK UPDATE.
SIP header values
INVITE2:
Supported: precondition,100rel
SDP a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory/optional local sendrecv
a=des:qos mandatory/optional remote sendrecv
183:
Require: precondition,100rel
SDP a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory/optional local sendrecv
a=des:qos mandatory/optional remote sendrecv
a=conf:qos remote sendrecv
UPDATE
SDP a=curr:qos local sendrecv
a=curr:qos remote none
a=des:qos mandatory/optional local sendrecv
a=des:qos mandatory/optional remote sendrecv
200 OK UPDATE
SDP a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory/optional local sendrecv
a=des:qos mandatory/optional remote sendrecv
| | | |
+
+
+
+| Message flow | |
+|--------------------------------|-------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE2 |
+| | 183 Session progress |
+| | PRACK |
+| | 200 OK PRACK |
+| | UPDATE |
+| | 200 OK UPDATE |
+| ISDN interworking | |
+| SETUP | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE2 |
+| | 183 Session progress |
+| | PRACK |
+| | 200 OK PRACK |
+| | UPDATE |
+| | 200 OK UPDATE |
+| Apply post test routine | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|-------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_024 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/14 |
+| Test purpose
Successful resource reservation procedure
Ensure that the IUT upon receiving a 421 (Extension Required) response to an initial INVITE request in which the precondition mechanism was not used, including the "precondition" option-tag in the Require header field, the SUT sends a new INVITE request and the Supported header contains the precondition option tag. | | | |
+
+###### **SIP header values**
+
+INVITE3:
+
+Supported: precondition,100rel
+
+SDP a=curr:qos local none
+a=curr:qos remote none
+a=des:qos mandatory/optional local sendrecv
+a=des:qos mandatory/optional remote sendrecv
+
+183:
+
+Require: precondition,100rel
+
+SDP a=curr:qos local none
+a=curr:qos remote none
+a=des:qos mandatory/optional local sendrecv
+a=des:qos mandatory/optional remote sendrecv
+a=conf:qos remote sendrecv
+
+UPDATE/PRACK
+
+SDP a=curr:qos local sendrecv
+a=curr:qos remote none
+a=des:qos mandatory/optional local sendrecv
+a=des:qos mandatory/optional remote sendrecv
+
+200 OK UPDATE/200 OK PRACK
+
+SDP a=curr:qos local sendrecv
+a=curr:qos remote sendrecv
+a=des:qos mandatory/optional local sendrecv
+a=des:qos mandatory/optional remote sendrecv
+
+| Message flow | |
+|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 421 Extension Required
→ ACK
→ INVITE3
← 183 Session progress
→ PRACK
← 200 OK PRACK
→ UPDATE
← 200 OK UPDATE |
+| ISDN interworking | |
+| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 421 Extension Required
→ ACK
→ INVITE3
← 183 Session progress
→ PRACK
← 200 OK PRACK
→ UPDATE
← 200 OK UPDATE |
+| Apply post test routine | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|-------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_025 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229] | Selection expression
PICS 5.2/14 |
+| Test purpose
SUT wishes to receive early media authorization indications | | | |
+| Ensure that the IUT, if it wishes to receive early media authorization indications, the SUT inserts the P-Early-Media header field with the "supported" parameter to the INVITE request. | | | |
+| SIP header values
INVITE2:
P-Early-Media: supported | | | |
+
+| Message flow | |
+|--------------------------------|-----------------------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 |
+| ISDN interworking | |
+| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------|-------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_026 | Reference
section 4 of [IETF RFC 3262] | Selection expression
PICS 5.2/15 |
+| Test purpose
SUT supports the reliable provisional response procedure | | | |
+| Ensure that the IUT supports the reliable provisional response procedure, the "supported" header set to '100rel' is present in the INVITE request.
Upon a 18x provisional response containing a Require header set to '100rel' and an RSeq header, the SUT sends a PRACK request containing the RAck header. The response-num is equal to the value in the received RSeq header. The CSeq-num is equal to the CSeq value in the sent INVITE. The Method parameter is set to 'INVITE'.
| | | |
+| SIP header values
INVITE2:
Supported: 100rel
CSeq: 2 INVITE
183:
Require: 100rel
RSeq: 3
PRACK
RAck: 3 2 INVITE | | | |
+
+| Message flow | |
+|--------------------------------|-----------------------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 |
+| CASE A | ← 183 Session Progress
→ PRACK
← 200 OK (PRACK) |
+| CASE B | ← 183 Session Progress
→ PRACK
← 200 OK (PRACK) |
+| ISDN interworking | |
+| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2 |
+| CASE A | ← 183 Session Progress
→ PRACK
← 200 OK (PRACK) |
+| CASE B | ← 183 Session Progress
→ PRACK
← 200 OK (PRACK) |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_027 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
Section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT presents received early media to the user. 183 received, no P-Early-Media header present.
Ensure that the IUT upon receiving a 183 Session Progress provisional response without a P-Early-Media header field and SDP answer is received, the SUT presents the received early media to the user. Forward early media is not gated. | | | |
+
+**SIP header values**
+ INVITE2:
+ P-Early-Media: supported
+ SDP offer
+
+ 183:
+ SDP answer
+
+
+
+| Message flow | | |
+|--------------------------------|------------|-----------------------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE2 |
+| | ← | 183 Session Progress |
+| Media | ← | Media |
+| Media | → | |
+| ISDN interworking | | |
+| SETUP | → | INVITE |
+| | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE2 |
+| | ← | 183 Session Progress |
+| Media | ← | Media |
+| Media | → | |
+| Apply post test routine | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_028 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT presents received early media to the user. 180 received, no P-Early-Media header present. | | | |
+| Ensure that the IUT upon receiving a 180 Ringing provisional response without a P-Early-Media header field and an SDP answer is received, the SUT presents the received early media to the user. Forward early media is not gated. | | | |
+| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer
183:
SDP answer | | | |
+
+
+
+| Message flow | | |
+|--------------------------------|------------|-----------------------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE2 |
+| | ← | 183 Session Progress |
+| Media | ← | Media |
+| Media | → | |
+| ISDN interworking | | |
+| SETUP | → | INVITE |
+| | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE2 |
+| | ← | 183 Session Progress |
+| Media | ← | Media |
+| Media | → | |
+| Apply post test routine | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_029 | Reference
clause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT presents received early media to the user. 183 received, P-Early-Media header present.
Ensure that the IUT upon receiving a 180 Ringing provisional response with a P-Early-Media header field indicating authorized early media and SDP answer is received, the SUT presents the received early media to the user. In case of P-Early-Media sendrecv, early media generated by the user is presented to the network. | | | |
+
+**SIP header values**
+
+INVITE2:
+P-Early-Media: supported
+SDP offer
+
+180:
+P-Early-Media: [sendonly]/[sendrecv]
+SDP answer
+
+
+
+| Message flow | | |
+|--------------------------------|------------|-----------------------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE2 |
+| | ← | 180 Ringing |
+| CASE A sendonly | | |
+| Media | ← | Media |
+| Media | → | |
+| CASE A sendrecv | | |
+| Media | ← | Media |
+| Media | → | Media |
+| ISDN interworking | | |
+| SETUP | → | INVITE |
+| | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE2 |
+| | ← | 180 Ringing |
+| CASE A sendonly | | |
+| Media | ← | Media |
+| Media | → | |
+| CASE A sendrecv | | |
+| Media | ← | Media |
+| Media | → | Media |
+| Apply post test routine | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_030 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT presents received early media to the user. 183 received, P-Early-Media header present.
Ensure that the IUT upon receiving a 183 Session Progress provisional response with a P-Early-Media header field indicating authorized early media and SDP answer is received, the SUT presents the received early media to the user. In case of P-Early-Media sendrecv, early media generated by the user is presented to the network. | | | |
+
+###### **SIP header values**
+
+INVITE2:
+
+P-Early-Media: supported
+
+SDP offer
+
+183:
+
+P-Early-Media: [sendonly]/[sendrecv]
+
+SDP answer
+
+###### **Message flow**
+
+**End device**
+
+**Test equipment**
+
+###### **Interworking POTS**
+
+Off hook
+
+Dial number
+
+→ INVITE
+← 407 Proxy Authentication Required
+→ ACK
+→ INVITE2
+← 183 Session Progress
+
+###### **CASE A sendonly**
+
+Media
+
+Media
+
+← Media
+→
+
+###### **CASE A sendrecv**
+
+Media
+
+Media
+
+← Media
+→ Media
+
+###### **ISDN interworking**
+
+SETUP
+
+→ INVITE
+← 407 Proxy Authentication Required
+→ ACK
+→ INVITE2
+← 183 Session Progress
+
+###### **CASE A sendonly**
+
+Media
+
+Media
+
+← Media
+→
+
+###### **CASE A sendrecv**
+
+Media
+
+Media
+
+← Media
+→ Media
+
+**Apply post test routine**
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_031 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 [IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT does not present early media to the user. 183 received, no P-Early-Media header present.
Ensure that the IUT upon receiving a 183 Session Progress provisional response without receipt of a P-Early-Media header field, the SUT does not present early media to the user if no RTP is received from the network. Forward early media is not gated. | | | |
+
+
+
+| | |
+|--------------------------|--|
+| SIP header values | |
+| INVITE2: | |
+| P-Early-Media: supported | |
+| SDP offer | |
+| 183: | |
+| SDP answer yes/no | |
+
+
+
+| | |
+|--------------------------------|-------------------------------------|
+| Message flow | |
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE2 |
+| | ← 183 Session Progress |
+| ISDN interworking | |
+| SETUP | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE2 |
+| | ← 183 Session Progress |
+| Apply post test routine | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_032 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT does not present early media to the user. 183 received, P-Early-Media header present.
Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is received, value sendonly or sendrecv, the SUT does not present early media to the user if no RTP is received from the network. Forward early media is not gated. | | | |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|
+| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer
183:
P-Early-Media: [sendonly]/[sendrecv]
SDP answer yes/no | |
+| Message flow | |
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | ➔ INVITE |
+| | ⬅ 407 Proxy Authentication Required |
+| | ➔ ACK |
+| | ➔ INVITE2 |
+| | ⬅ 183 Session Progress |
+|
ISDN interworking | |
+| SETUP | ➔ INVITE |
+| | ⬅ 407 Proxy Authentication Required |
+| | ➔ ACK |
+| | ➔ INVITE2 |
+| | ⬅ 183 Session Progress |
+| Apply post test routine | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_033 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT does not present early media to the user. 183 received, P-Early-Media header present. | | | |
+| Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is received, value inactive or recvonly, the SUT does not present early media to the user. Forward early media is not gated.
| | | |
+| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer
183:
P-Early-Media: [sendonly]/[sendrecv]
SDP answer yes/no | | | |
+
+| Message flow | |
+|--------------------------------|-------------------------------------------------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 183 Session Progress |
+| ISDN interworking | |
+| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 183 Session Progress |
+| Apply post test routine | |
+
+| | | | |
+|------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_034 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+|------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+
+| |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
SUT local ring back tone is presented to the user. 183 received, P-Early-Media header not present.
Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is not received, the SUT play ringing tones for the caller, indicating that the callee is being alerted. Forward early media is not gated. |
+| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer
183:
SDP answer yes/no |
+
+| Message flow | |
+|--------------------------------|-------------------------------------------------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 183 Session Progress |
+| ISDN interworking | |
+| SETUP | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE2
← 183 Session Progress |
+| Apply post test routine | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_035 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT local ring back tone is presented to the user. 183 received, P-Early-Media header value sendonly or sendrecv present.
Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is received value sendonly or sendrecv, the SUT plays ringing tones for the caller, indicating that the callee is being alerted if no media is received from the network. Forward early media is not gated. | | | |
+
+
+
+| | |
+|--------------------------------------|--|
+| SIP header values | |
+| INVITE2: | |
+| P-Early-Media: supported | |
+| SDP offer | |
+| | |
+| 183: | |
+| P-Early-Media: [sendonly]/[sendrecv] | |
+| SDP answer yes/no | |
+
+
+
+| | |
+|--------------------------------|-------------------------------------|
+| Message flow | |
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE2 |
+| | ← 183 Session Progress |
+| Local Ring back Tone | ← |
+| | |
+| ISDN interworking | |
+| SETUP | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE2 |
+| | ← 183 Session Progress |
+| Local Ring back Tone | ← |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_036 | Reference
subclause 5.1.3.1 of
[ETSI TS124 229]
section 6 and 8 of
[IETF RFC 5009] | Selection expression
PICS5.2/16 |
+| Test purpose
SUT local ring back tone is presented to the user. 183 received, P-Early-Media header value sendonly or sendrecv present.
Ensure that the IUT upon receiving a 183 Session Progress provisional response a P-Early-Media header field is received value recvonly or inactive, the SUT plays ringing tones for the caller, indicating that the callee is being alerted. Forward early media is not gated. | | | |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|
+| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer
183:
P-Early-Media: [recvonly]/[inactive]
SDP answer yes/no | |
+| Message flow | |
+| End device | Test equipment |
+| Interworking POTS
Off hook
Dial number | |
+| | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE2 |
+| | ← 183 Session Progress |
+| Local Ring back Tone | ← |
+| ISDN interworking
SETUP | |
+| | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE2 |
+| | ← 183 Session Progress |
+| Local Ring back Tone | ← |
+| Apply post test routine | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_037 | Reference
subclause 6.1.2 of
[ETSI TS124 229] | Selection expression |
+| Test purpose
Handling of SDP offer | | | |
+| Ensure that the IUT when sending an INVITE request contains a SDP offer and at least one media description. This SDP offer shall reflect the calling user's terminal capabilities and user preferences for the session. | | | |
+| SIP header values
INVITE2:
SDP offer | | | |
+| Message flow | | | |
+| End device | Test equipment | | |
+| Interworking POTS
Off hook
Dial number | | | |
+| | → INVITE | | |
+| | ← 407 Proxy Authentication Required | | |
+| | → ACK | | |
+| | → INVITE2 | | |
+
+| | |
+|--------------------------------|-------------------------------------|
+| ISDN interworking | |
+| SETUP | ➔ INVITE |
+| | ← 407 Proxy Authentication Required |
+| | ➔ ACK |
+| | ➔ INVITE2 |
+| Apply post test routine | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------------|-----------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_038 | Reference
subclause 6.1.2 of
[ETSI TS124 229] | Selection expression |
+| Test purpose | | | |
+| Handling of SDP answer | | | |
+| Ensure that the IUT Upon generating the SDP offer for an INVITE request generated after receiving a 488 (Not Acceptable Here) response, the SDP offer contains a subset of the allowed media types, codecs and other parameters from the SDP message bodies of all 488 (Not Acceptable Here) responses so far received for the same session establishment attempt (i.e. a set of INVITE requests used for the same session establishment). For each media line, the SUT shall order the codecs in the SDP offer according to the order of the codecs in the SDP message bodies of the 488 (Not Acceptable Here) responses. | | | |
+| SIP header values | | | |
+| INVITE2:
SDP offer1
488
SDP answer1
INVITE3:
SDP offer2 equal SDP answer1 | | | |
+| Message flow | | | |
+| End device | | | Test equipment |
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | | | |
+| | ➔ INVITE | | |
+| | ← 407 Proxy Authentication Required | | |
+| | ➔ ACK | | |
+| | ➔ INVITE2 | | |
+| | ← 488 (Not Acceptable Here) | | |
+| | ➔ ACK | | |
+| | ➔ INVITE3 | | |
+| ISDN interworking | | | |
+| SETUP | | | |
+| | ➔ INVITE | | |
+| | ← 407 Proxy Authentication Required | | |
+| | ➔ ACK | | |
+| | ➔ INVITE2 | | |
+| | ← 488 Not Acceptable Here | | |
+| | ➔ ACK | | |
+| | ➔ INVITE3 | | |
+| Apply post test routine | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|----------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|---------|--|---|--------------|--|---|--------------|--|---|------------------|--|---|-----|--|---|------|--|---|--------------|------------------------------|--|--|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|---------|--|---|--------------|--|---|--------------|--|---|------------------|--|---|-----|--|---|------|--|---|--------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_039 | Reference | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
SUT terminates the forked not confirmed dialogue with a BYE request.
Ensure that the IUT when a final answer is received for one of the (forked) early dialogues, the SUT proceeds to set up the SIP session. An ACK is sent to acknowledge the confirmed dialogue and a BYE is sent to terminate the remaining early dialogues. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE2:
P-Early-Media: supported
SDP offer
180 1:
P-Early-Media: [recvonly]/[inactive]
SDP answer yes/no | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 407 Proxy Authentication Required |
| → | ACK |
| → | INVITE2 |
| ← | 180 Ringing1 |
| ← | 180 Ringing2 |
| ← | 200 OK (INVITE)2 |
| → | ACK |
| → | BYE1 |
| ← | 200 OK (BYE) |
ISDN interworking |
| SETUP | → | INVITE |
| ← | 407 Proxy Authentication Required |
| → | ACK |
| → | INVITE2 |
| ← | 180 Ringing1 |
| ← | 180 Ringing2 |
| ← | 200 OK (INVITE)2 |
| → | ACK |
| → | BYE1 |
| ← | 200 OK (BYE) |
Apply post test routine
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE2 | | ← | 180 Ringing1 | | ← | 180 Ringing2 | | ← | 200 OK (INVITE)2 | | → | ACK | | → | BYE1 | | ← | 200 OK (BYE) |
ISDN interworking | | | SETUP | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE2 | | ← | 180 Ringing1 | | ← | 180 Ringing2 | | ← | 200 OK (INVITE)2 | | → | ACK | | → | BYE1 | | ← | 200 OK (BYE) |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK (INVITE)2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | BYE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK (INVITE)2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | BYE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK (BYE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|--|---|-------------------------|--|--|---|-----|--|--------------------------------------------------------------|--|--|--|--|---|--------|--|--------------------------|--|--|--|-------|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|--|---|-------------------------|--|--|---|-----|--|--------------------------------------------------------------|--|--|--|--|---|--------|--|--------------------------------|--|--|--|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_040 | Reference
section 8.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Retry of INVITE request after 503 with Retry-After header received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the SUT Upon receiving a 503 (Service Unavailable) response to an initial INVITE request containing a Retry-After header does not automatically reattempt the request until after the period indicated by the Retry-After header contents. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | | |
| Dial number | ➔ | INVITE |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ⬅ | 503 Service Unavailable |
| ➔ | ACK |
| Wait for the time indicated in the Retry-After header |
| ➔ | INVITE |
| ISDN interworking |
| SETUP | ➔ | INVITE |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ⬅ | 503 Service Unavailable |
| ➔ | ACK |
| Wait for the time indicated in the Retry-After header |
| ➔ | INVITE |
| Apply post test routine |
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | | ⬅ | 503 Service Unavailable | | | ➔ | ACK | | Wait for the time indicated in the Retry-After header | | | | | ➔ | INVITE | | ISDN interworking | | | | SETUP | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | | ⬅ | 503 Service Unavailable | | | ➔ | ACK | | Wait for the time indicated in the Retry-After header | | | | | ➔ | INVITE | | Apply post test routine | | | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 503 Service Unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Wait for the time indicated in the Retry-After header | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 503 Service Unavailable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Wait for the time indicated in the Retry-After header | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|-------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_041 | Reference
subclause 5.3.1.5.1 of
[ETSI TS183 043] | Selection expression
PICS 5.2/19 |
+| Test purpose
Sending of a P-Preferred-Identity or From header field | | | |
+| Ensure that the SUT is able to include the default identity associated with the analogue termination where the off-hook event was detected a P-Preferred-Identity header field or the From header. | | | |
+| SIP header values | | | |
+| INVITE: | | | |
+| P-Preferred-Identity: {default user identity} | | | |
+| From: {default user identity} | | | |
+
+| Message flow | |
+|--------------------------------|-------------------------------------|
+| End device | Test equipment |
+| Off hook | |
+| Dial number | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE |
+| Apply post test routine | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_042 | Reference
subclause 6.3.2.4 of
[ETSI TS 183 043] | Selection expression |
+| Test purpose
Modifying SDP in early dialogue | | | |
+| Ensure that the SUT is able to receive an UPDATE request to modify the SDP in early dialogue. A 200 OK UPDATE with SDP answer is sent. | | | |
+| SIP header values
183/180
SDP answer 1
UPDATE
SDP offer 2
200 OK (UPDATE)
SDP answer 2 | | | |
+| Message flow | | | |
+| End device | | Test equipment | |
+| Off hook | | | |
+| Dial number | → | INVITE | |
+| | ← | 407 Proxy Authentication Required | |
+| | → | ACK | |
+| | → | INVITE | |
+| | ← | 183/180 | |
+| | ← | UPDATE | |
+| | → | 200 OK UPDATE | |
+| Apply post test routine | | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_043 | Reference
subclause 5.3.1.4 of
[ETSI TS183 043] | Selection expression
PICS 5.3/2 |
+| Test purpose
Charging procedure with AOC-S | | | |
+| Ensure that the SUT is able to receive charging information for a communication in the call setup phase. After sending the initial INVITE request, a 18x reliable provisional response is received containing a aoc-extended/ aoc-s XML element, a PRACK is sent. | | | |
+
+###### **SIP header values**
+
+###### **18x:**
+
+Require: 100rel
+
+Content-Type: application/vnd.etsi.aoc+xml
+
+```
+
+
+
+
+
+
+ 1
+ normal-charging
+
+ 1
+ ten-seconds
+
+
+
+
+
+
+
+```
+
+###### **Message flow**
+
+###### **End device**
+
+###### **Test equipment**
+
+Off hook
+
+Dial number
+
+→ INVITE
+ ← 407 Proxy Authentication Required
+ → ACK
+ → INVITE
+ ← 18x
+ → PRACK
+ ← 200 OK (PRACK)
+
+**Apply post test routine**
+
+| | | | |
+|----------------------------------------------------|------------|-------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_044 | Reference
subclause 5.3.1.4 of
[ETSI TS183 043] | Selection expression
PICS 5.3/2 |
+|----------------------------------------------------|------------|-------------------------------------------------------|------------------------------------|
+
+###### **Test purpose**
+
+*Charging procedure with AOC-D*
+
+Ensure that the SUT is able to receive charging information for a communication in the active call phase. After the communication is in the confirmed state, a NOTIFY is received containing a aoc-extended/ aoc-d XML element, a 200 OK (INFO) is sent.
+
+###### **SIP header values**
+
+INFO:
+
+Content-Type: application/vnd.etsi.aoc+xml
+
+```
+
+
+ subtotal
+
+
+ UNIT
+ 2
+
+
+ normal-charging
+ aoc-d >
+
+```
+
+###### **Message flow**
+
+**End device**
+
+**Test equipment**
+
+Off hook
+
+Dial number
+
+➔ INVITE
+
+⬅ 407 Proxy Authentication Required
+
+➔ ACK
+
+➔ INVITE
+
+Ringing tone
+
+⬅ 180 Ringing
+
+Conversation
+
+⬅ 200 OK (INVITE)
+
+➔ ACK
+
+Update of charging info
+
+⬅ INFO
+
+➔ 200 OK (INFO)
+
+**Apply post test routine**
+
+| | | | |
+|----------------------------------------------------|------------|-------------------------------------------------------|------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_045 | Reference
subclause 5.3.1.4 of
[ETSI TS183 043] | Selection expression
PICS 5.3/2 |
+|----------------------------------------------------|------------|-------------------------------------------------------|------------------------------------|
+
+###### **Test purpose**
+
+*Charging procedure with AOC-E*
+
+Ensure that the SUT is able to receive charging information after a communication is terminated. When a communication is terminated, a BYE or a 200 OK (BYE) is received containing a aoc-extended XML element.
+
+| | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------|-----------------------------------------------|--|---------------|--|-----------------------------------------|-------------------------|---------------|--|--------------------------------|-------------------------|
+| SIP header values
BYE/200 OK:
Content-Type: application/vnd.etsi.aoc+xml
<aoc-extended> < aoc-e > < recorded-charges> <recorded-currency-units> <currency-id>UNIT</currency-id> <currency-amount>2</currency-amount> </recorded-currency-units> </ recorded-charges> <billing-id> normal-charging </billing-id> </ aoc-e > </aoc-extended>
| | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| A communication is already established |
| CASE A | |
| Update of charging info in 200 OK (BYE) | → BYE ← 200 OK (BYE) |
| CASE B | |
| Update of charging info in BYE | ← BYE → 200 OK (BYE) |
| | End device | Test equipment | A communication is already established | | CASE A | | Update of charging info in 200 OK (BYE) | → BYE
← 200 OK (BYE) | CASE B | | Update of charging info in BYE | ← BYE
→ 200 OK (BYE) |
+| End device | Test equipment | | | | | | | | | | | | |
+| A communication is already established | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | |
+| Update of charging info in 200 OK (BYE) | → BYE
← 200 OK (BYE) | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | |
+| Update of charging info in BYE | ← BYE
→ 200 OK (BYE) | | | | | | | | | | | | |
+
+##### **7.2.2.1.2 Test purposes for POTS**
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_101 | Reference
subclause 4.9.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.1.1/2 and 5.3/4 |
+| Test purpose
Overlap dialling using the multiple-INVITE method
Ensure that the SUT sends an additional INVITE request if an 404 or 484 final response is received on the previous sent INVITE request and the user dials further digits. The INVITE request contains the previous sent digits and the current dialled digit. The From header and the Call-ID are the same as used in the initial INVITE request. | | | |
+
+| | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|
+| SIP header values
INVITE1
Request Line Dialled number1
From: [value initial invite]
Call-ID: [value initial invite]
INVITE2
Request Line Dialled number1 + dialled digit1
From: [value initial invite]
Call-ID: [value initial invite]
INVITE3
Request Line Dialled number1+ dialled digit1 + dialled digit2
From: [value initial invite]
Call-ID: [value initial invite] | |
+| Message flow | |
+| End device | Test equipment |
+| Off hook | |
+| Dial number1 | |
+| | ➔ INVITE1 |
+| | ⬅ 407 Proxy Authentication Required |
+| | ➔ ACK |
+| | ➔ INVITE1 |
+| | ⬅ 404/484 |
+| | ➔ ACK |
+| Dial digit1 | |
+| | ➔ INVITE2 |
+| | ⬅ 404/484 |
+| | ➔ ACK |
+| Dial digit2 | |
+| | ➔ INVITE3 |
+| Ringing tone | ⬅ 180 |
+| Apply post test routine | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_102 | Reference
subclause 4.9.2.1 of
[ETSI TS 124 229] | Selection expression
PICS 5.1.1/2 and 5.3/5 |
+| Test purpose
Overlap dialling using the in-dialogue method
Ensure that the SUT sends an additional INVITE request if an 404 or 484 final response is received on the previous sent INVITE request and the user dials further digits. The INVITE request contains the previous sent digits and the current dialled digit. The From header and the Call-ID are the same as used in the initial INVITE request.
Ensure that when a 183 without an SDP is received additional dialled digits are transferred in an INFO request. | | | |
+
+###### **SIP header values**
+
+INVITE1
+
+Request Line Dialled number1
+
+From: [value initial invite]
+
+Call-ID: [value initial invite]
+
+INVITE2
+
+Request Line Dialled number1 + dialled digit1
+
+From: [value initial invite]
+
+Call-ID: [value initial invite]
+
+INFO
+
+Request Line Dialled number1+ dialled digit1
+
+From: [value initial invite]
+
+Call-ID: [value initial invite]
+
+Content-Type: application/session-info
+
+Content-Disposition : signal ; handling=optional
+
+SubsequentDigit : [Dial digit2]
+
+###### **Message flow**
+
+**End device**
+
+**Test equipment**
+
+Off hook
+
+Dial number1
+
+→ INVITE1
+← 407 Proxy Authentication Required
+→ ACK
+→ INVITE1
+← 404/484
+→ ACK
+
+Dial digit1
+
+→ INVITE2
+← 183 Session Progress
+
+Dial digit2
+
+→ INFO
+← 200 OK INFO
+
+Ringing tone
+
+← 180
+
+**Apply post test routine**
+
+##### 7.2.2.1.3 Test purposes for ISDN
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_201 | Reference
subclause 5.3.1.5.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | |
+| Test purpose
Indication of support of the PSTN XML schema | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the SUT supports the PSTN XML schema, the initial INVITE request contains the application/vnd.etsi.pstn+xml tag in the Accept header. | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE:
Accept: application/vnd.etsi.pstn+xml | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| SETUP | ➔ | INVITE |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 100 Trying |
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|-------------------|---|------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_202 | Reference
subclause D.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | |
+| Test purpose
SETUP without called party number IE received | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of a SETUP message and the Information Transfer Capability value for the BC is set to 'speech' or 'audio 3 kBit/s' and no called party number Information Element is present, no INVITE request is sent. The AGCF/VGW sends a SETUP ACKNOWLEDGE message and a Progress Indicator IE is present the Progress description is set to 8. | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 100 Trying |
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 100 Trying |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_203 | Reference
subclause D.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|--|--|-------------------|--|--|-------|--|--|-------|--|--|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|---------|--|---|---------------|--|---|-----|-----------|-------|-------------|--|---|---------------|--|---|-----|-----------|-------|-------------|----------|---|-------------|
+| Test purpose
Overlap sending using the multiple INVITE method | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that an initial INVITE is sent after a called party number was received in a SETUP followed by several digits in INFO messages. All digits collected from the SETUP and INFO messages are present in the Request line of the INVITE request. The sending of the INVITE request depends on the configuration of the digit map.
Ensure that after sending of the initial INVITE the SUT is able to process a received 404 Not Found. The final response is not relayed to the DSS1 user equipment. An additional received INFO is sent in a new INVITE request. The Request URI of all additionally sent INVITE requests contain all collected digits received in the SETUP and INFO messages.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE1:
Request URI (digits INFO 1 to 3)
INVITE2:
Request URI (digits INFO 1 to 4)
INVITE3:
Request URI (digits INFO 1 to 5) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
SETUP: Called party number
INFO: Called party number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
|---|
| SETUP | | |
| SETUP ACKNOWLEDGE | | |
| INFO1 | | |
| INFO2 | | |
| INFO3 | ➔ | INVITE |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE1 |
| ⬅ | 404 Not Found |
| ➔ | ACK |
INFO4 | ➔ | INVITE2 |
| ⬅ | 404 Not Found |
| ➔ | ACK |
INFO5 | ➔ | INVITE3 |
| ALERTING | ⬅ | 180 Ringing |
| | | | End device | | Test equipment | SETUP | | | SETUP ACKNOWLEDGE | | | INFO1 | | | INFO2 | | | INFO3 | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE1 | | ⬅ | 404 Not Found | | ➔ | ACK |
INFO4 |
➔ |
INVITE2 | | ⬅ | 404 Not Found | | ➔ | ACK |
INFO5 |
➔ |
INVITE3 | ALERTING | ⬅ | 180 Ringing |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO3 | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 404 Not Found | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
INFO4 |
➔ |
INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 404 Not Found | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
INFO5 |
➔ |
INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_204 | Reference
subclause D.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|--|--|-------------------|--|--|-------|--|--|-------|--|--|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|---------|--|---|------------------------|--|---|-----|-----------|-------|-------------|--|---|------------------------|--|---|-----|-----------|-------|-------------|----------|---|-------------|
+| Test purpose
Overlap sending using the multiple INVITE method | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that an initial INVITE is sent after a called party number was received in a SETUP followed by several digits in INFO messages. All digits collected from the SETUP and INFO messages are present in the Request line of the INVITE request. The sending of the INVITE request depends on the configuration of the digit map.
Ensure that after sending of the initial INVITE the SUT is able to process a received 484 Address Incomplete. The final response is not relayed to the DSS1 user equipment. An additional received INFO is sent in a new INVITE request. The Request URI of all additionally sent INVITE requests contain all collected digits received in the SETUP and INFO messages.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE1:
Request URI (digits INFO 1 to 3)
INVITE2:
Request URI (digits INFO 1 to 4)
INVITE3:
Request URI (digits INFO 1 to 5) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
SETUP: Called party number
INFO: Called party number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| SETUP | | |
| SETUP ACKNOWLEDGE | | |
| INFO1 | | |
| INFO2 | | |
| INFO3 | → | INVITE |
| ← | 407 Proxy Authentication Required |
| → | ACK |
| → | INVITE1 |
| ← | 484 Address Incomplete |
| → | ACK |
INFO4 | → | INVITE2 |
| ← | 484 Address Incomplete |
| → | ACK |
INFO5 | → | INVITE3 |
| ALERTING | ← | 180 Ringing |
Apply post test routine
| | | | End device | | Test equipment | SETUP | | | SETUP ACKNOWLEDGE | | | INFO1 | | | INFO2 | | | INFO3 | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE1 | | ← | 484 Address Incomplete | | → | ACK |
INFO4 |
→ |
INVITE2 | | ← | 484 Address Incomplete | | → | ACK |
INFO5 |
→ |
INVITE3 | ALERTING | ← | 180 Ringing |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO3 | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 484 Address Incomplete | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
INFO4 |
→ |
INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 484 Address Incomplete | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
INFO5 |
→ |
INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|--|--|-------------------|--|--|--|--------------------|--|-------|-------------|--|-------|-------------|--|-------|-------------|--|--|----------------------|--|--|----------|--|--|-------------------------------------|--|--|-------|--|--|-----------|--|--|-----------|--|--|-------|--|-----------|---------------|--|--|-----------|--|--|-------|--|-----------|---------------|--|----------|---------------|--|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_205 | Reference
subclause D.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Sending of initial INVITE based on timeout Tinfo
Ensure that an initial INVITE is sent after a called party number was received in a SETUP followed by several digits in INFO messages. All digits collected from the SETUP and INFO messages are present in the Request line of the INVITE request. The INVITE is sent after the timeout of timer Tinfo
Ensure that after sending of the initial INVITE the SUT is able to process a received 404 Not Found or 484 Address Incomplete. The final response is not relayed to the DSS1 user equipment. An additional received INFO is sent in a new INVITE request. The Request URI of all additionally sent INVITE requests contain all collected digits received in the SETUP and INFO messages. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE1:
Request URI (digits INFO 1 to 3)
INVITE2:
Request URI (digits INFO 1 to 4)
INVITE3:
Request URI (digits INFO 1 to 5) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
SETUP: Called party number
INFO: Called party number | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | | |
| SETUP ACKNOWLEDGE | | |
| Start Tinfo | |
| INFO1 | Start Tinfo | |
| INFO2 | Start Tinfo | |
| INFO3 | Start Tinfo | |
| Timeout Tinfo | |
| → INVITE | |
| ← 407 Proxy Authentication Required | |
| → ACK | |
| → INVITE1 | |
| ← 404/484 | |
| → ACK | |
INFO4 | → INVITE2 | |
| ← 404/484 | |
| → ACK | |
INFO5 | → INVITE3 | |
| ALERTING | ← 180 Ringing | |
| Apply post test routine |
| | | | End device | | Test equipment | SETUP | | | SETUP ACKNOWLEDGE | | | | Start Tinfo | | INFO1 | Start Tinfo | | INFO2 | Start Tinfo | | INFO3 | Start Tinfo | | | Timeout Tinfo | | | → INVITE | | | ← 407 Proxy Authentication Required | | | → ACK | | | → INVITE1 | | | ← 404/484 | | | → ACK | |
INFO4 |
→ INVITE2 | | | ← 404/484 | | | → ACK | |
INFO5 |
→ INVITE3 | | ALERTING | ← 180 Ringing | | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Start Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO1 | Start Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO2 | Start Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INFO3 | Start Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Timeout Tinfo | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → INVITE1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 404/484 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
INFO4 |
→ INVITE2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 404/484 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
INFO5 |
→ INVITE3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_206 | Reference
subclause 5.1.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | |
+| Test purpose
INVITE is sent after receipt of "#" character in the called party number, XML sendingCompleteIndication is contained | | | | | | | | | | | | | | | | | | |
+| Ensure that after initiating the normal incoming call establishment procedures, determining the end of address signalling and selecting to route the call to the IMS domain, the originating SUT sends the initial INVITE.
The end of address is detemined by receipt of a "#" character Sending complete Information Element as a sending complete indication.
– The INVITE contains the XML sendingCompleteIndication element
| | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE:
| | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
SETUP: Called Party number contained the "#" character
or
Sending complete | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
Apply post test routine
| | | | | End device | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE |
+| | End device | Test equipment | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_207 | Reference
subclause 5.1.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | |
+| Test purpose
En-bloc sending is used, the complete called party number is contained in the called party number | | | | | | | | | | | | | | | | | | |
+| Ensure that if the SETUP message contains the complete called number information, the called party number information is included in the Called party number information element possibly completed by the Called party subaddress information element.
The SUT sends a CALL PROCEEDING message. This acknowledges the SETUP message and indicates that the call is being processed and that no further address information is expected.
| | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE: Request URI Called party number digits
To: Called party number digits; isub= Called paery subaddress; isub-encoding=nsap-ia5 | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
SETUP: Called party number: Complete number information
Called party subaddress | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
Apply post test routine
| | | | | End device | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE |
+| | End device | Test equipment | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|-------------------|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_208 | Reference
subclause 5.1.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
One bearer capability information element is received. Mapped into the XML BearerCapability element | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the whole bearer capability information element, as received in the SETUP message, shall be mapped to the PSTN XML bearer capability body in SIP. A bearer capability information element is received. The Information transfer capability value is indicated in Table 7.2.2.1.4-1. | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE:
PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>ITC_value<
< BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011< | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
SETUP:
bearer capability Information transfer capability = ITC_value | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
Apply post test routine
| | | | | End device | | Test equipment | SETUP | ➔ | INVITE | | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_209 | Reference
subclause 5.1.1.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
Two bearer capability information element are received. Mapped into two XML BearerCapability element | | | |
+| Ensure that if two bearer capability information elements are received and the information transfer capability of the first BC is set to speech or 3,1 kHz audio and the information transfer capability of the second BC is set to unrestricted digital information with tones and announcements, two XML BearerCapability elements are contained in the PSTN XML attachment. | | | |
+| - • The InformationTransferCabability of the first is set to '00000' or '10000'.
- • The InformationTransferCabability of the second is set to '10001'.
| | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------|-----------------------------------|-----------------------|-------|--|---|--------|-------------------|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|--------------------------------|--|--|--|
+| SIP header values
INVITE:
PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>00000<
or
InformationTransferCapability>10000<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011<
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCapability>10001<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5
Layer1Identification>01<
UserInfoLayer1Protocol>00011<
SDP: m line contains as the first codec CLEARMODE and as the second codec a G.711 codec | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | | ➔ | INVITE |
| SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required |
| | ➔ | ACK |
| | ➔ | INVITE |
| Apply post test routine |
| | End device | | Test equipment | SETUP | | ➔ | INVITE | SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | Apply post test routine | | | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.1.4-1 – Mapping of bearer capability to PSTN XML BearerCapability**
+
+| ITC_value | BC Information transfer capability | XML InformationTransferCabability |
+|-----------|------------------------------------|-----------------------------------|
+| ITC_VA_1 | Speech | '00000' |
+| ITC_VA_2 | 3,1 kHz audio | '10000' |
+| ITC_VA_3 | unrestricted digital information | '01000' |
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_210 | Reference
subclause 5.1.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | |
+| Test purpose
Mapping of Progress Indicator
Ensure that the Progress Indicator received in the SETUP is mapped into the PSTN XML ProgressIndicator value as indicated in Table 7.2.2.1.4-2. An additionally ProgressIndicator element is is contained and the ProgressDescription value is set to '0000110' | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE:
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000110<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription>PI_value< | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
SETUP:
Progress Indicator Coding standard ='00', Location ='0000', Progress description='0000yyyy' | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| Apply post test routine |
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.1.4-2 – Mapping of progress indicator information element to PSTN XML ProgressIndicator**
+
+| PI_value | DSS1 progress indicator value | XML ProgressIndicator
ProgressDescription |
+|----------|--------------------------------------------------------------------------------------------|----------------------------------------------|
+| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' |
+| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' |
+| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' |
+| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' |
+| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' |
+| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' |
+
+| | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|-------------------|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_211 | Reference
subclause 5.1.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
No Progress Indicator received
Ensure that if no progress indicator was received in the a ProgressIndicator element is is contained and the ProgressDescription value is set to '0000110' | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE:
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000110<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>0000<
ProgressOctet4
ProgressDescription>PI_value< | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
SETUP: | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | | ➔ | INVITE |
| SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required |
| | ➔ | ACK |
| | ➔ | INVITE |
Apply post test routine
| | | | | End device | | Test equipment | SETUP | | ➔ | INVITE | SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_212 | Reference
clause 5.1.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
Mapping of high layer compatibility information element
Ensure that the high layer compatibility information element received in the SETUP is mapped into the PSTN XML HighLayerCompatibility | | | |
+| SIP header values
INVITE:
PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value< | | | |
+
+| | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|
+| DSS1 parameter values
SETUP:
High layer compatibility Coding standard='00', Interpretation='100', High layer characteristics identification=HLC_value as indicated in Table 7.2.2.1.4-3 | |
+| Message flow | |
+| End device | Test equipment |
+| SETUP | → INVITE |
+| SETUP ACKNOWLEDGE | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE |
+| Apply post test routine | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_213 | Reference
subclause 5.3.1.5.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
Two high layer compatibility information elements received | | | |
+| Ensure that the first high layer compatibility information element received in the SETUP is mapped into the first PSTN XML HighLayerCompatibility and the second High layer compatibility information element received in the SETUP is mapped into the second PSTN XML HighLayerCompatibility | | | |
+| SIP header values
INVITE:
PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>0000001<
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value< | | | |
+| DSS1 Parameter values
SETUP:
First High layer compatibility Coding standard='00', Interpretation='100', High layer characteristics identification=Telephony
Second High layer compatibility Coding standard='00', Interpretation='100', High layer characteristics identification=HLC_value as indicated in Table 7.2.2.1.4-3 | | | |
+| Message flow | | | |
+| End device | | | Test equipment |
+| SETUP | | → | INVITE |
+| SETUP ACKNOWLEDGE | | ← | 407 Proxy Authentication Required |
+| | | → | ACK |
+| | | → | INVITE |
+| Apply post test routine | | | |
+
+**Table 7.2.2.1.4-3 – Mapping of high layer compatibility information element to PSTN XML HighLayerCharacteristic**
+
+| HLC_value | DSS1 High layer characteristics identification | XML HighLayerCharacteristic |
+|-----------|------------------------------------------------------------------------|-----------------------------|
+| HLC_VA_1 | Telephony | '0000001' |
+| HLC_VA_2 | Facsimile Group 2/3 | '0000100' |
+| HLC_VA_3 | Facsimile Group 4 Class I | '0100001' |
+| HLC_VA_4 | Facsimile service Group 4, Classes II ad III | '0100100' |
+| HLC_VA_5 | Syntax based Videotex | '0110010' |
+| HLC_VA_6 | International Videotex interworking via gateways or interworking units | '0110011' |
+| HLC_VA_7 | Telex service | '0110101' |
+| HLC_VA_8 | FTAM application | '1000010' |
+| HLC_VA_9 | Videotelephony | '1100000' |
+
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_214 | Reference
5.1.1.2.1, 5.1.1.2.1.1/
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------|------------------------------------------------|------------|--|----------------|--|-------|---|--------|--|-------------------|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|----------|---|-------------|--|
+| Test purpose
180 received, No PSTN XML body present, PI 1 is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of a 180 (Ringing) and a PSTN XML body is not present, an ALERTING message is sent to the calling user equipment that contains a Progress Indicator Information Element and the Progress description is set to value 1. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 parameter values
ALERTING; Progress Indicator value 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| SETUP | ➔ | INVITE | |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | |
| ➔ | ACK | |
| ➔ | INVITE | |
| ALERTING | ⬅ | 180 Ringing | |
Apply post test routine
| | | | End device | | Test equipment | | SETUP | ➔ | INVITE | | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | ALERTING | ⬅ | 180 Ringing | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_215 | Reference
subclauses 5.1.1.2.1 and
5.1.1.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
180 received, PSTN XML body present two XML PI set to value 7 and x an ALERTING is sent PI value x | | | |
+| Ensure that on receipt of a 180 (Ringing) a PSTN XML body is present contains two ProgressIndicator elements set to x and 7, an ALERTING is sent to the calling user equipment and a Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-4 | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------------------|-------------------|-----------------------|-------|--|----------|-------------------|--|-------------------------------------|--|--|-------|--|--|----------|----------|--|---------------|--|-------------------------|--|
+| SIP header values
180 (Ringing): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
ALERTING: Progress Indicator value x | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| SETUP | | → INVITE |
| SETUP ACKNOWLEDGE | | ← 407 Proxy Authentication Required |
| | → ACK |
| | → INVITE |
| ALERTING | | ← 180 Ringing |
| Apply post test routine |
| | | End device | Test equipment | SETUP | | → INVITE | SETUP ACKNOWLEDGE | | ← 407 Proxy Authentication Required | | | → ACK | | | → INVITE | ALERTING | | ← 180 Ringing | | Apply post test routine | |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | → INVITE | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | | ← 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | |
+| | | → INVITE | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | |
+| | Apply post test routine | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.1.4-4 – Mapping of progress indicator information element to PSTN XML ProgressIndicator**
+
+| PI_value | DSS1 progress indicator value | XML ProgressIndicator
ProgressDescription |
+|----------|--------------------------------------------------------------------------------------------|----------------------------------------------|
+| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' |
+| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' |
+| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' |
+| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' |
+| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' |
+| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' |
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|-------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_216 | Reference
subclauses 5.1.1.2.1 and
5.1.1.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | |
+| Test purpose
180 received, PSTN XML body present XML PI set to value 7
Ensure that on receipt of the first 180 (Ringing) and a PSTN XML body present the XML PI is set to value 7, an ALERTING message is sent to the calling user equipment does not contain a Progress Indicator Information Element. | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
180 (Ringing): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
ALERTING: No Progress Indicator present | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ALERTING | ⬅ | 180 Ringing |
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_217 | Reference
subclauses 5.1.1.2.1 and
5.1.1.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
Subsequent 180 received, No PSTN XML body present, PI 1 is sent.
Ensure that on receipt of a subsequent 180 (Ringing) and a PSTN XML body is not present, a PROGRESS message is sent to the calling user equipment that contains a Progress Indicator Information Element and the Progress description is set to value 1 if a PROGRESS message was sent before that contains Progress Indicator value 4. | | | |
+
+| SIP header values
180 (Ringing) 1: no XML body present
180 (Ringing) 2: XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
180 (Ringing) 3 no XML body present | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------|----------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|--------------|------------|---|--------------|------------|---|--------------|
+| DSS1 Parameter values
PROGRESS 1: Progress Indicator value 4
PROGRESS 2: Progress Indicator value 1 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➠ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➠ | ACK |
| ➠ | INVITE |
| ALERTING | ⬅ | 180 Ringing1 |
| PROGRESS 1 | ⬅ | 180 Ringing2 |
| PROGRESS 2 | ⬅ | 180 Ringing3 |
Apply post test routine
| End device | | Test equipment | SETUP | ➠ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➠ | ACK | | ➠ | INVITE | ALERTING | ⬅ | 180 Ringing1 | PROGRESS 1 | ⬅ | 180 Ringing2 | PROGRESS 2 | ⬅ | 180 Ringing3 |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | |
+| | ➠ | ACK | | | | | | | | | | | | | | | | | | | | | | |
+| | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | |
+| PROGRESS 1 | ⬅ | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | |
+| PROGRESS 2 | ⬅ | 180 Ringing3 | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_218 | Reference
subclause 5.1.1.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|--------------|----------|---|--------------|
+| Test purpose
Subsequent 180 received and the P-Early-Media header set to sendonly, a PROGRESS message is sent.
Ensure that on receipt of a subsequent 180 (Ringing) that contains a P-Early-Media header set to sendonly, the SUT the Progress Indicator Information Element is present in the sent PROGRESS message and the Progress description is set to value 8. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
180 (Ringing) 2: P-Early-Media: sendonly | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
PROGRESS: Progress Indicator value 8 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➠ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➠ | ACK |
| ➠ | INVITE |
| ALERTING | ⬅ | 180 Ringing1 |
| PROGRESS | ⬅ | 180 Ringing2 |
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➠ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➠ | ACK | | ➠ | INVITE | ALERTING | ⬅ | 180 Ringing1 | PROGRESS | ⬅ | 180 Ringing2 |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | |
+| | ➠ | ACK | | | | | | | | | | | | | | | | | | | | | | |
+| | ➠ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | |
+| PROGRESS | ⬅ | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_219 | Reference
subclauses 5.1.1.2.1 and
5.1.1.2.1.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|-------------------|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|----------|---|--------------|--|----------|---|--------------|--|
+| Test purpose
Subsequent 180 received, PSTN XML body present two XML PI set to value 7 and x a PROGRESS is sent PI value x included
Ensure that on receipt of a subsequent 180 (Ringing) a PSTN XML body is present, which contains two Progress Indicator elements set to x and 7, a PROGRESS message is sent to the calling user equipment. A Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-5 and a second Progress Indicator Information Element is present, the Progress description is set to the value 4 if a 180 (Ringing) was received before and no PSTN XML body was present. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
180 (Ringing) 1: no XML body present
180 (Ringing) 2: XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location
ProgressOctet4
ProgressDescription>PI_value<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
PROGRESS: Progress Indicator value x and a Progress Indicator value 4 Call has returned to the 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ALERTING | ⬅ | 180 Ringing1 |
| PROGRESS | ⬅ | 180 Ringing2 |
Apply post test routine
| | | | | End device | | Test equipment | SETUP | ➔ | INVITE | | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | ALERTING | ⬅ | 180 Ringing1 | | PROGRESS | ⬅ | 180 Ringing2 | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| PROGRESS | ⬅ | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.1.4-5 – Mapping of progress indicator information element to PSTN XML ProgressIndicator**
+
+| PI_value | DSS1 Progress Indicator value | XML ProgressIndicator ProgressDescription |
+|----------|--------------------------------------------------------------------------------------------|-------------------------------------------|
+| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' |
+| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' |
+| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' |
+| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' |
+| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' |
+| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' |
+
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_220 | Reference subclauses 5.1.1.2.1 and 5.1.1.2.1.1 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|--------------|----------|---|--------------|
+| Test purpose
180 received, PSTN XML body present XML PI set to value 7
Ensure that on receipt of a subsequent 180 (Ringing) and a PSTN XML body present the XML PI is set to value 7 and PROGRESS is sent toward the calling user equipment and a Progress Indicator Information Element is present the Progress description is set to the value 4 if a 180 (Ringing) was received without a PSTN XML body. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
180 (Ringing) 1: no XML body present
180 (Ringing) 2: XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
ALERTING: No Progress Indicator present
PROGRESS: Progress Indicator value 4 Call has returned to the 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ALERTING | ⬅ | 180 Ringing1 |
| PROGRESS | ⬅ | 180 Ringing2 |
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing1 | PROGRESS | ⬅ | 180 Ringing2 |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing1 | | | | | | | | | | | | | | | | | | | | | | |
+| PROGRESS | ⬅ | 180 Ringing2 | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_221 | Reference
subclause 5.1.1.2.1.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
Receiving of PSTN XML HighLayerCompatibility fallback information an ALERTING is sent | | | |
+| Ensure that on receipt of a 180 (Ringing) that contains a PSTN XML HighLayerCompatibility element that indicates fallback, the SUT sends an ALERTING message to the calling user equipment that does not contain a High Layer Compatibility Information Element. | | | |
+| SIP header values
180 (Ringing): XML body
PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value< | | | |
+| DSS1 parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz
audio
Second Bearer Capability Information transfer capability = Unrestricted
digital information with tones/announcements
ALERTING: | | | |
+| Message flow | | | |
+| | End device | | Test equipment |
+| SETUP | | ➔ | INVITE |
+| SETUP ACKNOWLEDGE | | ⬅ | 407 Proxy Authentication Required |
+| | | ➔ | ACK |
+| | | ➔ | INVITE |
+| ALERTING | | ⬅ | 180 Ringing |
+| Apply post test routine | | | |
+
+**Table 7.2.2.1.4-5 – Mapping of high layer compatibility information element to PSTN XML HighLayerCharacteristic**
+
+| HLC_value | DSS1 high layer characteristics identification | XML HighLayerCharacteristic |
+|-----------|------------------------------------------------------------------------|-----------------------------|
+| HLC_VA_1 | Telephony | '0000001' |
+| HLC_VA_2 | Facsimile Group 2/3 | '0000100' |
+| HLC_VA_3 | Facsimile Group 4 Class I | '0100001' |
+| HLC_VA_4 | Facsimile service Group 4, Classes II ad III | '0100100' |
+| HLC_VA_5 | Syntax based Videotex | '0110010' |
+| HLC_VA_6 | International Videotex interworking via gateways or interworking units | '0110011' |
+| HLC_VA_7 | Telex service | '0110101' |
+| HLC_VA_8 | FTAM application | '1000010' |
+| HLC_VA_9 | Videotelephony | '1100000' |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|-------------------|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|----------|---|-------------|--|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_222 | Reference
subclause 5.1.1.2.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Receiving of PSTN XML BearerCapability fallback information an ALERTING is sent.
Ensure that on receipt of a 180 (Ringing) that contains a PSTN XML BearerCapability element that indicates fallback, the SUT sends an ALERTING message to the calling user equipment that does not contain a Bearer Capability Information Element.
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
180 (Ringing): XML body
<?xml version="1.0" encoding="utf-8"?>
PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>00000<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5>
Layer1Identification>01<
UserInfoLayer1Protocol>00011<
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz
audio
Second Bearer Capability Information transfer capability = Unrestricted
digital information with tones/announcements
ALERTING:
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | → | INVITE |
| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required |
| → | ACK |
| → | INVITE |
| ALERTING | ← | 180 Ringing |
Apply post test routine
| | | | | End device | | Test equipment | SETUP | → | INVITE | | SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | | ALERTING | ← | 180 Ringing | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_223 | Reference
subclause 5.1.1.2.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
No fallback information received, CLEARMODE codec not the preferred codec in the 180
Ensure that on receipt of 180 (Ringing) and the CLEARMODE codes is not the first codec in the codec list, the SUT sends an ALERTING toward the calling user equipment and fallback is not indicated. No BC is sent in the ALERTING.
| | | |
+
+| | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------------------|
+| SIP header values | | |
+| DSS1 Parameter values | | |
+| SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
ALERTING: | | |
+| Message flow | | |
+| End device | | Test equipment |
+| SETUP | → | INVITE |
+| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE |
+| ALERTING | ← | 180 Ringing |
+| Apply post test routine | | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_224 | Reference
subclause 5.1.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose | | | |
+| Receipt of first 183 with P-Early-Media header CALL PROCEEDING is sent | | | |
+| Ensure that on receipt of the first 183 (Session Progress) with P-Early-Media header, the SUT does not send a local ringing tone to the calling user. The early media is passed through. A CALL PROCEEDING message is sent to the calling user contains a Progress Indicator Information Element and the Progress description is set to value 8. | | | |
+| SIP header values | | | |
+| 183 (Session Progress): P-Early-Media: sendonly, SDP | | | |
+| DSS1 Parameter values | | | |
+| CALL PROCEEDING: Progress Indicator value 8 | | | |
+| Message flow | | | |
+| End device | | | Test equipment |
+| SETUP | | → | INVITE |
+| SETUP ACKNOWLEDGE | | ← | 407 Proxy Authentication Required |
+| | | → | ACK |
+| | | → | INVITE |
+| CALL PROCEEDING | | ← | 183 (Session Progress) |
+| Apply post test routine | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|-------------------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_225 | Reference
subclause 5.1.1.2.2 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.2/16 |
+| Test purpose | | | |
+| Receipt of 183 with P-Early-Media header PROGRESS is sent | | | |
+| Ensure that on receipt of a 183 (Session Progress) with P-Early-Media header, the SUT does not send a local ringing tone to the calling user. The early media is passed through. A PROGRESS message is sent to the calling user contains a Progress Indicator Information Element and the Progress description is set to value 8. | | | |
+| SIP header values | | | |
+| 183 (Session Progress): P-Early-Media: sendonly, SDP | | | |
+
+| | | |
+|--------------------------------------|---|-----------------------------------|
+| DSS1 Parameter values | | |
+| PROGRESS: Progress Indicator value 8 | | |
+| Message flow | | |
+| End device | | Test equipment |
+| SETUP | ➔ | INVITE |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
+| | ➔ | ACK |
+| | ➔ | INVITE |
+| ALERTING | ⬅ | 180 (Ringing) |
+| PROGRESS | ⬅ | 183 (Session Progress) |
+| Apply post test routine | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_226 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose | | | |
+| 183 received, PSTN XML body present two XML PI set to value 7 and x CALL PROCEEDING is sent PI value x | | | |
+| Ensure that on receipt of a 183 (Session Progress), a PSTN XML body is present that contains two ProgressIndicator elements set to x and 7, a CALL PROCEEDING is sent to the calling user equipment and a Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-6 | | | |
+| SIP header values | | | |
+| 180 (Ringing): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | |
+| DSS1 Parameter values | | | |
+| CALL PROCEEDING: Progress Indicator value x | | | |
+| Message flow | | | |
+| End device | | | Test equipment |
+| SETUP | ➔ | | INVITE |
+| SETUP ACKNOWLEDGE | ⬅ | | 407 Proxy Authentication Required |
+| | ➔ | | ACK |
+| | ➔ | | INVITE |
+| CALL PROCEEDING | ⬅ | | 183 (Session Progress) |
+| Apply post test routine | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--|--------|-------------------|---|--|-----------------------------------|--|---|--|-----|--|---|--|--------|-----------------|---|--|------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_227 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
183 received, PSTN XML body present XML PI set to value 7 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of a subsequent 183 (Session Progress) and a PSTN XML body is present, the XML PI is set to value 7 a CALL PROCEEDING is sent toward the calling user equipment, and a Progress Indicator Information Element is present. The Progress description is set to the value 4 if a 180 (Ringing) was received without a PSTN XML body.
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
180 (Ringing): XML body <?xml version="1.0" encoding="utf-8"?> PSTN ProgressIndicator ProgressOctet3 CodingStandard>00< Location>yyyy< ProgressOctet4 ProgressDescription>0000111<
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
CALL PROCEEDING: Progress Indicator not present | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | | 407 Proxy Authentication Required |
| ➔ | | ACK |
| ➔ | | INVITE |
| CALL PROCEEDING | ⬅ | | 183 (Session Progress) |
Apply post test routine
| | | | | End device | | Test equipment | SETUP | ➔ | | INVITE | SETUP ACKNOWLEDGE | ⬅ | | 407 Proxy Authentication Required | | ➔ | | ACK | | ➔ | | INVITE | CALL PROCEEDING | ⬅ | | 183 (Session Progress) |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | | INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | | ACK | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | | INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+| CALL PROCEEDING | ⬅ | | 183 (Session Progress) | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|-------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_228 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.2/16 |
+| Test purpose
183 received and the P-Early-Media header set to sendonly, a PROGRESS message is sent. | | | |
+| Ensure that on receipt of a 183 (Session Progress) that contains a P-Early-Media header set to sendonly, the SUT the Progress Indicator Information Element is present in the sent PROGRESS message and the Progress description is set to value 8.
| | | |
+| SIP header values
183 (Session Progress): P-Early-Media: sendonly | | | |
+| DSS1 Parameter values
ALERTING: No Progress Indicator present
PROGRESS: Progress Indicator value 8 | | | |
+
+| Message flow | | |
+|--------------------------------|---|-----------------------------------|
+| End device | | Test equipment |
+| SETUP | ➔ | INVITE |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
+| | ➔ | ACK |
+| | ➔ | INVITE |
+| ALERTING | ⬅ | 180 Ringing1 |
+| PROGRESS | ⬅ | 183 Session Progress |
+| Apply post test routine | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an_early_dialogue | TP_201_229 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
183 received, PSTN XML body present two XML PI set to value 7 and x a PROGRESS is sent PI value x Ensure that on receipt of a 183 (Session Progress) that contains a P-Early-Media header set to sendonly, in the SUT the Progress Indicator Information Element is present in the sent PROGRESS message and the Progress description is set to value 8.
| | | |
+| SIP header values
180 (Ringing):
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
183 (Session Progress): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | |
+| DSS1 Parameter values
ALERTING: No Progress Indicator present
PROGRESS: Progress Indicator value 8 | | | |
+| Comments
The Location value is don't care. The order of the received ProgressIndicator elements is accidental | | | |
+
+| Message flow | | |
+|-------------------------|---|-----------------------------------|
+| End device | | Test equipment |
+| SETUP | → | INVITE |
+| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE |
+| ALERTING | ← | 180 Ringing1 |
+| PROGRESS | ← | 183 Session Progress |
+| Apply post test routine | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_an
_early_dialogue | TP_201_230 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
183 received, PSTN XML body present two XML PI set to value 7 and x a PROGRESS is sent PI value x | | | |
+| Ensure that on receipt of a 183 (Session Progress), a PSTN XML body is present, which contains two ProgressIndicator elements set to x and 7, a PROGRESS is sent to the calling user equipment and a Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-6. In the previous 180 (Ringing) was a PSTN XML body. | | | |
+| SIP header values
180 (Ringing):
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
183 (Session Progress): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | |
+| DSSI Parameter values
PROGRESS: Progress Indicator value x | | | |
+| Comments
The Location value is don't care. The order of the received ProgressIndicator elements is accidental | | | |
+
+| Message flow | | |
+|--------------------------------|---|-----------------------------------|
+| End device | | Test equipment |
+| SETUP | ➔ | INVITE |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
+| | ➔ | ACK |
+| | ➔ | INVITE |
+| ALERTING | ⬅ | 180 Ringing |
+| PROGRESS | ⬅ | 183 Session Progress |
+| Apply post test routine | | |
+
+| TSS
Orig_Establishment_of_a
n_early_dialogue | TP_201_231 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 AND 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|-------------|----------|---|----------------------|--------------------------------|--|--|
+| Test purpose
183 received, PSTN XML body present two XML PI set to value 7 and x a PROGRESS is sent PI value x and value 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of a 183 (Session Progress) a PSTN XML body is present that contains two ProgressIndicator elements set to x and 7, a PROGRESS is sent to the calling user equipment and a Progress Indicator Information Element is present, the Progress description is set to the value PI_VA as indicated in Table 7.2.2.1.4-6 and in addition a second Progress Indicator Information Element is present, the Progress description is set to the value 4. In the previous 180 (Ringing) there was no PSTN XML body. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
180 (Ringing):
183 (Session Progress): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
PROGRESS: Progress Indicator value x and 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments
The Location value is don't care. The order of the received ProgressIndicator elements is accidental | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ALERTING | ⬅ | 180 Ringing |
| PROGRESS | ⬅ | 183 Session Progress |
| Apply post test routine |
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing | PROGRESS | ⬅ | 183 Session Progress | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+| PROGRESS | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|-------------|----------|---|----------------------|
+| TSS | TP_201_232 | Reference
subclause 5.1.1.2.2.1 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
183 received, PSTN XML body present XML PI set to value 7 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of the 183 (Session Progress) and if a PSTN XML body is present and the XML PI is set to value 7, a PROGRESS message is sent to the calling user equipment. A Progress Indicator Information Element is present, the Progress description is set to the value 4. | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
183 (Session Progress):
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
PROGRESS: Progress Indicator value x and 4 | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ALERTING | ⬅ | 180 Ringing |
| PROGRESS | ⬅ | 183 Session Progress |
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 Ringing | PROGRESS | ⬅ | 183 Session Progress |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | |
+| PROGRESS | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.1.4-6 – Mapping of progress indicator information element to PSTN XML ProgressIndicator**
+
+| PI_value | DSS1 Progress Indicator value | XML ProgressIndicator
ProgressDescription |
+|----------|--------------------------------------------------------------------------------------------|----------------------------------------------|
+| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' |
+| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' |
+| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' |
+| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' |
+| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' |
+| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' |
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|-----------------|---|----------------------|
+| TSS | TP_201_233 | Reference
clause 5.1.1.2.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | |
+| Test purpose
Receiving of PSTN XML BearerCapability fallback information in a 183 a CALL PROCEEDING is sent. | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of a 183 (Session Progress) that contains a PSTN XML BearerCapability element that indicates fallback, the SUT sends a CALL PROCEEDING message to the calling user equipment that does not contain a Bearer Capability Information Element. | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
183 (Session Progress):
00
00000
00
10000
01
00011
| | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CALL PROCEEDING | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| CALL PROCEEDING | ← | 183 Session Progress |
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | CALL PROCEEDING | ← | 183 Session Progress |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | |
+| CALL PROCEEDING | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------|------------------------------------------------|
+| TSS | TP_201_234 | Reference
subclause 5.3.1.5.3 of
[ETSI TS 183 043] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
Receiving of PSTN XML BearerCapability fallback information in a 183 a PROGRESS is sent. | | | |
+| Ensure that on receipt of a 183 (Session Progress) that contains a PSTN XML BearerCapability element that indicates fallback, the SUT sends a PROGRESS message to the calling user equipment that does not contain a Bearer Capability Information Element. | | | |
+
+| SIP header values
183 (Session Progress):
<?xml version="1.0" encoding="utf-8"?>
<BearerCapability>
<BCoctet3>
<CodingStandard>00</CodingStandard>
<InformationTransferCabability>00000</InformationTransferCabability>
</BCoctet3>
<BCoctet4>
<TransferMode>00</TransferMode>
<InformationTransferRate>10000</InformationTransferRate>
</BCoctet4>
<BCoctet5>
<Layer1Identification>01</Layer1Identification>
<UserInfoLayer1Protocol>00011</UserInfoLayer1Protocol>
</BCoctet5>
</BearerCapability>
| | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|----------------------|
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
PROGRESS:
| | | | | | | | | | | | | | | | | | | |
+| Message flow
| | End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| PROGRESS | ⬅ | 183 Session Progress |
Apply post test routine
| End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | PROGRESS | ⬅ | 183 Session Progress |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | |
+| PROGRESS | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------|------------------------------------------------|
+| TSS | TP_201_235 | Reference
subclause 5.1.1.2.2.3 of [ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
Receiving of PSTN XML HighLayerCompatibility fallback information a CALL PROCEEDING is sent.
Ensure that on receipt of a 183 (Session Progress) that contains a PSTN XML HighLayerCompatibility element according to Table 7.2.2.1.4-5 and a ProgressIndicator value set to 5 that indicates fallback, the SUT sends a CALL PROCEEDING message to the calling user equipment that does not contain a High Layer Compatibility Information Element.
| | | |
+
+| | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------------------------|-------------------|--|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|-----------------|---|----------------------|
+| SIP header values
183 (Session Progress): PSTN XML MIME body
PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000101< | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CALL PROCEEDING: | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| SETUP | ➔ | INVITE |
| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| CALL PROCEEDING | ⬅ | 183 Session Progress |
Apply post test routine
| | | End device | | Test equipment | SETUP | ➔ | INVITE | SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | CALL PROCEEDING | ⬅ | 183 Session Progress |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | |
+| CALL PROCEEDING | ⬅ | 183 Session Progress | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|
+| TSS | TP_201_236 | Reference
subclause 5.1.1.2.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
Receiving of PSTN XML HighLayerCompatibility fallback information a PROGRESS is sent.
Ensure that on receipt of a 183 (Session Progress) that contains a PSTN XML HighLayerCompatibility element according to Table 7.2.2.1.4-5 and a ProgressIndicator value set to 5 that indicates fallback, the SUT sends a PROGRESS message to the calling user equipment that does not contain a High Layer Compatibility Information Element. | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|-----------------------|-------|---|--------|-------------------|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|---------------|-----------|---|----------------------|
+| SIP header values
183 (Session Progress): PSTN XML MIME body
PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_value<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000101< | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
PROGRESS: | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | → | INVITE |
| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required |
| → | ACK |
| → | INVITE |
| ALERTING | ← | 180 (Ringing) |
| PROGRESS: | ← | 183 Session Progress |
Apply post test routine
| End device | | Test equipment | SETUP | → | INVITE | SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | ALERTING | ← | 180 (Ringing) | PROGRESS: | ← | 183 Session Progress |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | 180 (Ringing) | | | | | | | | | | | | | | | | | | | |
+| PROGRESS: | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|------------------------------------------------|
+| TSS | TP_201_237 | Reference
subclause 5.1.1.2.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
No fallback information received, CLEARMODE codec not the preferred codec in the 183. | | | |
+| Ensure that on receipt of 183 (Session Progress) and the CLEARMODE codes is not the first codec in the codec list, the SUT sends a CALL PROCEEDING toward the calling user equipment and fallback is not indicated. No BC is sent in the CALL PROCEEDING | | | |
+| SIP header values | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CALL PROCEEDING | | | |
+
+| Message flow | | |
+|--------------------------------|---|-----------------------------------|
+| End device | | Test equipment |
+| SETUP | → | INVITE |
+| SETUP ACKNOWLEDGE | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE |
+| CALL PROCEEDING | ← | 183 Session Progress |
+| Apply post test routine | | |
+
+| TSS | TP_201_238 | Reference
subclause 5.1.1.2.2.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|------------------------------------------------|
+| Test purpose
No fallback information received, CLEARMODE codec not the preferred codec in the 183 | | | |
+| Ensure that on receipt of 183 (Session Progress) and the CLEARMODE codes is not the first codec in the codec list, the SUT sends a PROGRESS toward the calling user equipment and fallback is not indicated. No BC is sent in the PROGRESS | | | |
+| SIP header values
183 (Session Progress): CLEARMODE not the first codec | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
PROGRESS | | | |
+| Message flow | | | |
+| | End device | | Test equipment |
+| SETUP | → | | INVITE |
+| SETUP ACKNOWLEDGE | ← | | 407 Proxy Authentication Required |
+| | → | | ACK |
+| | → | | INVITE |
+| ALERTING | ← | | 180 (Ringing) |
+| PROGRESS | ← | | 183 Session Progress |
+| Apply post test routine | | | |
+
+#### 7.2.2.2 Establishment of a confirmed dialogue
+
+##### 7.2.2.2.1 SIP basic procedures
+
+| TSS
Orig_Establishment_of_a_
confirmed_dialogue | TP_202_001 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------------------------------------------------------------------------|----------------------|------------|----------------|--------------------------|--|----------|--|-------------|----------|--|-----------------|--|-------|--------------------------|--|---------------|--|-------|----------|---------|-----------------|--|-------|---------------|--|-------|----------|---------|-----------------|---------------------|-------|
+| Test purpose
200 OK received, an ACK is sent
Ensure that when an early dialogue is not established that on receipt of a Success (200 OK) response an ACK request is sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| Interworking POTS |
| Off hook | |
| Dial number | → INVITE |
| ← 200 OK INVITE |
| → ACK |
| ISDN interworking |
| CASE A |
| SETUP | → INVITE |
| CONNECT | ← 200 OK INVITE |
| → ACK |
| CASE B |
| SETUP | → INVITE |
| CONNECT | ← 200 OK INVITE |
| CONNECT ACKNOWLEDGE | → ACK |
Apply post test routine
| | | | End device | Test equipment | Interworking POTS | | Off hook | | Dial number | → INVITE | | ← 200 OK INVITE | | → ACK | ISDN interworking | | CASE A | | SETUP | → INVITE | CONNECT | ← 200 OK INVITE | | → ACK | CASE B | | SETUP | → INVITE | CONNECT | ← 200 OK INVITE | CONNECT ACKNOWLEDGE | → ACK |
+| End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT ACKNOWLEDGE | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a_
_confirmed_dialogue | TP_202_002 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
200 OK received in the Proceeding state an ACK is sent
Ensure that when the client transaction in the Proceeding state that on receipt of a Success (200 OK) response an ACK request is sent. | | | |
+| SIP header values | | | |
+
+| Message flow | |
+|--------------------------------|------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 100 Trying
← 200 OK INVITE
→ ACK |
+| ISDN interworking | |
+| CASE A | |
+| SETUP | → INVITE |
+| SETUP ACKNOWLEDGE | ← 100 Trying |
+| CONNECT | ← 200 OK INVITE |
+| | → ACK |
+| CASE B | |
+| SETUP | → INVITE |
+| SETUP ACKNOWLEDGE | ← 100 Trying |
+| CONNECT | ← 200 OK INVITE |
+| CONNECT ACKNOWLEDGE | → ACK |
+| Apply post test routine | |
+
+| | | | |
+|-------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_003 | Reference
sections 12.2.1.1, 13.2.2.4, and 5
Figure 17.1.1.3 of
[IETF RFC 3261] | Selection expression |
+|-------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
200 OK received in an early dialogue an ACK is sent
Ensure that when an early dialogue is established that on receipt of a Success (200 OK) response an ACK request is sent. |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| |
+|--------------------------|
+| SIP header values |
+|--------------------------|
+
+| Message flow | |
+|--------------------------|-------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK |
+| ISDN interworking | |
+| CASE A | |
+| SETUP | → INVITE |
+| ALERTING | ← 180 Ringing |
+| CONNECT | ← 200 OK INVITE |
+| | → ACK |
+
+| | |
+|--------------------------------|---------------------|
+| CASE B | |
+| SETUP | ➔ INVITE |
+| ALERTING | ← 180 Ringing |
+| CONNECT | ← 200 OK INVITE |
+| CONNECT ACKNOWLEDGE | ➔ ACK |
+| Apply post test routine | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------------|----------------------|-------------------|-----------------------|--------------------------|--|----------|--|-------------|--------------|--|------------------|--|---------------------|--------------------------|--|-------|--------------|-------------------|------------------|---------|---------------------|--------------------------------|--|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_004 | Reference
section 8.1.3.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
200 OK containing two Via header discarded | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that when the client transaction is in the Proceeding state that on receipt of a Success (200 OK) response with more than one Via header value no ACK request is sent, discards the response. | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK INVITE
Via:SIP 2.0 ;branch=
Via:SIP 2.0 ;branch= | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | Test equipment |
| Interworking POTS |
| Off hook | |
| Dial number | ➔ INVITE |
| ← 100 Trying |
| ← 200 OK INVITE |
| ISDN interworking |
| SETUP | ➔ INVITE |
| SETUP ACKNOWLEDGE | ← 100 Trying |
| CONNECT | ← 200 OK INVITE |
| Apply post test routine |
| | | | End device | Test equipment | Interworking POTS | | Off hook | | Dial number | ➔ INVITE | | ← 100 Trying | | ← 200 OK INVITE | ISDN interworking | | SETUP | ➔ INVITE | SETUP ACKNOWLEDGE | ← 100 Trying | CONNECT | ← 200 OK INVITE | Apply post test routine | |
+| End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP ACKNOWLEDGE | ← 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_005 | Reference
section 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
ACK is sent with the same CSeq as in the initial INVITE | | | |
+| Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response an ACK request is sent with the same CSeq sequence number as in the original INVITE request and the CSeq method field value set to "ACK". | | | |
+| SIP header values
INVITE 1
CSeq: INVITE
ACK 1
CSeq: ACK | | | |
+
+| Message flow | | |
+|--------------------------------|------------|----------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE 1 |
+| | ← | 200 OK INVITE |
+| | → | ACK 1 |
+| ISDN interworking | | |
+| CASE A | | |
+| SETUP | → | INVITE 1 |
+| CONNECT | ← | 200 OK INVITE |
+| | → | ACK 1 |
+| CASE B | | |
+| SETUP | → | INVITE 1 |
+| CONNECT | ← | 200 OK INVITE |
+| CONNECT ACKNOWLEDGE | → | ACK 1 |
+| Apply post test routine | | |
+
+| | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|--|--|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_006 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression | | |
+| Test purpose | | | | | |
+| ACK is sent with the same To header filed as received in the 200 OK | | | | | |
+| Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response an ACK request is sent with the To header set to the same value as in the received final response. | | | | | |
+| SIP header values | | | | | |
+| 200 OK INVITE
To: ;tag= | | | | | |
+| ACK
To: ;tag= | | | | | |
+| Message flow | | | | | |
+| | End device | Test equipment | | | |
+| Interworking POTS | | | | | |
+| Off hook | | | | | |
+| Dial number | → | INVITE | | | |
+| | ← | 200 OK INVITE | | | |
+| | → | ACK 1 | | | |
+| ISDN interworking | | | | | |
+| CASE A | | | | | |
+| SETUP | → | INVITE | | | |
+| CONNECT | ← | 200 OK INVITE | | | |
+| | → | ACK 1 | | | |
+
+| | |
+|--------------------------------|-----------------|
+| CASE B | |
+| SETUP | ➔ INVITE |
+| CONNECT | ← 200 OK INVITE |
+| CONNECT ACKNOWLEDGE | ➔ ACK 1 |
+| Apply post test routine | |
+
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_007 | Reference
section 12.2.1.1, 13.2.2.4,
Figure 5 and 17.1.1.3 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|---------------|--|---|-----------------|--|---|-------|------------------------------|--|--|---------------|--|--|-------|---|--------|----------|---|---------------|---------|---|-----------------|--|---|-------|-------------------|--|--|-------|---|--------|----------|---|---------------|---------|---|-----------------|---------------------|---|-------|--------------------------------|--|--|
+| Test purpose
ACK is sent with the same To header filed as received in the 180
Ensure that when the client transaction is in the Proceeding state that on receipt of a Success (200 OK) response an ACK request is sent with the To header set to the same value as in the received provisional response.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK INVITE
To: <any URI>;tag=<any 200 OK tag value>
ACK
To: <any URI>;tag=<any 200 OK tag value>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ← | 180 Ringing 1 |
| ← | 200 OK INVITE 1 |
| ➔ | ACK 1 |
ISDN interworking |
| CASE A |
| SETUP | ➔ | INVITE |
| ALERTING | ← | 180 Ringing 1 |
| CONNECT | ← | 200 OK INVITE 1 |
| ➔ | ACK 1 |
CASE B |
| SETUP | ➔ | INVITE |
| ALERTING | ← | 180 Ringing 1 |
| CONNECT | ← | 200 OK INVITE 1 |
| CONNECT ACKNOWLEDGE | ➔ | ACK 1 |
| Apply post test routine |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ← | 180 Ringing 1 | | ← | 200 OK INVITE 1 | | ➔ | ACK 1 |
ISDN interworking | | | CASE A | | | SETUP | ➔ | INVITE | ALERTING | ← | 180 Ringing 1 | CONNECT | ← | 200 OK INVITE 1 | | ➔ | ACK 1 |
CASE B | | | SETUP | ➔ | INVITE | ALERTING | ← | 180 Ringing 1 | CONNECT | ← | 200 OK INVITE 1 | CONNECT ACKNOWLEDGE | ➔ | ACK 1 | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 180 Ringing 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | 180 Ringing 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ← | 200 OK INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | 180 Ringing 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ← | 200 OK INVITE 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT ACKNOWLEDGE | ➔ | ACK 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_008 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
ACK is sent without a To tag
Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response including a To header without tag an ACK request is sent with a To header without tag. | | | |
+
+
+
+| | |
+|--------------------------|--|
+| SIP header values | |
+| 200 OK INVITE | |
+| To: | |
+| ACK | |
+| To: | |
+
+
+
+| Message flow | |
+|--------------------------------|-----------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE |
+| | ← 200 OK INVITE 1 |
+| | → ACK 1 |
+| ISDN interworking | |
+| CASE A | |
+| SETUP | → INVITE |
+| CONNECT | ← 200 OK INVITE 1 |
+| | → ACK 1 |
+| CASE B | |
+| SETUP | → INVITE |
+| CONNECT | ← 200 OK INVITE 1 |
+| CONNECT ACKNOWLEDGE | → ACK 1 |
+| Apply post test routine | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_009 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.2 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
ACK is sent for each received 200 OK
Ensure that when the client transaction is in the Calling state that on receipt of Success (200 OK) responses differing only on the tag in the To header, an ACK request is sent with a To header identical to the one received for each received Success (200 OK) responses. | | | |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| SIP header values
200 OK INVITE 1
To: ;tag=
ACK 1
To: ;tag=
200 OK INVITE 2
To: ;tag=
ACK 2
To: ;tag= | |
+| Message flow | |
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | → INVITE |
+| Dial number | ← 200 OK INVITE 1 |
+| | → ACK 1 |
+| | ← 200 OK INVITE 2 |
+| | → ACK 2 |
+| ISDN interworking | |
+| CASE A | |
+| SETUP | → INVITE |
+| CONNECT | ← 200 OK INVITE 1 |
+| | → ACK 1 |
+| | ← 200 OK INVITE 2 |
+| | → ACK 2 |
+| CASE B | |
+| SETUP | → INVITE |
+| CONNECT | ← 200 OK INVITE 1 |
+| CONNECT ACKNOWLEDGE | → ACK 1 |
+| | ← 200 OK INVITE 2 |
+| | → ACK 2 |
+| Apply post test routine | |
+
+| | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_010 | Reference
section 12.2.1.1, 13.2.2.4,
Figure 5 and 17.1.1.3 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
ACK is sent with the same Session identifier as in the sent INVITE
Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response an ACK request is sent with the same Call-ID and From headers as in the original INVITE request. | | | |
+
+| | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|
+| SIP header values
INVITE 1
Call-ID:
From: ;tag=
ACK 1
Call-ID:
From: ;tag= | |
+| Message flow | |
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE 1
← 200 OK INVITE
→ ACK 1 |
+| ISDN interworking | |
+| CASE A | |
+| SETUP | → INVITE 1 |
+| CONNECT | ← 200 OK INVITE
→ ACK 1 |
+| CASE B | |
+| SETUP | → INVITE 1 |
+| CONNECT | ← 200 OK INVITE |
+| CONNECT ACKNOWLEDGE | → ACK 1 |
+| Apply post test routine | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_011 | Reference
sections 12.2.1.1, 13.2.2.4,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
ACK is sent to the address indicated in the 200 OK Contact header | | | |
+| Ensure, when the client transaction is in the Calling state , that on receipt of a Success (200 OK) response with no Record-Route header set, an ACK request is sent with the Request-URI set to the Contact URI included in the received final response and with no Route header set. | | | |
+| SIP header values
200 OK
Contact:
ACK
ACK sip: SIP 2.0 | | | |
+
+| Message flow | |
+|--------------------------------|------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 200 OK INVITE 1
→ ACK 1 |
+| ISDN interworking | |
+| CASE A | |
+| SETUP | → INVITE |
+| CONNECT | ← 200 OK INVITE 1
→ ACK 1 |
+| CASE B | |
+| SETUP | → INVITE |
+| CONNECT | ← 200 OK INVITE 1 |
+| CONNECT ACKNOWLEDGE | → ACK 1 |
+| Apply post test routine | |
+
+| | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_012 | Reference
sections 12.2.1.1, 13.2.2.4 and
Figure 5 of [IETF RFC 3261] | Selection expression |
+| Test purpose | | | |
+| ACK is sent to the address indicated in the Record-Route header with 'lr' parameter | | | |
+| Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response with a Record-Route header set to a list in which the last element contains lr parameter, an ACK request is sent with the Request-URI set to the Contact URI and a Route header set to the list in a reverse order of the Record-Route included in the received final response. | | | |
+| SIP header values | | | |
+| 200 OK 1
Record-Route: ,
Contact: | | | |
+| ACK 1
ACK sip: SIP 2.0
Route: , | | | |
+| Message flow | | | |
+| End device | | Test equipment | |
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | → INVITE
← 200 OK INVITE
→ ACK 1 | | |
+| ISDN interworking | | | |
+
+| | |
+|--------------------------------|-------------------|
+| CASE A | |
+| SETUP | ➔ INVITE |
+| CONNECT | ← 200 OK INVITE 1 |
+| | ➔ ACK 1 |
+| CASE B | |
+| SETUP | ➔ INVITE |
+| CONNECT | ← 200 OK INVITE 1 |
+| CONNECT ACKNOWLEDGE | ➔ ACK 1 |
+| Apply post test routine | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_013 | Reference
section 12.2.1.1, 13.2.2.4,
Figure 5 and 17.1.1.3 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
ACK is sent to the address indicated in the Record-Route header without 'lr' parameter | | | |
+| Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response with a Record-Route header set to a list in which the last element does not contain lr parameter, an ACK request is sent with the Request-URI set to this element and a Route header set to the remainder list in a reverse order of the received Record-Route appended with the received Contact URI. | | | |
+| SIP header values
200 OK
Record-Route: ,
Contact:
ACK
ACK sip: SIP 2.0
Route: , | | | |
+| Message flow | | | |
+| End device | | Test equipment | |
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | | | |
+| | ➔ | INVITE | |
+| | ← | 200 OK INVITE 1 | |
+| | ➔ | ACK 1 | |
+| ISDN interworking | | | |
+| CASE A | | | |
+| SETUP | ➔ | INVITE | |
+| CONNECT | ← | 200 OK INVITE 1 | |
+| | ➔ | ACK 1 | |
+| CASE B | | | |
+| SETUP | ➔ | INVITE | |
+| CONNECT | ← | 200 OK INVITE 1 | |
+| CONNECT ACKNOWLEDGE | ➔ | ACK 1 | |
+| Apply post test routine | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|---------------|------------------------------|--|--|-------|---|--------|--|---|---------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_014 | Reference
section 13.2.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
SDP offer sent in the initial INVITE request | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that while the client is establishing a call, a unique session description offer is sent in the INVITE request to answer the initial offers given in the final 2XX response. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
SDP
'm' line
'a' line
200 OK INVITE
SDP
'm' line
'a' line | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 200 OK INVITE |
ISDN interworking |
| SETUP | → | INVITE |
| ← | 200 OK INVITE |
Apply post test routine
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 200 OK INVITE |
ISDN interworking | | | SETUP | → | INVITE | | ← | 200 OK INVITE |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_015 | Reference
section 13.2.1 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
SDP answer sent in the initial ACK request | | | |
+| Ensure that while the client is establishing a call, a unique session description offer is sent in the ACK request to answer the initial offers given in the final 2XX response. | | | |
+| SIP header values
200 OK 1
SDP
'm' line
'a' line
ACK 1
SDP
'm' line
'a' line | | | |
+
+| Message flow | | |
+|--------------------------------|------------|-----------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 200 OK INVITE 1 |
+| | → | ACK 1 |
+| ISDN interworking | | |
+| CASE A | | |
+| SETUP | → | INVITE |
+| CONNECT | ← | 200 OK INVITE 1 |
+| | → | ACK 1 |
+| CASE B | | |
+| SETUP | → | INVITE |
+| CONNECT | ← | 200 OK INVITE 1 |
+| CONNECT ACKNOWLEDGE | → | ACK 1 |
+| Apply post test routine | | |
+
+| | | | |
+|-------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_016 | Reference
sections 13.2.2.3, 17, 17.1.1.2,
17.1.1.3. and Figure 5 of
[IETF RFC 3261] | Selection expression |
+|-------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------|----------------------|
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Update Record-Route header
Ensure that when the client transaction is in the Calling state that on receipt of a Success (200 OK) response, with a different Record-Route as in previous response, but with the same Via branch parameter and CSeq header method as in the INVITE request, an ACK request is sent with a Route header set according to this new Record-Route. |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| |
+|----------------------------------------------------------------------------------------------------------------|
+| SIP header values
200 OK 2
Record-Route:
ACK 2
Route: |
+|----------------------------------------------------------------------------------------------------------------|
+
+| Message flow | | |
+|--------------------------------|------------|-----------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE 1 |
+| | ← | 200 OK INVITE 1 |
+| | → | ACK 1 |
+| | ← | 200 OK INVITE 2 |
+| | → | ACK 2 |
+| ISDN interworking | | |
+| SETUP | → | INVITE 1 |
+| CONNECT | ← | 200 OK INVITE 1 |
+| CONNECT ACKNOWLEDGE | → | ACK 1 |
+| | ← | 200 OK INVITE 2 |
+| | → | ACK 2 |
+| Apply post test routine | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_017 | Reference
section 20.14 and 13.2.1 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
Content-Length header present in the initial INVITE request | | | |
+| Ensure that when the client transaction is establishing a call, a Content-Length header set to the size of the body in the message that contains the session description is sent. | | | |
+| SIP header values
INVITE
Content-Length:
SDP
'm' line
'a' line | | | |
+| Message flow | | | |
+| End device | | Test equipment | |
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | → | INVITE | |
+| ISDN interworking | | | |
+| SETUP | → | INVITE | |
+| Apply post test routine | | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------|----------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_018 | Reference
section 20.14 and 13.2.1 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
Content Type header indicated SDP | | | |
+| Ensure when the client transaction is establishing a call, a Content-Type header in the message that contains the session description is sent. | | | |
+| SIP header values
INVITE
Content-Type: application/sdp
SDP
'm' line
'a' line | | | |
+| Message flow | | | |
+| End device | | Test equipment | |
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | → | INVITE | |
+| | ← | 200 OK INVITE 1 | |
+| | → | ACK 1 | |
+| ISDN interworking | | | |
+
+| | | | | | |
+|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------------|---|-------|
+| CASE A | | | | | |
+| SETUP | ➔ INVITE | | | | |
+| CONNECT | | ⬅ | 200 OK INVITE 1 | ➔ | ACK 1 |
+| ⬅ | 200 OK INVITE 1 | | | | |
+| ➔ | ACK 1 | | | | |
+| CASE B | | | | | |
+| SETUP | ➔ INVITE | | | | |
+| CONNECT | ⬅ 200 OK INVITE 1 | | | | |
+| CONNECT ACKNOWLEDGE | ➔ ACK 1 | | | | |
+| Apply post test routine | | | | | |
+
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_019 | Reference
subclause 6.3.2.4 of
[ETSI TS 183 043] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|----------------------|--|------------|----------------|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|-------------|--|--|---------------|--|--|-----|-------------------|--|--|--|---|--------|--|---|---------------|--|---|-----|-------------------|--|--|--|---|--------|--|---|---------------|--------------------------------|--|--|
+| Test purpose
Modifying SDP in confirmed dialogue
Ensure that the SUT is able to receive an UPDATE request to modify the SDP in confirmed dialogue. A 200 OK UPDATE with SDP answer is sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE/UPDATE
SDP offer 2
200 OK (INVITE/UPDATE)
SDP answer 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ⬅ | 180 Ringing |
| | 200 OK INVITE |
| | ACK |
CASE A | | |
| ⬅ | INVITE |
| ➔ | 200 OK INVITE |
| ⬅ | ACK |
CASE B | | |
| ⬅ | UPDATE |
| ➔ | 200 OK UPDATE |
| Apply post test routine |
| | | | | End device | Test equipment | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | | ⬅ | 180 Ringing | | | 200 OK INVITE | | | ACK |
CASE A | | | | ⬅ | INVITE | | ➔ | 200 OK INVITE | | ⬅ | ACK |
CASE B | | | | ⬅ | UPDATE | | ➔ | 200 OK UPDATE | Apply post test routine | | |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
CASE B | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | UPDATE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | 200 OK UPDATE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+##### 7.2.2.2.3 Test purposes for ISDN
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|--|---|---------------|---------|--|---|-----------------|--|--|---|-----|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_201 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
200 OK received PSTN XML ProgressIndicator present value x, a CONNECT is sent PI x | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to PI_VA, a CONNECT message is sent to the calling user equipment and a Progress Indicator Information Element is included, the Progress description value is set to PI_VA as described in Table 7.2.2.2.3-1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (INVITE): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
CONNECT: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | | → | INVITE |
| | ← | 407 Proxy Authentication Required |
| | → | ACK |
| | → | INVITE |
| ALERTING | | ← | 180 (Ringing) |
| CONNECT | | ← | 200 OK (INVITE) |
| | → | ACK |
Apply post test routine
| | | | | End device | | Test equipment | SETUP | | → | INVITE | | | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | ALERTING | | ← | 180 (Ringing) | CONNECT | | ← | 200 OK (INVITE) | | | → | ACK |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | | ← | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_202 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose
200 OK received a PSTN XML ProgressIndicator value x present, a CONNECT is sent PI x | | | |
+| Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to PI_VA, a CONNECT message is sent to the calling user equipment and a Progress Indicator Information Element is included, the Progress description value is set to PI_VA. An additional Progress Indicator Information Element is present and the Progress description value is set to value 4 if a Progress Indicator value 1 was sent before in a ALERTING message as described in Table 7.2.2.2.3-1. | | | |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|
+| SIP header values
180 (Ringing): no PSTN XML body present
200 OK (INVITE): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000100< | |
+| DSS1 Parameter values
CONNECT: | |
+| Message flow | |
+| End device | Test equipment |
+| SETUP | → INVITE |
+| | ← 407 Proxy Authentication Required |
+| | → ACK |
+| | → INVITE |
+| ALERTING | ← 180 (Ringing) |
+| CONNECT | ← 200 OK (INVITE) |
+| | → ACK |
+| Apply post test routine | |
+
+| | | | |
+|-------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_203 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+|-------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
200 OK received PSTN XML ProgressIndicator present value 7, a CONNECT is sent.
Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to 7 and a CONNECT message is sent to the calling user equipment as described in Table 7.2.2.2.3-1. |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SIP header values
180 (Ringing): PSTN XML body present (PI #7)
200 OK (INVITE): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>PI_VA< |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| | | |
+|--------------------------------|-------------------|-----------------------------------|
+| DSSI Parameter values | | |
+| CONNECT: | | |
+| Message flow | | |
+| | End device | Test equipment |
+| SETUP | → | INVITE |
+| | ← | 407 Proxy Authentication Required |
+| | → | ACK |
+| | → | INVITE |
+| ALERTING | ← | 180 (Ringing) |
+| CONNECT | ← | 200 OK (INVITE) |
+| | → | ACK |
+| Apply post test routine | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_204 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 |
+| Test purpose | | | |
+| 200 OK received PSTN XML ProgressIndicator present value 7, a CONNECT is sent. | | | |
+| Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to 7 and a CONNECT message is sent to the calling user equipment as described in Table 7.2.2.2.3-1. | | | |
+| SIP header values | | | |
+| 180 (Ringing): PSTN XML body present (PI #7) | | | |
+| 200 OK (INVITE): XML body | | | |
+| | | | |
+| PSTN | | | |
+| ProgressIndicator | | | |
+| ProgressOctet3 | | | |
+| CodingStandard>00< | | | |
+| Location>yyyy< | | | |
+| ProgressOctet4 | | | |
+| ProgressDescription>PI_VA< | | | |
+| DSSI Parameter values | | | |
+| CONNECT: | | | |
+| Message flow | | | |
+| | End device | | Test equipment |
+| SETUP | → | INVITE | |
+| | ← | 407 Proxy Authentication Required | |
+| | → | ACK | |
+| | → | INVITE | |
+| ALERTING | ← | 180 (Ringing) | |
+| CONNECT | ← | 200 OK (INVITE) | |
+| | → | ACK | |
+| Apply post test routine | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|---------------|---------|---|-----------------|--|---|-----|-------------------------|--|--|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_205 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
200 OK received PSTN XML ProgressIndicator present value 7, a CONNECT is sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that on receipt of a 200 OK (INVITE) where a PSTN XML body is present, ProgressIndicator value is set to 7 and a CONNECT message is sent to the calling user equipment. A Progress Indicator Information Element is present the Progress description value is set to value 4 if a Progress Indicator value 1 was sent before in a ALERTING message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
180 (Ringing): PSTN XML body present (PI #7)
200 OK (INVITE): XML body
PSTN
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
ALERTING: PI #1
CONNECT: PI #4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | Test equipment |
| SETUP | → | INVITE |
| ← | 407 Proxy Authentication Required |
| → | ACK |
| → | INVITE |
| ALERTING | ← | 180 (Ringing) |
| CONNECT | ← | 200 OK (INVITE) |
| → | ACK |
| Apply post test routine |
| | | | | End device | Test equipment | SETUP | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | ALERTING | ← | 180 (Ringing) | CONNECT | ← | 200 OK (INVITE) | | → | ACK | Apply post test routine | | |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ← | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.2.3-1 – Mapping of progress indicator information element to PSTN XML ProgressIndicator**
+
+| PI_value | DSS1 Progress Indicator value | XML ProgressIndicator
ProgressDescription |
+|----------|--------------------------------------------------------------------------------------------|----------------------------------------------|
+| PI_VA_1 | Call is not end-to-end 5.1.1/2; further call progress information may be available in-band | '0000001' |
+| PI_VA_2 | Destination address is non-5.1.1/2 | '0000010' |
+| PI_VA_3 | Origination address is non-5.1.1/2 | '0000011' |
+| PI_VA_4 | Call has returned to the 5.1.1/2 | '0000100' |
+| PI_VA_5 | Interworking has occurred and has resulted in a telecommunication service change | '0000101' |
+| PI_VA_6 | In-band information or an appropriate pattern is now available | '0001000' |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|--|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|--|---|---------------|---------|--|---|-----------------|--|--|---|-----|-------------------------|--|--|--|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_206 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
PSTN XML body LowLayerCompatibility received in 200 OK. A CONNECT is sent LLC is present Ensure that on receipt of a LowLayerCompatibility PSTN XML element present in a 200 OK INVITE, a DSS1 CONNECT message is sent to the calling user equipment and a HLC IE is present as described in Table 7.2.2.2.3-2.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (INVITE): PSTN XML MIME body
00
ITC_VA
00
10000
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
CONNECT: HLC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | | ➔ | INVITE |
| | ⬅ | 407 Proxy Authentication Required |
| | ➔ | ACK |
| | ➔ | INVITE |
| ALERTING | | ⬅ | 180 (Ringing) |
| CONNECT | | ⬅ | 200 OK (INVITE) |
| | ➔ | ACK |
| Apply post test routine |
| | | | | End device | | Test equipment | SETUP | | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | ALERTING | | ⬅ | 180 (Ringing) | CONNECT | | ⬅ | 200 OK (INVITE) | | | ➔ | ACK | Apply post test routine | | | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | | ⬅ | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.2.3-2 – Mapping of low layer compatibility to PSTN XML
+LowLayerCompatibility**
+
+| ITC_value | LLC information transfer capability | XML LLC InformationTransferCabability |
+|-----------|-------------------------------------|---------------------------------------|
+| ITC_VA_1 | Speech | '00000' |
+| ITC_VA_2 | 3,1 kHz audio | '10000' |
+| ITC_VA_3 | Unrestricted digital info | '01001' |
+| ITC_VA_3 | 7 kHz audio | '10001' |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|-------------------|--|-----------------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|---------------|---------|---|-----------------|--|---|-----|--------------------------------|--|--|
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_207 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
PSTN XML body BearerCapability received in 200 OK CONNECT is sent BC present
Fallback connection type indicated in the SETUP. Ensure that on receipt of a 200 OK (INVITE) that contains a PSTN XML BearerCapability indicating fallback, a CONNECT message is sent to the calling user equipment and a Bearer Capability Information Element is present set to the value of the received BearerCapability XML element as described in Table 5.2.1.3-5. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (INVITE): PSTN XML MIME body
PSTN
BearerCapability
BCoctet3
CodingStandard>00<
InformationTransferCabability>ITC_VA<
BCoctet4
TransferMode>00<
InformationTransferRate>10000<
BCoctet5>
Layer1Identification>01<
UserInfoLayer1Protocol>00011<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111<
SDP: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CONNECT: BC | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ALERTING | ⬅ | 180 (Ringing) |
| CONNECT | ⬅ | 200 OK (INVITE) |
| ➔ | ACK |
| Apply post test routine |
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 (Ringing) | CONNECT | ⬅ | 200 OK (INVITE) | | ➔ | ACK | Apply post test routine | | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ⬅ | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.2.3-3 – Mapping of bearer capability to PSTN XML BearerCapability**
+
+| ITC_value | BC information transfer capability | XML InformationTransferCapability | SDP m - line: first stated codec |
+|-----------|-----------------------------------------|-----------------------------------|----------------------------------|
+| ITC_VA_1 | Speech | '00000' | 0 or 8 |
+| ITC_VA_2 | 3,1 kHz audio | '10000' | 0 or 8 |
+| ITC_VA_3 | Unrestricted digital inf.
W/tone/ann | '10001' | CLEARMODE |
+
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_208 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|------------------------------------------------|------------|--|----------------|-------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|----------|---|---------------|---------|---|-----------------|--|---|-----|
+| Test purpose
200 OK received no PSTN XML ProgressIndicator present, a CONNECT BC included is sent. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Fall-back connection type indicated in the SETUP. Ensure that on receipt of a 200 OK (INVITE) and no PSTN XML body is present, a CONNECT message is sent to the calling user equipment. A Bearer Capability Information Element is present set to the value speech or audio 3.1 kHz | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK (INVITE):
no XML body present
SDP: | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CONNECT: BC speech or audio 3.1 kHz | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ALERTING | ⬅ | 180 (Ringing) |
| CONNECT | ⬅ | 200 OK (INVITE) |
| ➔ | ACK |
Apply post test routine
| | | | End device | | Test equipment | SETUP | ➔ | INVITE | | ⬅ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | ALERTING | ⬅ | 180 (Ringing) | CONNECT | ⬅ | 200 OK (INVITE) | | ➔ | ACK |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ⬅ | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Establishment_of_a
_confirmed_dialogue | TP_202_209 | Reference
subclause 5.1.1.3 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 and 5.4/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|------------------------------------------------|--|-------------------|--|-----------------------|-------|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|--|----------|---|---------------|--|---------|---|-----------------|--|--|---|-----|--|
+| Test purpose
Fallback information received as PSTN XML body HLC in the 200 a CONNECT contains the fall-back information Fallback connection type indicated in the SETUP. Ensure that the SUT on receipt of a HighLayerCapability value set to HLC_VA and ProgressIndicator No. 5 PSTN XML body, a CONNECT message is sent to the calling user equipment. The CONNECT message contains a HLC Information Element derived from the received PSTN XML HighLayerCapability and a Progress Indicator Information Element derived from the received PSTN XML HighLayerCompatibility as described in Table 7.2.2.2.3-4.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
PSTN
HighLayerCompatibility
HLOctet3
CodingStandard>00<
Interpretation>100<
PresentationMethod>01<
HLOctet4
HighLayerCharacteristics>HLC_VA<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000101<
ProgressIndicator
ProgressOctet3
CodingStandard>00<
Location>yyyy<
ProgressOctet4
ProgressDescription>0000111< | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
SETUP: First Bearer Capability Information transfer capability = Speech or 3.1 kHz audio
Second Bearer Capability Information transfer capability = Unrestricted digital information with tones/announcements
CONNECT: BC speech or audio 3.1 kHz | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | ➔ | INVITE |
| ⬅ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ALERTING | ⬅ | 180 (Ringing) |
| CONNECT | ⬅ | 200 OK (INVITE) |
| ➔ | ACK |
Apply post test routine
| | | | | End device | | Test equipment | SETUP | ➔ | INVITE | | | ⬅ | 407 Proxy Authentication Required | | | ➔ | ACK | | | ➔ | INVITE | | ALERTING | ⬅ | 180 (Ringing) | | CONNECT | ⬅ | 200 OK (INVITE) | | | ➔ | ACK | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ⬅ | 180 (Ringing) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ⬅ | 200 OK (INVITE) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.2.3-4 – Mapping of high layer compatibility information element to PSTN XML HighLayerCharacteristic**
+
+| HLC_value | DSS1 high layer characteristics identification | XML HighLayerCharacteristic |
+|-----------|------------------------------------------------------------------------|-----------------------------|
+| HLC_VA_1 | Telephony | '0000001' |
+| HLC_VA_2 | Facsimile Group 2/3 | '0000100' |
+| HLC_VA_3 | Facsimile Group 4 Class I | '0100001' |
+| HLC_VA_4 | Facsimile service Group 4, Classes II and III | '0100100' |
+| HLC_VA_5 | Syntax based Videotex | '0110010' |
+| HLC_VA_6 | International Videotex interworking via gateways or interworking units | '0110011' |
+| HLC_VA_7 | Telex service | '0110101' |
+| HLC_VA_8 | FTAM application | '1000010' |
+| HLC_VA_9 | Videotelephony | '1100000' |
+
+##### 7.2.2.2.3 Call release
+
+###### 7.2.2.2.3.1 Release initiated by the originating user
+
+###### 7.2.2.2.3.1.1 SIP basic procedures
+
+| | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|--|--|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_001 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | | |
+| Test purpose
To header in BYE is used from the last final response | | | | | |
+| Ensure that once a dialogue has been established the IUT sends a BYE request to release it where a To header is set to the same value as in the last received final response. | | | | | |
+| SIP header values
200 OK
To:
BYE
To: | | | | | |
+| Message flow | | | | | |
+| End device | | Test equipment | | | |
+| Interworking POTS | | | | | |
+| Off hook | | | | | |
+| Dial number | | | | | |
+| | | → INVITE | | | |
+| | | ← 180 Ringing | | | |
+| | | ← 200 OK INVITE | | | |
+| | | → ACK | | | |
+| On hook | | | | | |
+| | | → BYE | | | |
+| | | ← 200 OK BYE | | | |
+| ISDN interworking | | | | | |
+| CASE A | | | | | |
+| SETUP | | | | | |
+| | | → INVITE | | | |
+| ALERTING | | | | | |
+| | | ← 180 Ringing | | | |
+| CONNECT | | | | | |
+| | | ← 200 OK INVITE | | | |
+| DISCONNECT | | | | | |
+| | | → ACK | | | |
+| RELEASE | | | | | |
+| | | → BYE | | | |
+| RELEASE COMPLETE | | | | | |
+| | | ← 200 OK BYE | | | |
+| | | → | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------|-----------------------|--|-------------------|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|---------------|--|--|---|-----|---------|--|---|-----|--|--|---|------------|--------------------------|--|--|--|-------|--|---|--------|---------|--|---|---------------|--|--|---|-----|------------|--|---|-----|---------|--|---|------------|------------------|--|---|--|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_002 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
BYE is sent without To tag | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that if a dialog had been established with a final response in which the 'tag' in the To header was omitted, to release it the IUT sends a BYE request with an identical To header without 'tag' value. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
200 OK
To:
BYE
To: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | | |
| Dial number | | ➔ | INVITE |
| | ⬅ | 200 OK INVITE |
| | ➔ | ACK |
| On hook | | ➔ | BYE |
| | ⬅ | 200 OK BYE |
| ISDN interworking |
| SETUP | | ➔ | INVITE |
| CONNECT | | ⬅ | 200 OK INVITE |
| | ➔ | ACK |
| DISCONNECT | | ➔ | BYE |
| RELEASE | | ⬅ | 200 OK BYE |
| RELEASE COMPLETE | | ➔ | |
| | | | | End device | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | ➔ | INVITE | | | ⬅ | 200 OK INVITE | | | ➔ | ACK | On hook | | ➔ | BYE | | | ⬅ | 200 OK BYE | ISDN interworking | | | | SETUP | | ➔ | INVITE | CONNECT | | ⬅ | 200 OK INVITE | | | ➔ | ACK | DISCONNECT | | ➔ | BYE | RELEASE | | ⬅ | 200 OK BYE | RELEASE COMPLETE | | ➔ | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| On hook | | ➔ | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | | ⬅ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DISCONNECT | | ➔ | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE | | ⬅ | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE COMPLETE | | ➔ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_003 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
To header in BYE is used from the last final response | | | |
+| Ensure that the IUT, once a dialogue has been established to release, it sends a BYE request with a To header set to the same value as in the last received final response. | | | |
+| SIP header values
200 OK
To:
BYE
To: | | | |
+
+| Message flow | | |
+|--------------------------|------------|----------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 180 Ringing |
+| | ← | 200 OK INVITE |
+| | → | ACK |
+| On hook | → | BYE |
+| | ← | 200 OK BYE |
+| ISDN interworking | | |
+| SETUP | → | INVITE |
+| ALERTING | ← | 180 Ringing |
+| CONNECT | ← | 200 OK INVITE |
+| | → | ACK |
+| DISCONNECT | → | BYE |
+| RELEASE | ← | 200 OK BYE |
+| RELEASE COMPLETE | → | |
+
+| | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|--|--|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_004 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression | | |
+| Test purpose | | | | | |
+| Call-ID is set to the value as in the original INVITE | | | | | |
+| Ensure that the IUT, once a dialogue has been established to release, it sends a BYE request with the same Call-ID, From headers as in the original INVITE message. | | | | | |
+| SIP header values | | | | | |
+| 200 OK
Call-ID: | | | | | |
+| BYE
Call-ID: | | | | | |
+| Message flow | | | | | |
+| | End device | Test equipment | | | |
+| Interworking POTS | | | | | |
+| Off hook | | | | | |
+| Dial number | → | INVITE | | | |
+| | ← | 180 Ringing | | | |
+| | ← | 200 OK INVITE | | | |
+| | → | ACK | | | |
+| On hook | → | BYE | | | |
+| | ← | 200 OK BYE | | | |
+| ISDN interworking | | | | | |
+| SETUP | → | INVITE | | | |
+| ALERTING | ← | 180 Ringing | | | |
+| CONNECT | ← | 200 OK INVITE | | | |
+| | → | ACK | | | |
+| DISCONNECT | → | BYE | | | |
+| RELEASE | ← | 200 OK BYE | | | |
+| RELEASE COMPLETE | → | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------|----------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|--|---|---------------|--|---|-----|---------|---|-----|--|---|------------|--------------------------|--|--|-------|---|--------|----------|---|-------------|---------|---|---------------|--|---|-----|------------|---|-----|---------|---|------------|------------------|---|--|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_005 | Reference
section 12.2.1.1 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
CSeq in BYE is incremented | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, once a dialogue has been established to release, it sends a BYE request with an increment of one CSeq value, a method field in the CSeq header set to "BYE". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
CSeq: INVITE
BYE
CSeq: BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow | End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 180 Ringing |
| ← | 200 OK INVITE |
| → | ACK |
| On hook | → | BYE |
| ← | 200 OK BYE |
| ISDN interworking |
| SETUP | → | INVITE |
| ALERTING | ← | 180 Ringing |
| CONNECT | ← | 200 OK INVITE |
| → | ACK |
| DISCONNECT | → | BYE |
| RELEASE | ← | 200 OK BYE |
| RELEASE COMPLETE | → | |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 180 Ringing | | ← | 200 OK INVITE | | → | ACK | On hook | → | BYE | | ← | 200 OK BYE | ISDN interworking | | | SETUP | → | INVITE | ALERTING | ← | 180 Ringing | CONNECT | ← | 200 OK INVITE | | → | ACK | DISCONNECT | → | BYE | RELEASE | ← | 200 OK BYE | RELEASE COMPLETE | → | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| On hook | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DISCONNECT | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE | ← | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE COMPLETE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_006 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
BYE is sent to the address indicated in the 200 OK Contact header | | | |
+| Ensure that the IUT, once a dialogue has been established with a Success (200 OK) response including no Record Route header set, to release it, sends a BYE request with the Request URI set to the Contact URI included in the received final response and with no Route header set. | | | |
+| SIP header values
200 OK
Contact:
BYE: SIP/2.0 | | | |
+
+| Message flow | |
+|--------------------------|-------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK |
+| On hook | → BYE
← 200 OK BYE |
+| ISDN interworking | |
+| SETUP | → INVITE |
+| ALERTING | ← 180 Ringing |
+| CONNECT | ← 200 OK INVITE
→ ACK |
+| DISCONNECT | → BYE |
+| RELEASE | ← 200 OK BYE |
+| RELEASE COMPLETE | → |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_007 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
BYE is sent to the address indicated in the Record-Route header with 'lr' parameter
Ensure that the IUT, once a dialogue has been established with a Success (200 OK) response including a Record-Route header set to a list in which the last element contains lr parameter, to release the call, sends a BYE request with the Request-URI set to the Contact URI and a Route header set to the list in a reverse order of the Record-Route included in the received final response. | | | |
+| SIP header values
200 OK
Record-Route: ,
Contact:
BYE
BYE sip: SIP 2.0
Route: , | | | |
+
+| Message flow | | |
+|--------------------------|-------------------|-----------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 180 Ringing |
+| | ← | 200 OK INVITE |
+| | → | ACK |
+| On hook | → | BYE |
+| | ← | 200 OK BYE |
+| ISDN interworking | | |
+| SETUP | → | INVITE |
+| ALERTING | ← | 180 Ringing |
+| CONNECT | ← | 200 OK INVITE |
+| | → | ACK |
+| DISCONNECT | → | BYE |
+| RELEASE | ← | 200 OK BYE |
+| RELEASE COMPLETE | → | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_008 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
Route set in BYE is derived from the Record-Route headers in revers order | | | |
+| Ensure that the IUT, once a dialogue has been established with a Success (200 OK) response including a Record-Route header set to a list in which the last element does not contain lr parameter, to release the call, sends an BYE request with the Request-URI set to this element and a Route header set to the remainder list in a reverse order of the received Record-Route appended with the received Contact URI. | | | |
+| SIP header values
200 OK
Record-Route: ,
Contact:
BYE
BYE sip: SIP 2.0
Route: , | | | |
+
+| Message flow | |
+|--------------------------|-------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK |
+| On hook | → BYE
← 200 OK BYE |
+| ISDN interworking | |
+| SETUP | → INVITE |
+| ALERTING | ← 180 Ringing |
+| CONNECT | ← 200 OK INVITE
→ ACK |
+| DISCONNECT | → BYE |
+| RELEASE | ← 200 OK BYE |
+| RELEASE COMPLETE | → |
+
+| | | | |
+|----------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_009 | Reference
section 12.2.1.1 and 15 of
[IETF RFC 3261] | Selection expression |
+|----------------------------------------------------------------|------------|------------------------------------------------------------|----------------------|
+
+| |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Session in confirmed dialogue is terminated by sending a BYE message
Ensure that the IUT, when a dialogue has been established, having sent a BYE request, on receipt of a (200 OK) response considers the session and the dialogue terminated.
|
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| |
+|--------------------------|
+| SIP header values |
+|--------------------------|
+
+| Message flow | |
+|--------------------------|-----------------------------------------------------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE 1
← 180 Ringing
← 200 OK INVITE
→ ACK |
+| On hook | → BYE
Start timer K
← 200 OK BYE
Timeout timer K
← BYE
→ 481 Call Leg Does Not Exist |
+
+| | | |
+|--------------------------|-------------------|-------------------------------|
+| ISDN interworking | | |
+| SETUP | → | → INVITE 1 |
+| ALERTING | ← | ← 180 Ringing |
+| CONNECT | ← | ← 200 OK INVITE |
+| | | → ACK |
+| DISCONNECT | → Start timer K | → BYE |
+| RELEASE | ← | ← 200 OK BYE |
+| RELEASE COMPLETE | → Timeout timer K | |
+| | ← | ← BYE |
+| | → | → 481 Call Leg Does Not Exist |
+
+| | | | |
+|----------------------------------------------------------------|------------|----------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_010 | Reference
section 12.2.1.1 and 15.1.1 of
[IETF RFC 3261] | Selection expression |
+|----------------------------------------------------------------|------------|----------------------------------------------------------------|----------------------|
+
+###### **Test purpose**
+
+*BYE received after 200 OK BYE was sent*
+
+Ensure that the IUT, when a dialogue has been established, having sent a BYE request, on receipt of a Call Leg/Transaction Does Not Exist (481 Call Leg/Transaction Does Not Exist) considers the session and the dialogue terminated.
+
+###### **SIP header values**
+
+###### **Message flow**
+
+| | End device | Test equipment |
+|--------------------------|-------------------|-------------------------------|
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE 1 |
+| | ← | 180 Ringing |
+| | ← | 200 OK INVITE |
+| | → | ACK |
+| On hook | → | BYE |
+| | Start timer K | |
+| | ← | 200 OK BYE |
+| | Timeout timer K | |
+| | ← | ← BYE |
+| | → | → 481 Call Leg Does Not Exist |
+| ISDN interworking | | |
+| SETUP | → | → INVITE 1 |
+| ALERTING | ← | ← 180 Ringing |
+| CONNECT | ← | ← 200 OK INVITE |
+| | | → ACK |
+| DISCONNECT | → Start timer K | → BYE |
+| RELEASE | ← | ← 200 OK BYE |
+| RELEASE COMPLETE | → Timeout timer K | |
+| | ← | ← BYE |
+| | → | → 481 Call Leg Does Not Exist |
+
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_011 | Reference
section 15 and 9.1, Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|---------|---|--------|--|---|---------------|--|---|------------------------|--|---|-----|------------------------------|--|--|-------|---|----------|--|--|--------------|---------|---|--------------|------------------|---|---------------------|--|--|--------------------------|--|--|-------|
+| Test purpose
Session in early dialogue is terminated by sending a CANCEL or BYE message | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, to give up the call, sends a CANCEL/BYE request. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 100 Trying |
| On hook | → | CANCEL |
| ← | 200 OK CANCEL |
| ← | 487 Request Terminated |
| → | ACK |
ISDN interworking |
| SETUP | → | → INVITE |
| | ← 100 Trying |
| RELEASE | → | → CANCEL/BYE |
| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE |
| | ← 487 Request Terminated |
| | → ACK |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 100 Trying | On hook | → | CANCEL | | ← | 200 OK CANCEL | | ← | 487 Request Terminated | | → | ACK |
ISDN interworking | | | SETUP | → | → INVITE | | | ← 100 Trying | RELEASE | → | → CANCEL/BYE | RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | | | ← 487 Request Terminated | | | → ACK |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| On hook | → | CANCEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 200 OK CANCEL | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE | → | → CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_012 | Reference
section 15 and 9.1, Figure 5 of
[IETF RFC 3261] | Selection expression |
+| Test purpose
Header in the CANCEL or BYE message | | | |
+| Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, to give up the call, sends a CANCEL/BYE request with the same Request-URI, Call-ID, From, To headers as in the original INVITE message. | | | |
+| SIP header values | | | |
+| INVITE
INVITE sip:
From: sip:;tag=
To: sip: sip:
Call-ID:
CANCEL
INVITE sip:
From: sip:;tag=
To: sip: sip:
Call-ID: | | | |
+
+| Message flow | | |
+|--------------------------|-------------------|--------------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 100 Trying |
+| On hook | → | CANCEL/BYE |
+| | ← | 200 OK CANCEL/BYE |
+| | ← | 487 Request Terminated |
+| | → | ACK |
+| ISDN interworking | | |
+| SETUP | → | → INVITE |
+| | | ← 100 Trying |
+| RELEASE | → | → CANCEL/BYE |
+| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE |
+| | | ← 487 Request Terminated |
+| | | → ACK |
+
+| | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------|----------------------|--|--|
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_013 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | | |
+| Test purpose
CSeq method parameter in CANCEL or BYE | | | | | |
+| Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, sends a CANCEL request with the same numeric part of CSeq as in the original INVITE message with a method field in the CSeq header set to "CANCEL/BYE ". | | | | | |
+| SIP header values | | | | | |
+| INVITE
Call-ID: INVITE | | | | | |
+| CANCEL
Call-ID: CANCEL | | | | | |
+| Message flow | | | | | |
+| | End device | Test equipment | | | |
+| Interworking POTS | | | | | |
+| Off hook | | | | | |
+| Dial number | → | INVITE | | | |
+| | ← | 100 Trying | | | |
+| On hook | → | CANCEL/BYE | | | |
+| | ← | 200 OK CANCEL/BYE | | | |
+| | ← | 487 Request Terminated | | | |
+| | → | ACK | | | |
+| ISDN interworking | | | | | |
+| SETUP | → | → INVITE | | | |
+| | | ← 100 Trying | | | |
+| RELEASE | → | → CANCEL/BYE | | | |
+| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | | | |
+| | | ← 487 Request Terminated | | | |
+| | | → ACK | | | |
+
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_014 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|------------|---------|---|------------|--|---|-------------------|--|---|------------------------|--|---|-----|------------------------------|--|--|-------|---|----------|--|--|--------------|---------|---|--------------|------------------|---|---------------------|--|--|--------------------------|--|--|-------|
+| Test purpose
CANCEL or BYE contains the Via header from the initial INVITE request
Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, sends a CANCEL/BYE request with a single Via header value matching the top Via value of the Via header of the original INVITE message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values
INVITE
Via: SIP/2.0/ ;branch=
CANCEL
Via: SIP/2.0/ ;branch= | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ⬅ | 100 Trying |
| On hook | ➔ | CANCEL/BYE |
| ⬅ | 200 OK CANCEL/BYE |
| ⬅ | 487 Request Terminated |
| ➔ | ACK |
ISDN interworking |
| SETUP | ➔ | ➔ INVITE |
| | ⬅ 100 Trying |
| RELEASE | ➔ | ➔ CANCEL/BYE |
| RELEASE COMPLETE | ⬅ | ⬅ 200 OK CANCEL/BYE |
| | ⬅ 487 Request Terminated |
| | ➔ ACK |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ⬅ | 100 Trying | On hook | ➔ | CANCEL/BYE | | ⬅ | 200 OK CANCEL/BYE | | ⬅ | 487 Request Terminated | | ➔ | ACK |
ISDN interworking | | | SETUP | ➔ | ➔ INVITE | | | ⬅ 100 Trying | RELEASE | ➔ | ➔ CANCEL/BYE | RELEASE COMPLETE | ⬅ | ⬅ 200 OK CANCEL/BYE | | | ⬅ 487 Request Terminated | | | ➔ ACK |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| On hook | ➔ | CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ⬅ | 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ 100 Trying | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE | ➔ | ➔ CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE COMPLETE | ⬅ | ⬅ 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ⬅ 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Orig_Release_initiated
_by_the_terminating_user | TP_203_015 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|
+| Test purpose
The CANCEL or BYE does not contain a Require or Proxy Require header
Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, to give up the call, sends a CANCEL/BYE request without Require or Proxy-Require header. | | | |
+| SIP header values
CANCEL
Require: [not present]
Proxy-Require: [not present] | | | |
+
+| Message flow | | |
+|--------------------------|-------------------|--------------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 100 Trying |
+| On hook | → | CANCEL/BYE |
+| | ← | 200 OK CANCEL/BYE |
+| | ← | 487 Request Terminated |
+| | → | ACK |
+| ISDN interworking | | |
+| SETUP | → | → INVITE |
+| | | ← 100 Trying |
+| RELEASE | → | → CANCEL/BYE |
+| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE |
+| | | ← 487 Request Terminated |
+| | | → ACK |
+
+| | | | |
+|----------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_016 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+|----------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|
+
+| |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
A CANCEL or BYE is sent after 180 was received
Ensure that the IUT, having received a 180 Ringing provisional response to its INVITE request, to give up the call, sends a CANCEL/BYE request.
|
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| Message flow | | |
+|--------------------------|-------------------|--------------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE |
+| | ← | 180 Ringing |
+| On hook | → | CANCEL/BYE |
+| | ← | 200 OK CANCEL/BYE |
+| | ← | 487 Request Terminated |
+| | → | ACK |
+| ISDN interworking | | |
+| SETUP | → | → INVITE |
+| | | ← 180 Ringing |
+| RELEASE | → | → CANCEL/BYE |
+| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE |
+| | | ← 487 Request Terminated |
+| | | → ACK |
+
+| | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_017 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+| Test purpose | | | |
+| A CANCEL or BYE is sent after 181 was received | | | |
+| Ensure that the IUT, having received a 181 Call Is Being Forwarded provisional response to its INVITE request, to give up the call, sends a CANCEL/BYE request. | | | |
+
+
+
+| Message flow | | | | | |
+|--------------------------|---|---------------------------|--|--|--|
+| End device | | Test equipment | | | |
+| Interworking POTS | | | | | |
+| Off hook | | | | | |
+| Dial number | | → INVITE | | | |
+| | | ← Call Is Being Forwarded | | | |
+| On hook | | → CANCEL/BYE | | | |
+| | | ← 200 OK CANCEL/BYE | | | |
+| | | ← 487 Request Terminated | | | |
+| | | → ACK | | | |
+| ISDN interworking | | | | | |
+| SETUP | → | → INVITE | | | |
+| | | ← 180 Ringing | | | |
+| RELEASE | → | → CANCEL/BYE | | | |
+| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE | | | |
+| | | ← 487 Request Terminated | | | |
+| | | → ACK | | | |
+
+| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_018 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|--|--|
+| Test purpose | | | | | |
+| A CANCEL or BYE is sent after 182 was received | | | | | |
+| Ensure that the IUT, having received a 182 Queued provisional response to its INVITE request, to give up the call, sends a CANCEL/BYE request. | | | | | |
+| Message flow | | | | | |
+| End device | | Test equipment | | | |
+| Interworking POTS | | | | | |
+| Off hook | | | | | |
+| Dial number | | → INVITE | | | |
+| | | ← 182 Queued | | | |
+| On hook | | → CANCEL/BYE | | | |
+| | | ← 200 OK CANCEL/BYE | | | |
+| | | ← 487 Request Terminated | | | |
+| | | → ACK | | | |
+
+| | | |
+|--------------------------|---|----------------------------------------------------------|
+| ISDN interworking | | |
+| SETUP | → | → INVITE
← 182 Queued |
+| RELEASE | → | → CANCEL/BYE |
+| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE
← 487 Request Terminated
→ ACK |
+
+| | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------|----------------------|--|--|
+| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_019 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression | | |
+| Test purpose | | | | | |
+| A CANCEL or BYE is sent after 183 was received | | | | | |
+| Ensure that the IUT, having received a 183 Session Progress provisional response to its INVITE request, to give up the call, sends a CANCEL/BYE request. | | | | | |
+| Message flow | | | | | |
+| End device | | Test equipment | | | |
+| Interworking POTS | | | | | |
+| Off hook | | | | | |
+| Dial number | | | | | |
+| | | → INVITE
← 183 Session Progress | | | |
+| On hook | | | | | |
+| | | → CANCEL/BYE
← 200 OK CANCEL/BYE
← 487 Request Terminated
→ ACK | | | |
+| ISDN interworking | | | | | |
+| SETUP | → | → INVITE
← 183 Session Progress | | | |
+| RELEASE | → | → CANCEL/BYE | | | |
+| RELEASE COMPLETE | ← | ← 200 OK CANCEL/BYE
← 487 Request Terminated
→ ACK | | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------|----------------------|
+| TSS
Orig_Orig_Release_initiated_
by_the_terminating_user | TP_203_020 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+| Test purpose | | | |
+| A CANCEL or BYE is sent a 200 OK INVITE was received at the same time | | | |
+| Ensure that the IUT, having received a Trying (100 Trying) response to its INVITE request, to give up the call having sent a CANCEL/BYE request, on receipt of a 2XX response to the original INVITE sends an ACK request. | | | |
+| SIP header values | | | |
+
+| Message flow | | |
+|--------------------------|-------------------|-----------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | ➔ | INVITE |
+| | ➔ | 100 Trying |
+| On hook | ➔ | CANCEL/BYE |
+| | ➔ | 200 OK INVITE |
+| | ➔ | ACK |
+| | ➔ | BYE |
+| | ➔ | 200 OK BYE |
+| ISDN interworking | | |
+| SETUP | ➔ | ➔ INVITE |
+| | | ➔ 100 Trying |
+| RELEASE | ➔ | ➔ CANCEL/BYE |
+| RELEASE COMPLETE | ➔ | ➔ 200 OK INVITE |
+| | | ➔ ACK |
+| | | ➔ BYE |
+| | | ➔ 200 OK BYE |
+
+##### 7.2.2.3.2 Release initiated by the terminating user
+
+###### 7.2.2.3.2.1 SIP basic procedures
+
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_001 | Reference
section 15, 9.1 and Figure 5 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------|--------------------------------------|---------------------|--|--|--|-------------------|-----------------------|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|-------------|--------------|---|---------------|--|---|-----|------------|---|-----|--|---|------------|
+| Test purpose
A BYE is received, a 200 OK BYE is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, in the confirmed state when a BYE is received, a 200 OK BYE is sent. The connection is terminated. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Message flow |
| End device | Test equipment |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ➔ | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ➔ | 180 Ringing |
| Conversation | ➔ | 200 OK INVITE |
| ➔ | ACK |
| Terminated | ➔ | BYE |
| ➔ | 200 OK BYE |
| | | | Message flow | | | | End device | Test equipment | Off hook | | | Dial number | ➔ | INVITE | | ➔ | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | | ➔ | 180 Ringing | Conversation | ➔ | 200 OK INVITE | | ➔ | ACK | Terminated | ➔ | BYE | | ➔ | 200 OK BYE |
+| Message flow | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Conversation | ➔ | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Terminated | ➔ | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|--------------------------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|-------------|--|---|--------------------|--|---|-----|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_002 | Reference
section 13.2.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Receipt of a final response before a provisional response was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that a final response as indicated in Table 7.2.2.3.2-1 is received after an early dialogue was established, a 180 Ringing was received and the SUT sends an ACK message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ← | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ← | 180 Ringing |
| ← | SIP_FINAL_RESPONSE |
| ➔ | ACK |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ← | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | | ← | 180 Ringing | | ← | SIP_FINAL_RESPONSE | | ➔ | ACK |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | SIP_FINAL_RESPONSE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------|--------------------------------------|-------------------|--|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|-----------------------------|--|---|--------------------|--|---|-----|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_003 | Reference
section 13.2.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Receipt of a final response after a 181 Call Is Being Forwarded provisional response was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that a final response as indicated in Table 7.2.2.3.2-1 is received after an early dialogue was established, a 181 Call Is Being Forwarded was received and the SUT sends an ACK message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| ← | 407 Proxy Authentication Required |
| ➔ | ACK |
| ➔ | INVITE |
| ← | 181 Call Is Being Forwarded |
| ← | SIP_FINAL_RESPONSE |
| ➔ | ACK |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | ← | 407 Proxy Authentication Required | | ➔ | ACK | | ➔ | INVITE | | ← | 181 Call Is Being Forwarded | | ← | SIP_FINAL_RESPONSE | | ➔ | ACK |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 181 Call Is Being Forwarded | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | SIP_FINAL_RESPONSE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|------------|--|---|--------------------|--|---|-----|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_004 | Reference
section 13.2.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Receipt of a final response after a 182 Queued provisional response was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that a final response as indicated in Table 7.2.2.3.2-1 is received after an early dialogue was established, a 182 Queued was received and the SUT sends an ACK message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| Interworking POTS | | |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 407 Proxy Authentication Required |
| → | ACK |
| → | INVITE |
| ← | 182 Queued |
| → | SIP_FINAL_RESPONSE |
| → | ACK |
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | | ← | 182 Queued | | → | SIP_FINAL_RESPONSE | | → | ACK |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 182 Queued | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | SIP_FINAL_RESPONSE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-----------------------------------|--|---|-----|--|---|--------|--|---|----------------------|--|---|--------------------|--|---|-----|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_005 | Reference
section 13.2.2 of
[IETF RFC 3261] | Selection expression
PICS 5.1.1/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
Receipt of a final response after a 183 Session Progress provisional response was received | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that a final response as indicated in Table 7.2.2.3.2-1 is received after an early dialogue was established, a 183 Session Progress was received, the SUT sends an ACK message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| Interworking POTS | | |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 407 Proxy Authentication Required |
| → | ACK |
| → | INVITE |
| ← | 183 Session Progress |
| → | SIP_FINAL_RESPONSE |
| → | ACK |
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 407 Proxy Authentication Required | | → | ACK | | → | INVITE | | ← | 183 Session Progress | | → | SIP_FINAL_RESPONSE | | → | ACK |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 183 Session Progress | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | SIP_FINAL_RESPONSE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Table 7.2.2.3.2-1 – 3xx/4xx/5xx/6xx final response**
+
+| CAUSE_VA | ←DISCONNECT (cause value) | ←SIP_FINAL_RESPONSE |
+|-----------------|----------------------------------------------------------------|-------------------------------------|
+| CAUSE_VA_01 | 127 (interworking unspecified) | 400 Bad Request |
+| CAUSE_VA_02 | 127 (interworking unspecified) | 401 Unauthorized |
+| CAUSE_VA_03 | 127 (interworking unspecified) | 402 Payment Required |
+| CAUSE_VA_04 | 127 (interworking unspecified) | 403 Forbidden |
+| CAUSE_VA_05 | 1 (Unallocated number) | 404 Not Found |
+| CAUSE_VA_06 | 127 (interworking unspecified) | 405 Method Not Allowed |
+| CAUSE_VA_07 | 127 (interworking unspecified) | 406 Not Acceptable |
+| CAUSE_VA_08 | 127 (interworking unspecified) | 407 Proxy authentication required |
+| CAUSE_VA_09 | 127 (interworking unspecified) | 408 Request Timeout |
+| CAUSE_VA_10 | 22 (Number changed) | 410 Gone |
+| CAUSE_VA_11 | 127 (interworking unspecified) | 413 Request Entity too long |
+| CAUSE_VA_12 | 127 (interworking unspecified) | 414 Request-URI too long |
+| CAUSE_VA_13 | 127 (interworking unspecified) | 415 Unsupported Media type |
+| CAUSE_VA_14 | 127 (interworking unspecified) | 416 Unsupported URI scheme |
+| CAUSE_VA_15 | 127 (interworking unspecified) | 420 Bad Extension |
+| CAUSE_VA_16 | 127 (interworking unspecified) | 421 Extension required |
+| CAUSE_VA_17 | 127 (interworking unspecified) | 423 Interval Too Brief |
+| CAUSE_VA_18 | 24 (call rejected due to ACR supplementary service) | 433 Anonymity Disallowed |
+| CAUSE_VA_19 | 20 Subscriber absent | 480 Temporarily Unavailable |
+| CAUSE_VA_20 | 127 (interworking unspecified) | 481 Call/Transaction does not exist |
+| CAUSE_VA_21 | 127 (interworking unspecified) | 482 Loop detected |
+| CAUSE_VA_22 | 127 (interworking unspecified) | 483 Too many hops |
+| CAUSE_VA_23 | 28 (Invalid Number format) | 484 Address Incomplete |
+| CAUSE_VA_24 | 127 (interworking unspecified) | 485 Ambiguous |
+| CAUSE_VA_25 | 17 (User busy) | 486 Busy Here |
+| CAUSE_VA_26 | 127 (Interworking unspecified) or not interworked.
(Note 1) | 487 Request terminated |
+| CAUSE_VA_27 | 127 (interworking unspecified) | 488 Not acceptable here |
+| CAUSE_VA_28 | 127 (interworking unspecified) | 493 Undecipherable |
+| CAUSE_VA_29 | 127 (interworking unspecified) | 500 Server Internal error |
+| CAUSE_VA_30 | 127 (interworking unspecified) | 501 Not implemented |
+| CAUSE_VA_31 | 127 (interworking unspecified) | 502 Bad Gateway |
+| CAUSE_VA_32 | 127 (interworking unspecified) | 503 Service Unavailable |
+| CAUSE_VA_33 | 127 (interworking unspecified) | 504 Server timeout |
+| CAUSE_VA_34 | 127 (interworking unspecified) | 505 Version not supported |
+
+**Table 7.2.2.3.2-1 – 3xx/4xx/5xx/6xx final response**
+
+| CAUSE_VA | ←DISCONNECT (cause value) | ←SIP_FINAL_RESPONSE |
+|-------------|--------------------------------|-----------------------------|
+| CAUSE_VA_35 | 127 (interworking unspecified) | 513 Message too large |
+| CAUSE_VA_36 | 127 (interworking unspecified) | 580 Precondition failure |
+| CAUSE_VA_37 | 17 (User busy) | 600 Busy Everywhere |
+| CAUSE_VA_38 | 21 (Call rejected) | 603 Decline |
+| CAUSE_VA_39 | 1 (unallocated number) | 604 Does not exist anywhere |
+| CAUSE_VA_40 | 127 (interworking unspecified) | 606 Not acceptable |
+
+###### 7.2.2.3.2.3 Test purposes for ISDN
+
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_101 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------|--|------------|--|----------------|-------|---|---|--------|--|--|---|-----------------------------------|--|--|---|-----|--|--|---|--------|----------|---|---|-------------|---------|---|---|---------------|--|--|---|-----|------------|---|---|-----|---------|---|---|------------|------------------|---|--|--|
+| Test purpose
Receipt of BYE, a DSSI DISCONNECT is sent cause value 16
Ensure that on receipt of a BYE request a DSS1 DISCONNECT is sent to the calling user equipment. The cause value of the DISCONNECT is set to '16'. The location of the cause IE is set to '1010' network beyond interworking point. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DSS1 Parameter values
DISCONNECT: Cause IE cause value=16 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| SETUP | → | → | INVITE |
| | ← | 407 Proxy Authentication Required |
| | → | ACK |
| | → | INVITE |
| ALERTING | ← | ← | 180 Ringing |
| CONNECT | ← | ← | 200 OK INVITE |
| | → | ACK |
| DISCONNECT | ← | ← | BYE |
| RELEASE | → | → | 200 OK BYE |
| RELEASE COMPLETE | → | | |
| | | | | End device | | Test equipment | SETUP | → | → | INVITE | | | ← | 407 Proxy Authentication Required | | | → | ACK | | | → | INVITE | ALERTING | ← | ← | 180 Ringing | CONNECT | ← | ← | 200 OK INVITE | | | → | ACK | DISCONNECT | ← | ← | BYE | RELEASE | → | → | 200 OK BYE | RELEASE COMPLETE | → | | |
+| | End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 407 Proxy Authentication Required | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CONNECT | ← | ← | 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DISCONNECT | ← | ← | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE | → | → | 200 OK BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| RELEASE COMPLETE | → | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_102 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 |
+| Test purpose
Receipt of a final response before a provisional response was received Reason header not included.
Ensure that when a final response is received before an early dialogue was established and if no Reason header is included, a DISCONNECT is sent to the calling user equipment. The cause value of the DISCONNECT is derived according the mapping in Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point. | | | |
+
+| | | |
+|-----------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------|
+| SIP header values | | |
+| DSS1 Parameter values
DISCONNECT: Cause IE cause value = CAUSE_VA | | |
+| Message flow | | |
+| | End device | Test equipment |
+| SETUP | → | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE |
+| DISCONNECT | ← | ← SIP_FINAL_RESPONSE |
+| RELEASE | → | → ACK |
+| RELEASE COMPLETE | → | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|----------------------------------------------------------------------|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_103 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 |
+| Test purpose
Receipt of a final response after a 180 provisional response was received Reason header not included. | | | |
+| Ensure that when a final response is received after a 180 Ringing is received to establish an early dialogue and a no Reason header is included, a DISCONNECT is sent to the calling user equipment. The case value of the DISCONNECT is derived according to the mapping in Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point. | | | |
+| SIP header values | | | |
+| DSS1 Parameter values
DISCONNECT: Cause IE cause value = CAUSE_VA | | | |
+| Message flow | | | |
+| | End device | | Test equipment |
+| SETUP | → | | → INVITE
← 407 Proxy Authentication Required
→ ACK
→ INVITE |
+| ALERTING | ← | | ← 180 Ringing |
+| DISCONNECT | ← | | ← SIP_FINAL_RESPONSE |
+| RELEASE | → | | → ACK |
+| RELEASE COMPLETE | → | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_104 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 |
+| Test purpose
Receipt of a final response after a 181 provisional response was received Reason header not included. | | | |
+| Ensure that when a final response is received after a 181 Call Is Being Forwarded is received to establish an early dialogue and a no Reason header is included, a DISCONNECT is sent to the calling user equipment. The case value of the DISCONNECT is derived according to the mapping Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point | | | |
+| SIP header values | | | |
+
+| | | |
+|---------------------------------------------|-------------------|-------------------------------------|
+| DSSI Parameter values | | |
+| DISCONNECT: Cause IE cause value = CAUSE_VA | | |
+| Message flow | | |
+| | End device | Test equipment |
+| SETUP | → | → INVITE |
+| | | ← 407 Proxy Authentication Required |
+| | | → ACK |
+| | | → INVITE |
+| NOTIFY | ← | ← 181 Call Is Being Forwarded |
+| DISCONNECT | ← | ← SIP_FINAL_RESPONSE |
+| RELEASE | → | → ACK |
+| RELEASE COMPLETE | → | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_105 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 |
+| Test purpose | | | |
+| Receipt of a final response after a 182 provisional response was received Reason header not included. | | | |
+| Ensure that when a final response is received after a 182 Queued is received to establish an early dialogue and no Reason header is included, a DISCONNECT is sent to the calling user equipment. The case value of the DISCONNECT is derived according to the mapping Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point. | | | |
+| SIP header values | | | |
+| DSSI Parameter values | | | |
+| DISCONNECT: Cause IE cause value = CAUSE_VA | | | |
+| Message flow | | | |
+| | End device | | Test equipment |
+| SETUP | → | | → INVITE |
+| | | | ← 407 Proxy Authentication Required |
+| | | | → ACK |
+| | | | → INVITE |
+| NOTIFY/ CALL PROCEEDING | ← | | ← 182 Queued |
+| DISCONNECT | ← | | ← SIP_FINAL_RESPONSE |
+| RELEASE | → | | → ACK |
+| RELEASE COMPLETE | → | | |
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_106 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 |
+| Test purpose | | | |
+| Receipt of a final response after a 183 provisional response was received Reason header not included. | | | |
+| Ensure that when a final response is received after a 183 Session Progress is received to establish an early dialogue and a no Reason header is included, a DISCONNECT is sent to the calling user equipment. The case value of the DISCONNECT is derived according to the mapping Table 7.2.2.3.2-1. The location of the cause IE is set to '1010' network beyond interworking point. | | | |
+| SIP header values | | | |
+
+| | | |
+|---------------------------------------------|-------------------|-------------------------------------|
+| DSS1 Parameter values | | |
+| DISCONNECT: Cause IE cause value = CAUSE_VA | | |
+| Message flow | | |
+| | End device | Test equipment |
+| SETUP | → | → INVITE |
+| | | ← 407 Proxy Authentication Required |
+| | | → ACK |
+| | | → INVITE |
+| CALL PROCEEDING | ← | ← 183 Session Progress |
+| DISCONNECT | ← | ← SIP_FINAL_RESPONSE |
+| RELEASE | → | → ACK |
+| RELEASE COMPLETE | → | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Release_initiated_by
_the_terminating_user | TP_204_107 | Reference
subclause 5.1.1.4 of
[ETSI TS 183 036] | Selection expression
PICS 5.1.1/2 |
+| Test purpose | | | |
+| DISCONNECT received, a BYE is sent | | | |
+| Ensure that the IUT, while the dialogue is in a confirmed state, of an ISDN DISCONNECT message sends a BYE request. | | | |
+| SIP header values | | | |
+| DSS1 Parameter values | | | |
+| DISCONNECT: Cause IE cause value= | | | |
+| Message flow | | | |
+| | End device | | Test equipment |
+| Interworking POTS | | | |
+| SETUP | → | | → INVITE |
+| | | | ← 407 Proxy Authentication Required |
+| | | | → ACK |
+| | | | → INVITE |
+| | ← | | ← |
+| DISCONNECT | ← | | ← SIP_FINAL_RESPONSE |
+| RELEASE | → | | → ACK |
+| RELEASE COMPLETE | → | | |
+
+#### 7.2.2.4 Timers
+
+| | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_001 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+| Test purpose | | | |
+| UDP: INVITE is repeated if timer T1 expires | | | |
+| Ensure that the IUT, when an INVITE client transaction is in the Calling state repeats its INVITE request on the timeout condition of timer A set with a value of T1 if an unreliable transport (UDP) is used. | | | |
+
+| Message flow | | |
+|--------------------------------|-------------------------|-----------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | Start timer A
1*T1 | → INVITE |
+| Dial number | Timeout timer A | → INVITE |
+| ISDN interworking | | |
+| SETUP | → Start timer A
1*T1 | → INVITE |
+| | Timeout timer A | → INVITE |
+| Apply post test routine | | |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_002 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/2 |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+
+| Test purpose | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------|
+| TCP: INVITE is not repeated if timer T1 expires | | |
+| Ensure that the IUT, when an INVITE client transaction is in the Calling state, does not repeat its INVITE request on the timeout condition of timer A set with a value of T1 if a reliable transport (TCP) is used. | | |
+| Message flow | | |
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | Start timer A
1*T1 | → INVITE |
+| | Timeout timer A | |
+| ISDN interworking | | |
+| SETUP | → Start timer A
1*T1 | → INVITE |
+| | Timeout timer A | |
+| Apply post test routine | | |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_003 | Reference
section 17.1.1.1 and
Annex A/[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+|--------------------|------------|--------------------------------------------------------------|--------------------------------------|
+
+| Test purpose | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
+| UDP: INVITE is retransmitted if timer T1 expires repeatedly | | |
+| Ensure that the IUT, when an INVITE client transaction is in the Calling state having already repeated its INVITE, wait for a timer A set with a value of 2*T1 before sending it again if an unreliable transport (UDP) is used. | | |
+
+| Message flow | | |
+|--------------------------------|-------------------------|-----------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | Start timer A
1*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A
2*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A
4*T1 | → INVITE |
+| ISDN interworking | | |
+| SETUP | → Start timer A
1*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A
2*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A
4*T1 | → INVITE |
+| Apply post test routine | | |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_004 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+
+| |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
UDP: the INVITE is retransmitted with intervals that double after each transmission |
+| Ensure that the IUT, when an INVITE client transaction is in the Calling state, retransmits its INVITE request with intervals that double after each transmission if an unreliable transport (UDP) is used. |
+
+| Message flow | | |
+|--------------------------|---------------------|-----------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | Start timer A 1*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A 2*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A 4*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A 8*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A 16*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A 32*T1 | → INVITE |
+| | Timeout timer A | |
+| | Start timer A 64*T1 | → INVITE |
+
+| | | |
+|--------------------------------|----------------------|----------|
+| ISDN interworking | | |
+| SETUP | → Start timer A 1*T1 | → INVITE |
+| | Timeout timer A | → INVITE |
+| | Start timer A 2*T1 | |
+| | Timeout timer A | → INVITE |
+| | Start timer A 4*T1 | |
+| | Timeout timer A | → INVITE |
+| | Start timer A 32*T1 | |
+| | Timeout timer A | → INVITE |
+| | Start timer A 64*T1 | |
+| Apply post test routine | | |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------------|----------------------|
+| TSS
Orig_Timers | TP_205_005 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression |
+|--------------------|------------|--------------------------------------------------------------------|----------------------|
+
+**Test purpose**
+*Timer B expires no ACK is sent*
+
+Ensure that the IUT, when an INVITE client transaction is in the Calling state, when timer B set to a value of 64\*T1 expires, does not send an ACK.
+
+| Message flow | |
+|--------------------------|--------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | |
+| | Start timer A → INVITE |
+| | Start timer B |
+| | Timeout timer B |
+| | ← 200 OK INVITE |
+| ISDN interworking | |
+| SETUP | → Start timer A → INVITE |
+| | Start timer B |
+| | Timeout timer B |
+| | ← 200 OK INVITE |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------|----------------------|
+| TSS
Orig_Timers | TP_205_006 | Reference
section 17.1.1.1 and
Annex A/[IETF RFC 3261] | Selection expression |
+|--------------------|------------|--------------------------------------------------------------|----------------------|
+
+**Test purpose**
+*Timer B expires, Transaction is in terminated state*
+
+Ensure that the IUT, when an INVITE client transaction is in the Calling state, when timer B set to a value of 64\*T1 expires, considers the transaction terminated.
+
+
+
+**Message flow**
+
+| | End device | | Test equipment |
+|--------------------------|----------------------------------|---|-------------------------------------|
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | Start timer A
Start timer B | → | INVITE |
+| | Timeout timer B | | |
+| | | ← | BYE |
+| | | → | 481 Call/Transaction Does Not Exist |
+| | | → | ACK |
+| ISDN interworking | | | |
+| SETUP | → Start timer A
Start timer B | → | INVITE |
+| | Timeout timer B | | |
+| | | ← | BYE |
+| | | → | 481 Call/Transaction Does Not Exist |
+| | | → | ACK |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_007 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+
+**Test purpose**
+*100 received, the INVITE is not repeated*
+
+Ensure that the IUT, when an INVITE client transaction is in the Proceeding state, does not repeat its INVITE request.
+
+
+
+**Message flow**
+
+| | End device | | Test equipment |
+|--------------------------|-------------------|---|-----------------------|
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | | → | INVITE |
+| | | ← | 100 Trying |
+| ISDN interworking | | | |
+| SETUP | → | → | INVITE |
+| | | ← | 100 Trying |
+
+**Apply post test routine**
+
+| TSS
Orig_Timers | TP_205_008 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--------------------------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|----------------------|---------------|--|---|-----|--|--|--|--|---|---------------|--|---|-----|--------------------------|--|--|-------|---|----------|--|----------------------|---------------|--|---|-----|--|--|--|--|---|---------------|--|---|-----|
+| Test purpose
486 received, timer D is started ACK is repeated
Ensure that the IUT, when an INVITE client transaction is in the Completed state, on receipt of final responses that matches the transaction, still answer with an ACK request until timer D set to at least 32 second expires if an unreliable transport is used.
Message flow
| End device | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| Start timer D ➔ | 486 Busy Here |
| ➔ | ACK |
| | |
| ➔ | 486 Busy Here |
| ➔ | ACK |
| ISDN interworking |
| SETUP | ➔ | ➔ INVITE |
| Start timer D ➔ | 486 Busy Here |
| ➔ | ACK |
| | |
| ➔ | 486 Busy Here |
| ➔ | ACK |
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | Start timer D ➔ | 486 Busy Here | | ➔ | ACK | | | | | ➔ | 486 Busy Here | | ➔ | ACK | ISDN interworking | | | SETUP | ➔ | ➔ INVITE | | Start timer D ➔ | 486 Busy Here | | ➔ | ACK | | | | | ➔ | 486 Busy Here | | ➔ | ACK |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Start timer D ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | ➔ | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Start timer D ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Timers | TP_205_009 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/2 | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--------------------------------------------------------------------|--------------------------------------|--|-------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|----------------------|---------------|--|---|-----|--|--|--|--|---|---------------|
+| Test purpose
486 received, timer D is started ACK is not repeated
Ensure that the IUT, when an INVITE client transaction is in the Completed state, on receipt of a final response that matches the transaction, does not repeat its ACK request if a reliable transport is used.
Message flow
| End device | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | ➔ | INVITE |
| Start timer D ➔ | 486 Busy Here |
| ➔ | ACK |
| | |
| ➔ | 486 Busy Here |
| | | | | End device | Test equipment | Interworking POTS | | | Off hook | | | Dial number | ➔ | INVITE | | Start timer D ➔ | 486 Busy Here | | ➔ | ACK | | | | | ➔ | 486 Busy Here |
+| | End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Start timer D ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ➔ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+
+
+**ISDN interworking**
+
+```
+
+SETUP → → INVITE
+ Start timer D ← 486 Busy Here
+ → ACK
+ ← 486 Busy Here
+
+```
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_010 | Reference
section 17.1.1.1 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+
+**Test purpose**
+*486 repeated Via with different values, ACK is not sent*
+
+Ensure that the IUT, when an INVITE client transaction is in the Completed state, on receipt of new final responses with different Via branch parameter value, does not repeat its ACK request until timer D set to at least 32 second expires if an unreliable transport is used.
+
+**SIP header values**
+
+486 1
+ Via: ;branch=
+
+486 2
+ Via: ;branch=
+
+
+
+**Message flow**
+
+| End device | | Test equipment |
+|--------------------------------|---------------|-------------------|
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | | → INVITE |
+| | Start timer D | ← 486 Busy Here 1 |
+| | | → ACK |
+| | | ← 486 Busy Here 2 |
+| ISDN interworking | | |
+| SETUP | → | → INVITE |
+| | Start timer D | ← 486 Busy Here 1 |
+| | | → ACK |
+| | | ← 486 Busy Here 2 |
+| Apply post test routine | | |
+
+| TSS
Orig_Timers | TP_205_011 | Reference
section 13.2.2.4 and
Annex A of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------|----------------------|------------|----------------|--------------------------|--|----------|--|-------------|----------|---------------------|-----------------|--|-------|--|--|--|-----------------|--|-------|--------------------------|--|---------|----------|---------------------|-----------------|--|-------|--|--|--|-----------------|--|-------|--------------------------------|--|
+| Test purpose
200 OK received, ACK is sent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, when an INVITE client transaction has been in the Terminated state, on receipt of a retransmitted Success (200 OK) response sends an ACK request until $64*T1$ duration expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| Interworking POTS |
| Off hook | |
| Dial number | → INVITE |
| Start timer | ← 200 OK INVITE |
| → ACK |
| |
| ← 200 OK INVITE |
| → ACK |
| ISDN interworking |
| SETUP → | → INVITE |
| Start timer | ← 200 OK INVITE |
| → ACK |
| |
| ← 200 OK INVITE |
| → ACK |
| Apply post test routine |
| | | | End device | Test equipment | Interworking POTS | | Off hook | | Dial number | → INVITE | Start timer $64*T1$ | ← 200 OK INVITE | | → ACK | | | | ← 200 OK INVITE | | → ACK | ISDN interworking | | SETUP → | → INVITE | Start timer $64*T1$ | ← 200 OK INVITE | | → ACK | | | | ← 200 OK INVITE | | → ACK | Apply post test routine | |
+| End device | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Start timer $64*T1$ | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Start timer $64*T1$ | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Apply post test routine | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Timers | TP_205_012 | Reference
section 13.2.2.4 and
Annex A of
[IETF RFC 3261] | Selection expression | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------|----------------------|------------|----------------|--------------------------|--|----------|--|-------------|----------|---------------------|-----------------|--|-------|--|--|-----------------|--|--|-----------------|
+| Test purpose
Timeout ACK is not repeated | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, when an INVITE client transaction has been in the Terminated state, after $64*T1$ duration expires, on receipt of a retransmitted Success (200 OK) response does not send an ACK request. | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | Test equipment |
| Interworking POTS |
| Off hook | |
| Dial number | → INVITE |
| Start timer | ← 200 OK INVITE |
| → ACK |
| |
| Timeout | |
| ← 200 OK INVITE |
| | | | End device | Test equipment | Interworking POTS | | Off hook | | Dial number | → INVITE | Start timer $64*T1$ | ← 200 OK INVITE | | → ACK | | | Timeout $64*T1$ | | | ← 200 OK INVITE |
+| End device | Test equipment | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → INVITE | | | | | | | | | | | | | | | | | | | | |
+| Start timer $64*T1$ | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | |
+| | → ACK | | | | | | | | | | | | | | | | | | | | |
+| | | | | | | | | | | | | | | | | | | | | | |
+| Timeout $64*T1$ | | | | | | | | | | | | | | | | | | | | | |
+| | ← 200 OK INVITE | | | | | | | | | | | | | | | | | | | | |
+
+| | | |
+|--------------------------------|-------------------|-----------------|
+| ISDN interworking | | |
+| SETUP | → | → INVITE |
+| | Start timer 64*T1 | ← 200 OK INVITE |
+| | | → ACK |
+| | Timeout 64*T1 | ← 200 OK INVITE |
+| Apply post test routine | | |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_013 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+
+| |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
BYE was sent start timer E; on timeout timer E the BYE is repeated |
+| Ensure that the IUT, having sent a BYE request on an established dialog, repeats its request after timer E set to T1 value expires if an unreliable transport is used. |
+
+| Message flow | |
+|--------------------------|-------------------------------------------------------|
+| End device | Test equipment |
+| Interworking POTS | |
+| Off hook | |
+| Dial number | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK |
+| On hook | Start timer E → BYE
Timeout timer E → BYE |
+| ISDN interworking | |
+| SETUP | → INVITE |
+| ALERTING | ← 180 Ringing |
+| CONNECT | ← 200 OK INVITE
→ ACK |
+| DISCONNECT | → Start timer E → BYE
Timeout timer E → BYE |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_014 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+
+| |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
BYE is repeated after timeout 2 x timer E |
+| Ensure that the IUT, having transmitted a BYE request on an established dialogue, repeats its request after timer E set to the MIN(2*T1,T2) value expires if an unreliable transport is used. |
+
+| |
+|--------------------------|
+| SIP header values |
+|--------------------------|
+
+| Message flow | | |
+|--------------------------|---------------------------------------------------------------------------------|-------------------------------------------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK |
+| On hook | Start timer E
Timeout timer E
Start timer E 2*T1 +T2
Timeout timer E | → BYE
→ BYE
→ BYE |
+| ISDN interworking | | |
+| SETUP | → | → INVITE |
+| ALERTING | ← | ← 180 Ringing |
+| CONNECT | ← | ← 200 OK INVITE
→ ACK |
+| DISCONNECT | → Start timer E
Timeout timer E
Start timer E 2*T1 +T2
Timeout timer E | → BYE
→ BYE
→ BYE |
+
+| | | | |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_015 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+|--------------------|------------|--------------------------------------------------------------------|--------------------------------------|
+
+| |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
BYE is repeated after timeout 3 x timer E |
+| Ensure that the IUT, having transmitted three times a BYE request on an established dialogue, repeats its request after timer E set to the MIN(4*T1,T2) value expires, if an unreliable transport is used. |
+
+| |
+|--------------------------|
+| SIP header values |
+|--------------------------|
+
+| Message flow | | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
+| | End device | Test equipment |
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | | → INVITE
← 180 Ringing
← 200 OK INVITE
→ ACK |
+| On hook | Start timer E
Timeout timer E
Start timer E 2*T1 +T2
Timeout timer E
Start timer E 4*T1+T2
Timeout timer E | → BYE
→ BYE
→ BYE
→ BYE |
+
+| | | |
+|--------------------------------|------------------------|-----------------|
+| ISDN interworking | | |
+| SETUP | → | → INVITE |
+| ALERTING | ← | ← 180 Ringing |
+| CONNECT | ← | ← 200 OK INVITE |
+| | | → ACK |
+| DISCONNECT | → | → BYE |
+| | Start timer E | |
+| | Timeout timer E | → BYE |
+| | Start timer E 2*T1 +T2 | |
+| | Timeout timer E | → BYE |
+| | Start timer E 4*T1+T2 | |
+| | Timeout timer E | → BYE |
+| Apply post test routine | | |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------|--------------------------------------|
+| TSS
Orig_Timers | TP_205_016 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.1.2/1 |
+| Test purpose | | | |
+| Timeout timer F, the BYE is not repeated | | | |
+| Ensure that the IUT does not repeat a BYE request on an established dialogue after timer F set to 64*T1 expires, if an unreliable transport is used. | | | |
+| SIP header values | | | |
+| Message flow | | | |
+| | End device | | Test equipment |
+| Interworking POTS | | | |
+| Off hook | | | |
+| Dial number | | | → INVITE |
+| | | | ← 180 Ringing |
+| | | | ← 200 OK INVITE |
+| | | | → ACK |
+| On hook | | Start timer F | → BYE |
+| | | Timeout timer F | |
+| ISDN interworking | | | |
+| SETUP | → | | → INVITE |
+| ALERTING | ← | | ← 180 Ringing |
+| CONNECT | ← | | ← 200 OK INVITE |
+| | | | → ACK |
+| DISCONNECT | → | Start timer F | → BYE |
+| | | Timeout timer F | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------|-------------------------------------|-------------------|--|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|-------------|---------|---------------|---|-----|--|-----------------|---|-----|--------------------------|--|--|--|-------|---|---|--------|----------|---|---|-------------|------------|---|-------------------|-----|--|--|---------------------|-----|
+| TSS
Orig_Timers | TP_205_017 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.2/18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
BYE is sent and timer E is started; on timeout timer E, the BYE is repeated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, when a BYE client transaction is in the Proceeding state , repeats its BYE request after timer E set to T1 value expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | | |
| Dial number | | → | INVITE |
| | ← | 180 Ringing |
| On hook | Start timer E | → | BYE |
| Timeout timer E | → | BYE |
| ISDN interworking |
| SETUP | → | → | INVITE |
| ALERTING | ← | ← | 180 Ringing |
| DISCONNECT | → | Start timer E → | BYE |
| | Timeout timer E → | BYE |
| | | | End device | | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | → | INVITE | | | ← | 180 Ringing | On hook | Start timer E | → | BYE | | Timeout timer E | → | BYE | ISDN interworking | | | | SETUP | → | → | INVITE | ALERTING | ← | ← | 180 Ringing | DISCONNECT | → | Start timer E → | BYE | | | Timeout timer E → | BYE |
+| End device | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| On hook | Start timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Timeout timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DISCONNECT | → | Start timer E → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | Timeout timer E → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------------------------------------------------------------------|-------------------------------------|-------------------|--|--|-----------------------|--------------------------|--|--|--|----------|--|--|--|-------------|--|---|--------|--|--|---|-------------|---------|---------------|---|-----|--|-----------------|---|-----|--|------------------|---|-----|--|-----------------|---|-----|--------------------------|--|--|--|-------|---|---|--------|----------|---|-------------------|-----|------------|---|---------------------|-----|--|--|----------------------|-----|--|--|---------------------|-----|
+| TSS
Orig_Timers | TP_205_018 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.2/18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Test purpose
BYE is repeated after timeout 2 x timer E | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, when a BYE client transaction is in the Proceeding state and BYE request have been already repeated in this state, repeats its BYE request after timer E set to T2 value expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | | |
| Dial number | | → | INVITE |
| | ← | 180 Ringing |
| On hook | Start timer E | → | BYE |
| Timeout timer E | → | BYE |
| Start timer E T2 | → | BYE |
| Timeout timer E | → | BYE |
| ISDN interworking |
| SETUP | → | → | INVITE |
| ALERTING | ← | Start timer E → | BYE |
| DISCONNECT | → | Timeout timer E → | BYE |
| | Start timer E T2 → | BYE |
| | Timeout timer E → | BYE |
| | | | End device | | | Test equipment | Interworking POTS | | | | Off hook | | | | Dial number | | → | INVITE | | | ← | 180 Ringing | On hook | Start timer E | → | BYE | | Timeout timer E | → | BYE | | Start timer E T2 | → | BYE | | Timeout timer E | → | BYE | ISDN interworking | | | | SETUP | → | → | INVITE | ALERTING | ← | Start timer E → | BYE | DISCONNECT | → | Timeout timer E → | BYE | | | Start timer E T2 → | BYE | | | Timeout timer E → | BYE |
+| End device | | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| On hook | Start timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Timeout timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Start timer E T2 | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Timeout timer E | → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | Start timer E → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DISCONNECT | → | Timeout timer E → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | Start timer E T2 → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | Timeout timer E → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Timers | TP_205_019 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.2/18 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------|-------------------------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|--|---|-------------|---------|-----------------|-----|--|-----------------|--|--------------------------|--|--|-------|---|--------|----------|---|-------------|------------|-------------------|-----|--|-----------------|--|
+| Test purpose
BYE is nit repeated after timeout timer F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, when a BYE client transaction is in the Proceeding state , does not repeat a BYE request on an established dialogue, after timer F set to 64*T1 expires. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | → | INVITE |
| ← | 180 Ringing |
| On hook | Start timer F → | BYE |
| Timeout timer F | |
| ISDN interworking |
| SETUP | → | INVITE |
| ALERTING | ← | 180 Ringing |
| DISCONNECT | → Start timer F → | BYE |
| Timeout timer F | |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | | ← | 180 Ringing | On hook | Start timer F → | BYE | | Timeout timer F | | ISDN interworking | | | SETUP | → | INVITE | ALERTING | ← | 180 Ringing | DISCONNECT | → Start timer F → | BYE | | Timeout timer F | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| On hook | Start timer F → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Timeout timer F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ISDN interworking | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SETUP | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| ALERTING | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| DISCONNECT | → Start timer F → | BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | Timeout timer F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Orig_Timers | TP_205_020 | Reference
section 17.1.2.2 and
Annex A of
[IETF RFC 3261] | Selection expression
PICS 5.2/18 | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------|-------------------------------------|------------|--|----------------|--------------------------|--|--|----------|--|--|-------------|---|--------|---------|-----------------|-----|--|-----------------|--|
+| Test purpose
Timeout timer F, the BYE is not repeated | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, when a BYE client transaction is in the Trying state , considers the transaction terminated after timer F set to 64*T1 duration expires without receiving any final response. | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values | | | | | | | | | | | | | | | | | | | | | |
+| Message flow
| End device | | Test equipment |
| Interworking POTS |
| Off hook | | |
| Dial number | → | INVITE |
| On hook | Start timer F → | BYE |
| Timeout timer F | |
| | | | End device | | Test equipment | Interworking POTS | | | Off hook | | | Dial number | → | INVITE | On hook | Start timer F → | BYE | | Timeout timer F | |
+| End device | | Test equipment | | | | | | | | | | | | | | | | | | | |
+| Interworking POTS | | | | | | | | | | | | | | | | | | | | | |
+| Off hook | | | | | | | | | | | | | | | | | | | | | |
+| Dial number | → | INVITE | | | | | | | | | | | | | | | | | | | |
+| On hook | Start timer F → | BYE | | | | | | | | | | | | | | | | | | | |
+| | Timeout timer F | | | | | | | | | | | | | | | | | | | | |
+
+| | | | |
+|--------------------------|---|---------------|--------|
+| ISDN interworking | | | |
+| SETUP | → | → | INVITE |
+| RELEASE | → | Start timer F | → BYE |
+| Timeout timer F | | | |
+
+#### 7.2.2.5 Abnormal situations
+
+| | | | |
+|---------------------------------|------------|-------------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Abnormal_situations | TP_206_001 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5, of
[IETF RFC 3261] | Selection expression |
+|---------------------------------|------------|-------------------------------------------------------------------------------------------|----------------------|
+
+##### Test purpose
+
+*404 received in calling state; setting of Call-ID, From headers and Request-URI*
+
+Ensure that when the client transaction is in the **Calling state** that on receipt of a Not Found (404 Not Found) response, an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response.
+
+##### SIP header values
+
+INVITE 1 sip: [Request URI] SIP/2.0
+
+Call-ID:
+
+From: ;tag=
+
+ACK 1 sip: [Request URI] SIP/2.0
+
+Call-ID:
+
+From: ;tag=
+
+##### Message flow
+
+| | End device | Test equipment |
+|--------------------------|------------|-----------------|
+| Interworking POTS | | |
+| Off hook | | |
+| Dial number | → | INVITE 1 |
+| Busy tone | ← | 404 Not Found |
+| On hook | → | ACK 1 |
+| ISDN interworking | | |
+| SETUP | → | INVITE 1 |
+| DISCONNECT | ← | 404 Not Found 1 |
+| RELEASE | → | ACK 1 |
+| RELEASE COMPLETE | ← | |
+
+| | | | |
+|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|
+| TSS
Orig_Abnormal_situations | TP_206_002 | Reference
sections 13.2.2.3, 17.1.1.2,
17.1.1.3 and Figure 5 of
[IETF RFC 3261] | Selection expression |
+|---------------------------------|------------|------------------------------------------------------------------------------------------|----------------------|
+
+##### Test purpose
+
+*404 received in proceeding state; setting of Call-ID, From headers and Request-URI*
+
+Ensure that when the client transaction is in the **Proceeding state**, that on receipt of a Not Found (404 Not Found) response, an ACK request is sent with the same Call-ID, From headers and Request-URI as in the original INVITE request and the same Tag in the To header as in this response.
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------|-----------------------|--------------------------|--|--|----------|--|--|-------------|---|----------|--|---|----------------------|-----------|---|---------------|---------|---|-------|------------------------------|--|--|-------|---|----------|-----------------|---|----------------------|------------|---|-----------------|---------|---|-------|------------------|---|--|
+| SIP header values
INVITE 1 sip: [Request URI] SIP/2.0
Call-ID:
From: ;tag=
404 1
To: ;tag=
ACK 1 sip: [Request URI] SIP/2.0
Call-ID:
From: ;tag=