What Is CSTA?

What is CSTA?
ECMA-323 (CSTA XML) Overview
by Tom Miller (Siemens)

Topics
CSTA History
CSTA Standards Suite
CSTA Features
ECMA-323 (CSTA XML)
Call Control Details
Voice Browsers & ECMA-323
CSTA Evolution
Phase I
• published June ‘92
• 40 features, 66 pages
• focus on call control
Phase II
• published Dec. ‘94
• I/O & Voice Unit Services, more call control services
Phase III
• Published Dec. ‘98
• CSTA Phase II Features & Versit CTI Technology
• Published as an ISO Standard July 2000
• Published XML (ECMA-323) June 2001
What is CSTA?
Abstraction Layer for telecommunication applications:

• Independent of underlying signaling protocols
• H.323, SIP, Analog, T1, ISDN, etc.
• Independent of devices
• intelligent endpoints, low-function/stimulus devices, SIP Signaling models - 3PCC vs. Peer/Peer
Operates equally well in different environments:

• 3rd party call control
• 1st party call control
Basic call model standardized in 1992 – continually refined and
enhanced based upon significant industry implementation
experiences, new protocols, etc.
Design goal to enhance application portability across CSTA
implementations:
• Specifies normalized call model and behavior
• Complete functional definition of each service
• Specific conformance criteria
CSTA Standards
ECMA-269: Services for CSTA Phase III

ECMA-285: ASN.1 Protocol for CSTA Phase III
ECMA-323: XML Protocol for CSTA Phase III
Ecma-348: Web Services Description Language (WSDL) for
CSTA Phase III
ECMA TR/72: Glossary of Definitions & Terms for CSTA Phase
III
ECMA TR/80: Migrating to CSTA Phase III
ECMA TR/82: Scenarios for CSTA Phase III
Ecma TR/85: Using Ecma-323 (CSTA XML) in a Voice Browser
Environment
CSTA Features
Standardized CSTA Features
25 Call Control features (making call, answering call, etc.)

5 Call Associated features (sending user data, etc.)
19 Logical Device features (do not disturb, forwarding, etc.)
23 Physical Device features (writing to device display, etc.)
5 Capability Exchange features (feature discovery, etc.)
4 Snapshot features (query existing calls at a device, etc.)
3 Monitor features (subscribing to event reports, etc.)
Other: Routeing services, Media Attachment services, Maintenance
services, Data Collection services, Voice Unit services, Accounting
services, etc.
Implementation does not need to support all of these features to

conform to CSTA!!!! (See Slide 12 on Profiles)
Features: Call Control Overview
Exhaustive set of standardized call control features:

• Services: Accept, Alternate, Answer, Call Back, Call Back Message,
Camp On, Clear Call, Clear Connection, Conference, Consultation,
Deflect, Dial Digits, Directed Pick up, Group Pick Up, Hold, Intrude, Join,
Make Call, Make Predictive Call, Park, Reconnect, Retrieve, Single Step
Conference, Single Step Transfer, Transfer.
• Events: Bridged, Call Cleared, Conferenced, Connection Cleared,
Delivered, Digits Dialed, Diverted, Established, Failed, Held, Network
Capabilities Changed, Network Reached, Offered, Originated, Queued,
Retrieved, Service Initiated, Transferred.
(features included in Basic Telephony profile are underlined)
Each feature includes a complete operational model on how the
feature works, from an application perspective.
• Before/After conditions
• State transitions
• Event flow
• Textual behavior description
Call Control Model: Connection
States
Alerting – Indicates an incoming call at an endpoint. Typically the connection

may be ringing or it may be in a pre-alerting (e.g. offered) condition.
Connected – Indicates that a connection is actively participating in a call. This
connection state can be the result of an incoming or outgoing call.
Failed – Indicates that call progression has stalled. Typically this could
represent that an outgoing call attempt that encountered a busy endpoint.
Held – Indicates that an endpoint is no longer actively participating in a call. For
implementations that support multiple calls per endpoint (i.e. line), a connection
could be Held while the line is used to place another call (consultation transfer
on an analog line, for example).
Initiated – A transient state, usually indicating that the endpoint is initiating a
service (e.g. dialtone).
Null – There is no relationship between the call and the endpoint.
Queued – Indicates that the call is temporarily suspended at a device (e.g. call
has been parked, camped on).
Event Sequences
typical call events for incoming call
Accept Connection
Offered Delivered Answer Established Clear
Call Call Connection Cleared
typical call events for outgoing call (Make Call)
Connection
Originated Call Offered Called Delivered Called Established Called
Offered Device Party Party Cleared
To alerted answers clears
Called
device
Extensibility – Enhancing
functionality of CSTA
Standard is extensible:
• Additional features can be added to the standard via new
editions of the standard
• New Parameters, new values to existing parameters can
be added via new editions of the standard
• Backward compatibility must be maintained in any future
editions
• Implementations can add proprietary features using built
in CSTA extension mechanisms
Profiles – Defining Minimal
Implementation Sets
CSTA Includes a set of Profiles:

• Specifies minimal set of features required to conform to
CSTA
• At least one profile must be supported by an
implementation
• Applications can be developed with feature set in mind
Existing Profiles:
• Basic Telephony profile
• Routing profile
Additional profiles can be standardized via new editions
The ECMA-323 Standard
XML Encoding for CSTA feature set

• Set of W3C XML Schemas
• One schema per service/event
Contains XML encoding for all CSTA features
standardized in ECMA-269
CSTA XML facilitates use of CSTA features by Internet

developers – when combined with Scripting languages such as
ECMAScript, it becomes very easy to use the CSTA XML
interface directly
ECMA-323 Examples:
Monitoring a device
<?xml version="1.0" encoding="UTF-8"?>

