Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Call transfer supplementary service

Is one of a series of standards defining services and signalling protocols applicable to Private Services Networks (PISN). The Series uses ISDN concepts as developed by ITU-T and conforms to the framework of Standards for Open Systems Interconnections as defined by ISO/IEC. Specifies the Call transfer supplementary service.

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 — Service supplémentaire de transfert d'appel

General Information

Status
Withdrawn
Publication Date
15-Nov-1995
Withdrawal Date
15-Nov-1995
Current Stage
9599 - Withdrawal of International Standard
Completion Date
21-Mar-2003
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 13869:1995 - Information technology -- Telecommunications and information exchange between systems -- Private Integrated Services Network -- Inter-exchange signalling protocol -- Call transfer supplementary service
English language
60 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 13869
First edition
1995-1 l-l 5
Information technology -
Telecommunications and information
exchange between Systems - Private
Integrated Services Network -
Inter-exchange signalling protocol - Call
transfer supplementary Service
- TMcommunications et behange
Technologies de I’informa tion
en tre sys temes - R&eau priv6 ~3 in tbgration de
d ‘in forma tion
Services - Protocole de signalisation d’in terkhange - Service
suppkmen taire de trans fert d’appel
Reference number
ISO/IEC 13869:1995(E)

---------------------- Page: 1 ----------------------
PSOIIEC 13869: 1995 (E)
Contents
vi
Foreword
vii
Introduction
1
1 Scope
2
2 Conformance
2
3 Normative references
3
4 Definitions
3
4.1 External definitions
4
4.2 Other definitions
4
5 List of acronyms
4
6 Signalling protocol for the support of SS-CT
4
6.1 SS-CT description
5
6.2 SS-CT operational requirements
5
ProvisionAMt hdrawal
6.2.1
5
6.2.2 Requirements on a Transferring PINX
5
6.2.3 Requirements on a Primary PINX
5
6.2.4 Requirements on a Secondary PINX
5
6.2.5 Requirements on a Transit PINX
6
6.3 SS-CT coding requirements
6
6.3.1 Operations
13
6.3.2 Information elements
13
6.3.2.1 Facility information element
6.3.2.2 Information elements embedded in the Facility information
14
element
14
6.3.2.3 Other information elements
14
6.3.3 Messages
14
6.4 SS-CT state definitions
14
6.4.1 States at a Transferring PINX
15
6.4.1 .l CT-ldle
15
6.4.1.2 CT-Await-Answer-From-User-C
0 ISO/IEC 1995
All rights reserved. Unless otherwise specified, no part of this publication may be
reproduced or utilized in any form or by any means, electronie or mechanical,
without Permission in writing from the
including photocopying and microfilm,
pu blisher.
ISO/IEC Copyright Office l Case postale 56 l CH-121 1 Geneve 20 l Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
0 ISO/IEC
ISO/IEC 13869: 1995 (E)
6.4.1.3 CT-Await-Identify-Response 15
6.4.1.4 CT-Await-lnitiate-Response 15
6.4.2 States at a Primary PINX 15
6.4.2.1 CT-ldle 15
6.4.2.2 CT-Await-Setup-Response 15
6.4.2.3 CT-Await-Connect 15
6.4.3 States at a Secondary PINX 15
6.4.3.1 CT-ldle 15
6.4.3.2 CT-Await-Setup 15
6.5 SS-CT signalling procedures
16
6.5.1 Actions at a Transferring PINX 16
6.5.1 .l Normal procedures for transfer by join
16
6.5.1.2 Exceptional procedures for transfer by join
17
6.5.1.3 Normal procedures for transfer by rerouteing 18
6.5.1.4 Exceptional procedures for transfer by rerouteing 18
6.5.2 Actions at a Primary PINX 19
6.5.2.1 Normal procedures for transfer by join 19
6.5.2.2 Exceptional procedures for transfer by join
19
6.5.2.3 Normal procedures for transfer by rerouteing
19
6.5.2.4 Exceptional procedures for transfer by rerouteing
20
6.5.3 Actions at a Secondaty PINX
21
6.5.3.1 Normal procedures for transfer by join
21
6.5.3.2 Exceptional procedures for transfer by join 21
6.5.3.3 Normal procedures for transfer by rerouteing 21
6.5.3.4 Exceptional procedures for transfer by rerouteing 22
6.5.4 Actions at a Transit PINX
23
6.5.5 Subsequent actions at a Primary and a Secondary PINX
23
6.6 SS-CT impact of interworking with public ISDNs 24
6.6.1 Actions at a Gateway PINX 24
6.6.1 .l Impact of interworking if User A is in the PISN
24
6.6.1.2 Impact of interworking if a PISN User is transferred by the
public ISDN 24
6.6.2 Actions at other types of PINX 24
6.7 SS-CT impact of interworking with non-ISDNs 25
6.7.1 Actions at a Gateway PINX 25
6.7.1 .l Transfer within the PISN 25
6.7.1.2 Transfer within the non-ISDN
25
6.7.1.3 Cooperation with a non-ISDN in providing transfer by
rerouteing
26
6.7.2 Actions at other types of PINX
26
6.8 Protocol Interactions between SS-CT and other supplementary sewices and
ANFs 26
. . .
Ill
\

