ISO/IEC 18051:2004

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

ISO/IEC 18051:2004 specifies the Services and Event Reports for Computer-Supported Telecommunications Applications (CSTA), Phase III. It is focused on providing application service interfaces to a Switching Function, Computing Function and a Special Resource Function. A CSTA application interface is disassociated from the various user-network interfaces and network-network interfaces CSTA applications may serve, observe or manipulate. Because CSTA operates with existing telecommunications interfaces indirectly, it operates generically, so that differences among various existing interfaces are hidden from CSTA applications. Support of user-to-network interfaces is outside the scope of CSTA. Although most terminal equipment (TE) is suitable for use with CSTA, there will be instances of TE that will not be suitable in certain circumstances. Examples are: FAX terminals and modems that are unable to adjust their transmission modes to prevent carrier conflict when both parties are alerted via CSTA during call establishment; and Functional terminals that perform telecommunication functions outside the control of the Switching Function. Services defined in ISO/IEC 18051:2004 allow functional integration between a computing network and a telecommunications network. Computing platforms (i.e. Application Programming Interfaces or APIs) that support such functionally-integrated applications are outside the scope of ISO/IEC 18051:2004. Communication between the computing and switching (i.e. telecommunications) networks may take place via intervening networks ranging from simple point-to-point connections to local or wide area telecommunications networks. ISO/IEC 18051:2004 is part of a suite of CSTA International Standards and Technical Reports that provide a comprehensive description of the architectural and practical issues involved in applying, implementing and utilizing CSTA-based CTI applications.

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

General Information

• Status: Withdrawn
• Publication Date: 23-Nov-2004
• Withdrawal Date: 23-Nov-2004
• 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: 13-Jul-2005

Relations

• Revised: ISO/IEC 18051:2005 - Information technology — Telecommunications and information exchange between systems — Services for Computer Supported Telecommunications Applications (CSTA) Phase III
• Effective Date: 15-Apr-2008
• Revises: ISO/IEC 18051:2000 - Information technology — Telecommunications and information exchange between systems — Services for Computer Supported Telecommunications Applications (CSTA) Phase III
• Effective Date: 15-Apr-2008
• Consolidated By: ISO 18219:2015 - Leather — Determination of chlorinated hydrocarbons in leather — Chromatographic method for short-chain chlorinated paraffins (SCCP)
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 18051
Second edition
2004-12-01

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




Reference number
ISO/IEC 18051:2004(E)
©
ISO/IEC 2004

