SIST-TS TS 101 335 V4.1.1:2004

• Abstract:

  The scope of the WI is to define interoperability test specifications for the following scenarios: - PC to PC - PC to Phone - Phone to PC - Phone to Phone This document is a revision of TS 101 335 Version 2.1.1

• Status: Published
• Publication Date: 31-Mar-2004
• ICS: 33.020 - Telecommunications in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2004
• Due Date: 01-Apr-2004
• Completion Date: 01-Apr-2004
• Ref Project: ETSI TS 101 335 V4.1.1 (2001-10) - Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Release PICS; Interoperability test

SIST-TS TS 101 335 V4.1.1:2004 is the Slovenian adoption of ETSI TS 101 335 V4.1.1 for TIPHON Release 3 interoperability testing. It specifies test cases for H.323-based voice and call control across IP and SCN scenarios, so vendors, test labs, and network teams can check how terminals, telephones, gateways, and gatekeepers work together.

What does SIST-TS TS 101 335 V4.1.1:2004 specify?

SIST-TS TS 101 335 V4.1.1:2004 specifies interoperability test specifications for PC to PC, PC to Phone, Phone to PC, Phone to Phone using IP, and PC to PC using the SCN. In practice, it defines how to exercise common TIPHON call setups and failures across packet and switched-circuit networks.

The document is organized into scope, references, abbreviations, test strategy, overview, prerequisites, test parameters, configurations, and one informative bibliography annex. Clause 8 then breaks the tests into four configuration families: Terminal to Terminal, Terminal to Telephone, Telephone to Telephone using IP Network, and Terminal to Terminal using SCN Network. That structure matters because each family uses a different route, different signaling roles, and different expected call outcomes.

What are the key requirements of SIST-TS TS 101 335 V4.1.1:2004?

The standard is built around interoperability testing after product and system testing has already been completed. Clause 4 says the vendor should first use its own procedures and the TIPHON conformance test standards in TS 101 804 (all parts) and TS 101 890 (all parts), and that speech quality testing is a separate activity in TS 101 329-5. For a test program, that means this document is for call-flow interoperability, not for replacing conformance or voice-quality validation.

Core IP-side prerequisites

Clause 6.1 sets the baseline IP behavior for the test cases. H.323 version 3 and TS 101 319 shall be used, H.225.0 version 3 Fast Connect shall be used for all calls, and H.245 version 6 tunnelling shall be used whenever H.245 messages are exchanged. Gatekeeper Routed Signalling is mandatory.

These rules matter because they define the signaling model the tests expect. H.323 terminals register with a Gatekeeper using an E.164 alias only, gateways register using prefixes only, and endpoints shall support the keep alive procedure. For Fast Connect calls, the SETUP message shall include the fastStart parameter, and the fast parameter shall appear in exactly one message up to and including CONNECT.

SCN-side routing assumptions

Clause 6.2 separates SCN behavior into UNI and (P)NNI cases. If the SCN interface is UNI, the gateway may act as the user side or the network side. If the interface is (P)NNI, the gateway or two gateways connected by IP can either transfer SCN signaling transparently across IP or interwork signaling between SCN and IP transit nodes.

In practice, this tells the reader which kind of gateway role to set up before testing. The standard expects (P)NNIs to sit between originating, transit, and terminating network nodes, so the lab topology has to match the network interface under test.

Test parameters that change from case to case

Clause 7 says the audio codec is a selectable parameter, and the selected codec must be specified before the test. The listed codecs are G.711, G.723.1, G.729, GSM Full Rate, and GSM Half Rate. That matters because the same call flow can be rerun with different media encodings.

Clause 7.2 says the number of intermediate Gatekeepers is also a test parameter. The tests can run with one or more Gatekeepers, and the description must be extended if more than two Gatekeepers are involved. If only one Gatekeeper participates, the not relevant lines are marked n.a. in the succeeded column.

The main scenario families

Clause 8 groups the interoperability checks into four topologies:

• Terminal to Terminal
• Terminal to Telephone
• Telephone to Telephone using IP Network
• Terminal to Terminal using SCN Network

Across these families, the document checks successful calls, failed calls, alerting, release handling, media exchange, and Fast Connect fallback to H.245 tunnelling. That is important because it verifies not only call setup but also what users hear, when media becomes available, and how the system behaves when a destination is not registered or cannot be terminated.

What the call-flow tests verify

The detailed procedures in clause 8 show ARQ, ACF, LRQ, LCF, LRJ, ARJ, SETUP, ALERT, CONNECT, RELEASE_COMPLETE, DRQ, and call disestablishment handling. Successful call cases confirm registration, address resolution, routing across Gatekeepers, and media exchange. Unsuccessful cases check that the user gets a failure indication when a terminal or number is unknown or when the SCN cannot terminate the call.