---------------------- Page: 3 ----------------------
ISO/IEC 13869: 1995 (E) 0 ISO/IEC
6.8.1
Calling Name Identification Presentation (SS-CNIP) 26
6.8.2 Connected Name Identification Presentation (SS-CONP) 26
6.8.3 Completion of Calls to Busy Subscribers (SS-CCBS) 27
6.8.4 Completion of Calls on No Reply (SS-CCNR) 27
6.8.5 Call Forwarding Unconditional (SS-CFU) 27
6.8.6 Call Fotwarding Busy (SS-CFB) 27
6.8.7 Call Fotwarding No Reply (SS-CFNR) 27
6.8.7.1 Actions at a Transferring PINX for rerouteing and SS-CFNR
Originating PINX 27
6.8.7.2 Actions at a Transferring PINX for join or rerouteing and SS-
CFNR Originating PINX 27
6.8.7.3 Actions at a Secondary PINX for rerouteing and SS-CFNR
Send User PINX 27
6.8.7.4 Actions at a Secondary PINX for rerouteing and SS-CFNR
28
Served User and Rerouteing PINX
6.8.7.5 Actions at a Secondary PINX for join and SS-CFNR Setved
User and Rerouteing PINX 28
6.8.7.6 Actions at a Transferring PINX for join 28
6.8.7.7 Actions at a Primary PINX for join 28
6.8.8 Call Deflection (SS-CD) 28
6.8.9 Path Replacement (ANF-PR) 29
6.8.9.1 Actions at an ANF-PR Requesting PINX 29
6.8.9.1.1 Invocation of Call transfer 29
29
6.8.9.1.2 Initiation of ANF-PR during Call Transfer
6.8.9.2 Actions at an ANF-PR Cooperating PINX 29
29
6.8.9.2.1 lnvocation of Cal1 Transfer
30
6.8.9.2.2 Initiation of ANF-PR during Call Transfer
6.9 SS-CT Parameter values (Timers) 30
6.9.1 Timer Tl 30
6.9.2 Timer T2 30
6.9.3 Timer T3 31
6.9.4 Timer T4 31
Annex A 32
A.l Introduction 32
32
A.2 Instructions for completing the PICS proforma
A.2.1 General structure of the PICS proforma 32
A.2.2 Additional information 33
A.2.3 Exceptional information 33
A.3 PICS proforma 34
iv

