ISO/IEC 15054:1997

Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Call interception additional network feature

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseau privé à intégration de services — Protocole de signalisation d'interéchange — Facilité de réseau additionnelle d'interception d'appel

General Information

• Status: Withdrawn
• Publication Date: 14-May-1997
• Withdrawal Date: 14-May-1997
• ICS: 33.040.35 - Telephone networks
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 25-Mar-2003

Relations

• Revised: ISO/IEC 15054:2003 - Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Call Interception additional network feature
• Effective Date: 15-Apr-2008

Standards Content (Sample)

ISOIIEC
INTERNATIONAL
15054
STANDARD
First edition
1997-05- 15
Information technology -
Telecommunications and information
exchange between systems - Private
Integrated Services Network -
Inter-exchange signalling protocol - Call
interception additional network feature
T6lkommunica tions et bhange
Technologies de I’informa tion -
d’informa tion entre systkmes - Rbseau privb 2 intkgration de services -
Protocole de signalisation d’interkhange - Facilitg de r&eau
additionnelle d’interception d’appel
Reference number
ISOA EC 15054: 1997(E)

---------------------- Page: 1 ----------------------
ISO/IEC 15054:1997 (E)
Contents
Foreword
Introduction
1
1 Scope
1
2 Conformance
1
3 Normative references
2
4 Definitions
2
4.1 External definitions
3
4.2 Other definitions
3
5 List of acronyms
3
6 Signalling protocol for the support of ANF-CINT
3
6.1 ANF-CINT description
3
6.2 ANF-CINT operational requirements
6.2.1 Requirements on an Originating PINX
6.2.2 Requirements on a Terminating PINX
6.2.3 Requirements on an Intercepted-to PINX
6.2.4 Requirements on a Transit PINX
6.2.5 Requirements on an Intercepting PINX
5
6.3 ANF-CINT coding requirements
5
6.3.1 Operations
8
6.3.2 Information elements
8
6.3.3 Messages
8
6.4 ANF-CINT state definitions
6.4.1 States at the Originating PINX
6.4.2 States at the Intercepting PINX
6.4.3 States at the Intercepted-to PINX
6.4.4 States at a Transit PINX
6.4.5 States at the Terminating PINX
6.5 ANF-CINT Signalling procedures for activation, deactivation, registration and interrogation 8
9
6.6 ANF-CINT Signalling procedures for invocation and operation
9
6.6.1 Actions at a Terminating PINX
9
6.6.2 Actions at a Transit PINX
9
6.6.3 Actions at the Originating PINX
10
6.6.4 Actions at an Intercepting PINX for interception immediate
11
6.6.5 Actions at an Intercepting PINX for interception delayed
12
6.6.6 Actions at an Intercepted-to PINX
0 ISO/IEC 1997
AI rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from the publisher.
ISOAEC Copyright Office l Case postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland

---------------------- Page: 2 ----------------------
01s0AEc ISO/IEC 15054:1997 (E)
6.7 ANF-CINT Impact of interworking with a public ISDN 12
6.7.1 Incoming Gateway PINX 12
6.7.2 Outgoing Gateway PINX 12
6.8 ANF-CINT Impact of interworking with a non-ISDN 13
6.8.1 Incoming Gateway PINX 13
6.8.2 Outgoing Gateway PINX 13
6.9 Protocol interaction between ANF-CINT and other supplementary services and ANFs 13
13
6.9.1 Interaction with Calling Name Identification Presentation (SS-CNIP)
6.9.2 Interaction with Connected Name Identification Presentation (SS-CONP) 13
13
6.9.3 Interaction with Call Forwarding Unconditional (SS-CFU)
6.9.4 Interaction with Call Forwarding Busy (SS-CFB) 14
6.9.5 Interaction with Call Forwarding No Reply (SS-CFNR) 14
6.9.6 Interaction with Do Not Disturb (SS-DND) 14
6.9.7 Interaction with Do Not Disturb Override (SS-DNDO) 14
6.9.8 Interaction with Call Completion To Busy Subscriber (SS-CCBS) 14
6.9.9 Interaction with Call Completion On No Reply (SS-CCNR) 14
6.9.10 Interaction with Call Offer (SS-CO) 15
6.9.11 Interaction with Call Intrusion (SS-CI) 15
6.9.12 Interaction with Call Transfer (SS-CT) 15
6.9.13 Interaction with Path Replacement (ANF-PR) 16
6.9.14 Interaction with Recall (SS-RE) 16
6.9.15 Interaction with Advice Of Charge (SS-AOC)
16
Annex A - Protocol Implementation Conformance Statement (PIGS) Proforma 17
Annex B - Examples of message sequences 28
Annex C - Specification and Description Language (SDL) Representation of procedures 34
. . .
111

