ISO/IEC 18056:2005

Information technology — Telecommunications and information exchange between systems — XML Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III

ISO/IEC 18056:2005 specifies an XML protocol for the services described in ECMA-269, Services for Computer Supported Telecommunications Applications (CSTA) Phase III. It provides an alternative protocol to the ASN.1 based protocol specified in ECMA-285.

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Protocole XML pour applications en télécommunications supportées par ordinateur (CSTA) en phase III

General Information

• Status: Withdrawn
• Publication Date: 10-Jul-2005
• Withdrawal Date: 10-Jul-2005
• ICS: 35.100.30 - Network layer
• 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: 10-Dec-2007

Relations

• Revised: ISO/IEC 18056:2007 - Information technology — Telecommunications and information exchange between systems — XML Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III
• Effective Date: 15-Apr-2008
• Revises: ISO/IEC 18056:2004 - Information technology — Telecommunications and information exchange between systems — XML Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 18056
Second edition
2005-07-15

Information technology —
Telecommunications and information
exchange between systems — XML
Protocol for Computer-Supported
Telecommunications Applications (CSTA)
Phase III
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Protocole XML pour applications en
télécommunications supportées par ordinateur (CSTA) en phase III




Reference number
ISO/IEC 18056:2005(E)
©
ISO/IEC 2005