---------------------- Page: 4 ----------------------
0 ISO/IEC ISO/IEC 13869: 1995 (E)
A.3.1 Implementation identification
34
A.3.2 Protocol summary
34
A.3.3 General 35
A.3.4 Procedures for SS-CT-Join 35
A.3.5 Additional procedures for SS-CT-Rerouteing 36
A.3.6 Coding
37
A.3.7 Interactions between SS-CT and SS-CFNRBS-CD 38
A.3.8 Interactions between SS-CT and ANF-PR 39
A.3.9 Timers 39
Annex B 40
Annex C 42
C.l Example message sequence for normal operations of call transfer by join, both
calls active 43
C.2 Example message sequence for cal1 transfer by join, one call alerting 44
C.3 Example message sequence for normal Operation of call transfer by rerouteing 45
C.4 Example message sequence for normal Operation of call transfer by rerouteing,
one call alerting
47
Annex D 49
SDL Representation of SS-CT at a Transferring PINX
D. 1 50
D.2 SDL Representation of SS-CT at a Primary PINX 55
D.3 SDL Representation of SS-CT at a Secondary PINX 58
Annex E 60
V

---------------------- Page: 5 ----------------------
ISO/IEC 13869: 1995 (E) 0 ISO/IEC
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized System for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through
technical committees established by the respective organization to deal with particular fields of
technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-govemmental, in liaison with ISO and IEC, also
take patt in the work.
In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1. Draft International Standards adopted by the joint technical committee are
circulated to the 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 13869 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC6, Telecommunications and information exchange
between Systems.
Annex A forms an integral patt of this I nternat ional Standard. Annexes B to E are for information
only.
Vi

---------------------- Page: 6 ----------------------
0 ISOAEC ISO/IEC 1’38:69r,. 1995 (E)
Introduction
This International Standard is one of a series of Standards defining Services and signalling
protocols applicable to Private Integrated Services Networks (PISN)., The series uses ISDN
concepts as developed by ITU-T and conforms to the framework of Standards for Open Systems
Interconnection as defined by ISOAEC.
This particular International Standard specifies the Call Transfer supplementary,service.
vii

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

---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD 0 lSO/IEC
ISO/IEC 13869: 1995(E)
Information technology - Telecommunications
and information exchange between Systems -
Private Integrated Services Network - Inter-
exchange signalling protocol - Cal1 transfer
supplementary Service
1 Scope
This International Standard specifies the signalling protocol for the support of the Call Transfer
supplementary Service (SS-CT) at the Q reference Point between Private lntegrated Network
Services Exchanges (PINXs) connected together within a Private Integrated Services Network
(PISN).
SS-CT is a supplementary Service which enables a User to transform two of that User’s calls (at
least one of which must be answered) into a new call between the two other users in the two calls.
The Q reference Point is defined in ISOIIEC 115794.
Service specifications are produced in three stages and according to the method specified in
CCITT Recommendation 1.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 ISOAEC 13865.
The signalling protocol for SS-CT operates on top of the signalling protocol for basic circuit
switched call control, as specified in ISOAEC 11572, and uses certain aspects of the generic
procedures for the control of supplementary Services specified in ISOAEC 11582.

