ETSI EN 301 455-1 V1.1.4 (2000-09)
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless Terminal Incoming Call additional network feature (ANF-CTMI) for the VPN b service entry point; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless Terminal Incoming Call additional network feature (ANF-CTMI) for the VPN b service entry point; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification
DEN/SPS-05194-2
Zasebno omrežje z integriranimi storitvami (PISN) – Signalizacijski protokol med centralami – Dodatna lastnost omrežja za odhodni klic brezvrvičnega terminala (ANF-CTMI) za vstopno točko VPN "b" storitve – 1. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) – Specifikacija
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 301 455-1 V1.1.4:2005
01-januar-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL 3,61 ±6LJQDOL]DFLMVNLSURWRNROPHG
FHQWUDODPL±'RGDWQDODVWQRVWRPUHåMD]DRGKRGQLNOLFEUH]YUYLþQHJDWHUPLQDOD
$1)&70, ]DYVWRSQRWRþNR931EVWRULWYH±GHO =JUDGEDSUHVNXãDOQHJD
QL]DLQQDPHQSUHVNXãDQMD 766 73 ±6SHFLILNDFLMD
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless
Terminal Incoming Call additional network feature (ANF-CTMI) for the VPN b service
entry point; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification
Ta slovenski standard je istoveten z: EN 301 455-1 Version 1.1.4
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST EN 301 455-1 V1.1.4:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 301 455-1 V1.1.4:2005
---------------------- Page: 2 ----------------------
SIST EN 301 455-1 V1.1.4:2005
ETSI EN 301 455-1 V1.1.4 (2000-09)
European Standard (Telecommunications series)
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Cordless Terminal Incoming Call additional network feature
(ANF-CTMI) for the VPN b service entry point;
Part 1: Test Suite Structure and Test Purposes (TSS&TP)
specification
---------------------- Page: 3 ----------------------
SIST EN 301 455-1 V1.1.4:2005
2 ETSI EN 301 455-1 V1.1.4 (2000-09)
Reference
DEN/SPS-05194-2
Keywords
PSS1, DSS1, ANF, QSIG, VPN, testing, mobility,
TSS&TP,CTM,PISN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33 493654716
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://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
editor@etsi.fr
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 2000.
All rights reserved.
ETSI
---------------------- Page: 4 ----------------------
SIST EN 301 455-1 V1.1.4:2005
3 ETSI EN 301 455-1 V1.1.4 (2000-09)
Contents
Intellectual Property Right.4
Foreword.4
1 Scope .5
2 References .5
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations .7
4 Test Suite Structure (TSS).8
5 Test Purposes (TP) .9
5.1 Introduction .9
5.1.1 TP naming convention.9
5.1.2 Source of TP definition.9
5.1.3 TP structure.9
5.1.4 Test strategy.10
5.2 TPs for ANF-CTMI.10
5.2.1 ANF-CTMI signalling procedures.11
5.2.1.1 Actions at the Rerouteing PINX.11
5.2.1.2 Actions at the CTMI-detect PINX .12
5.2.1.2.1 Normal procedures .12
5.2.1.2.2 Exceptional procedures.13
5.2.1.2.3 Rerouteing procedures.14
5.2.1.3 Actions at the Home PINX .14
5.2.1.3.1 Normal procedures .14
5.2.1.3.2 CTMI-detect procedures.15
5.2.1.3.3 Exceptional procedures.16
5.2.1.3.4 Additional procedures .16
5.2.1.4 Actions at the Visitor PINX .17
5.2.2 Protocol Interaction between ANF-CTMI and other Supplementary Services and ANFs.17
5.2.2.1 Interaction with Call Forwarding Unconditional .17
5.2.2.2 Interaction with Call Offer .17
5.2.2.3 Interaction with Do Not Disturb Override .18
5.2.2.4 Interaction with Call Intrusion .18
6 Compliance.19
7 Requirements for a comprehensive testing service .19
Bibliography.20
History .21
ETSI
---------------------- Page: 5 ----------------------
SIST EN 301 455-1 V1.1.4:2005
4 ETSI EN 301 455-1 V1.1.4 (2000-09)
Intellectual Property Right
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/ipr).
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 European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocol and Switching (SPS).
The present document covers the Private Integrated Service Network (PISN) Inter-exchange signalling
protocol - Cordless Terminal Incoming Call Additional Network Feature (ANF-CTMI) - Test Suite Structure and Test
Purposes (TSS&TP) specification.
The present document is part 1 of a multi-part deliverable covering Inter-exchange signalling protocol, as identified
below:
Part 1: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Part 2: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma".
National transposition dates
Date of adoption of this EN: 8 September 2000
Date of latest announcement of this EN (doa): 31 December 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 June 2001
Date of withdrawal of any conflicting National Standard (dow): 30 June 2001
ETSI
---------------------- Page: 6 ----------------------
SIST EN 301 455-1 V1.1.4:2005
5 ETSI EN 301 455-1 V1.1.4 (2000-09)
1 Scope
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the Cordless Terminal
Incoming Call Additional Network Feature (ANF-CTMI) of the Interexchange signalling protocol for Private Integrated
Services Networks (PISN).
The objective of the present document is to provide conformance tests, which give a greater probability of
inter-operability. The TSS&TPs specification covers the procedures described in ETS 300 696 [5].
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [7], ISO/IEC 9646-2 [8] and
ISO/IEC 9646-3 [9]) is used as basis for the test methodology.
The TSS&TPs specification standard is applicable for the support of the Cordless Terminal Incoming Call Additional
Network Feature (ANF-CTMI) at the Q-reference point between Private Integrated Services Network Exchanges
(PINXs) connected together within a PISN. The Test Suite Structure and Test Purposes specified in the present
document are only intended for VPN scenarios at the "b" service entry point.
The Q-reference point is defined in ETS 300 475-1 [16].
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, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
[1] ETSI EN 300 171 (V1.2): "Private Integrated Services Network (PISN); Specification, functional
models and information flows; Control aspects of circuit-mode basic services
[ISO/IEC 11574 (1994) modified]".
[2] ETSI EN 300 172 (V1.4): "Private Integrated Services Network (PISN); Inter-exchange signalling
protocol; Circuit-mode basic services [ISO/IEC 11572 (1996) modified]".
[3] ETSI ETS 300 239 (1993): "Private Telecommunication Network (PTN); Inter-exchange
signalling protocol; Generic functional protocol for the support of supplementary services".
[4] ETSI ETS 300 415 (1996): "Private Integrated Services Network (PISN); Terms and definitions".
[5] ETSI ETS 300 696 (1996): "Private Integrated Services Network (PISN); Inter-exchange
signalling protocol; Cordless Terminal Incoming Call additional network feature".
[6] ETSI ETS 300 695 (1995): "Private Integrated Services Network (PISN); Cordless Terminal
Mobility (CTM); Call handling additional network features; Functional capabilities and
information flows".
[7] ISO/IEC 9646-1 (1994): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 1: General concepts".
[8] ISO/IEC 9646-2 (1994): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 2: Abstract test suite specification".
[9] ISO/IEC 9646-3 (1992): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".
[10] ISO/IEC 11571 (1994): "Information Technology – Telecommunication and information exchange
between systems – Numbering and Sub-addressing in Private Integrated Services Network".
ETSI
---------------------- Page: 7 ----------------------
SIST EN 301 455-1 V1.1.4:2005
6 ETSI EN 301 455-1 V1.1.4 (2000-09)
[11] ISO/IEC 11579-1 (1994): "Information Technology – Telecommunication and information
exchange between systems – Private Integrated Services Network – Part 1: Reference
configurations for PISN exchanges (PINX)".
[12] ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".
[13] ITU-T Recommendation I.210 (1993): "Principles of the telecommunication services supported by
an ISDN and the means to describe them".
[14] ETSI ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[15] ETSI EN 301 060-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service
entry point for Virtual Private Network (VPN) applications; Part 1: Protocol specification".
[16] ETSI ETS 300 475-1 (1995): "Private Telecommunication Network (PTN); Reference
configuration; Part 1: Reference configuration for PTN eXchanges (PTNX)
[ISO/IEC 11579-1 (1994), modified]".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions apply:
abstract test case: Refer to ISO/IEC 9646-1 [7].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [7].
active test: Test case where the IUT is required to send a particular message, but not in reaction to a received message.
This would usually involve the use of PIXIT information to see how this message can be generated and quite often is
specified in an ATS using an implicit send event.
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [7].
implicit send event: Refer to ISO/IEC 9646-3 [9].
lower tester: Refer to ISO/IEC 9646-1 [7].
passive test: Test case where the IUT is required to respond to a protocol event (e.g. received message) with another
protocol event (e.g. send message) which normally does not require any special operator intervention as associated with
the implicit send event.
point of control and observation: Refer to ISO/IEC 9646-1 [7].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [7].
PICS proforma: Refer to ISO/IEC 9646-1 [7].
Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [7].
PIXIT proforma: Refer to ISO/IEC 9646-1 [7].
system under test: Refer to ISO/IEC 9646-1 [7].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [7].
Virtual Private Network (VPN): Refer to EN 301 060-1 [15].
Application Protocol Data Unit (APDU): See ETS 300 239 [3].
Basic Call: Instance of the use of a basic service.
ETSI
---------------------- Page: 8 ----------------------
SIST EN 301 455-1 V1.1.4:2005
7 ETSI EN 301 455-1 V1.1.4 (2000-09)
Basic Service: See ITU-T Recommendation I.210 [13].
Call independent signalling connection: See ETS 300 239 [3], definition 4.7.
Call related: See ETS 300 239 [3], definition 4.9.
Complete Number: See ISO/IEC 11571 [10].
Co-ordination Function: See ETS 300 239 [3].
CTM user: See ETS 300 695 [6].
CTMI-detect PINX: PINX which detects that an incoming call is to a CTM user.
End PINX: See ETS 300 239 [3].
Gateway PINX: See EN 300 172 [2].
Home Data Base (HDB): See ETS 300 415 [4].
Home PINX: See ETS 300 695 [6].
Incoming call: See EN 300 172 [2], subclause 4.4.
Incoming Gateway PINX: See EN 300 172 [2], subclause 4.6.
Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [12], definition 308.
Invoke component: See ETS 300 239 [3], subclause 11.3.3.4.
Originating PINX: See EN 300 172 [2], subclause 4.5.
Private Integrated Services Network (PISN): See ISO/IEC 11579-1 [11].
Private Integrated Services Network Exchange (PINx): See ISO/IEC 11579-1 [11].
PISN Number: See ISO/IEC 11571 [10].
Rerouteing PINX: PINX which executes the rerouteing of the CTMI call to the current Visitor PINX.
Signalling: See ITU-T Recommendation I.112 [12].
Supplementary service: See ITU-T Recommendation I.210 [13], subclause 2.4.
Supplementary Services Control Entity: See ETS 300 239 [3].
Terminating PINX: See EN 300 172 [2], subclause 4.5.
Transit PINX: See EN 300 172 [2], subclause 4.5.
User: See EN 300 171 [1].
Visitor area: See ETS 300 415 [4].
Visitor Data Base (VDB): See ETS 300 415 [4].
Visitor PINX: See ETS 300 695 [6].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ANF Additional Network Feature
ANF-CTMI Cordless Terminal Incoming Call Additional Network Feature
APDU Application Protocol Data Unit
ATS Abstract Test Suite
CTM Cordless Terminal Mobility
ETSI
---------------------- Page: 9 ----------------------
SIST EN 301 455-1 V1.1.4:2005
8 ETSI EN 301 455-1 V1.1.4 (2000-09)
HDB Home Data Base
IE Information Element
ISDN Integrated Services Digital Network
IUT Implementation Under Test
PICS Protocol Implementation Conformance Statement
PINX Private Integrated Services Network eXchange
PISN Private Integrated Services Network
PIXIT Protocol Implementation eXtra Information for Testing
PSS1 Private Integrated Signalling System Number 1
sc call independent signalling connection
SS-CFU Call Forwarding Unconditional supplementary service
SS-CI Call Intrusion supplementary service
SS-CO Call Offer supplementary service
T1 Timer T1
T2 Timer T2
TP Test Purpose
TSS Test Suite Structure
VDB Visitor Data Base
VPN Virtual Private Network
4 Test Suite Structure (TSS)
Signalling procedures at the VPN "b"service entry Point Group
Actions at the Rerouteing PINX Reroute01
Actions at the CTMI-detect PINX
Normal procedures Detect01
Exceptional procedures Detect02
Rerouteing procedures Detect03
Home procedures Detect04
Actions at the Home PINX Home01
Actions at the Visitor PINX Visitor01
Procedures for interactions between ANF-CTMI and other supplementary services and ANFs SS01
ETSI
---------------------- Page: 10 ----------------------
SIST EN 301 455-1 V1.1.4:2005
9 ETSI EN 301 455-1 V1.1.4 (2000-09)
5 Test Purposes (TP)
5.1 Introduction
For each test requirement a TP is defined.
5.1.1 TP naming convention
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite and whether it applies to the network or the user (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= supplementary service: "CTMI"
= group up to 8 digit field representing group reference according to TSS
= sequential number (001-999)
5.1.2 Source of TP definition
The TPs are based on ETS 300 696 [5].
5.1.3 TP structure
Each TP has been written in a manner, which is consistent with all other TPs. The intention of this is to make the TPs
more readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should be
read in conjunction with any TP, i.e. use a TP as an example to fully understand the table.
ETSI
---------------------- Page: 11 ----------------------
SIST EN 301 455-1 V1.1.4:2005
10 ETSI EN 301 455-1 V1.1.4 (2000-09)
Table 2: Structure of a single TP for ANF-CTMI
TP part Text Example
Header tab seetable1
tab Subclause 0.0.0
Stimulus Ensure that the IUT in the
or State 3 or CTMI-Idle, etc.
see below for message structure
Receiving a XXXX message
or to request a.
Reaction Sends, saves, does, etc.
Using en bloc sending, .
if the action is sending
see below for message structure
, etc.
and remains in the same state
or and enters state
Message SETUP, FACILITY, CONNECT, .
structure
message containing a
a) Bearer capability, Facility, .
information element with
b)a
encoded as or including
andbacktoaorb,
Selection Selection criteria reference Behaviour as CTMI-detect PINX for ANF-
CTMI. PICS: A1
NOTE 1: In order to use the same structure as for test group selection, the selection criteria is indicated at the
bottom of the test purpose.
NOTE 2: Unless specified the messages are valid and contain at least the mandatory information elements and
possibly optional information elements, the information elements are valid and contain at least the
mandatory parameters and possibly optional parameters.
5.1.4 Test strategy
As the base standard ETS 300 696 [5] contains no explicit requirements for testing, the TPs were generated as a result
of an analysis of the base standard and the corresponding PICS proforma.
The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, and are
limited to conceivable situations to which a real implementation is likely to be faced (ETS 300 406 [14]).
All the test purposes are mandatory unless they have a selection criteria. Optional test purposes (with selection criteria),
are applicable according to the configuration options of the IUT. The configuration option shall be covered by a PICS
item.
5.2 TPs for ANF-CTMI
All PICS items referred to in this subclause are as specified in ETS 300 696 [5] unless indicated otherwise by another
numbered reference.
Unless specified:
- Only the requirements from the point of view of the VPN "b" service entry point are considered. This implies
that the interactions with other networks are out of scope of the present document and causes that the
corresponding Test Purposes are not included in the present document.
- The messages indicated are valid and contain at least the mandatory information elements and possibly optional
information elements.
- The information elements indicated are valid and contain at least the mandatory parameters and possibly optional
parameters.
ETSI
---------------------- Page: 12 ----------------------
SIST EN 301 455-1 V1.1.4:2005
11 ETSI EN 301 455-1 V1.1.4 (2000-09)
The following wording convention was defined to make the test purposes more readable:
- When a message is to be sent or received on a call independent signalling connection, the message name shall be
followed by a '(sc)', e.g. CONNECT (sc) means that the CONNECT message is conveyed on a call independent
signalling connection.
- All the test purposes are valid for both user and network side of the VPN b interface. In order to simplify the text
and to make the test purposes more readable, only the User side Call states (Ux) are indicated in the test
purposes. For the network side of the VPNb interface, the mapping table below indicates which network call
state (Ny) corresponds to the user call state used in the test purpose. Equivalent call state means there that the
same message flow applies from the IUT point of view (e.g.: IUT sends a SETUP message gives the call state
U01 or N06).
User side call state equivalent network
side call state
U00 N00
U01 N06
U10 N10
EXAMPLE:
Ensure that the IUT in the call state U01 …
is equivalent to the following network side test purpose:
Ensure that the IUT in the call state N06 …
5.2.1 ANF-CTMI signalling procedures
5.2.1.1 Actions at the Rerouteing PINX
Groupselection: IUT supports behaviour as Rerouteing PINX for ANF-CTMI. PICS: A7 AND NOT A1.
CTMI_Reroute01_001 subclause 6.5.1.1
Ensure that the IUT in the call state U03, on receipt of a FACILITY message from the CTMI detect PINX containing a
ctmiDivert invoke APDU and it can proceed with ANF-CTMI,
sends a DISCONNECT message to the CTMI detect PINX containing a ctmiDivert return result APDU, sends a SETUP
message to the Visitor PINX containing the data element Called party number, containing the number received in the
visitPINX data element within the ctmiDivert invoke APDU; Called party subaddress, containing the subaddress
received in the ctmUserSub data element within the ctmiDivert invoke APDU (optional); Calling party number,
containing the number received in the callingNumber data element within the ctmiDivert invoke APDU; Calling party
subaddress, containing the subaddress received in the callingUserSub data element within the ctmiDivert invoke APDU
(optional); ctmiDivert invoke APDU; Bearer capability information element as received in embedded form within the
ctmiDivert invoke APDU, and any of the following information elements which were also received in embedded form
in this APDU: High layer compatibility, Low layer compatibility, Progress indicator and Party category information
elements; Transit counter, with value zero (optional); a ctmiInform invoke APDU with the data element pisnNumber
with the same contents as the corresponding data element in the argument of the received ctmiDivert invoke APDU and
enters state ExecIdle.
ETSI
---------------------- Page: 13 ----------------------
SIST EN 301 455-1 V1.1.4:2005
12 ETSI EN 301 455-1 V1.1.4 (2000-09)
CTMI_Reroute01_002 subclause 6.5.1.1
Ensure that the IUT in the call state U03, on receipt of a FACILITY message from the CTMI detect PINX containing a
ctmiDivert invoke APDU with the element callingUserName and it can proceed with ANF-CTMI,
sends a DISCONNECT message to the CTMI detect PINX containing a ctmiDivert return result APDU, sends a SETUP
message to the Visitor PINX containing the data element Called party number, containing the number received in the
visitPINX data element within the ctmiDivert invoke APDU; Called party subaddress, containing the subaddress
received in the ctmUserSub data element within the ctmiDivert invoke APDU (optional); Calling party number,
containing the number received in the callingNumber data element within the ctmiDivert invoke APDU; Calling party
subaddress, containing the subaddress received in the callingUserSub data element within the ctmiDivert invoke APDU
(optional); ctmiDivert invoke APDU; Bearer capability information element as received in embedded form within the
ctmiDivert invoke APDU, and any of the following information elements which were also received in embedded form
in this APDU: High layer compatibility, Low layer compatibility, Progress indicator and Party category information
elements; Transit counter, with value zero (optional); a callingName invoke APDU and a ctmiInform invoke APDU
with the data element pisnNumber with the same contents as the corresponding data element in the argument of the
received ctmiDivert invoke APDU and enters state ExecIdle.
CTMI_Reroute01_003 subclause 6.5.1.2
Ensure that the IUT in the call state U03, on receipt of a FACILITY message from the CTMI detect PINX containing a
ctmiDivert invoke APDU but it can not proceed with ANF-CTMI,
sends a FACILITY message to the CTMI-detect PINX containing a ctmiDivert return error APDU with the error
notAvailable and enters state ExecIdle.
5.2.1.2 Actions at the CTMI-detect PINX
Groupselection: IUT supports behaviour as CTMI-detect PINX for ANF-CTMI. PICS: A1.
5.2.1.2.1 Normal procedures
CTMI_Detect01_001 subclause 6.5.2.1
Ensure that the IUT in the call state U00 and in the CTMI-Idle state, on determining that ANF-CTMI is to be invoked
following the received SETUP message from the Rerouteing PINX,
sends a SETUP (sc) message to the Home PINX containing a ctmiEnquiry invoke APDU with the data elements
pisnNumber as received in the incoming SETUP message in the Called party number information element;
qSIGInfoElement containing an embedded Bearer capability information element, as received in the incoming SETUP
message, and any of the following information elements which were received in the incoming SETUP message: High
layer compatibility and Low layer compatibility, starts timer T1 and enters state CTMI-Detected.
CTMI_Detect01_002 subclause 6.5.2.1
Ensure that the IUT in the call state U03 (sc) and in the CTMI-Detected state, on receipt of a CONNECT (sc) message
from the Home PINX containing a ctmiEnquiry return result APDU with choice currLocation,
sends a FACILITY message to the Rerouteing PINX containing a ctmiDivert invoke APDU using the call reference of
the
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.