---------------------- Page: 3 ----------------------
ISO/IEC 15054: 1997 (E) OISO/IEC
Foreword
IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the
National bodies that are members of IS0 or IEC participate in the
specialized system for worldwide standardization.
development of International Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. IS0 and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work.
In the field of information technology, IS0 and IEC have established a joint technical committee, ISO/IEC JTC 1. Draft
International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the national bodies casting a vote.
International Standard ISO/IEC 15054 was prepared by ECMA (as ECMA-221) and was adopted, under a special “fast-track
procedure”, by Joint Technical Committee ISO/IEC JTC 1, Informatiort technology, in parallel with its approval by national
bodies of IS0 and IEC.
Annex A forms an integral part of this International Standard. Annexes B, C and D are for information only.
iv

---------------------- Page: 4 ----------------------
OISOLIEC ISO/IEC 15054:1997 (E)
Introduction
This International Standard is one of a series of standards defining services and signalling protocols applicable to Private
Integrated Services Networks. The series uses the ISDN concepts as developed by ITU-T (formerly CCITT.) and is also within
the framework of standards for open systems interconnection as defined by ISO.
This International Standard specifies the signalling protocol for use at the Q reference point in support of the Call Intercepti on
additional network feature.
The International Standard is based upon the practical experience of ECMA member companies and the results of their active
and continuous participation in the work of ISO/IEC JTC 1, ITU-T, ETSI and other international and national standardization
bodies. It has been produced under ETSI work item DE/ECMA-00103. It represents a pragmatic and widely based consensus.

---------------------- Page: 5 ----------------------
This page intentionally left blank

---------------------- Page: 6 ----------------------
ISO/IEC 15054: 1997 (E)
INTERNATIONAL STANDARD 0 ISO/IEC
Information technology - Telecommunications and information exchange between
- Inter-exchange signalling protocol -
systems - Private Integrated Services Network
Call interception additional network feature
1 Scope
This International Standard specifies the signalling protocol for the support of the additional network feature Call Interception
(ANF-CINT) at the Q reference point between Private Integrated Services Network Exchanges (PINX) connected together
within a Private Integrated Services Network (PISN).
ANF-CINT is an additional network feature which enables calls that cannot be completed due to certain conditions to be
redirected to a predetermined intercepted-to user.
The Q reference point is defined in ISO/IEC 11579-l.
Service specifications are produced in three stages and according to the method specified in CCITT Recommendation I. 130.
This International Standard contains the stage 3 specification for the Q reference point and satisfies the requirements identified
by the stage 1 and stage 2 specifications in ISO/IEC 15053.
The signalling protocol for ANF-CINT operates on top of the signalling protocol for basic circuit switched call control, as
specified in ISO/IEC 11572, and uses certain aspects of the generic procedures for the control of supplementary services
specified in ISO/IEC 11582.
This International Standard also specifies additional signalling protocol requirements for the support of interactions at the Q
reference point between ANF-CINT and other supplementary services and ANFs.
Note - Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the relevant stage 1 specifications.
This International Standard is applicable to PINXs which can interconnect to form a PISN.
2 Conformance
In order to conform to this International Standard, a PINX shall satisfy the requirements identified in the Protocol
Implementation Conformance Statement (PICS) proforma in annex A.
Conformance to this International Standard includes conforming to those clauses that specify protocol interactions between
ANF-CINT and other supplementary services and ANFs for which signalling protocols at the Q reference point are supported
in accordance with the stage 3 standards concerned.
Normative references
3
The following standards contain provisions which, through reference in this text, constitute provisions of this International
Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to
agreements based on this International Standard are encouraged to investigate the possibility of applying the most recent
editions of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid International
Standards.
ISO/IEC 11572:1997, Information technology - Telecommunications and information exchange between systems -
Private Integrated Services Network - Circuit mode bearer services - Inter-exchange signalling
procedures and protocol.
Information technology -
ISOIIEC 11574: 1994, Telecommunications and information exchange between systems -
Private Integrated Services Network - Circuit-mode 64 kbit/s bearer services - Service description,
functional capabilities and information flows.
ISO/IEC 11579- 1: 1994, Information technology - Telecommunications and information exchange between systems -
Private Integrated Services Network - Part 1: Reference configuration for PISN Exchanges
(PINX).
ISOIIEC 11582: 1995, Information technology - Telecommunications and information exchange between systems -
Private Integrated Services Network - of
Generic functional protocol for the support
supplementary services - Inter-exchange signalling procedures and protocol.