Several tests also exercise Fast Connect fallback to H.245 tunnelling. In those cases, the calling side includes fastConnect, the called side does not return fastStart, and the call is established through an H.225.0 tunnel for H.245. For a developer or tester, that means the system must still complete the call setup when the preferred fast path is not available.

What terms does SIST-TS TS 101 335 V4.1.1:2004 define?

• ACF (Admissions Confirm) - A gatekeeper response that allows the call to proceed.
• ARQ (Admissions Request) - The request sent to a gatekeeper before a call can be admitted.
• ARJ (Admissions Reject) - The negative gatekeeper response when a call is not admitted.
• LRQ (Location Request) - A request between Gatekeepers to find the called party.
• LCF (Location Confirm) - The positive answer to an LRQ.
• LRJ (Location ReJect) - The negative answer to an LRQ, often used when the number or endpoint cannot be found.
• DRQ (Disengage Request) - The message used to release resources after call termination.
• SCN (Switched Circuit Networks) - The switched-network side used in the scenarios where IP interworks with circuit-switched telephony.

Who uses SIST-TS TS 101 335 V4.1.1:2004?

SIST-TS TS 101 335 V4.1.1:2004 is used by H.323 terminal vendors, gateway vendors, Gatekeeper implementers, interoperability test labs, and telecom quality teams. It is especially relevant where IP voice systems must interoperate with telephone networks or other SCN elements.

The test strategy in clause 4 shows the intended users: organizations that have already done their own product testing and TIPHON conformance testing, and now need interoperability checks against other implementations. In practice, buyers and quality managers use it to confirm that a product can register, route calls, exchange media, and handle failures in the same way as another TIPHON-compliant product.

What changed in SIST-TS TS 101 335 V4.1.1:2004 from the previous edition?

This document is a revision of TS 101 335 Version 2.1.1.

Which standards are used with SIST-TS TS 101 335 V4.1.1:2004?

Clause 2 names the standards and specifications that support this test plan:

• ETSI TS 101 319 - provides signaling for basic calls from an H.323 terminal to a terminal in an SCN.
• ETSI TS 101 804 (all parts) - provides TIPHON Release PICS material used before interoperability testing.
• ETSI TS 101 329-5 - provides QoS measurement methodologies, kept separate from interoperability testing.
• ETSI TS 101 890 (all parts) - another TIPHON Release PICS reference used with the test framework.
• ITU-T Recommendation H.323 - defines the packet-based multimedia communication system under test.
• ITU-T Recommendation H.225.0 - defines call signaling protocols and media stream packetization.
• ITU-T Recommendation E.164 - supplies the numbering plan used for addressing.
• ITU-T Recommendation G.711, G.723.1, and G.729 - define the audio codecs selected as test parameters.
• ITU-T Recommendation H.245 - defines the control protocol for multimedia communication.

What does the SIST-TS TS 101 335 V4.1.1:2004 document contain?

The document contains a set of configuration drawings and step-by-step call-flow tables for the main TIPHON scenarios. Figures 1 to 4 show the basic topologies, including terminal-to-terminal, terminal-to-telephone, telephone-to-telephone using IP, and terminal-to-terminal using SCN.

Tables 1, 4, 11, and 14 summarize the scenario families, directions, test flow references, and extra features such as Fast Connect fallback or H.245 tunnelling. Tables 2 to 16 then expand those cases into procedural actions that cover registration, routing, alerting, media exchange, release, and failure handling. Annex A provides the bibliography, and the history section records the publication versions.

SLOVENSKI STANDARD
01-april-2004
Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 3.
izdaja - Izdaja PICS - Preskus medobratovalnosti
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON)
Release 3; Release PICS; Interoperability test
Ta slovenski standard je istoveten z: TS 101 335 Version 4.1.1
ICS:
33.020 Telekomunikacije na splošno Telecommunications in
general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Technical Specification
Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON) Release 3;
Release PICS;
Interoperability test
2 ETSI TS 101 335 V4.1.1 (2001-10)