---------------------- Page: 1 ----------------------
ISO/IEC 18056:2005(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 2005
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 [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2005 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 18056:2005(E)
Contents
1  Scope 1
2  Conformance 1
2.1 Static Requirements 1
2.2 Dynamic Requirements 1
2.3 PICS Requirement 1
3  References 2
3.1 ECMA/ISO Standards and Technical Reports 2
3.2 World Wide Web Consortium Specifications 2
4  Definitions and Abbreviations 2
5  CSTA Service Definition Model 2
5.1 Request/Response Interactions 2
5.2 Request/Response Protocol Requirements 2
5.3 Cross Referencing of Event Reports 3
5.4 Handling of Private Data 3
6  Interconnection service boundary 3
7  Association Management 3
7.1 Implicit association 3
7.2 Explicit association 3
8  XML Template Description 3
9  CSTA parameter types 5
9.1 Switching function objects 5
9.2 Device Identifiers  6
9.3 Call and connection identifiers  9
9.4 Connection states  11
9.5 Status reporting  12
9.6 Device and feature types and other parameters  17
9.7 Security  26
9.8 Common extensions  27
9.9 Call control  28
© ISO/IEC 2005 - All rights reserved
iii

---------------------- Page: 3 ----------------------
ISO/IEC 18056:2005(E)
9.10 Capability Exchange  33
9.11 Call Detail Record  95
9.12 Charge information  98
9.13 Data call types  100
9.14 Escape types  101
9.15 Media services  102
9.16 Physical device features  105
9.17 Data Collection  108
9.18 Event Cause  109
9.19 Error Value  111
9.20 Empty (null element)  116
10  Top level schema 117
11  Capability exchange services 123
11.1Services 123
11.1.1 Get csta features 123
11.1.2 Get logical device information 125
11.1.3 Get physical device information 127
11.1.4 Get switching function capabilities 128
11.1.5 Get switching function devices 132
11.1.6 Switching function devices 133
12  System services 134
12.1 Registration services 134
12.1.1 Change system status filter 134
12.1.2 System register 135
12.1.3 System register abort 136
12.1.4 System register cancel 137
12.2Services  138
12.2.1 Request system status 138
12.2.2 System status 139
12.2.3 Switching function capabilities changed 140
12.2.4 Switching function devices changed 141
13  Monitoring services 142
13.1Services 142
13.1.1 Change monitor filter 142
© ISO/IEC 2005 - All rights reserved
iv

---------------------- Page: 4 ----------------------
ISO/IEC 18056:2005(E)
13.1.2 Monitor start 143
13.1.3 Monitor stop 144
14  Snapshot services 145
14.1Services 145
14.1.1 Snapshot call 145
14.1.2 Snapshot device 146
14.1.3 Snapshot calldata 147
14.1.4 Snapshot devicedata 148
15  Call control services and events 149
15.1Services 149
15.1.1 Accept call 149
15.1.2 Alternate call 150
15.1.3 Answer call 151
15.1.4 Call back call-related 152
15.1.5 Call back message call-related 153
15.1.6 Camp on call 154
15.1.7 Clear call 155
15.1.8 Clear Connection 156
15.1.9 Conference call 157
15.1.10 Consultation call 158
15.1.11 Deflect call 159
15.1.12 Dial digits 160
15.1.13 Directed pickup call 161
15.1.14 Group pickup call 162
15.1.15 Hold call 163
15.1.16 Intrude call 164
15.1.17 Join call 165
15.1.18 Make call 166
15.1.19 Make predictive call 167
15.1.20 Park call 169
15.1.21 Reconnect call 170
15.1.22 Retrieve call 171
15.1.23 Send Message 172
15.1.24 Single step conference call 173
15.1.25 Single step transfer call 174
15.1.26 Transfer call 175
© ISO/IEC 2005 - All rights reserved
v

---------------------- Page: 5 ----------------------
ISO/IEC 18056:2005(E)
15.2Events  176
15.2.1Bridged 176
15.2.2 Call cleared 177
15.2.3Conferenced 178
15.2.4 Connection cleared 179
15.2.5Delivered 180
15.2.6 Digits dialed 181
15.2.7Diverted 182
15.2.8Established 183
15.2.9Failed 184
15.2.10Held 185
15.2.11 Network capabilities changed 186
15.2.12 Network reached 187
15.2.13Offered 188
15.2.14Originated 189
15.2.15Queued 190
15.2.16Retrieved 191
15.2.17 Service initiated 192
15.2.18Transferred 193
16  Call associated features 194
16.1Services 194
16.1.1 Associate data 194
16.1.2 Cancel telephony tones 195
16.1.3 Change connection information 196
16.1.4 Generate digits 197
16.1.5 Generate telephony tones 198
16.1.6 Send user information 199
16.2Events  200
16.2.1 Call information 200
16.2.2Charging 201
16.2.3 Digits generated 202
16.2.4 Telephony tones generated 203
16.2.5 Service completion failure 204
17  Media attachment services and events 205
17.1Services 205
17.1.1 Attach media service 205
17.1.2 Detach media service 206
© ISO/IEC 2005 - All rights reserved
vi

---------------------- Page: 6 ----------------------
ISO/IEC 18056:2005(E)
17.2 Events  207
17.2.1 Media attached 207
17.2.2 Media detached 208
18  Routeing services 209
18.1 Registration services 209
18.1.1 Route register 209
18.1.2 Route register abort 210
18.1.3 Route register cancel 211
18.2 Services  212
18.2.1Re-Route 212
18.2.2 Route end 213
18.2.3 Route reject 214
18.2.4 Route request 215
18.2.5 Route select 216
18.2.6 Route used 217
19  Physical device features 218
19.1Services 218
19.1.1 Button press 218
19.1.2 Get auditory apparatus information 219
19.1.3 Get button information 220
19.1.4 Get display 221
19.1.5 Get hookswitch status 222
19.1.6 Get lamp information 223
19.1.7 Get lamp mode 224
19.1.8 Get message waiting indicator 225
19.1.9 Get microphone gain 226
19.1.10 Get microphone mute 227
19.1.11 Get ringer status 228
19.1.12 Get speaker mute 229
19.1.13 Get speaker volume 230
19.1.14 Set button information 231
19.1.15 Set display 232
19.1.16 Set hookswitch status 233
19.1.17 Set lamp mode 234
19.1.18 Set message waiting indicator 235
19.1.19 Set microphone gain 236
19.1.20 Set microphone mute 237
© ISO/IEC 2005 - All rights reserved
vii

---------------------- Page: 7 ----------------------
ISO/IEC 18056:2005(E)
19.1.21 Set ringer status 238
19.1.22 Set speaker mute 239
19.1.23 Set speaker volume 240
19.2Events  241
19.2.1 Button information 241
19.2.2 Button press 242
19.2.3 Display updated 243
19.2.4Hookswitch 244
19.2.5 Lamp mode 245
19.2.6 Message waiting 246
19.2.7 Microphone gain 247
19.2.8 Microphone mute 248
19.2.9 Ringer status 249
19.2.10 Speaker mute 250
19.2.11 Speaker volume 251
20  Logical device features 252
20.1Services 252
20.1.1 Call back non-call-related 252
20.1.2 Call back message non-call-related 253
20.1.3 Cancel call back 254
20.1.4 Cancel call back message 255
20.1.5 Get agent state 256
20.1.6 Get auto answer 258
20.1.7 Get auto work mode 259
20.1.8 Get caller id status 260
20.1.9 Get do not disturb 261
20.1.10 Get forwarding 262
20.1.11 Get last number dialed 263
20.1.12 Get routeing mode 264
20.1.13 Set agent state 265
20.1.14 Set auto answer 266
20.1.15 Set auto work mode 267
20.1.16 Set caller id status 268
20.1.17 Set do not disturb 269
20.1.18 Set forwarding 270
20.1.19 Set routeing mode 271
20.2Events  272
© ISO/IEC 2005 - All rights reserved
viii

---------------------- Page: 8 ----------------------
ISO/IEC 18056:2005(E)
20.2.1 Agent busy 272
20.2.2 Agent logged off 273
20.2.3 Agent logged on 274
20.2.4 Agent not ready 275
20.2.5 Agent ready 276
20.2.6 Agent working after call 277
20.2.7 Auto answer 278
20.2.8 Auto work mode 279
20.2.9 Call back 280
20.2.10 Call back message 281
20.2.11 Caller id status 282
20.2.12 Do not disturb 283
20.2.13Forwarding 284
20.2.14 Routeing mode 285
21  Device maintenance events 286
21.1Events 286
21.1.1 Back in service 286
21.1.2 Device capabilities changed 287
21.1.3 Out of service 288
21.1.4 Partially In service 289
22  I/O services 290
22.1 Registration services 290
22.1.1 I/O register 290
22.1.2 I/O register abort 291
22.1.3 I/O register cancel 292
22.2 Services  293
22.2.1 Data path resumed 293
22.2.2 Data path suspended 294
22.2.3 Fast data 295
22.2.4 Resume data path 296
22.2.5 Send broadcast data 297
22.2.6 Send data 298
22.2.7 Send multicast data 299
22.2.8 Start data path 300
22.2.9 Stop data path 301
22.2.10 Suspend data path 302
© ISO/IEC 2005 - All rights reserved
ix

---------------------- Page: 9 ----------------------
ISO/IEC 18056:2005(E)
23  Data Collection Services 303
23.1Services 303
23.1.1 Data Collected 303
23.1.2 Data Collection Resumed 305
23.1.3 Data Collection Suspended 306
23.1.4 Resume Data Collection 307
23.1.5 Start Data Collection 308
23.1.6 Stop Data Collection 309
23.1.7 Suspend Data Collection 310
24  Voice services and events 311
24.1Services 311
24.1.1Activate 311
24.1.2Clear 312
24.1.3 Concatenate message 313
24.1.4Deactivate 314
24.1.5 Delete message 315
24.1.6 Play message 316
24.1.7 Query voice attribute 317
24.1.8 Queue service 318
24.1.9 Record message 319
24.1.10Reposition 320
24.1.11Resume 321
24.1.12Review 322
24.1.13 Set voice attribute 323
24.1.14Start 325
24.1.15Stop 326
24.1.16Suspend 327
24.1.17 Synthesize message 328
24.2Events  329
24.2.1 Bookmark reached 329
24.2.2Completed 330
24.2.3 DTMF detected 331
24.2.4Emptied 332
24.2.5 Interruption detected 333
24.2.6 Not recognized 334
24.2.7Play 335
24.2.8Recognized 336
© ISO/IEC 2005 - All rights reserved
x

---------------------- Page: 10 ----------------------
IISSO/IO/IEC 1805EC 18056:20056:2005(E)(E)
24.2.9Record 337
24.2.10Review 338
24.2.11 Silence timeout expired 339
24.2.12 Speech detected 340
24.2.13Started 341
24.2.14Stop 342
24.2.15 Suspend play 343
24.2.16 Suspend record 344
24.2.17 Voice attribute changed 345
24.2.18 Voice error occurred 347
25  Call detail record services 348
25.1Services 348
25.1.1 Call detail records notification 348
25.1.2 Call detail records report 349
25.1.3 Send stored call detail records 350
25.1.4 Start call detail records transmission 351
25.1.5 Stop call detail records transmission 352
26  Vendor specific extensions services and events 353
26.1 Registration services 353
26.1.1 Escape register 353
26.1.2 Escape register abort 354
26.1.3 Escape register cancel 355
26.2 Services  356
26.2.1Escape 356
26.2.2 Private data version selection 357
26.3 Events  358
26.3.1 Private event 358
Annex A - Protocol Implementation Conformance
Statement (PICS) Proforma 359
A.1Introduction 359
A.2 Conformance 359
A.3 Instructions for completing the PICS proforma 359
A.4 Implementation identification 360
A.5 PICS proforma 360
A.5.1 CSTA Profiles 360
A.5.2 Capability Exchange Services 361
A.5.3 System Services 367
© ISO/IEC 2005 - All rights reserved
xi

---------------------- Page: 11 ----------------------
ISO/IEC 18056:2005(E)
A.5.4 Monitoring Services 371
A.5.5 Snapshot Services 373
A.5.6 Call Control Services 375
A.5.7 Call Control Events 391
A.5.8 Call Associated Feature Services 404
A.5.9 Call Associated Feature Events 407
A.5.10 Media Attachment Services 410
A.5.11 Media Attachment Events 411
A.5.12 Routeing Services 412
A.5.13 Physical Device Services 416
A.5.14 Physical Device Events 428
A.5.15 Logical Device Services 432
A.5.16 Logical Device Events 441
A.5.17 Device Maintenance Events 446
A.5.18 I/O Services 447
A.5.19 Data Collection Services 453
A.5.20 Voice Services 457
A.5.21 Voice Events 465
A.5.22 Call Detail Record (CDR) Services 474
A.5.23 Vendor Specific Extension Services 476
A.5.24 Vendor Specific Extension Events 478
Annex B - Examples of Device Identifier Element Encodings 479
B.1 Simple DeviceID (no attributes) 479
B.2 DeviceID typed as a dialing number 479
B.3 DeviceID typed as a device number 479
B.4 DeviceID typed as a explicit national number 479
B.5 DeviceID typed as other type of numbering plan 479
B.6 DeviceID media characteristics 479
B.7 DeviceID including all attributes 479
Annex C - Examples of Connection ID Encodings 480
C.1 Fully Specified Connection ID 480
C.2 CallID only ConnectionID 480
C.3 DeviceID only ConnectionID 480
Annex D - Examples of CSTA-specific XML 481
D.1 Make Call service request - with only mandatory elements 481
D.2 Make Call service request - with optional elements 481
D.3 Make Call - Positive Acknowledgement 482
© ISO/IEC 2005 - All rights reserved
xii

---------------------- Page: 12 ----------------------
ISO/IEC 18056:2005(E)
D.4 Make Call - Negative Acknowledgement 482
D.5 Delivered Event 482
Annex E - CSTA XML with SOAP 483
E.1 CSTA service request 483
E.2 CSTA service response (positive acknowledgement) 483
E.3 CSTA service response (negative acknowledgement) 484
E.4 Delivered Event 484
Annex F - CSTA XML with SOAP with HTTP 486
F.1 CSTA service request 486
F.2 CSTA service response (positive acknowledgement) 486
F.3 CSTA service response (negative acknowledgement) 487
F.4 Delivered Event 487
Annex G - CSTA XML over TCP 489
G.1 Message Format 489
G.2 TCP without SOAP 489
G.3 TCP with SOAP 490
Annex H - CSTA Data Type Schema for Encapsulation 491
H.1 CSTA Data Type Schema 491
H.2 CSTA Data Type Example 491
Annex I - Registration Template for application/CSTA+XML
MIME Media Type 492
Annex J - Registration Template for text/CSTA-type
MIME Media Type 493
Annex K - CSTA Over SIP Transport Mechanism 494
K.1 Establishing a CSTA Application Session 494
K.2 Transporting CSTA Service Requests and Responses 495
K.3 Starting a Monitor and Transporting CSTA Events 496
Annex L - Summary of changes in this edition 497
© ISO/IEC 2005 - All rights reserved
xiii

---------------------- Page: 13 ----------------------
ISO/IEC 18056:2005(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. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. 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 document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 18056 was prepared by Ecma International (as ECMA-323) and was adopted, under a special
“fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee
SC 6, Telecommunications and information exchange between systems, in parallel with its approval by
national bodies of ISO and IEC.
This second edition cancels and replaces the first edition (ISO/IEC 18056:2004), which has been technically
revised.

© ISO/IEC 2005 - All rights reserved
xiv

---------------------- Page: 14 ----------------------
ISO/IEC 18056:2005(E)
Introduction
This Standard defines an XML protocol for Phase III of Computer Supported Telecommunications Applications
(CSTA). This 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.
Phase III of CSTA extends the previous Phase I and Phase II Standards 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.
This edition of Phase III XML Protocol for CSTA adds the ability to:
• support non-voice media interactions such as Email, Instant Messaging, and Chat.
 utilize SIP based features supported by underlying protocol layers.
 use CSTA Standards for Voice Browser applications by the addition of three new profiles.
© ISO/IEC 2005 - All rights reserved
xv

---------------------- Page: 15 ----------------------
INTERNATIONAL STANDARD ISO/IEC 18056:2005(E)

Information technology — Telecommunications and information
exchange between systems — XML Protocol for Computer-
Supported Telecommunications Applications (CSTA) Phase III

1 Scope
This Standard specifies an XML protocol for the services described in ECMA-269, Services for Computer
Supported Telecommunications Applications (CSTA) Phase III.
This Standard provides an alternative protocol to the ASN.1 based protocol specified in ECMA-285.
Clause 5 to clause 8 inclusive describes the concepts underlying the request/response model, application
association, notation and service, and a description of the template used in this Standard.
Clause 9 to clause 26 inclusive contains CSTA-specific protocol details and forms the main part of this
Standard.
Annex A specifies the PICS for this Standard.
Examples of CSTA XML encodings are provided in annex B through annex G.
2 Conformance
A manufacturer may select any part of the CSTA protocol, as specified in this Standard, for
implementation on a system as long as it satisfies the minimum conformance requirements as specified in
clause 2 of ECMA-269.
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.
2.1 Static Requirements
To conform to this Standard, a system shall support the syntax as defined by the XML 1.0 specification
and the structures and data types as defined in the XML Schema Structure and XML Schema Data Types
specifications for the purpose of generating and interpreting CSTA protocol information for the operations
supported.
2.2 Dynamic Requirements
To conform to this Standard, a system shall:
a. follow the procedures as specified in this Standard, and ECMA-269, relevant to each CSTA
operation that the system claims to implement; and
b. satisfy the definitions, as specified in ECMA-269, relevant to each CSTA service that the system
claims to implement.
2.3 PICS Requirement
To conform to this 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 ECMA-269, are supported by the system for the particular
implementation; and
b. which optional parameters are supported by each supported operations.
A PICS proforma is specified in annex A of this Standard.
© ISO/IEC 2005 - All rights reserved
1

---------------------- Page: 16 ----------------------
ISO/IEC 18056:2005(E)
3 References
3.1 ECMA/ISO Standards and Technical Reports
ECMA-269 Services for Computer Supported Telecommunications Applications (CSTA)
Phase III, 6th edition (June 2004)
ECMA-285 Protocol for Computer Supported Telecommunications Applications (CSTA)
Phase III, 2nd edition (June 2000)
ECMA-354 Application Session Services (June 2004)
ECMA TR/72 Glossary of Definitions and Terminology for Computer Supported
Telecommunications Applications (CSTA) Phase III, 3rd edition (June 2000)
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)
3.2 World Wide Web Consortium Specifications
XML 1.0 XML 1.0. W3C Recommendation February 1998 (revised October 2000)
XML Schema Part 1 XML Schema Language Part 1: Structures. W3C Recommendation 2 May 2001
XML Schema Part 2 XML Schema Language Part 2: Datatypes. W3C Recommendation 2 May 2001
SOAP 1.1 Simple Object Access Protocol (SOAP) 1.1, W3C Note 08 May 2000
4 Definitions and Abbreviations
CSTA-specific terminology is defined in ECMA TR/72.
5 CSTA Service Definition Model
CSTA services specified in ECMA-269 are modeled as a request/response interaction.
Typically, one entity requests that a particular operation be performed; the other entity attempts to perform
the operation and responds to the requestor.
5.1 Request/Response Interactions
CSTA services consist of the following types of request/response interactions:
 Services which specify a response in case of success or failure. The protocol description for these
services includes a response element that represents the success (i.e. positive acknowledgement). In
case of service failure, a fault element is used to provide the failure information (i.e. negative
acknowledgement).
 Services which only specify a response in case of failure. The protocol description for these services
do not include a response element. A fault element is used to provide the failure information (i.e.
negative acknowledgement).
For CSTA event reports, no response is generated.
5.2 Request/Response Protocol Requirements
This Standard specifies CSTA-specific XML-encoded content for messages that are sent across a CSTA
Service boundary. Typically this CSTA-specific XML is enveloped by a request/response protocol that
provides a mechanism for correlating a CSTA request with a CSTA response, manages faults, defines
header information, etc.
This Standard does not mandate that a specific request/response protocol be used. However, this
Standard provides examples of how the CSTA-specific XML can be used with several industry request/
response protocols and transports such as SOAP (Simple Object Access Protocol), HTTP, and TCP.
These examples are provided beginning in annex E.
© ISO/IEC 2005 - All rights reserved
2

---------------------- Page: 17 ----------------------
ISO/IEC 18056:2005(E)
5.3 Cross Referencing of Event Reports
The Monitor Cross Reference Identifier in CSTA event reports is used to correlate events to an earlier
Monitor Start service request (see 6.7.2.1 of ECMA-269).
5.4 Handling of Private Data
If an entity receives CSTA Private Data in a CSTA message, and it can not recognize the information
contained, the CSTA Private Data shall be discarded, and the rest of the message shall be processed.
6 Interconnection service boundary
The protocol in this Standard is an OSI Application Layer protocol that assumes certain services are
provided by the underlying layers, and these services are also assumed by the protocol for CSTA.
This protocol also provides a mechanism for secure transmission of CSTA messages as defined in this
Standard.
7 Association Management
The protocol in this Standard operates in the context of an application association. This application
association can be achieved by:
 an implicit association achieved via off-line agreement; or
 an explicit association that is achieved dynamically.
7.1 Implicit association
An a-priori agreement exists between switching and computing functions: the application context is
implicit, dynamic negotiation is not possible.
7.2 Explicit association
An explicit application association is established by a process of exchanging messages that define the
application context for the association.
This Standard does not require that a particular standard be used as part of the application association
establishment procedure.
When ACSE (ISO/IEC 8649) is used to establish an application association per 7.3 of ECMA-269, the
CSTA Association Information includes CSTA Version information that indicates the CSTA protocol
versions supported by an implementation. The protocol defined in this Standard is indicated by setting the
versionEight bit in the CSTAVersion parameter of the CSTA Association Information as defined in 8.2.2 of
ECMA-285. Note that the ACSE messages are ASN.1 encoded while the CSTA messages are XML
encoded as defined by this Standard.
An explicit application can also be established by using ECMA-354, Application Session Services.
8 XML Template Description
This clause describes the template format used to describe the XML schemas for CSTA services, events,
and parameter types as specified in ECMA-269.
The template consists of the following parts:
 XML header - this consists of the text “” which identifies the
XML version used.
 XML Schema header - this identifies the start of an XML schema and provides information such as:
 the target namespace. In this edition of the Standard the target namespace is defined as “http://
www.ecma-international.org/standards/ecma-323/csta/ed3”. Note that this namespace is
different than the namespace used in ECMA-323, 1st Edition and ECMA-323, 2nd Edition.
© ISO/IEC 2005 - All rights reserved
3

---------------------- Page: 18 ----------------------
ISO/IEC 18056:2005(E)
 the csta namespace is defined in the same way as the target namespace. XML names that refer
to names in the CSTA namespace are prefixed with “csta:”.
 the xsd namespace. This identifies the XML Schema. XML names that refer to names in the
XML Schema namespace are prefixed with “xsd:”.
 the element form default is specified as “qualified” which requires that all element names must
be prefixed with a namespace (csta: or xsd:)
 documentation - this provides a comment that indicates the CSTA specific service, event report, or
data-type set.
 included schemas - this provides a list of other CSTA schemas that are referenced by the service,
event, or data type set.
 CSTA specific XML:
 for CSTA services, this consists of a service request element and a service response element.
(A comment is provided in some cases where a service response is not specified per ECMA-
269.). This is followed, in some cases, by service-specific XML types that are referenced in the
previous elements.
 for CSTA event reports, this consists of an event report element followed, in some cases, by
event-specific XML type definitions that are referenced in the event report element.
 for CSTA data types, this consists of the data types that are referenced (included) by other CSTA
XML schemas.
 XML Schema end tag - indicates the end of the schema.
Note that in general, each parameter defined in ECMA-269 is represented as an XML element and each
parameter type in ECMA-269 is represented as an XML simple or complex type.
© ISO/IEC 2005 - All rights reserved
4

---------------------- Page: 19 ----------------------
ISO/IEC 18056:2005(E)
9 CSTA parameter types
9.1 Switching function objects

xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed3"
elementFormDefault="qualified" attributeFormDefault="unqualified">
 
  CSTA-switching-function-objects
 
 
 
 
  
   
   
  
 

© ISO/IEC 2005 - All rights reserved
5

---------------------- Page: 20 ----------------------
ISO/IEC 18056:2005(E)
9.2 Device Identifiers

xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed3"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefa
...