---------------------- Page: 9 ----------------------
0 ISO/IEC
ISO/IEC 13869: 1995 (E)
This International Standard also specifies additional signalling protocol requirements for the
support of interactions at the Q reference Point between Call Transfer and other supplementary
Services and ANFs.
This International Standard is applicable to PINXs which tan interconnect to form a PISN.
Conformance
2
In Order to conform to this International Standard, a PINX shall satisfy the requirements identified in
the Protocol lmplementation Conformance Statement (PICS) proforma in annex A.
3 Normative references
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
and ISO maintain registers of currently valid
Standards indicated below. Members of IEC
International Standards.
Telecommunica tions and in forma tion exchange
ISO/IEC 11571:1994 lnformation technology -
between Systems - Numbering and sub-addressing in private integrated services networks.
ISO/IEC 11572:1994, Information technology - Telecommunications and information exchange
between Systems - Private Integrated Services Network - Circuit-mode bearer Services - lnter-
exchange signalling procedures and protocol.
ISO/IEC 11574:1994, Information technology - Telecommunications and information exchange
between Systems - Private lntegrated Services Network- Circuit-mode 64 kbit/s bearer services-
Service description, functional capabilities and in forma tion flo ws.
ISO/1 EC 11579-1: 1994, Information technology - Telecommunica tions and information exchange
between Systems - Private Integrated Services Network- Part 1: Reference configuration for PISN
Exchanges (PINX).
ISO/IEC 11582: 1995, Information technology - Te/ecommunications and information exchange
between Systems - Private lntegrated Services Network - Generic functional protocol for the
support of supplementary Services - Inter-exchange signalling procedures and protocol .
I SO/I EC 13865: 1995, Information technology - Telecommunica tions and informa tion exchange
between Systems -
Private lntegrated Services Network - Specification, functional model and
information flows - Cal/ transfer supplementary Service.
ISO/IEC 13868:1995, Information technology - Telecommunications and information exchange
between Systems - Private lntegrated Services Network - lnter-exchange signalling protocol-
Name identification supplementary Services.
ISO/1 EC 13873: 1995, lnforma tion technology - Telecommunications and information exchange
between Systems - Private lntegrated Services Network - lnter-exchange signalling protocol -
Diversion supplementary Services.

---------------------- Page: 10 ----------------------
0 ISO/IEC ISOhEC 13869: 1995 (E)
ISO/IEC 13874: 1995, Information technology - Telecommunications and information exchange
between Systems - Private lntegrated Services Network - lnter-exchange signalling protocol - Path
replacement additional network fea ture.
CCIlT Rec. 1.112(1988), Vocabuary of terms for ISDNs (Blue Book).
CCITT Rec. l.l3( 1988), Method for the characterization of telecommunication Services supported
by an ISDN and network capabilities of an ISDN (Blue Book).
CCITT Rec. I .210( 1988), Principles of telecommunications Services supported by an ISDN and
the means to describe them (Blue Book).
ITU-T Rec. Q.950(1993), Digital Subscriber Signalling System No. 1 (DSSI) - Supplementary
Services protocols, structure and general principles.
CCITT Rec. Z. 1 00( 1988), Specification and Description Langage (Blue Book).
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:
Alerting (ISO/IEC 13865)
Answered (ISO/IEC 13865)
Application Protocol Data Unit (APDU) (ISO/lEC 11582)
(CCll-l- Rec. 1.210)
Basic Service
(ISO/1 EC 11572)
Gateway PINX
Complete Number (ISO/IEC 11571)
Interpretation APDU (ISO/IEC 11582)
Network Facility Extension (NFE) (ISOIEC 11582)
Originating PINX (lSO/IEC 11582)
(ISO/IEC 13865)
Primary Call
Private Integrated Services Network (PISN) (SO/1 EC 11579-1)
Private Integrated Services Network Exchange (PINX) (ISO/1 EC 11579-1)
Secondaty Call (ISO/lEC 13865)
Signalling (CCllT Rec. 1.112)
(CCI-FT Rec. 1.210)
Supplementarg Service
(ISO/IEC 11582)
Supplementary Service Control Entity
(lSO/IEC 11582)
Terminating PINX
(ISOIEC 13865)
Transfer by join
(ISO/IEC 13865)
Transfer by rerouteing
3