Reference
RTS/TIPHON-06015
Keywords
IP, protocol, testing, VoIP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2001.
All rights reserved.
ETSI
3 ETSI TS 101 335 V4.1.1 (2001-10)
Contents
Intellectual Property Rights.4
Foreword.4
Introduction .4
1 Scope.5
2 References.5
3 Abbreviations.6
4 Test Strategy.6
5 Overview.6
6 Prerequisites.7
6.1 IP related.7
6.2 SCN related.7
7 Parameter for each test .8
7.1 Audio Codec.8
7.2 Number of intermediate Gatekeepers.8
8 Configurations.8
8.1 Terminal to Terminal.8
8.1.1 Successful call from a H.323 Terminal to another H.323 Terminal .9
8.1.2 Unsuccessful call from H.323 Terminal to another H.323 Terminal.9
8.1.3 Fast Connect Fallback to H.245 tunnelling.10
8.2 Terminal to Telephone .10
8.2.1 Successful call from a H.323 Terminal to a Telephone .11
8.2.2 Successful call from a Telephone to a H.323 Terminal .12
8.2.3 Unsuccessful Call from a Terminal to an "unknown SCN Number".12
8.2.4 Unsuccessful call with voice after DISCONNECT .13
8.2.5 Unsuccessful call with voice before connect .14
8.2.6 Unsuccessful Call from a Telephone to an "unknown IP Number".14
8.2.7 Fast Connect Fallback to H.245 tunnelling.15
8.3 Telephone to Telephone using IP Network .15
8.3.1 Successful call from a Telephone to a Telephone using IP Network.16
8.3.2 Unsuccessful call from a Telephone to a Telephone using IP Network.17
8.3.3 Fast Connect Fallback to H.245 tunnelling.17
8.4 Terminal to Terminal using SCN Network .17
8.4.1 Successful call from a H.323 Terminal to a H.323 Terminal using SCN Network .18
8.4.2 Unsuccessful call from a H.323 Terminal to a H.323 Terminal using SCN Network .18
Annex A (informative): Bibliography .20
History .21