---------------------- Page: 7 ----------------------
OISO/IEC
ISO/IEC 15054: 1997 (E)
Telecommunications and information exchange between systems -
ISO/IEC 13868: 1995, Information technology -
Inter-exchange signalling protocol - Name identification
Private Integrated Services Network -
supplementary services.
ISO/IEC 13869: 1995, Information technology - Telecommunications and information exchange between systems -
Private Integrated Services Network - Inter-exchange signalling protocol - Call transfer
supplementary service.
Information technology - Telecommunications and information exchange between systems -
ISO/IEC 13870: 1995,
Private Integrated Services Network - Inter-exchange signalling protocol - Call completion
supplementary services.
ISO/IEC 13873: 1995, Information technology - Telecommunications and information exchange between systems -
Private Integrated Services Network - Inter-exchange signalling protocol - Call diversion
supplementary services.
ISO/IEC 15050: 1997, Information technology - Telecommunications and information exchange between systems -
Private Integrated Services Network - Inter-exchange signalling protocol - Advice of charge
supplementary services.
Information technology - Telecommunications and information exchange between systems -
ISO/IEC 15052: 1997,
Private Integrated Services Network - Inter-exchange signalling protocol - Recall supplementary
service.
CCITT Rec. I. 112: 1988, Vocabulary of terms for ISDNs.
Method for the characterization of telecommunication services supported by an ISDN and network
CCITT Rec. I. 130: 1988,
capabilities of an ISDN.
CCITT Rec. 1.210:1988, Principles of telecommunication services supported by an ISDN and the means to describe them.
CCITI’ Rec. 2.100: 1988, Specification and description language.
4 Definitions
For the purposes of this International Standard, the following definitions apply.
4.1 External definitions
This International Standard uses the following terms defined in other documents:
- Application Protocol Data Unit (APDU) (ISO/IEC 11582)
- Basic Service (CCITT. Rec. 1.210)
- Call, Basic Call (ISO/IEC 11582)
(ISO/IEC 11582)
- End PINX
(ISO/IEC 11572)
- Incoming Gateway PINX
(ISO/IEC 11572)
- Outgoing Gateway PINX
(ISO/IEC 11572)
- Originating PINX
(ISO/IEC 11572)
- Preceding PINX
-
(ISO/IEC 11579- 1)
Private Integrated Services Network (PISN)
-
(ISO/IEC 11579- 1)
Private Integrated Services Network Exchange (PINX)
(CCITT Rec. I. 112)
- Signalling
- Subsequent PINX (ISO/IEC 11572)
- Supplementary Service (CCITT Rec. 1.210)
- Supplementary Service Control Entity (ISO/IEC 11582)
- Terminating PINX (ISO/IEC 11572)
- Transit PINX (ISO/IEC 11572)
- User (ISO/IEC 11574)
4.2 Other definitions
forward switching : Network rout&g algorithm which performs the interception by joining together the first connection from
the calling user to the Intercepting PINX and the new connection from the Intercepting PINX to the intercepted-to user.
Intercepting PINX : The PINX where the interception is invoked.
2