<MonitorStart xmlns="http://www.ecma.ch/standards/ecma-323/csta">
<monitorObject>
<deviceObject>22343</deviceObject>
</monitorObject>
</MonitorStart>
XML Example:
Answering an Alerting Call

<AnswerCall xmlns="http://www.ecma.ch/standards/ecma-
323/csta">
<callToBeAnswered>
<callID>1</callID>
<deviceID>22343</deviceID>
</callToBeAnswered>
</AnswerCall>
Example:
Clearing a connection

<ClearConnection xmlns="http://www.ecma.ch/standards/ecma-
323/csta">
<connectionToBeCleared>
<callID>1</callID>
</connectionToBeCleared>
</ClearConnection>
Example:
Notification of Incoming Call
Rich content – application “picks” info it needs

<DeliveredEvent xmlns="http://www.ecma.ch/standards/ecma-323/csta">
<monitorCrossRefID>99</monitorCrossRefID>
<connection>
<callID>1</callID>
</connection>
<alertingDevice><deviceIdentifier>22343</deviceIdentifier></alertingDevice>
<callingDevice><deviceIdentifier>14085551212</deviceIdentifier></callingDevice>
<calledDevice><deviceIdentifier>22343</deviceIdentifier></calledDevice>
<lastRedirectionDevice><notRequired/></lastRedirectionDevice>
<localConnectionInfo>alerting</localConnectionInfo>
<cause>newCall</cause>
<networkCallingDevice><deviceIdentifier>14085551212</deviceIdentifier>
</networkCallingDevice>
<networkCalledDevice><deviceIdentifier>18001234567</deviceIdentifier>
</networkCalledDevice>
<associatedCallingDevice><deviceIdentifier>023</deviceIdentifier>
</associatedCallingDevice>
</DeliveredEvent>
CSTA Phase III
Second Edition
Support for non-voice media interactions (IM, Email, Chat)

• CSTA call model applicable to non-voice media (Email, Chat, IM,
etc.)
• CSTA “call” and “connection” objects are media independent
• chat can be modeled as an interactive “text call”
• Email can be modeled as an non-interactive “text call”
• Additional parameters for message information, subject of call,
priority, sensitivity of calls, etc.
Enhancements to enhance SIP support
• Features to improve control of media (connection information),
support of SIP 3PCC, etc.
ECMA-269
Detailed Discussion Topics:

• Connection model (ECMA-269: 6.5.1)
• Monitoring Concepts (ECMA-269: 15)
• Snapshot Services (ECMA-269: 16)
• Summary of Parameter Types (elements) used in ECMA-
323 messages (ECMA-269: 12.2)
• Call Control Services Walkthrough (ECMA-269: 17.1)
• Call Control Events Walkthrough (ECMA-269: 17.2)
ECMA-323 & Voice Browsers
CSTA XML ideally suited for VB platforms that support a messaging

interface w/ asynchronous events (such as SALT smex)
ECMA-323 chosen as the recommended call control messaging
interface for SALT
• Alternative to SALT CC Object Model
• Used with the SALT platform messaging (smex)
• Easy to create & access ECMA-323 XML messages via ECMAScript/DOM
• Examples of ECMA-323, ECMAScript, SALT in SALT 1.0
ECMA Standardization Opportunities:
• Can add another profile that is optimized for Voice Browser applications.
• Publish a Technical Report that shows how ECMA-323 can be used in a
Voice Browser environment.
• Enhance CSTA, if necessary, to support additional features for VBs.
Summary
CSTA is an existing (ECMA, ISO) Standard with an exhaustive feature set,

comprehensive call model
CSTA supports range of application landscapes – from basic 1st party cc to

advanced 3rd party cc with same standardized model
CSTA exposes advanced features of a communications platform to applications

developers while insulating applications from underlying protocol specifics
CSTA XML facilitates use of call control features by Internet developers – when
combined with Scripting languages such as ECMAScript, it becomes easy to
program directly to the CSTA XML interface
CSTA XML ideally suited for VB platforms that support a messaging interface w/
asynchronous events (such as SALT smex)
CSTA supports voice and non-voice interactions (Email, Chat, IM, etc.) with
same call model.

What Is CSTA?

Uploaded by

Copyright:

Available Formats

What Is CSTA?

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

What Is CSTA?

Uploaded by

Copyright:

Available Formats

What is CSTA?

ECMA-323 (CSTA XML) Overview

by Tom Miller (Siemens)

Abstraction Layer for telecommunication applications:

Operates equally well in different environments:

ECMA-269: Services for CSTA Phase III

25 Call Control features (making call, answering call, etc.)

Implementation does not need to support all of these features to

Exhaustive set of standardized call control features:

Alerting – Indicates an incoming call at an endpoint. Typically the connection

typical call events for incoming call

 typical call events for outgoing call (Make Call)

CSTA Includes a set of Profiles:

XML Encoding for CSTA feature set

CSTA XML facilitates use of CSTA features by Internet

<?xml version="1.0" encoding="UTF-8"?>

Answering an Alerting Call

<?xml version="1.0" encoding="UTF-8"?>

<?xml version="1.0" encoding="UTF-8"?>

Notification of Incoming Call

Rich content – application “picks” info it needs

Support for non-voice media interactions (IM, Email, Chat)

Detailed Discussion Topics:

CSTA XML ideally suited for VB platforms that support a messaging

CSTA is an existing (ECMA, ISO) Standard with an exhaustive feature set,

CSTA supports range of application landscapes – from basic 1st party cc to

CSTA exposes advanced features of a communications platform to applications

You might also like

typical call events for outgoing call (Make Call)