---------------------- Page: 11 ----------------------
o ISO/IEC
ISO/IEC 13869: 1995 (E)
(ISO/IEC 11582)
Transit PINX
(ISO/IEC 11574)
User
(ISO/lEC 13865)
User A
(ISO/1 EC 13865)
User B
(ISO/IEC 13865)
User C
4.2 Other definitions
4.2.1 End PINX: Within the context of a call, a PINX which is not acting as a Transit PINX, i.e. an
Originating PINX, a Terminating PINX, or a Gateway PINX.
4.2.2 Primary PINX: The End PINX which is on the end of the Primat-y Call nearest to User B.
4.2.3 redirection number: The number of a transferred User, as provided to the PINX of the
other transferred User.
4.2.4 Secondary PINX: The End PINX which is on the end of the Secondary Call nearest to
User C.
4.2.5 Transferring PINX: The End PINX which initiates the call transfer procedures on behalf
of User A.
5 List of acronyms
Application Protocol Data Unit
APDU
ASN.l Abstract Syntax Notation no. 1
Integrated Services Digital Network
ISDN
NFE Network Facility Extension
PNP Private Numbering Plan
Protocol Implementation Conformance Statement
PICS
PISN Private Integrated Services Network
PINX Private Integrated Services Network Exchange
SDL Specification and Description Language
Supplementary Service Cal1 Transfer
SS-CT
6 Signalling protocol for the support of SS=CT
8 SS-CT description
6 1
Cal1 Transfer (CT) is a supplementary Service which enables a user to transform two of that user’s
calls (at least one of which must be answered) into a new call between the two other users in the
two calls.
4

---------------------- Page: 12 ----------------------
o ISOAEC
ISODEC 13869: 1995 (E)
This supplementary Service is applicable to all basic Services defined in ISOAEC 11574.
Call transfer tan be achieved by using one of two methods; transfer by join and transfer by
rerouteing. Support of transfer by join is mandatory. Support of transfer by rerouteing is an Option,
which, if not supported by all PINXs involved in the Operation of cal1 transfer, allows fall back to
using transfer by join.
NOTE - When an active cal1 has been transferred to an alerting call, the Supervision during the
alerting Phase and the possible procedures to be followed in case the alerting call remains
unanswered are outside the scope of this International Standard.
6.2 SS-CT operational requirements
6.2.1 Provision/WithdrawaI
Provision and withdrawal shall be in accordance with 6.2.1 of ISOAEC 13865.
6.2.2 Requirements on a Transferring PINX
The basic call procedures specified in ISOAEC 11572 shall be supported. Generic procedures for
the call-related control of supplementaty Services, as specified in ISOAEC 11582 for an End PINX,
shall apply.
6.2.3 Requirements on a Primary PINX
The basic call procedures specified in ISOAEC 11572 shall be supported.
Generic procedures for the call-related control of supplementary Services, as specified in ISOAEC
11582 for an End PINX, shall apply.
6.2.4 Requirements on a Secondary PINX
The basic cal1 procedures specified in ISOAEC 11572 shall be supported.
Generic procedures for the call-related control of supplementary Services, as specified in ISOAEC
11582 for an End PINX, shall apply.
6.2.5 Requirements on a Transit PINX
The basic cal1 procedures specified in ISOAEC 11572 shall be suppotted.
Generic procedures for the call-related control of supplementary Services, as specified in ISOAEC
11582 for a Transit PINX, shall apply.
For SS-CT the requirements are limited to the passing on of Facility information elements for
which the destination, as indicated in the NFE, is not the Transit PINX.
5

---------------------- Page: 13 ----------------------
0 ISO/IEC
ISO/IEC 13869: 1995 (E)
SS-CT coding requirements
6.3
Operations
6.3.1
The following operations, defined in Abstract Syntax Notation number 1 (ASN.1) in table 1 shall
aPPlY *
Operations in support of SS-CT
Table 1 -
__---_--------------------------------------_---------
Call-Transfer-Operations {k(l) Standard(O) pssl -call-transfer(l3869) call-transfer-operations (0))
DEFINITIONS EXPLICIT TAGS ::=
BEGIN
IMPORTS
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(O)
pssl -generic-procedures (11582) msi-definition(0))
Name
FROM Name-Operations { iso( 1) Standard(O) pssl -name (13868) name-operat ions (0))
supplementaryServiceInteractionNotAllowed,
notAvailable,
invaIidCalIState
FROM General-Error-List {ccitt (0) recommendation (0) q 950 general-error-list (1))
PresentedAddressScreened,
PresentedNumberScreened,
PartyNumber,
PartySubaddress
FROM Addressing-Data-Elements { iso( 1) Standard (0) pssl -generic-procedures (11582)
addressing-data-elements (9))
6