---------------------- Page: 8 ----------------------
ISO/IEC 15054:1997 (E)
OISOAEC
Intercepted-to PINX : The PINX serving the intercepted-to user.
intercepted-to user : The user to whom the intercepted call is directed.
interception immediate : The redirection of a call to an alternative destination as a result of detecting a call failure condition
that prevents the call reaching an alerting or waiting on busy state.
interception delayed : The redirection of a call to an alternative destination as a result of remaining too long in an alerting
waiting on busy state.
call failure : In the context of a particular PINX, the inability to route a call or, having routed a call, the receipt of a call
clearing message from the Subsequent PINX without the call having reached an alerting or waiting on busy state.
waiting on busy : A call state in which a call is awaiting answer at a user that is busy on another call.
Note - This can arise, for example, as a result of the use of supplementary service Call Offer (SS-CO) during call establishment. A call that is waiting on busy
can be transferred.
5 List of acronyms
ANF Additional Network Feature
Application Protocol Data Unit
APDU
ASN. 1 Abstract Syntax Notation no. 1
CINT Call Interception
ISDN Integrated Services Digital Network
NFE Network Facility Extension
PIGS Protocol Implementation Conformance Statement
PINX Private Integrated Services Network Exchange
PISN Private Integrated Services Network
SDL Specification and Description Language
ss Supplementary Services
Signalling protocol for the support of ANF-CINT
6
6.1 ANF-CINT description
ANF-CINT is invoked for an unanswered or unsuccessful call, allowing the call to be routed to a special destination in the
PISN. The special destination may be dependant of the interception cause.
The conditions leading to invocation of ANF-CINT are considered as implementation options. Examples of factors that can be
taken in to account are:
-
the source of the call (e.g. the geographic location of the calling user, the network from which the call has entered the
PISN);
- the particular interception cause;
-
the type of connection (e.g. the originating user is an attendant);
- the call destination;
-
time of the day.
6.2 ANF-CINT operational requirements
6.2.1 Requirements on an Originating PINX
Call establishment procedures for the outgoing side of an inter-PINX link and call release procedures, as specified in ISO/IEC
11572, shall apply.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for an End PINX,
shall apply.
6.2.2 Requirements on a Terminating PINX
Call establishment procedures for the incoming side of.an inter-PINX link and call release procedures, as specified in ISO/IEC
11572, shall apply.

---------------------- Page: 9 ----------------------
oISO/IEC
ISO/IEC 15054: 1997 (E)
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for an End PINX,
shall apply.
6.2.3 Requirements on an Intercepted-to PINX
Call establishment procedures for the incoming side of an inter-PINX link and call release procedures, as specified in ISO/IEC
11572, shall apply.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for an End PINX,
shall apply.
6.2.4 Requirements on a Transit PINX
Basic call procedures for call establishment and call clearing at a Transit PINX, as specified in ISO/IEC 11572, shall apply.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for a Transit PINX,
shall apply.
6.2.5 Requirements on an Intercepting PINX
Call establishment procedures for the outgoing side of an inter-PINX link and call release procedures, as specified in ISO/IEC
11572, shall apply.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for an End PINX,
shall apply.
Where, as a result of invocation of ANF-CINT, an Intercepting PINX can become a Transit PINX, generic procedures for the
call-related control of supplementary services, as specified in ISO/IEC 11582 for a Transit PINX, shall apply.