ETSI
4 ETSI TS 101 335 V4.1.1 (2001-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://www.etsi.org/legal/home.htm).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON).
Introduction
The present document describes interoperability and compatibility tests for ITU-T Recommendation H.323 [5] entities
concerning the different TIPHON scenarios. It is not intended to provide an exhaustive testing of all facets of
ITU-T Recommendation H.323 [5] and SCN operation. Specific configurations were chosen to provide coverage of the
more common commercial deployments.
The test cases specified in this test plan must be performed on many different platforms. Therefore, specific details on
how to perform each test are not included, only instructions on what information must be exchanged are included.
ETSI
5 ETSI TS 101 335 V4.1.1 (2001-10)
1 Scope
The present document defines the interoperability test specifications for the following scenarios:
• PC to PC;
• PC to Phone;
• Phone to PC;
• Phone to Phone using IP;
• PC to PC using the SCN.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
[1] ETSI TS 101 319: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON); Signalling for basic calls from a H.323 terminal to a terminal in a Switched-Circuit
Network (SCN)".
[2] ETSI TS 101 804 (all parts): "Telecommunications and Internet protocol Harmonization Over
Networks (TIPHON) Release 3; Release PICS".
[3] ETSI TS 101 329-5: "Telecommunications and Internet protocol Harmonization Over Networks
(TIPHON) Release 3; Technology Compliance Specification; Part 5: Quality Of Service (QoS)
measurement methodologies".
[4] ETSI TS 101 890 (all parts): "Telecommunications and Internet protocol Harmonization Over
Networks (TIPHON) Release 3; Release PICS".
[5] ITU-T Recommendation H.323 (1999): "Packet-based multimedia communications systems" (See
note).
[6] ITU-T Recommendation H.225.0 (1999): "Call signalling protocols and media stream
packetization for packet-based multimedia communication systems".
[7] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[8] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies".
[9] ITU-T Recommendation G.723.1 (1996): "Dual rate speech coder for multimedia communications
transmitting at 5,3 and 6,3 kit/sec".
[10] ITU-T Recommendation G.729: "Coding of speech at 8 kbit/s using conjugate structure algebraic-
code-excited linear-prediction (CS-ACELP)".
[11] ITU-T Recommendation H.245 (1999): "Control protocol for multimedia communication" (See
note).
NOTE: The Interoperability Testing can be performed for any version of H.323, but this specification is
applicable for the versions defined in clause 6.1 of the present document.
ETSI
6 ETSI TS 101 335 V4.1.1 (2001-10)
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
A Audio
ACF Admissions Confirm
ARJ Admissions Reject
ARQ Admissions Request
D Data
DRQ Disengage Request
GSM Global System for Mobile communications
IE Information Element
IP Internet Protocol
ISDN Intergrated Service Digital Networks
LCF Location Confirm
LRJ Location ReJect
LRQ Location Request
(P)NNI (Private) Network to Network Interface
PSTN Public Switched Telephone Network
QoS Quality of Service
SCN Switched Circuit Networks
UNI User-Network Interface
4 Test Strategy
The purpose of interoperability testing is to test compatibility with other products, which use the same TIPHON
specifications.
Interoperability testing should be performed after a vendor has completed product and system testing with its own test
procedures and/or using the TIPHON Conformance Test standards as defined in TS 101 804 (all parts) [2] and
TS 101 890 (all parts) [4].
When performing interoperability testing for Signalling, the vendor's test procedures should include those contained in
the present document.
Speech Quality Testing is considered to be a separate activity and is not a part of interoperability testing. TIPHON
Speech Quality Testing procedures are defined in TS 101 329-5 [3].
5 Overview
For set up of equipment, the present document uses a number of basic configurations. These are used to run a certain
number of tests.
The basic configurations are:
1) Terminal to Terminal;
2) Telephone to Terminal;
3) Telephone to Telephone using IP as a transit Network;
4) Terminal to Terminal using SCN as a transit Network.
Using these test configurations a number of different tests are performed. For example a call first from the Telephone to
the Terminal and then the other way around or using different codex.
These tests can include a variety of special features like FastConnect, or QoS.
The number of Gatekeepers involved in these configurations depends on the actual executed test.
ETSI
7 ETSI TS 101 335 V4.1.1 (2001-10)
All the call flows shown in the tables are an example flows that should be followed if possible. In some cases not all the
described messages occur.
6 Prerequisites
6.1 IP related
The following prerequisites are taken from TIPHON specifications:
• ITU-T Recommendation H.323 [5] (version 3, 1999) and TS 101 319 [1] shall be used;
• ITU-T Recommendation H.225.0 [6] (version 3, 1999) Fast Connect shall be used for all calls;
• ITU-T Recommendation H.245 [11] (version 6, 1999) Tunnelling shall be used whenever H.245 messages are
exchanged;
• Gatekeeper Routed Signalling is mandatory;
• H.323 Terminals shall register to the Gatekeeper using an ITU-T Recommendation E.164 [7] alias only;
• Gateways shall register to the Gatekeeper using Prefixes only;
• Endpoints shall support the keep Alive procedure as specified in clauses 6.2.2 and 7.4.2 of
ITU-T Recommendation H.323 [5];
• When Fast Connect procedure is used, the SETUP Message shall include the fastStart Parameter, and the fast
parameter shall be returned in exactly one message up to and including the CONNECT Message.
6.2 SCN related
To identify the different types of SCN interfaces the following shall be considered:
• If the SCN interface is an UNI interface, the gateway can play either the "role" of the user or of the network side.
• If the SCN interface is an (P)NNI interface, the gateway (or two gateways connected by the IP) can offer two
types of services in principle:
- transparent transfer of SCN Signalling across IP connections;
- signalling interworking between SCN and IP "transit nodes".
• (P)NNIs are located between Originating, Transit and Terminating Network nodes.
ETSI
8 ETSI TS 101 335 V4.1.1 (2001-10)
7 Parameter for each test
There are some extra parameters that can be selected for each test:
7.1 Audio Codec
As TIPHON is not only focussing on the call establishment but also on the Media stream, the audio Codec should be an
extra parameter that should vary from test to test:
Here is a list of all Codec that are defined in ETSI TIPHON:
• ITU-T Recommendation G.711 [8];
• ITU-T Recommendation G.723.1 [9];
• ITU-T Recommendation G.729 [10];
• GSM Full Rate;
• GSM Half Rate.
Which Codec is selected should be specified prior to the test.
7.2 Number of intermediate Gatekeepers
All tests can be executed with one or more Gatekeepers. The Number of Gatekeepers is just another parameter for these
tests.
The description has to be extended accordingly, if more than 2 Gatekeepers are involved.
If only one Gatekeeper is participating in a scenario, simply mark the not relevant lines of the table with n.a. in the
succeeded column and simply ignore them.
8 Configurations
8.1 Terminal to Terminal
IP
(RTP/RTCP)
B1
A1
IP
IP
IP
Gatekeeper B
Gatekeeper A
NOTE: Gatekeeper B is only present in specific test cases.
Figure 1: Terminal to Terminal
ETSI
9 ETSI TS 101 335 V4.1.1 (2001-10)
All tests can be executed with one or more Gatekeepers. The Number of Gatekeepers is just another parameter for these
tests.
Table 1: Terminal to Terminal
Direction Description Test Flow Extra feature Comment
A1 →→→→ B1 Successful call 8.1.1 Fast connect TIPHON Scenario 0
Successful call 8.1.1 Fast connect TIPHON Scenario 0
B1 →→→→ A1
A1 →→→→ B1 Successful call 8.1.3 Fast connect TIPHON Scenario 0
fallback
B1 →→ A1 Successful call 8.1.3 Fast connect TIPHON Scenario 0
→→
fallback
Basic unsuccessful call 8.1.2 TIPHON Scenario 0
A1 →→→→ D
Basic unsuccessful call
B1 →→→→ D 8.1.2 TIPHON Scenario 0