---------------------- Page: 1 ----------------------
ISO/IEC 18051:2004(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 2004
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 2004 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 18051:2004(E)
Contents
1  Scope 1
2  Conformance 1
2.1 Switching Function 2
2.1.1 Conformant Services 2
2.1.2 Conformant Events 2
2.1.3 CSTA Profiles 2
2.1.4 Support of Service Requests And Manual Mode 3
2.2 Special Resource Function Conformance 3
2.2.1 Conformant Services 3
2.2.2 Conformant Events 4
2.2.3 Support of Service Requests And Manual Mode 4
2.3 Computing Function Conformance 4
3  Normative references 4
4  Terms and definitions 5
5  Functional Architecture 5
6  CSTA Operational Model 5
6.1 Switching Sub-Domain Model 6
6.1.1 Switching Sub-Domain Name 6
6.1.2 Application Working Domain 6
6.1.3 Device 7
6.1.4 Call 28
6.1.5 Connection 35
6.1.6 Call State Definitions 38
6.1.7 Referencing Devices, Elements, Appearances and Device Configurations 39
6.1.8 Management of Dynamically-Assigned Identifiers 41
6.2 Special Resource Functions 41
6.2.1 Voice Unit 41
6.3 I/O Services 43
6.3.1 Data Path Definition 43
6.3.2 I/O Registration Services 44
6.3.3 Data Path States and Operational Model 44
6.3.4 I/O Services Example 44
6.4 Call Detail Record (CDR) Services 45
6.4.1 CDR Services Examples 45
6.5 Capabilities Exchange 47
6.5.1 Switching Function Capabilities 47
6.5.2 Device Capabilities 48
© ISO/IEC 2004 - All rights reserved
iii

---------------------- Page: 3 ----------------------
ISO/IEC 18051:2004(E)
6.5.3 Dynamic Feature Availability 48
6.6 Switching Function Information Synchronization 48
6.6.1 Switching Function Level Information 49
6.6.2 Device Level Information 49
6.6.3 Call Level Information 49
6.7 Status Reporting Services 49
6.7.1 System Status 49
6.7.2 Monitoring 51
6.7.3 Snapshot Services 54
6.8 Additional Services, Features & Behaviour 54
6.8.1 Forwarding 54
6.8.2 Connection Failure 56
6.8.3 Recall 58
6.8.4 Call Back 58
6.8.5 External Calls 59
6.8.6 Tracking a Diverted Call 60
6.8.7 Media Stream Access 60
6.8.8 Routeing Services 63
6.8.9 Device Maintenance 68
6.8.10 Prompting 68
6.8.11 Telephony Tones Features 68
6.8.12 DTMF and Rotary Pulse Digits Features 68
6.8.13 Data Collection Services 69
7  Association Establishment 69
7.1 Implicit Association 69
7.2 Explicit Association 70
8  Security Service 71
9  Generic Service Requirements 71
9.1 Service Request 71
9.2 Service Response (Acknowledgements) 72
9.2.1 Positive Acknowledgement Models 72
9.2.2 Negative Acknowledgement 73
9.3 Diagnostic Error Definitions 73
9.3.1 Error Categories 73
9.3.2 Error Values 73
9.4 Vendor Specific Extensions 74
9.4.1 Private Data 74
9.4.2 Escape Services and Private Event 75
9.5 General Services and Event Functional Requirements 76
9.5.1 Services 76
9.5.2 Events 77
© ISO/IEC 2004 - All rights reserved
iv

---------------------- Page: 4 ----------------------
ISO/IEC 18051:2004(E)
10  CSTA Device Identifier Formats 78
10.1 Device Identifier Formats 78
10.1.1 Diallable Digits 78
10.1.2 Switching Function Representation 79
10.1.3 Device Number 81
10.2 Functional Requirements 81
11  Template Descriptions 81
11.1 Service Template 81
11.1.1 Service Description 81
11.1.2 Service Request 82
11.1.3 Service Response 82
11.1.4 Operational Model 83
11.2 Event Template 83
11.2.1 Event Description 83
11.2.2 Event Parameters 83
11.2.3 Event Causes 83
11.2.4 Functional Requirements 84
11.3 Parameter Type Template 84
11.3.1 Parameter Type Description 84
11.3.2 Format 84
11.3.3 Functional Requirements 84
12  Parameter Types 85
12.1 Definitions 85
12.2 Defined Parameter Types  86
12.2.1 AccountInfo 87
12.2.2AgentPassword 87
12.2.3 AuthCode 87
12.2.4CallCharacteristics 87
12.2.5CallLinkageData 88
12.2.6CallQualifyingData 90
12.2.7 ChargingInfo 90
12.2.8ConnectionInformation 90
12.2.9ConnectionList 91
12.2.10CorrelatorData 92
12.2.11CSTAPrivateData 93
12.2.12CSTASecurityData 93
12.2.13 DeviceHistory 93
12.2.14 ErrorValue 94
12.2.15 EventCause 104
12.2.16LanguagePreferences 107
12.2.17LocalConnectionState 108
12.2.18MediaCallCharacteristics 108
© ISO/IEC 2004 - All rights reserved
v

---------------------- Page: 5 ----------------------
ISO/IEC 18051:2004(E)
12.2.19MediaServiceType 110
12.2.20 MessageInfo 111
12.2.21MonitorFilter 111
12.2.22ServicesPermitted 111
12.2.23SimpleCallState 112
12.2.24SubjectOfCall 113
12.2.25SystemStatus 113
12.2.26 TimeInfo 113
12.2.27 UserData 114
12.3 Identifier Parameter Types  115
12.3.1 AgentID 116
12.3.2AssociatedCalledDeviceID 116
12.3.3AssociatedCallingDeviceID 116
12.3.4AuditoryApparatusID 117
12.3.5 ButtonID 117
12.3.6CalledDeviceID 117
12.3.7CallingDeviceID 118
12.3.8CDRCrossRefID 118
12.3.9ConnectionID 118
12.3.10DCollCrossRefID 120
12.3.11 DeviceID 120
12.3.12 DisplayID 120
12.3.13EscapeRegisterID 120
12.3.14HookswitchID 120
12.3.15IOCrossRefID 121
12.3.16IORegisterReqID 121
12.3.17 LampID 121
12.3.18MediaServiceInstanceID 121
12.3.19MediaStreamID 121
12.3.20 MessageID 122
12.3.21MonitorCrossRefID 122
12.3.22NetworkCalledDeviceID 122
12.3.23NetworkCallingDeviceID 123
12.3.24RedirectionDeviceID 123
12.3.25 RingerID 124
12.3.26RouteingCrossRefID 124
12.3.27RouteRegisterReqID 124
12.3.28ServiceCrossRefID 124
12.3.29SubjectDeviceID 125
12.3.30SysStatRegisterID 125
13  Capability Exchange Services 126
13.1 Services 126
13.1.1 Get Logical Device Information 127
13.1.2 Get Physical Device Information 136
© ISO/IEC 2004 - All rights reserved
vi

---------------------- Page: 6 ----------------------
ISO/IEC 18051:2004(E)
13.1.3 Get Switching Function Capabilities 140
13.1.4 Get Switching Function Devices 155
13.1.5 Switching Function Devices 157
14  System Services 160
14.1 Registration Services 160
14.1.1 Change System Status Filter 161
14.1.2 System Register 163
14.1.3 System Register Abort 166
14.1.4 System Register Cancel 167
14.2 Services  168
14.2.1 Request System Status  169
14.2.2 System Status 171
14.2.3 Switching Function Capabilities Changed 173
14.2.4 Switching Function Devices Changed 174
15  Monitoring Services 175
15.1 Services 175
15.1.1 Change Monitor Filter 176
15.1.2 Monitor Start 178
15.1.3 Monitor Stop 182
16  Snapshot Services 183
16.1 Services 183
16.1.1 Snapshot Call 184
16.1.2 Snapshot Device 187
16.1.3 Snapshot CallData 190
16.1.4 Snapshot DeviceData 192
17  Call Control Services & Events 195
17.1 Services 195
17.1.1 Accept Call  196
17.1.2 Alternate Call 198
17.1.3 Answer Call 201
17.1.4 Call Back Call-Related 203
17.1.5 Call Back Message Call-Related 206
17.1.6 Camp On Call 209
17.1.7 Clear Call 211
17.1.8 Clear Connection 214
17.1.9 Conference Call 218
17.1.10 Consultation Call 221
17.1.11 Deflect Call 227
17.1.12 Dial Digits 230
17.1.13 Directed Pickup Call 233
17.1.14 Group Pickup Call 237
© ISO/IEC 2004 - All rights reserved
vii

---------------------- Page: 7 ----------------------
ISO/IEC 18051:2004(E)
17.1.15 Hold Call 240
17.1.16 Intrude Call 242
17.1.17 Join Call 246
17.1.18 Make Call 250
17.1.19 Make Predictive Call 256
17.1.20 Park Call 261
17.1.21 Reconnect Call 264
17.1.22 Retrieve Call 266
17.1.23 Send Message 268
17.1.24 Single Step Conference Call 273
17.1.25 Single Step Transfer Call 277
17.1.26 Transfer Call 280
17.2 Events 283
17.2.1 Bridged 284
17.2.2 Call Cleared 286
17.2.3 Conferenced 289
17.2.4 Connection Cleared 295
17.2.5 Delivered 299
17.2.6 Digits Dialled 304
17.2.7 Diverted 307
17.2.8 Established 312
17.2.9 Failed 317
17.2.10 Held 322
17.2.11 Network Capabilities Changed 324
17.2.12 Network Reached 327
17.2.13 Offered 331
17.2.14 Originated 336
17.2.15 Queued 339
17.2.16 Retrieved 343
17.2.17 Service Initiated 345
17.2.18 Transferred 348
18  Call Associated Features 352
18.1 Services 352
18.1.1 Associate Data  353
18.1.2 Cancel Telephony Tones 355
18.1.3 Change Connection Information 357
18.1.4 Generate Digits 360
18.1.5 Generate Telephony Tones 362
18.1.6 Send User Information 365
18.2 Events  367
18.2.1 Call Information 368
18.2.2 Charging 370
18.2.3 Digits Generated 371
18.2.4 Telephony Tones Generated 372
© ISO/IEC 2004 - All rights reserved
viii

---------------------- Page: 8 ----------------------
ISO/IEC 18051:2004(E)
18.2.5 Service Completion Failure 375
19  Routeing Services 378
19.1 Registration Services 378
19.1.1 Route Register 379
19.1.2 Route Register Abort  381
19.1.3 Route Register Cancel 382
19.2 Services   383
19.2.1 Re-Route 384
19.2.2 Route End  385
19.2.3 Route Reject 387
19.2.4 Route Request 389
19.2.5 Route Select 391
19.2.6 Route Used 393
20  Media Attachment Services & Events 395
20.1 Services 395
20.1.1 Attach Media Service 396
20.1.2 Detach Media Service 400
20.2 Events  403
20.2.1 Media Attached 404
20.2.2 Media Detached 405
21  Physical Device Features 407
21.1 Services 407
21.1.1 Button Press 408
21.1.2 Get Auditory Apparatus Information 409
21.1.3 Get Button Information 411
21.1.4 Get Display 413
21.1.5 Get Hookswitch Status 415
21.1.6 Get Lamp Information 416
21.1.7 Get Lamp Mode 418
21.1.8 Get Message Waiting Indicator 421
21.1.9 Get Microphone Gain 422
21.1.10 Get Microphone Mute 423
21.1.11 Get Ringer Status 424
21.1.12 Get Speaker Mute 426
21.1.13 Get Speaker Volume 427
21.1.14 Set Button Information 428
21.1.15 Set Display 429
21.1.16 Set Hookswitch Status 431
21.1.17 Set Lamp Mode 432
21.1.18 Set Message Waiting Indicator 434
21.1.19 Set Microphone Gain 435
21.1.20 Set Microphone Mute 437
© ISO/IEC 2004 - All rights reserved
ix

---------------------- Page: 9 ----------------------
ISO/IEC 18051:2004(E)
21.1.21 Set Ringer Status 438
21.1.22 Set Speaker Mute 440
21.1.23 Set Speaker Volume 441
21.2 Events  443
21.2.1 Button Information 444
21.2.2 Button Press 445
21.2.3 Display Updated 446
21.2.4 Hookswitch 448
21.2.5 Lamp Mode 449
21.2.6 Message Waiting 450
21.2.7 Microphone Gain 451
21.2.8 Microphone Mute 452
21.2.9 Ringer Status 453
21.2.10 Speaker Mute 454
21.2.11 Speaker Volume 455
22  Logical Device Features 456
22.1 Services 456
22.1.1 Call Back Non-Call-Related 457
22.1.2 Call Back Message Non-Call-Related 458
22.1.3 Cancel Call Back 460
22.1.4 Cancel Call Back Message 461
22.1.5 Get Agent State 462
22.1.6 Get Auto Answer 464
22.1.7 Get Auto Work Mode 465
22.1.8 Get Caller ID Status 466
22.1.9 Get Do Not Disturb 467
22.1.10 Get Forwarding 469
22.1.11 Get Last Number Dialled 472
22.1.12 Get Routeing Mode 473
22.1.13 Set Agent State 474
22.1.14 Set Auto Answer 478
22.1.15 Set Auto Work Mode 480
22.1.16 Set Caller ID Status 482
22.1.17 Set Do Not Disturb 483
22.1.18 Set Forwarding 485
22.1.19 Set Routeing Mode 487
22.2 Events   488
22.2.1 Agent Busy 489
22.2.2 Agent Logged Off 490
22.2.3 Agent Logged On 491
22.2.4 Agent Not Ready 492
22.2.5 Agent Ready 493
22.2.6 Agent Working After Call 494
22.2.7 Auto Answer 496
© ISO/IEC 2004 - All rights reserved
x

---------------------- Page: 10 ----------------------
ISO/IEC 18051:2004(E)
22.2.8 Auto Work Mode 497
22.2.9 Call Back 498
22.2.10 Call Back Message 499
22.2.11 Caller ID Status 500
22.2.12 Do Not Disturb 501
22.2.13 Forwarding 502
22.2.14 Routeing Mode 504
23  Device Maintenance Events 505
23.1 Events 505
23.1.1 Back In Service 506
23.1.2 Device Capabilities Changed 507
23.1.3 Out Of Service 508
24  I/O Services 509
24.1 Registration Services 509
24.1.1 I/O Register 510
24.1.2 I/O Register Abort 512
24.1.3 I/O Register Cancel 513
24.2 I/O Services   514
24.2.1 Data Path Resumed 515
24.2.2 Data Path Suspended 516
24.2.3 Fast Data 517
24.2.4 Resume Data Path 519
24.2.5 Send Broadcast Data 520
24.2.6 Send Data 522
24.2.7 Send Multicast Data 524
24.2.8 Start Data Path 526
24.2.9 Stop Data Path 528
24.2.10 Suspend Data Path 529
25  Data Collection Services 530
25.1 Services 530
25.1.1 Data Collected 531
25.1.2 Data Collection Resumed 534
25.1.3 Data Collection Suspended 535
25.1.4 Resume Data Collection 536
25.1.5 Start Data Collection 537
25.1.6 Stop Data Collection 539
25.1.7 Suspend Data Collection 540
26  Voice Unit Services & Events 541
26.1 Services 541
26.1.1 Concatenate Message 542
26.1.2 Delete Message 543
© ISO/IEC 2004 - All rights reserved
xi

---------------------- Page: 11 ----------------------
ISO/IEC 18051:2004(E)
26.1.3 Play Message 544
26.1.4 Query Voice Attribute 546
26.1.5 Record Message 548
26.1.6 Reposition 550
26.1.7 Resume 552
26.1.8 Review 553
26.1.9 Set Voice Attribute 555
26.1.10 Stop 557
26.1.11 Suspend 558
26.1.12 Synthesize Message 560
26.2 Events  561
26.2.1 Play 562
26.2.2 Record 563
26.2.3 Review 564
26.2.4 Stop 565
26.2.5 Suspend Play 566
26.2.6 Suspend Record 567
26.2.7 Voice Attribute Changed 568
27  Call Detail Record (CDR) Services 569
27.1 Services 569
27.1.1 Call Detail Records Notification 570
27.1.2 Call Detail Records Report 571
27.1.3 Send Stored Call Detail Records 575
27.1.4 Start Call Detail Records Transmission 577
27.1.5 Stop Call Detail Records Transmission 579
28  Vendor Specific Extensions Services & Events 581
28.1 Registration Services 581
28.1.1 Escape Register  582
28.1.2 Escape Register Abort 583
28.1.3 Escape Register Cancel 584
28.2 Services  585
28.2.1 Escape 586
28.2.2 Private Data Version Selection 587
28.3 Events  588
28.3.1 Private Event 589
Annex A - Device Appearances 590
A.1 Standard Appearance 590
A.1.1 Selected-Standard Appearance 590
A.1.2 Basic-Standard Appearance 591
A.2 Bridged Appearance 591
A.2.1Basic-Bridged 592
© ISO/IEC 2004 - All rights reserved
xii

---------------------- Page: 12 ----------------------
ISO/IEC 18051:2004(E)
A.2.2Exclusive-Bridged 593
A.2.3Shared-Bridged 594
Annex B - ISDN User-User Information Element Encoding for CSTA 598
Annex C - Capability Bitmap Parameters Types 600
Annex D - Connection State Transition Examples 653
Annex E - Summary of changes in this edition 663
© ISO/IEC 2004 - All rights reserved
xiii

---------------------- Page: 13 ----------------------
ISO/IEC 18051:2004(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.
International Standard ISO/IEC 18051 was prepared by Ecma International (as ECMA-269) 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 18051:2000), which has been

technically revised.
© ISO/IEC 2004 - All rights reserved
xiv

---------------------- Page: 14 ----------------------
ISO/IEC 18051:2004(E)
Introduction
This Standard defines Phase III of Services for 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 adds features that:
• enhance the ability to support non-voice media interactions such as Email, Instant Messaging, and
Chat.
 enhance the ability for CSTA applications to utilize SIP based features supported by underlying
protocol layers.
 enhance the ability to leverage CSTA Standards for Voice Browser applications by the addition of three
new profiles.
© ISO/IEC 2004 - All rights reserved
xv

---------------------- Page: 15 ----------------------
INTERNATIONAL STANDARD ISO/IEC 18051:2004(E)

Information technology - Telecommunications and information
exchange between systems - Services for Computer Supported
Telecommunications Applications (CSTA) Phase III
1 Scope
This Standard specifies the Services and Event Reports for Computer-Supported Telecommunications Applications,
Phase III (CSTA).
This Standard is focused on providing application service interfaces to a Switching Function, Computing Function
and a Special Resource Function. A CSTA application interface is disassociated from the various user-network
interfaces and network-network interfaces CSTA applications may serve, observe or manipulate. Because CSTA
operates with existing telecommunications interfaces indirectly, it operates generically, so that differences among
various existing interfaces are hidden from CSTA applications. Support of user-to-network interfaces is outside the
scope of CSTA.
Although most terminal equipment (TE) are suitable for use with CSTA there will be instances of TE that will not
be suitable in certain circumstances. Examples are:
 FAX terminals and modems that are unable to adjust their transmission modes to prevent carrier conflict when
both parties are alerted via CSTA during call establishment;
 Functional terminals that perform telecommunication functions outside the control of the Switching Function.
Services defined in this Standard allow functional integration between a computing network and a
telecommunications network. Computing platforms (i.e., Application Programming Interfaces - APIs) that support
such functionally-integrated applications are outside the scope of this Standard.
Communication between the computing and switching (i.e., telecommunications) networks may take place via
intervening networks ranging from simple point-to-point connections to local- or wide-area telecommunications
networks.
This Standard is part of a suite of CSTA Standards and Technical Reports that provide a comprehensive description
of the architectural and practical issues involved in applying, implementing, and utilizing CSTA-based CTI
applications.
2 Conformance
This Clause specifies the conformance requirements for a Switching Function, Special Resource Function, and a
Computing Function.
Conformance requirements specify the parts of this Standard that a CSTA conformant implementation shall support.
This Standard specifies an operational model (Clause 6, “CSTA Operational Model” and Clause 9, “Generic Service
Requirements”) that defines a collection of objects (e.g. domains and sub-domains, logical and physical elements,
calls) and the relationships between these objects.
The behaviours of CSTA-conformant services, features, and event reports are determined by this model.
© ISO/IEC 2004 - All rights reserved
1

---------------------- Page: 16 ----------------------
ISO/IEC 18051:2004(E)
2.1 Switching Function
In order to conform to this Standard a switching function shall support the following as a minimum:
1. the requirements pertaining to CSTA features as specified in Clause 6, “CSTA Operational Model”.
2. the requirements as specified in Clause 9, “Generic Service Requirements”.
3. the Get Switching Function Capability service for all CSTA profiles specified in 2.1.3, “CSTA Profiles” unless
otherwise noted in the profile.
4. either the Implicit or Explicit Application Association Establishment sequence, including the mandatory
aspects in the sequence (such as the System Status service), as specified in Figure 7-1 and Figure 7-2.
5. at least one of the profiles as specified in 2.1.3, “CSTA Profiles”.
2.1.1 Conformant Services
In order to conform to a specific CSTA service an implementation shall support the following as a minimum:
1. the requirements of the service as specified by its service description, service request parameters, service
response parameters, and operational model including connection state transitions, monitoring event
sequences, and functional requirements.
2. the requirements associated with each parameter used in the service as specified by its parameter description,
format, and functional requirements in Clause 12, “Parameter Types”.
3. all of the events that are associated with its service completion criteria, as documented in its event monitoring
tables.
4. service requests that contain a device identifier parameter, an implementation shall support, at a minimum, the
Diallable Digits format as specified in 10.1.1, “Diallable Digits”.
2.1.2 Conformant Events
In order to conform to a specific CSTA event an implementation shall support the following as a minimum:
1. the requirements of the event as specified by its event description, event parameters, event causes, and
functional requirements.
2. the requirements associated with each parameter used in the event as specified by its parameter description,
format, and functional requirements in Clause 12, “Parameter Types”.
3. events that contain a device identifier parameter, an implementation shall support, at a minimum, the
Switching Function Representation format as specified in 10.1.2, “Switching Function Representation”.
2.1.3 CSTA Profiles
Some CSTA services and events are grouped together as profiles.
2.1.3.1 Basic Telephony Profile
This profile includes the following:
1. CSTA Services: Answer Call, Clear Connection, Make Call, Monitor Start (with the monitorType of device-
type), and Monitor Stop.
2. CSTA Events: Connection Cleared, Delivered, Established, Failed, Network Reached, Originated, and Service
Initiated.
Other CSTA services and events may be provided in any combination in addition to this set.
2.1.3.2 Routeing Profile
If the switching function supports Routeing Services as specified in Clause 19, “Routeing Services”, it shall support
a minimum set of Routeing Services that includes: Route Request, Route Select, and Route End (from the switching
function only).
Other Routeing services may be provided in any combination in addition to this set.
© ISO/IEC 2004 - All rights reserved
2

---------------------- Page: 17 ----------------------
ISO/IEC 18051:2004(E)
If a switching function supports the routeing for digital data calls, then the Route Register and CSTA Route Register
Cancel shall also be included in the minimum set.
2.1.3.3 Level 1a Voice Browser Profile
This profile includes the following:
1. CSTA Services: Answer Call, Clear Connection, Single Step Transfer Call (of a connected call), Monitor Start
(with the monitorType of device-type), and Monitor Stop.
2. CSTA Events: Connection Cleared, Delivered, Established, Failed, and Transferred.
Note that the Get Switching Function Capability service is not a required service in this profile.
Other CSTA services and events may be provided in any combination in addition to this set.
2.1.3.4 Level 1b Voice Browser Profile
This profile includes the following:
1. CSTA Services: Answer Call, Clear Connection, Deflect Call (of a connected call), Monitor Start (with the
monitorType of device-type), and Monitor Stop.
2. CSTA Events: Connection Cleared, Delivered, Diverted, Established, and Failed.
Note that the Get Switching Function Capability service is not a required service in this profile.
Other CSTA services and events may be provided in any combination in addition to this set.
2.1.3.5 Level 2 Voice Browser Profile
This profile includes the following:
All of the services and events in either the Level 1a Voice Browser Profile or the Level 1b Voice Browser Profile
and the following:
1. additional CSTA Service: Make Call
2. additional CSTA Events: Network Reached, Originated.
Other CSTA services and events may be provided in any combination in addition to this set.
2.1.4 Support of Service Requests And Manual Mode
A conformant switching function may support a given service defined in this Standard through the CSTA service
boundary but is not required to support the equivalent service in a manual mode.
A conformant switching function may support a feature associated with an equivalent CSTA service defined in this
Standard through manual mode but is not required to support the equivalent service through the service boundary.
2.2 Special Resource Function Conformance
In order to conform to this Standard a special resource function shall support the following as a minimum:
1. the requirements pertaining to CSTA features as specified in Clause 6, “CSTA Operational Model”.
2. the requirements as specified in Clause 9, “Generic Service Requirements”.
3. for a supported service, the special resource function shall not reject as unsupported all of the events specified
in the monitoring event sequences associated with the service.
4. the atomic service request acknowledgment model as specified in 9.2, “Service Response
(Acknowledgements)”.
2.2.1 Conformant Services
In order to conform to a specific CSTA service an implementation shall support the following as a minimum:
1. the requirements of the service as specified by its service description, service request parameters, service
response parameters, and operational model including connection state transitions, monitoring event
sequences, and functional requirements.
2. the requirements associated with each parameter used in the service as specified by its parameter description,
format, and functional requirements in Clause 12, “Parameter Types”.
© ISO/IEC 2004 - All rights reserved
3

---------------------- Page: 18 ----------------------
ISO/IEC 18051:2004(E)
3. all of the events that are associated with its service completion criteria, as documented in its event monitoring
tables.
2.2.2 Conformant Events
In order to conform to a specific CSTA event an implementation shall support the following as a minimum:
1. the requirements of the event as specified by its event description, event parameters, event causes, and
functional requirements.
2. the requirements associated with each parameter used in the event as specified by its parameter description,
format, and functional requirements in Clause 12, “Parameter Types”.
2.2.3 Support of Service Requests And Manual Mode
A conformant special resource function may support a given service defined in this Standard through the CSTA
service boundary but is not required to support the equivalent service in a manual mode.
A conformant special resource function may support a feature associated with an equivalent CSTA service defined
in this Standard through manual mode but is not required to support the equivalent service through the service
boundary.
2.3 Computing Function Conformance
In order to conform to this Standard a computing function shall support the following as a minimum:
1. the requirements pertaining to CSTA features as specified in Clause 6, “CSTA Operational Model”.
2. the requirements as spec
...