---------------------- Page: 10 ----------------------
ISOAEC 15054:1997 (E)
OISO/IEC
6.3 ANFWINT coding requirements
6.3.1 Operations
The operations defined in Abstract Syntax Notation number 1 (ASN.1) in table 1 shall apply.
In addition the operation divertingLegInformation3, as defined in ISO/IEC 13873, shall apply.
Table 1 - Operations in Support of ANIGCINT
;all-Interception-Operations {iso (1) standard (0) pssl -tint (15054) tint-operations (0) }
)EFINITIONS EXPLICIT TAGS ::=
lEGIN
MPORTS OPERATION, ERROR FROM Remote-Operation-Notation
(joint-iso-ccitt (2) remote-operations (4) notation (0))
Extension FROM Manufacturer-specific-service-extension-definition
{iso (1) standard (0) pssl-generic-procedures (11582) msi-definition (0))
PartyNumber, PresentedNumberUnscreened, PresentationAllowedlndicator
FROM Addressing-Data-Elements
{iso (1) standard (0) pssl -generic procedures (11582)
addressing-data-elements (9))
Name FROM Name-Operations
{iso (1) standard (0) pssl -name (13868) name-operations (0));
ZintLeglnformationl::= OPERATION
-- Sent from the Intercepting PINX to the Originating PINX --
ARGUMENT Cintlnformationl Arg
CintLeglnformation2::= OPERATION
-- Sent from the Intercepting PINX to the Intercepted-to PINX --
ARGUMENT Cintlnformation2Arg
OPERATION
CintCondition::=
-- Sent to a preceding PINX to indicate a condition for possible --
-- interception --
ARGUMENT CintCondArg
5

