ISO/IEC 18052:2000
(Main)Information technology — Telecommunications and information exchange between systems — Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III
Information technology — Telecommunications and information exchange between systems — Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Protocole pour applications en télécommunications supportées par ordinateur (CSTA) en phase III
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 18052
First edition
2000-07-15
Information technology —
Telecommunications and information
exchange between systems — Protocol
for Computer Supported
Telecommunications Applications (CSTA)
Phase III
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Protocole pour applications en
télécommunications supportées par ordinateur (CSTA) en phase III
Reference number
ISO/IEC 18052:2000(E)
©
ISO/IEC 2000
---------------------- Page: 1 ----------------------
ISO/IEC 18052:2000(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO/IEC 2000
All 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 either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 � CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO/IEC 2000 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 18052:2000(E)
Contents
Foreword x
Introduction xi
1 Scope 1
2 Normative References 1
3 Conformance 2
3.1 Static Requirements 2
3.2 Dynamic Requirements 2
3.3 PICS Requirement 2
4 Definitions and Abbreviations 2
5 CSTA Service Definition Model 2
5.1 CSTA Application Layer Structure 2
5.2 Remote Operations 2
5.3 The CSTA Service Response 3
5.4 Cross Referencing of Event Reports 3
5.5 Handling of Private Data 3
6 Interconnection service boundary 3
7 Security 3
8 Association Management 4
8.1 Implicit association 4
8.2 Dynamic association management using ACSE 4
8.2.1 Encoding of application context name 4
8.2.2 Encoding of application context information 4
9 CSTA parameter types 8
9.1 Switching function objects 8
9.2 Device Identifiers 9
9.3 Call and connection identifiers 11
9.4 Connection states 12
9.5 Status reporting 13
9.6 Device and feature types and other parameters 15
9.7 Security 20
9.8 Common extensions 21
9.9 Call control 22
9.10 Capability Exchange 24
9.11 Call Detail Record 73
9.12 Charge information 75
9.13 Data call types 76
9.14 Escape types 77
9.15 Media services 78
9.16 Physical device features 80
9.17 Data Collection 82
9.18 Event Cause 83
9.19 Error Value 85
iii
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC 18052:2000(E)
10 Event Report Service 90
11 Capability exchange services 95
11.1 Services 95
11.1.1 Get logical device information 95
11.1.2 Get physical device information 97
11.1.3 Get switching function capabilities 98
11.1.4 Get switching function devices 101
11.1.5 Switching function devices 102
12 System services 103
12.1 Registration services 103
12.1.1 Change system status filter 103
12.1.2 System register 104
12.1.3 System register abort 105
12.1.4 System register cancel 106
12.2 Services 107
12.2.1 Request system status 107
12.2.2 System status 108
12.2.3 Switching function capabilities changed 109
12.2.4 Switching function devices changed 110
13 Monitoring services 111
13.1 Services 111
13.1.1 Change monitor filter 111
13.1.2 Monitor start 112
13.1.3 Monitor stop 113
14 Snapshot services 114
14.1 Services 114
14.1.1 Snapshot call 114
14.1.2 Snapshot device 116
14.1.3 Snapshot calldata 117
14.1.4 Snapshot devicedata 118
15 Call control services and events 119
15.1 Services 119
15.1.1 Accept call 119
15.1.2 Alternate call 120
15.1.3 Answer call 121
15.1.4 Call back call-related 122
15.1.5 Call back message call-related 123
15.1.6 Camp on call 124
15.1.7 Clear call 125
15.1.8 Clear Connection 126
15.1.9 Conference call 127
15.1.10 Consultation call 128
15.1.11 Deflect call 129
iv
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 18052:2000(E)
15.1.12 Dial digits 130
15.1.13 Directed pickup call 131
15.1.14 Group pickup call 132
15.1.15 Hold call 133
15.1.16 Intrude call 134
15.1.17 Join call 135
15.1.18 Make call 136
15.1.19 Make predictive call 137
15.1.20 Park call 139
15.1.21 Reconnect call 140
15.1.22 Retrieve call 141
15.1.23 Single step conference call 142
15.1.24 Single step transfer call 143
15.1.25 Transfer call 144
15.2 Events 145
15.2.1 Bridged 145
15.2.2 Call cleared 146
15.2.3 Conferenced 147
15.2.4 Connection cleared 148
15.2.5 Delivered 149
15.2.6 Digits dialed 150
15.2.7 Diverted 151
15.2.8 Established 152
15.2.9 Failed 153
15.2.10 Held 154
15.2.11 Network capabilities changed 155
15.2.12 Network reached 156
15.2.13 Offered 157
15.2.14 Originated 158
15.2.15 Queued 159
15.2.16 Retrieved 160
15.2.17 Service initiated 161
15.2.18 Transferred 162
16 Call associated features 163
16.1 Services 163
16.1.1 Associate data 163
16.1.2 Cancel telephony tones 164
16.1.3 Generate digits 165
16.1.4 Generate telephony tones 166
16.1.5 Send user information 167
16.2 Events 168
16.2.1 Call information 168
16.2.2 Charging 169
16.2.3 Digits generated 170
16.2.4 Telephony tones generated 171
16.2.5 Service completion failure 172
17 Media attachment services and events 173
17.1 Services 173
v
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 18052:2000(E)
17.1.1 Attach media service 173
17.1.2 Detach media service 174
17.2 Events 175
17.2.1 Media attached 175
17.2.2 Media detached 176
18 Routeing services 177
18.1 Registration services 177
18.1.1 Route register 177
18.1.2 Route register abort 178
18.1.3 Route register cancel 179
18.2 Services 180
18.2.1 Re-Route 180
18.2.2 Route end 181
18.2.3 Route reject 182
18.2.4 Route request 183
18.2.5 Route select 184
18.2.6 Route used 185
19 Physical device features 186
19.1 Services 186
19.1.1 Button press 186
19.1.2 Get auditory apparatus information 187
19.1.3 Get button information 188
19.1.4 Get display 189
19.1.5 Get hookswitch status 190
19.1.6 Get lamp information 191
19.1.7 Get lamp mode 192
19.1.8 Get message waiting indicator 193
19.1.9 Get microphone gain 194
19.1.10 Get microphone mute 195
19.1.11 Get ringer status 196
19.1.12 Get speaker mute 197
19.1.13 Get speaker volume 198
19.1.14 Set button information 199
19.1.15 Set display 200
19.1.16 Set hookswitch status 201
19.1.17 Set lamp mode 202
19.1.18 Set message waiting indicator 203
19.1.19 Set microphone gain 204
19.1.20 Set microphone mute 205
19.1.21 Set ringer status 206
19.1.22 Set speaker mute 207
19.1.23 Set speaker volume 208
19.2 Events 209
19.2.1 Button information 209
19.2.2 Button press 210
19.2.3 Display updated 211
vi
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 18052:2000(E)
19.2.4 Hookswitch 212
19.2.5 Lamp mode 213
19.2.6 Message waiting 214
19.2.7 Microphone gain 215
19.2.8 Microphone mute 216
19.2.9 Ringer status 217
19.2.10 Speaker mute 218
19.2.11 Speaker volume 219
20 Logical device features 220
20.1 Services 220
20.1.1 Call back non-call-related 220
20.1.2 Call back message non-call-related 221
20.1.3 Cancel call back 222
20.1.4 Cancel call back message 223
20.1.5 Get agent state 224
20.1.6 Get auto answer 225
20.1.7 Get auto work mode 226
20.1.8 Get caller id status 227
20.1.9 Get do not disturb 228
20.1.10 Get forwarding 229
20.1.11 Get last number dialed 230
20.1.12 Get routeing mode 231
20.1.13 Set agent state 232
20.1.14 Set auto answer 233
20.1.15 Set auto work mode 234
20.1.16 Set caller id status 235
20.1.17 Set do not disturb 236
20.1.18 Set forwarding 237
20.1.19 Set routeing mode 238
20.2 Events 239
20.2.1 Agent busy 239
20.2.2 Agent logged off 240
20.2.3 Agent logged on 241
20.2.4 Agent not ready 242
20.2.5 Agent ready 243
20.2.6 Agent working after call 244
20.2.7 Auto answer 245
20.2.8 Auto work mode 246
20.2.9 Call back 247
20.2.10 Call back message 248
20.2.11 Caller id status 249
20.2.12 Do not disturb 250
20.2.13 Forwarding 251
20.2.14 Routeing mode 252
21 Device maintenance events 253
21.1 Events 253
21.1.1 Back in service 253
21.1.2 Device capabilities changed 254
21.1.3 Out of service 255
vii
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 18052:2000(E)
22 I/O services 256
22.1 Registration services 256
22.1.1 I/O register 256
22.1.2 I/O register abort 257
22.1.3 I/O register cancel 258
22.2 Services 259
22.2.1 Data path resumed 259
22.2.2 Data path suspended 260
22.2.3 Fast data 261
22.2.4 Resume data path 262
22.2.5 Send broadcast data 263
22.2.6 Send data 264
22.2.7 Send multicast data 265
22.2.8 Start data path 266
22.2.9 Stop data path 267
22.2.10 Suspend data path 268
23 Data Collection Services 269
23.1 Services 269
23.1.1 Data Collected 269
23.1.2 Data Collection Resumed 271
23.1.3 Data Collection Suspended 272
23.1.4 Resume Data Collection 273
23.1.5 Start Data Collection 274
23.1.6 Stop Data Collection 275
23.1.7 Suspend Data Collection 276
24 Voice unit services and events 277
24.1 Services 277
24.1.1 Concatenate message 277
24.1.2 Delete message 278
24.1.3 Play message 279
24.1.4 Query voice attribute 280
24.1.5 Record message 281
24.1.6 Reposition 282
24.1.7 Resume 283
24.1.8 Review 284
24.1.9 Set voice attribute 285
24.1.10 Stop 286
24.1.11 Suspend 287
24.1.12 Synthesize message 288
24.2 Events 289
24.2.1 Play 289
24.2.2 Record 290
24.2.3 Review 291
24.2.4 Stop 292
24.2.5 Suspend play 293
24.2.6 Suspend record 294
viii
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 18052:2000(E)
24.2.7 Voice attribute changed 295
25 Call detail record services 296
25.1 Services 296
25.1.1 Call detail records notification 296
25.1.2 Call detail records report 297
25.1.3 Send stored call detail records 298
25.1.4 Start call detail records transmission 299
25.1.5 Stop call detail records transmission 300
26 Vendor specific extensions services and events 301
26.1 Registration services 301
26.1.1 Escape register 301
26.1.2 Escape register abort 302
26.1.3 Escape register cancel 303
26.2 Services 304
26.2.1 Escape 304
26.2.2 Private data version selection 305
26.3 Events 306
26.3.1 Private event 306
Annex A - Protocol Implementation Conformance Statement (PICS) Proforma 307
ix
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 18052:2000(E)
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-governmental, in
liaison with ISO and IEC, also take part in the work.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
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 national bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this International Standard may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
International Standard ISO/IEC 18052 was prepared by ECMA (as ECMA-285) and was adopted, under a special
"fast-track procedure", by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its
approval by national bodies of ISO and IEC.
Annex A forms a normative part of this International Standard.
x
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 18052:2000(E)
Introduction
This International Standard defines Phase III of Protocol for Computer Supported Telecommunications
Applications (CSTA) for OSI Layer 7 communication between a computing network and a telecommunications
network. This International Standard is part of a Suite of Standards and Technical Reports for Phase III of CSTA.
All of the Standards and Technical Reports in the Suite are based on practical experience of ECMA member
companies and each one represents a pragmatic and widely-based consensus.
The evolution of this Suite began with CSTA Phase I, which included the CSTA Services and Protocol Standards
(ECMA-179 and ECMA-180). In Phase II, Technical Report ECMA TR/68 was added illustrating how CSTA
services and events may be used in typical call scenarios.
Phase III of CSTA extends the previous Phase II Standards (ECMA-217 and ECMA-218) in major theme directions
as well as numerous details. This incorporates technology based upon the versit CTI Encyclopedia (Version 1.0),
which was contributed to ECMA by versit. Major areas of advancement include:
New categories of services and events such as capabilities exchange, charging, media attachment services, call
data recording (CDR), etc.
Additional services and events for call and device control.
Enhancement to existing services and events.
Organization of services and events to reflect a grouping based on function (call control, device control, etc.).
xi
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 18052:2000(E)
INTERNATIONAL STANDARD
Information technology - Telecommunications and information exchange
between systems - Protocol for Computer Supported Telecommunications
Applications (CSTA) Phase III
1 Scope
This International Standard specifies application protocol data units (APDUs) for the services described in ISO/IEC
18051, Information technology - Telecommunications and information exchange between systems - Services for
Computer Supported Telecommunications Applications (CSTA) Phase III.
Clause 5 to clause 7 inclusive describes the concepts underlying the Remote Operations model, notation and service.
Clause 8 to clause 26 inclusive contains CSTA-specific protocol details and forms the main part of this
International Standard.
The protocol in this International Standard operates in the context of an application association.
2 Normative References
The following normative documents contain provisions which, through reference in this text, constitute provisions
of this International Standard. For dated references, subsequent amendments to, or revisions of, any of these
publications do not apply. However, parties to agreements based on this International Standard are encouraged to
investigate the possibility of applying the most recent editions of the normative documents indicated below. For
undated references, the latest edition of the normative document referred to applies. Members of IEC and ISO
maintain registers of currently valid International Standards.
ISO/IEC 8649:1996, Information technology - Open Systems Interconnection - Service definition for the
Association Control Service Element (this corresponds to ITU-T Rec. X.217 1995).
ISO/IEC 8650-1:1996, Information technology - Open Systems Interconnection - Connection-oriented
protocol for the Association Control Service Element: Protocol specification (this
corresponds to ITU-T Rec. X.227 4/95).
ISO/IEC 9545:1994, Information technology - Open Systems Interconnection - Application Layer structure.
ISO/IEC 13712-1:1995, Information technology - Remote Operations: Concepts, model, and notation (this
corresponds to ITU-T Rec. X.880, 1994).
ISO/IEC 13712-2:1994, Information technology - Remote Operations: OSI realisations - Remote Operations
Service Element (ROSE) service definition (this corresponds to ITU-T Rec. X.881,
1994).
ISO/IEC 13712-3:1994, Information technology - Remote Operations: OSI realisations - Remote Operations
Service Element (ROSE) protocol specification (this corresponds to ITU-T Rec. X.882,
1994).
ISO/IEC 18051:2000, Information technology - Telecommunications and information exchange between
systems - Services for Computer Supported Telecommunications Applications (CSTA)
Phase III.
ISO/IEC TR 18053:2000, Information technology - Telecommunications and information exchange between
systems - Glossary of definitions and terminology for Computer Supported
Telecommunications Applications (CSTA) Phase III.
1
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 18052:2000(E)
ITU-T X.680, Information technology - Abstract Syntax Notation One (ASN.1): Specification of
basic notation.
ITU-T X.690, Information technology - ASN.1 encoding rules - Specificaion of Basic Encoding Rules
(BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER).
3 Conformance
A manufacturer may select any part of the CSTA protocol, as specified in this International Standard, for
implementation on a system as long as it satisfies the minimum conformance requirements as specified in clause 3
of ISO/IEC 18051.
A Protocol Implementation Conformance Statement (PICS) shall be used to specify the operations which are
provided by a particular implementation. A PICS shall also specify the parameter options which are used.
3.1 Static Requirements
To conform to this International Standard, a system shall support the transfer syntax (derived from the encoding
rules specified in ITU-T X.690) named {joint-iso-ccitt asn1(1) basic-encoding(1)}; for the purpose of generating
and interpreting CSTA protocol information as defined by the abstract syntax “CSTA-ASN.1-Object-Descriptor”
for the operations supported.
3.2 Dynamic Requirements
To conform to this International Standard, a system shall:
a. follow the procedures as specified in this International Standard, and ISO/IEC 18051, relevant to each
CSTA operation that the system claims to implement; and
b. satisfy the definitions, as specified in ISO/IEC 18051, relevant to each CSTA service that the system claims
to implement.
3.3 PICS Requirement
To conform to this International Standard, the following shall be stated by the implementer when defining a PICS
corresponding to an application or implementation:
a. which CSTA operations, as defined in ISO/IEC 18051, are supported by the system for the particular
implementation; and
b. which optional parameters are supported by the PDUs belonging to the supported operations.
A PICS proforma is given in Annex A of this International Standard.
4 Definitions and Abbreviations
CSTA-specific terminology is defined in ISO/IEC TR 18053. For the purposes of this International Standard, the
following additional definitions, defined in other standards, shall apply:
Remote Operations (as per ISO/IEC 13712-1)
Application Association (as per ISO/IEC 8649)
Application Context (as per ISO/IEC 8649)
5 CSTA Service Definition Model
5.1 CSTA Application Layer Structure
The CSTA Application Layer structure conforms to the model described in ISO/IEC 9545.
5.2 Remote Operations
The services of CSTA are modeled as Remote Operations as described in ISO/IEC 13712-1. Typically, one entity
requests that a particular operation be performed; the other entity attempts to perform the operation and responds to
the requestor. Consequently the operation of the protocol is an elementary request/reply interaction, supported
within the OSI Application Layer, and carried out within the context of an application association.
2
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 18052:2000(E)
For some of the CSTA services, the entity to which the request is sent generates a reply which can indicate success
or failure. For these services, CSTA shall adopt the operations Class 2, defined in ISO/IEC 13712-2 as:
Asynchronous, reporting success or failure (result or error).
For some of the CSTA services, the entity to which the request is sent generates a reply which can only indicate
failure. For these services, CSTA shall adopt the operations Class 3, defined in ISO/IEC 13712-2 as:
Asynchronous, reporting failure (error) only, if any.
For some of the CSTA services, particularly the ongoing reporting of events, no reply is generated. For these
services, CSTA shall adopt the operations Class 5, defined in ISO/IEC 13712-2 as:
Asynchronous, outcome not reported.
The protocol description for the particular service defines the relevant class of the operation used for that service.
CSTA shall correlate the single response, denoting success or failure, with the originating request by using the
mechanisms within the ROSE protocol.
5.3 The CSTA Service Response
CSTA employs a generic response mechanism which is, in principle, decoupled from the specifics of the switching
activity. The following points describe the operation of the CSTA service response:
a. Specific services may have an unconfirmed mode where responses to correct requests are not returned.
b. The server shall check the correctness of the request (e.g. syntactical checks) before issuing the response.
Incorrect requests shall result in an error response, even in the unconfirmed mode.
5.4 Cross Referencing of Event Reports
A computer application process may need to cross reference a CSTAEventReport to one of the following:
a. a CSTA Object ID (Call ID or Device ID),
b. an earlier Monitor request; or
c. one of many Monitor requests (pertaining to the same CSTA Object).
For the above scenarios the necessary cross referencing function may be fulfilled by use of the parameter
“MonitorCrossRefID”. The content of MonitorCrossRefID depends upon the context and it may be one of the
following: Call ID, Device ID or another independently switch managed static identifier. The independent identifier
may have a unique correlation to either: one device, one call, or one monitor request.
The switching system limit on the number of monitor requests on one CSTA Object (Call or Device) is an
implementation option. This International Standard does not stipulate how many monitor requests on one object are
to be supported by the switch. If using Static Device or Call identifiers the limit can only be one.
5.5 Handling of Private Data
If an entity receives the parameter CSTAPrivateData, and it can not recognize the information contained, the
parameter shall be discarded, and the rest of the message shall be processed.
6 Interconnection service boundary
The protocol in this International Standard is an OSI Application Layer protocol and uses the Remote Operations
protocol defined in ISO/IEC 13712-3. The Remote Operations protocol assumes certain services are provided by
the underlying layers, and these services are also assumed by the protocol for CSTA.
7 Security
This protocol also provides a mechanism for secure transmission of CSTA PDUs as defined in this International
Standard.
3
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 14 ----------------------
ISO/IEC 18052:2000(E)
8 Association Management
The protocol in this International Standard operates in the context of an application association. This application
association can be either:
an implicit association achieved via off-line agreement; or
a dynamically negotiated association realized through the use of ACSE.
8.1 Implicit association
An a-priori agreement exists between switching and computing functions: the application context is implicit,
dynamic negotiation is not possible.
8.2 Dynamic association management using ACSE
ACSE requires the use of an application context Name (as defined by ISO 8649). This is an object id that uniquely
identifies CSTA independently of the different versions of the protocol.
The CSTA protocol version information is carried within the User Information field of the A-ASSOCIATE request
and response PDUs.
An application context is established (using ACSE) as follows:
the system generating the A-ASSOCIATE request includes the CSTA application context name and a list of all
protocol versions that it is prepared to offer in the User Information field;
on receipt of the A-ASSOCIATE request, the receiving system selects the protocol version to be used by
identifying the highest version that is common to both systems;
the protocol version selected is conveyed to the requestor in the User Information field of the A-ASSOCIATE
response.
In addition to negotiating the protocol version, it is necessary for the requesting and responding systems to specify
the CSTA services that they support. As with the protocol version information, this is also achieved by carrying
additional information in the User Information field of the A-ASSOCIATE request and response PDUs. The
application association requestor shall:
list the services required from the serving application;
list the services it can supply.
The responder shall include similar information for the responding application. At this point the association
requestor will either accept or reject the association.
8.2.1 Encoding of application context name
CSTA-application-context-name
{ iso( 1) identified-organization( 3) icd-ecma( 12)
standard( 0) csta( 218)}
-- Common to all CSTA protocol versions
8.2.2 Encoding of application context information
CSTA-application-context-information-csta3
{ iso( 1) identified-organization( 3) icd-ecma( 12)
standard( 0) csta3( 285) application-context-information( 200) }
DEFINITIONS ::=
BEGIN
IMPORTS
CSTAFunctionality FROM CSTA-application-context-information
{ iso( 1) identified-organization( 3) icd-ecma( 12)
standard( 0) csta2( 218) application-context-information( 200) };
ACSEUserInformationForCSTA ::= CHOICE
{ oldDefinition OldACSEUserInformationForCSTA,
newDefinition [0] IMPLICIT NewACSEUserInformationForCSTA }
4
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC 18052:2000(E)
OldACSEUserInformationForCSTA ::= SEQUENCE
{cSTAVersion CSTAVersion,
cSTAFunctionsRequiredByApplication CSTAFunctionality,
cSTAFunctionsThatCanBeSupplied CSTAFunctionality }
NewACSEUserInformationForCSTA ::= SEQUENCE
{ cSTAVersion CSTAVersion,
--
--Note that the following two parameters are defined in ECMA-218 (CSTA Phase II).
--They are defined in the context of CSTA Phase II Services and Events for
--backward compatibility considerations.
--For CSTA Phase III (and later), implementations should use CSTA Capability Exchange Services
--to determine the Services and Events supported by a switching function.
--
cSTAFunctionsRequiredByApplication [0] IMPLICIT CSTAFunctionality OPTIONAL,
cSTAFunctionsThatCanBeSupplied [1] IMPLICIT CSTAFunctionality OPTIONAL,
cSTAPrivateDataVersionList [2] IMPLICIT CSTAPrivateDataVersionList OPTIONAL}
CSTAPrivateDataVersionList ::= SEQUENCE OF INTEGER
CSTAVersion ::= BIT STRING
{ versionOne (0), -- CSTA protocol version defined in ECMA-180
versionTwo (1), -- CSTA protocol version defined in ECMA-218
versionThree (2), -- CSTA protocol version defined in ECMA-285
versionFour (3), -- CSTA protocol version defined in ISO/IEC 18052
versionFive (4), -- Reserved for future use
versionSix (5), -- Reserved for future use
versionSeven (6), -- Reserved for future use
versionEight (7), -- Reserved for future use
versionNine (8), -- Reserved for future use
versionTen (9), -- Reserved for future use
versionEleven (10), -- Reserved for future use
versionTwelve (11), -- Reserved for future use
versionThirteen (12), -- Reserved for future use
versionFourteen (13), -- Reserved for future use
versionFifteen (14), -- Reserved for future use
versionSixteen (15)} -- Reserved for future use
CallControlServices ::= BIT STRING
{ acceptCall (0),
alternateCall (1),
answerCall (2),
callBack (3),
callBackMessage (4),
campOnCall (5),
clearCall (6),
clearConnection (7),
conferenceCall (8),
consultationCall (9),
deflectCall (10),
dialDigits (11),
directedPickupCall (12),
groupPickupCall (13),
holdCall (14),
intrudeCall (15),
joinCall (16),
makeCall (17),
makePredictiveCall (18),
parkCall (19),
reconnectCall (20),
retrieveCall (21),
singleStepConference (22),
singleStepTransfer (23),
transferCall (24)}
CallAssociatedServices ::= BIT STRING
{ associateData (0),
5
© ISO/IEC 2000 - All rights reserved
---------------------- Page: 16 ----------------------
ISO/IEC 18052:2000(E)
cancelTelephonyTones (1),
generateDigits (2),
generateTelephonyTones (3),
sendUserInformation (4)}
MediaAttachmentServices ::= BIT STRING
{ attachMediaService (0),
detachMediaService (1)}
RouteingServices ::= BIT STRING
{ routeRegister ( 0),
routeRegisterCancel ( 1),
routeRegisterAbort ( 2),
reRoute ( 3),
routeEnd ( 4),
routeReject ( 5),
routeRequest ( 6),
routeSelect ( 7),
routeUsed ( 8)}
VoiceUnitServices ::= BIT STRING
{ concatenateMessage (0),
deleteMessage (1),
playMessage (2),
queryVoiceAttribute (3),
recordMessage (4),
reposition (5),
resume (6),
review (7),
setVoiceAttribut
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.