8.1.1 Successful call from a H.323 Terminal to another H.323 Terminal
This test verifies the TIPHON Scenario-0 service where the Originating Terminal and the Terminating Terminal are
registered with the same Gatekeeper or where the two Gatekeepers have a trusted relationship.
Table 2: Successful call from a H.323 Terminal to another H.323 Terminal
No. Action Succeeded
1 Both Terminal A1 and the Terminal B1 shall register with their respective Gatekeeper(s).
2 Terminal A1 initiates a call using an E.164 address.
3 Terminal A1 sends ARQ to Gatekeeper A.
4 Gatekeeper A issues LRQ (uni/multicast) to Gatekeeper B (see note).
5 Gatekeeper B returns LCF(see note).
6 Gatekeeper A returns ACF.
7 Terminal A1 sends SETUP its Gatekeeper (including fast connect options).
8 Gatekeeper A forwards SETUP to Gatekeeper B(see note).
9 Gatekeeper B forwards SETUP to Terminal B1.
10 Terminating Terminal B1 performs ARQ/ACF sequence.
11 Terminal B1 sends an ALERT Message back.
12 The User at Terminal A1 should be informed that the other Terminal is alerting.
13 After Terminal B1 has accepted the call, the CONNECT message should travel back to the
originating Terminal A1.
14 Media is exchanged and Media connection is evaluated.
15 Terminal A1 terminates the call and
sends a RELEASE_COMPLETE and a DRQ to its Gatekeeper.
16 The Gatekeeper(s) forward(s) the RELEASE_COMPLETE to the Terminal B1.
17 The User at Terminal B1 should be informed that the remote peer terminated the call.
18 The Terminal B1 should send the DRQ to its Gatekeeper.
NOTE: Only present if this test is run with two Gatekeepers.

8.1.2 Unsuccessful call from H.323 Terminal to another H.323 Terminal
This test verifies the TIPHON Scenario-0 service where the Originating Terminal and the Terminating Terminal should
be registered with the same Gatekeeper or where the two Gatekeepers have a trusted relationship, but the connection
fails as the Terminating Terminal is not registered.
ETSI
10 ETSI TS 101 335 V4.1.1 (2001-10)
Table 3: Unsuccessful call from H.323 Terminal to another H.323 Terminal
No. Action Succeeded
1 Both Terminal A1 and the Terminal B1 should register with their respective Gatekeeper(s).
2 Terminal A1 initiates a call using a E.164 address.
3 Terminal A1 sends ARQ to Gatekeeper A.
4 Gatekeeper A issues LRQ (uni/multicast) to Gatekeeper B (see note).
5 Gatekeeper B returns LRJ (see note).
6 Gatekeeper A returns ARJ.
7 The user should be informed that the call failed indicating the cause.
NOTE: Only present if this test is run with two Gatekeepers.

If there are three Gatekeepers involved, the procedure should be extended accordingly.
8.1.3 Fast Connect Fallback to H.245 tunnelling
This test verifies the support of fallback for the Fast Connect Procedure.
The calling party shall include the fast Connect parameter in the setup message and set the H245 Tunnelling to TRUE.
The called party shall not include the fastStart IE in any message but set the H245Tunneling to TRUE. As a result, the
call has to be established using an H.225.0 tunnel for the H.245 connection.
The high-level call flow is described in clause 8.1.1.
8.2 Terminal to Telephone
IP
SCN
(RTP/RTCP)
Gateway B1
Telephone
Terminal A1 IP
IP
IP
Gatekeeper A
Gatekeeper B
NOTE: Gatekeeper B is only present in specific test cases.
Figure 2: Terminal-to-Telephone
All tests can be executed with one or more Gatekeepers. The number of Gatekeepers is just another parameter for these
tests.
Table 4: Terminal to Telephone
Direction Description Test Flow Extra feature Comment
Successful call 8.2.1 Fast connect TIPHON Scenario 1
A1 →→→→ Tel
Successful call 8.2.2 Fast connect TIPHON Scenario 2
Tel →→→→ A1
A1 →→→→ Tel Successful call 8.2.7 Fast connect TIPHON Scenario 1
fallback
Tel →→→→ A1 Successful call 8.2.7 Fast connect TIPHON Scenario 2
fallback
A1 →→ D Basic unsuccessful call 8.2.3 TIPHON Scenario
...