---------------------- Page: 14 ----------------------
0 ISO/IEC
ISO/IE,C- l3369: 1995 (E)
PSSI InformationElement
FROM pssl -generic-parameters-definition { iso(1) Standard (0) pss+generic-procedures (11582)
pssl -generic-Parameters (6));
-- TYPE DEFINITIONS FOR CT OPERATIONS FOLLOW
CalITransferldentify ::= OPERATION
ARGUMENT
DummyArg
RESULT
CTldentifyRes
ERRORS{
notAvailable,
invalidCallState,
unspecified,
supplementaryServiceInteractionNotAllowed
1
CallTransferAbandon ::= OPERATION
ARGUMENT
DummyArg
CallTransferlnitiate ::= OPERATION
ARGUMENT
CTInitiateArg
RESULT
DummyRes
ERRORS{
notAvailable,
invalidCallState,
invalidRerouteingNumber,
unrecognizedCallldentity,
establishmentfailure,

---------------------- Page: 15 ----------------------
o ISO/IEC
ISOAEC 13869: 1995 (E)
unspecified,
supplementaryServiceInteractionNotAllowed
CallTransferSetup ::= OPERATION
ARGUMENT
CTSetupArg
RESULT
DummyRes
ERRORS(
notAvailable,
invalidCallState,
invalidRerouteingNumber,
unrecognizedCallldentity,
unspecified,
supplementaryServiceInteractionNotAllowed
1
CaIITransferActive ::= OPERATION
ARGUMENT
CTActiveArg
CallTransferComplete ::= OPERATION
ARGUMENT
CTCompleteArg
CallTransferUpdate ::= OPERATION
ARGUMENT
CTUpdateArg
SubaddressTransfer ::= OPERATION

---------------------- Page: 16 ----------------------
ISO/IEC 13869: 1995 (E)
o ISO/IEC
ARGUMENT
SubaddressTransferArg
-- TYPE DEFINITIONS FOR CT DATA TYPES FOLLOW
DummyArg ::= CHOICE {
NULL,
[l] IMPLICIT Extension,
[2] IMPLICIT SEQUENCE OF Extension
DummyRes ::= CHOICE {
NULL,
[ 1 ] IMPLICIT Extension,
[2] IMPLICIT SEQUENCE OF Extension
CTIdentifyRes ::= SEQUENCE {
Callldentity,
callldentity
rerouteingNumber PartyNumber,
CHOICE {
result Extension
[6] IMPLICIT Extension,
[7] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
CTlnitiateArg ::= SEQUENCE {
callldentity Callldentity,
rerouteingNumber PartyNumber,
CHOICE {
argumentExtension
[6] IMPLICIT Extension,

---------------------- Page: 17 ----------------------
0 ISO/IEC
lSO/IEC 13869: 1995 (E)
[7] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
CTSetupArg ::= SEQUENCE {
Callldentity,
callldentity
argumentExtension CHOICE {
[0] IMPLICIT Extension,
[l] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
CTActiveArg ::= SEQUENCE{
PresentedAddressScreened,
ConnectedAddress
OPTIONAL,
basicCaIIInfoElements PSSI InformationElement
-- ISO/IEC 11572 information element
-- Progress indicator is conveyed
OPTIONAL,
connectedName Name
a rgumentExtens ion CHOICE {
[9] IMPLICIT Extension,
[IO] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
CTCompleteArg ::= SEQUENCE {
endDesignation EndDesignation,
redirectionNumber PresentedNumberScreened,
OPTIONAL,
basicCallInfoElements PSS 1 I nformat ion Element
-- ISO/IEC 11572 information element
-- Progress indicator is conveyed
10

---------------------- Page: 18 ----------------------
0 ISO/IEC ISOAEC 13869: 1995 (E)
OPTIONAL,
redirectionName Name
callStatus CallStatus DEFAULT answered,
argumentExtension CHOICE {
(91 IMPLICIT Extension,
[IO] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
CTUpdateArg ::= SEQUENCE {
PresentedNumberScreened,
redirectionNumber
OPTIONAL,
redirectionName Name
OPTIONAL,
basicCalllnfoElements PSSI InformationElement
-- ISO/IEC 11572 information element
-- Progress indicator is conveyed
argumentExtension CHOKE {
[9] I.MPLlCIT Extension,
[l O] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
SubaddressTransferArg ::= SEQUENCE {
redirectionsubaddress PartySubaddress,
argumentExtension CHOKE {
[0] IMPLICIT Extension,
[l ] IMPLICIT SEQUENCE OF Extension
} OPTIONAL
CallStatus ::= ENUMERATED{
11

---------------------- Page: 19 ----------------------
ISO/IEC 13869: 1995 (E) 0 ISO/IEC
answered(O),
alerting(1)
1
Callldentity ::= NumericString (SIZE (1. .4))
EndDesignation ::= ENUMERATED {
primatyEnd(O),
secondatyEnd(1)
-- TYPE DEFINITIONS FOR CT ERRORS FOLLOW
Unspecified ERROR PARAMETER Extension
-- VALUE DEFINITIONS FOR OPERATIONS AND ERRORS FOLLOW
unspecified Unspecified ::= 1008
* l -
calITransferldentify CaIITransferIdentify .- 7
n n -
CaIITransferAbandon CalITransferAbandon . .- 8
l *-
call’rransferlnitiate CallTransferlnitiate m.- 9
l --
calITransferSetup CallTransferSetup .- 10
‘=-
calITransferActive CalITransferActive . .- 11
callTransferComplete CalITransferComplete ::=12
l l -
CallTransferUpdate CallTransferUpdate eo- 13
SubaddressTransfer SubaddressTransfer ::=14
invalidRerouteingNumber ERROR ::= 1004
00
used when establishment of the new
12

---------------------- Page: 20 ----------------------
0 lSO/IEC ISO/IEC 13869: 1995 (E)
-0
connection fails because
-- the rerouteingNumber is not a valid
-- PISN address
unrecognizedCallIdentity ERROR ::= 1005
00
used when establishment of the new
-- connection fails because it could not be
-- associated with a SS-CT entity
-- at the Secondary PINX
establishment Failure
ERROR ::= 1006
00
used when establishment of the new
-- connection fails and no other error applies
00
END
of Call-Transfer-Operations
6.3.2 Information elements
6.3.2.1 Facility information element
APDUs of the operations defined in 6.3.1 shall be coded in the Facility information element in
accordance wit h ISO/1 EC 11582.
When conveying the invoke APDU of the operations defined in 6.3.1, the destinationEntity data
element of the NFE shall contain value endPINX.
When conveying the invoke APDU of operations CallTransferAbandon, callTransferComplete,
callTransferActive, CalITransferUpdate or SubaddressTransfer, the Interpretation APDU shall
contain value discardAnyUnrecognisedInvokePdu.
When conveying the invoke APDU of Operation callTransferSetup, the Interpretation APDU shall
contain value clearCalIIfAnyInvokePduNotRecognised.
When conveying the invoke APDU of Operation callTransferldentify or callTransferlnitiate, the
Interpretation APDU shall be included with the value rejectUnrecognizedlnvokePdu or omitted.
13

---------------------- Page: 21 ----------------------
ISO/IEC 13869: 1995 (E) 0 ISO/IEC
Information elements embedded in the Facility information
6.3.2.2
element
APDUs of the operations defined in 6.3.1 may contain information elements defined in and coded
according to ISO/IEC 11572. These shall be embedded in data elements of type
PSSI InformationElement as specified in Annex B of ISO/IEC 11582.
In data element basicCalllnfoElements, which is of type PSSI InformationElement, the embedded
contents shall be coded as Progress indicator information elements specified in ISO/IEC 11572 .
6.3.2.3 Other information elements
The following information elements used during the establishment of the new connection
(transfer by rerouteing) shall be coded as specified in ISO/1 EC 11572 :
Bearer capability,
Called Party number,
Cause,
Sending complete.
6.3.3 Messages
Except for cases where a basic call message is to be conveyed at the same time, the Facility
information element shall be conveyed in a FACILITY message as specified in ISO/IEC 11582.
The following messages used during the establishment of the new connection and release of the
old connections (in case of transfer by rerouteing) shall be as specified in lSO/IEC 11572 and,
where applicable, augmented in ISO/IEC 11582:
CALL PROCEEDING
CONNECT
CONNECT ACKNOWLEDGE
DISCONNECT
PROGRESS
RELEASE
RELEASE COMPLETE
SETUP
SS-CT state definitions
6.4.1 States at a Transferring PINX
The procedures at the Transferring PINX are written in terms of the following conceptual states
existing within the SS-CT control entity in that PINX in association with a particular Call Transfer
request from User A.
14

---------------------- Page: 22 ----------------------
ISO/IEC 13869: 1995 (E)
0 ISO/IEC
6.4.1.1 CT-ldle
SS-CT is not operating.
6.4.1.2 CT-Await-Answer-From-User-C
A calITransferComplete invoke APDU with callStatus having value aletting has been sent to the
Primary PINX. This state may be used during transfer by join.
CT-Await-ldentify-Response
6.4.1.3
A callTransferldentify invoke APDU has been sent to the Secondary PINX. This state is used
during transfer by rerouteing.
6.4.1.4 CT-Await-lnitiate-Response
A call’rransferlnitiate invoke APDU has been sent to the Primary PINX. This state is used during
transfer by rerouteing.
6.4.2 States at a Primar-y PINX
The procedures at the Primary PINX are written in terms of the following conceptual states existing
within the SS-CT control entity in that PINX in association with the primary call, i.e. a particular call of
User B.
6.4.2.1 CT-ldle
SS-CT is not operating.
6.4.2.2 CT-Await-Setup-Response
A calITransferSetup invoke APDU has been sent to the Secondary PINX. This state is used during
transfer by rerouteing.
6.4.2.3 CT-Await-Connect
The Primary Call has been transferred to an alerting Secondary User, and the Primary User has
been notified. A CONNECT message indicating answering by the Secondary User is awaited.
6.4.3 States at a Secondary PINX
The procedures at the Secondary PINX are written in terms of the following conceptual states
existing within the SS-CT control entity in that PINX in association with a particular call of User C.
6.4.3.1 CT-ldle
SS-CT is not operating.
6.4.3.2 CT-Await-Setup
A calITransferldentify return result APDU has been sent to the Transferring PINX. This state is
used during transfer by rerouteing.
15

---------------------- Page: 23 ----------------------
ISO/IEC 13869: 1995 (E)
0 ISO/IEC
6.5 SS-CT signalling procedures
References in this clause to protocol control states refer to basic call protocol control states
defined in ISO/IEC 11572.
NOTE - The specification in this section is based on each of the End PINXs being a different PINX,
but this section is also applicable to seenarios where two of the three PINXs are the Same. In those
seenarios some of the signalling procedures and message flows described in this section are
internal to the PINX implementation and therefore outside the scope of this International
Standard.
Annex C contains some examples of message sequences.
6.5.1 Actions at
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.