---------------------- Page: 11 ----------------------
01s0/IEc
ISO/IEC 15054: 1997 (E)
Table 1 - Operations in Support of ANF-CINT (continued)
.*-
OPERATION
SintDisable l m-
-- Sent to a Preceding PINX to disable interception delayed --
ARGUMENT CintExtension
.=-
>intEnable a*- OPERATION
-- Sent to a Preceding PINX to reenable interception --
ARGUMENT CintExtension
-.-
Zintlnformationl Arg SEQUENCE
. l -
1
interceptioncause CintCause,
interceptedToNumber PartyNumber,
extension CintExtension OPTIONAL
I
l .-
Cintlnformation2Arg SEQUENCE
. l -
{
interceptioncause CintCause,
calledNumber [IlPresentedNumberUnscreened OPTIONAL,
originalCalledNumber [2]PresentedNumberUnscreened OPTIONAL,
calledName [3]Name OPTIONAL,
originalCalledName [4]Name OPTIONAL,
extension CintExtension OPTIONAL
I
’ ‘-
CintCondArg .a- SEQUENCE
t
interceptioncause Condition,
originalCalledNumber [IlPresentedNumberUnscreened OPTIONAL,
calledName [2]Name OPTIONAL,
originalCalledName [3]Name OPTIONAL,
extension CintExtension OPTIONAL
‘.-
CHOICE
CintExtension .*-
1
none NULL,
[5] IMPLICIT Extension,
single
multiple [6] IMPLICIT SEQUENCE OF Extension
I
6

---------------------- Page: 12 ----------------------
ISO/IEC 15054:1997 (E)
OISO/IEC
Table 1 - Operations in Support of ANF-CINT (concluded)
;intCause INTEGER {
unknown
!
0
cintBnan -- timeout in waiting on busy condition
!
(1)
cintBus -- busy user
(2) 9
II
cintCug closed user group rejection
9
(3)
cintDnd -- do not disturb activated
(4) 9
II
cintlbd incoming barred destination
!
(5)
--
cintlnn invalid number
(6) !
--
cintMob1 mobile user location not known
9
(7)
I-
cintMob2 mobile user no longer registered
9
(8)
I-
cintMob3 mobile terminal not responding
!
(9)
-I
cintNcmp no compatible destination
f
(10)
I-
cintNcong network congestion
(11) 9
cintNre -- no reply (i.e. timeout during alerting)
J
(12)
-0
cintOos called user out of service
9
(13)
-I
cintRrs route restriction (calling user not authorized for
9
(14)
-- the route)
II
cintTbnan timeout in wait on busy condition after transfer
II
cintTnre no reply after transfer (i.e. timeout during alerting
I-
after transfer
--
cintTrans upper limit of transit counter reached
-0
cintUpl upper limit of number of diversions reached
II
cintlnvDiv invalid call diversion destination
cintHold -- timeout after call hold
} (0.127)
l .-
>ondition . .- INTEGER {
unknown
cintBus -- busy user
I-
cintCug closed user group rejection
cintDnd -- do not disturb activated
-I
cintlbd incoming barred destination
I-
cintlnn invalid number
--
cintMob1
mobile user location not known
-I
cintMob2 mobile user no longer registered
--
mobile terminal not responding
cintMob3
a-
cintNcmp no compatible destination
-0
cintNcong network congestion
--
cintOos called user out of service
-I
cintRrs route restriction (calling user not authorized for
-- the route
I-
cintTrans upper limit of transit counter reached
9
(17)
--
cintUpl upper limit of number of diversions
(18)
-a
reached
--
cintlnvDiv invalid call diversion destination
} (0.J 27)
.‘-
CintLeglnformationl .-
cintLeglnformation1 66
.‘-
cintLeglnformation2 CintLeglnformation2 .- 67
.‘-
CintCondition .-
cintcondition 68
-a-
cintDisable CintDisable .- 69
l m-
CintEnable . .- 70
cintEnable
of Call-Interception-Operations
END --
7

---------------------- Page: 13 ----------------------
ISO/IEC 15054:1997 (E) 01s0/IEc
6.3.2 Information elements
6.3.2.1 Facility information element
The operations defined in 6.3.1 shall be coded in the Facility information element in accordance with ISO/IEC 11582.
When conveying the invoke APDU of the operations defined in 6.3.1 except for cintcondition, the destinationEntity data
element of the NFE shall contain value endPINX.
When conveying the invoke APDU of operation cintcondition, the destinationEntity data element of the NFE shall contain
value anyTypeOfPINX.
When conveying invoke APDUs of the operations defined in 6.3.1. the Interpretation APDU shall be included and shall contain
the value discardAnyUnrecognisedInvokePdu.
6.3.2.2 Other information elements
Any other information elements (e.g. Progress indicator, Calling party number) shall be coded in accordance with the rules of
ISO/IEC 11572.
6.3.3 Messages
The Facility information element shall be conveyed in the messages specified in clause 10 of ISO/IEC 11582. The basic call
messages shall be used for call establishment and release as specified in ISO/IEC 11572.
6.4 ANF-CINT state definitions
6.4.1 States at the Originating PINX
The procedures for the Originating PINX are written in terms of the following conceptual states existing within the ANF-CINT
Supplementary Service Control entity in that PINX in association with a particular call.
6.4.1.1 State CINT-orig-idle
Call interception is not in progress.
6.4.2 States at the Intercepting PINX
The procedures for the Intercepting PINX are written in terms of the following conceptual states existing within the ANF-CINT
Supplementary Service Control entity in that PINX in association with a particular call.
6.4.2.1 State CINT-intrcp-idle
Call interception is not in progress.
6.4.2.2 State CINT-intercepting
Interception delayed is in progress.
6.4.3 States at the Intercepted-to PINX
The procedures for the Intercepted-to PINX are written in terms of the following conceptual states existing within the ANF-
CINT Supplementary Service Control entity in that PINX in association with a particular call.
6.4.3.1 State CINT-intrcpto-idle
ANF-CINT is not in progress.
6.4.3.2 State CINT-intrcpto-presented
An intercepted call has arrived and the PINX is waiting for valid presentation restriction information to become available.
6.4.4 States at a Transit PINX
6.4.4.1 State CINT-transit-idle
ANF-CINT is not in progress.
6.4.5 States at the Terminating PINX
6.4.5.1 State CINT-term-idle
ANF-CINT is not in progress.
6.5
ANF-CINT Signaliing procedures for activation, deactivation, registration and interrogation
Not applicable.
8

---------------------- Page: 14 ----------------------
ISO/IEC 15054:1997 (E)
OISO/IEC
6.6 ANF-CINT Signalling procedures for invocation and operation
Examples of message sequences are shown in annex B.
6.6.1 Actions at a Terminating PINX
The SDL representation of procedures at the Terminating PINX is shown in C.4 of annex C.
If call failure is detected, the Terminating PINX, instead of initiating call clearing towards the preceding PINX, may invoke
interception immediate in accordance with the procedures of 6.6.4.
If call failure is detected and interception immediate is not invoked, the Terminating PINX may send a cintcondition invoke
APDU in the DISCONNECT message or, if an in-band tone or announcement is applied, in the PROGRESS message.
When the Terminating PINX sends an ALERTING, PROGRESS or FACILITY message indicating that the call is entering an
alerting or waiting on busy state and if the Terminating PINX is to become the Intercepting PINX for interception delayed, it
shall:
i)
send a cintDisable invoke APDU in the ALERTING, PROGRESS or FACILITY message; and
ii) if the call remains unanswered for an implementation-dependent length of time, invoke interception delayed in accordance
with the procedures of 6.6.5.
Note - The sending of a cintDisable invoke APDU prevents another PINX becoming the Intercepting PINX.
When a call enters an alerting or waiting on busy state, if the Terminating PINX is not to become the Intercepting PINX and
requires that interception delayed be disabled, it shall send a cintDisable invoke APDU in the ALERTING, PROGRESS or
FACILITY message.
During an alerting or waiting on busy state, if a cintDisable invoke APDU has previously been sent and there is a need to
reenable interception delayed, then a cintEnable invoke APDU shall be sent in a FACILITY or ALERTING message.
6.6.2 Actions at a Transit PINX
The SDL representation of procedures at the Transit PINX is shown in C.5 of annex C.
On receipt of a cintcondition invoke APDU from the subsequent PINX in conjunction with a call failure, a Transit PINX may
take note of the condition indicated with a view to possible interception immediate.
If call failure is detected, whether or not a cintcondition invoke APDU has been received, a Transit PINX, instead of
continuing call clearing towards the Preceding PINX, may invoke interception immediate in accordance with the procedures of
6.6.4, provided that the Transit PINX has not already relayed on any APDUs from the Subsequent PINX to the Preceding
PINX.
If call failure is detected, interception immediate is not invoked and a cintcondition invoke APDU has been received from the
Subsequent PINX, a cintcondition invoke APDU containing the same interception cause shall be sent in the DISCONNECT or
PROGRESS message, as received from the Subsequent PINX, to the Preceding PINX. If call failure is detected, interception
immediate is not invoked and a cintcondition invoke APDU has not been received from the Subsequent PINX, a cintcondition
invoke APDU may be sent in the DISCONNECT message to the Preceding PINX.
6.6.3 Actions at the Originating PINX
The SDL representation of procedures at the Originating PINX is shown in C.l of annex C.
On receipt of a cintcondition invoke APDU from the subsequent PINX in conjunction with a call failure, the Originating PINX
may take note of the condition indicated with a view to possible interception immediate.
If call failure is detected, whether or not a cintcondition invoke APDU has been received, the Originating PINX may, instead
of indicating call failure to the calling user, invoke interception immediate in accordance with the procedures of 6.6.4.
On receipt of a cintDisable invoke APDU in an ALERTING, PROGRESS or FACILITY message, the Originating PINX shall
disable interception delayed for the call concerned.
On receipt of a cintEnable invoke APDU in a FACILITY or ALERTING message, the Originating PINX shall cancel the effect
of any previously received cintDisable invoke APDU.
When a call remains unanswered in an alerting or waiting on busy state for an implementation-dependent length of time, the
Originating PINX may invoke interception delayed in accordance with the procedures of 6.6.5, provided that interception
delayed is not disabled.

---------------------- Page: 15 ----------------------
ISO/IEC 15054:1997 (E) 01s0lIEc
On receipt of a cintLegInformation1 invoke APDU in an ALERTING or CONNECT message or in a FACILITY message prior
to receipt of a CONNECT message, the Originating PINX shall take account of the information therein. Provided this is the
first cintLegInformation1 invoke APDU received or an alerting or waiting on busy state has bee
...