1、ETSI TR 102 171 1.1.1 (2003-02) Technical Repor Using ECMA-323 (CSTA XML) in a Voice Browser Environment 2 ETSI TR 102 171 VI .I .I (2003-02) Reference DTR/ECMA-00285 Keywords CSTA, voice ETSI 650 Route des Lucioles F-O6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47
2、16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of the present document can be downloaded from: http:lwmv.etsi .arq The present document may be made available in more than one electronic
3、version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETS
4、I Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at ha p:/pa rta I. etsi I a rgltbistat uslstatus .as p If you find errors in the present docu
5、ment, send your comment to: Cori vriaht Notifica tion No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTST
6、Mand UMTSTMare Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partne
7、rs. ETSI 3 ETSI TR 102 171 VI . 1 . 1 (2003-02) Contents Intellectual Property Rights 5 Foreword . 5 Brief History . 5 1 2 3 4 4.1 4.2 4.3 4.3.1 4.3.2 5 5.1 5.1.1 5.1.2 5.2 5.2.1 5.2.2 5.3 5.3.1 5.3.2 5.4 5.4.1 5.4.2 5.5 6 6.1 6.2 6.2.1 6.2.2 6.3 6.3.1 6.4 6.4.1 6.4.2 6.5 6.5.1 6.6 6.6.1 6.6.2 6.7 6
8、.7.1 6.8 6.8.1 6.8.2 6.9 6.9.1 6.9.2 6.9.3 6.9.4 6.10 Scope 6 References 6 Brief Overview of ECMA-323 . 6 Fundamental Concepts . 7 CSTA Connection 7 CSTA Connection State Model 7 Connection State Transitions for CSTA Calls 8 Incoming Call . 8 Outgoing Call 8 CSTA Profiles 8 Level la Voice Browser Pr
9、ofile . 9 Services . 9 Events . 9 Level lb Voice Browser Profile . 9 Services . 9 Events . 10 Level 2 Voice Browser Profile . 10 Services . 10 Events . 10 Basic Telephony Profile . 11 Services . 11 Events . 11 Other Features 12 ECMA-323 Illustrative Examples 12 12 12 12 Monitor Start . Service Respo
10、nse example . 13 Notification of an Inbound Call 13 Delivered Event example 13 Answering an Inbound Call 14 Answer Call . Service Request example . 14 Answer Call . Service Response example 15 Notification of a Connected Call 15 Established Event example . 15 Clearing a Connection 15 Clear Connectio
11、n . Service Request example . 16 Clear Connection . Service Response example 16 Notification of a Cleared Connection . 16 Connection Cleared Event example 16 Initiating an Outbound Call 17 Make Call . Service Request example (refer to Profile) . 17 Make Call . Service Response example 17 Outbound Ca
12、ll Event Sequence 17 Originated Event Example 17 Network Reached Event . 18 Delivered Event 19 Established Event 20 Single Step Transfer . 20 Discovering the Capabilities of a Telephony Platform Starting a Monitor (i.e. listening for incoming calls) Monitor Start - Service Request example . ETSI 4 E
13、TSI TR 102 171 VI .I .I (2003-02) 6.10.1 6.10.2 6.11 6.11.1 6.12 6.12.1 6.12.2 6.13 6.13.1 6.14 6.14.1 6.14.2 6.15 6.15.1 6.16 Single Step Transfer - Service Request example 20 Single Step Transfer - Service Response exampl 20 Notification of a Transferred Connection . .20 Transferred Event example
14、. 20 Deflect. . 21 Deflect - Service Request example. 21 Deflect - Service Response example . .22 Notification of a Diverted Connection. . .22 Diverted Event example 22 Single Step Conference . .22 . .22 . .23 Notification of an Party Added to a call . 23 Conferenced Event example .23 Failure Respon
15、se example .24 Single Step Conference - Service Single Step Conference - Service 7 SALTKSTA XML Programming Example . 25 8 CCXMLKSTA XML Programming Example 29 9 CSTA Call Control Features 32 9.1 Services . .32 9.2 Events . . .33 History . .3 5 ETSI 5 ETSI TR 102 171 VI .I .I (2003-02) Intellectual
16、Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (7PRs
17、); Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). All published ETSI deliverables shall include information which directs the reader to the above source of
18、information. Foreword This Technical Report (TR) has been produced by ECMA on behalf of its members and those of the European Telecommunications Standards Institute (ETSI). Brief History The present document illustrates how CSTA XML (ECMA-323) can be used in a Voice Browser environment. The present
19、document is part of a suite of ECMA CSTA Phase III Standards and Technical Reports. All of the Standards and Technical Reports in this Suite are based upon the practical experience of ECMA member companies and each one represents a pragmatic and widely based consensus. ETSI 6 ETSI TR 102 171 VI .I .
20、I (2003-02) 1 Scope Services for Computer Supported Telecommunications Applications are defined by Standard ECMA-269 and the XML Protocol for those services is defiied by Standard ECMA-323. In many cases, applications require only a small subset of the features standardized in CSTA. In a voice brows
21、er environment, processing speech (not call control) is usually the major focus of the application. For example, from a CSTA feature perspective, an application may simply need to answer an incoming call and then later clear it. As these speech-centric applications evolve they can use additional, mo
22、re advanced, features standardized by CSTA that are provided by CSTA-conformant communications platforms. Since ECMA-269 and ECMA-323 are relatively large standards (combined over 1100 pages), it is a challenge for application developers without prior knowledge of the CSTA standards to know where to
23、 find basic concepts that they need to understand in order to implement basic CSTA features. The present document illustrates how ECMA-323 can be used in a Voice Browser environment. These concepts illustrated in the present document can be applied to any Voice Browser environment that provides an X
24、ML-based readwrite messaging interface (i.e. CSTA Service Boundary) that supports asynchronous events from a CSTA conformant communication platform. SALT enabled browsers that implement a ECMA-323 interface for call control using the SALT smex mechanism is an example of a browser with this capabilit
25、y. Throughout the present document the term “ECMA-323 enabled voice browser“ is used, in a generic sense, to refer to browser implementation that support a CSTA conformant ECMA-323 interface. Examples are provided that show how ECMA-323 can be used in several different environments such as SALT-enab
26、led browsers and CCXML. 2 Re fe re nces The present document provides informative examples of how to use ECMA-323 in a Voice Browser environment. The following ECMA Standards should be used as the definitive references for CSTA. ECMA-269: “Services for Computer Supported Telecommunications Applicati
27、ons (CSTA) Phase III“. ECMA-323 : “XMLProtocol for Computer Supported Telecommunications Applications (CSTA) Phase III“. ECMA CSTA Standards can be used for call control in many different environments. The following references provide additional information on using the ECMA CSTA standards in differ
28、ent environments: SALT: “Speech Application Language Tags Specification Version 1 .O“, SALT Forum, 15 July 2002. (Inttn : llwww. sait forum. mg). CCXML: “Voice Browser Call Control: CCXML Version 1 .O“, W3C Working Draft, 11 October 2002. (httn : l/wmv.w3 c .ordTW/ccxinl. 3 Brief Overview of ECMA-32
29、3 ECMA-323 consists of a set of XML Schemas based upon the W3C XML Schema Language Recommendation. The Standard includes Schemas for many categories of services defined in ECMA-269. Call control is just one category of services in ECMA-323. Examples of other categories of services are: capability ex
30、change (feature discovery) services, call routing services, services to control a device (e.g. message waiting, writing to display, forwarding settings), and many others. CSTA provides a protocol independent abstraction layer for applications. It provides a consistent, standards-based messaging inte
31、rface that can be used with basic lSt party call control based platforms as well as more complex 3d party call control (CTI) platforms, or a combination of both ( lSt party call control with some additional 3d party call control features). ETSI 7 ETSI TR 102 171 VI .I .I (2003-02) CSTA modelling and
32、 concepts are also compatible with many procedural and object models such as the SALT CallControl object (chapter 3 of the SALT specification). 4 Fun dam en ta I Con ce pts This clause introduces some informative modelling concepts that are useful to illustrate how ECMA-323 enabled voice browsers ca
33、n use ECMA-323 messages. The actual ECMA CSTA standards should be used for the definitive descriptions. 4.1 CSTA Connection CSTA call control services are applied to CSTA connections. A CSTA connection refers to a relationship between a call and a telephony endpoint. A CSTA connection is referenced
34、via a CSTA connection identifier. A CSTA connection identifier consists of a call identifier and a device (endpoint) identifier. In a typical lSt party call control implementation, a voice browser application manipulates only the CSTA connection directly associated with the voice browser platform. H
35、owever, other call control implementations may also provide application control of other endpoints in the call using CSTA services (via 3d party call control, for example). A device identifier is included in a CSTA connection identifier to allow any endpoint to be addressed by a voice browser applic
36、ation. 4.2 CSTA Connection State Model A ECMA-323 enabled voice browser application is informed of connection state transitions (via ECMA-323 call control events) by placing a monitor on a telephony endpoint via an associated address (e.g. this is how an application “listens“ for incoming calls). Ea
37、ch CSTA connection in a call is associated with a connection state. CSTA specifies a connection state model (see ECMA-269, figure 6-19) that consists of the following connection states: Alerting: Indicates an incoming call at an endpoint. Typically the connection may be ringing or it may be in a pre
38、-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 t
39、hat 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 analogue lin
40、e, 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).
41、The CSTA Connection State is provided in ECMA-323 events. ETSI 8 4.3 Connection State Transitions 4.3.1 Incoming Call ETSI TR 102 171 VI .I .I (2003-02) for CSTA Calls The following figure illustrates the CSTA events for an incoming call. The connection state of endpoint on the voice browser platfor
42、m (called connection) is indicated in parenthesis. Delivered Event (Alerting): Indicates call is alerting. Calls that are “auto-answered“ do not sent this event. A CSTA Answer Call service can be used to answer the call. This results in an Established event. Established Event (Connected): Indicates
43、call has been answered. Media path has been established. The CSTA Clear Connection service can be used to clear the call. A Connection Cleared event is generated as the result of the Clear Connection service. Connection Cleared Event (Null): Indicates connection has cleared. This can be the result o
44、f the Clear Connection service or as the result of any party clearing from the call. 4.3.2 Outgoing Call The following figure illustrates the CSTA events for an outgoing call. The connection state of the endpoint on the Voice Browser platform (originating connection) is indicated in parenthesis. Thi
45、s sequence could be the result of a CSTA Make Call service. Originated Event (Connected): Indicates that the originating connection (an endpoint on the voice browser platform) is connected, Delivered Event (Connected): Indicates the call is alerting the called party. Established Event (Connected): I
46、ndicates the called party has answered the call. Media path has been established. Connection Cleared Event (Null): Indicates connection has cleared. 5 CSTA Profiles Since many CSTA features are optional, and to enhance application portability across different CSTA implementations, CSTA standards req
47、uire a minimal subset of functionality as conformance criteria. ECMA-269 specifies a set of Profiles. At least one profile is required to be supported. The following profiles most closely match the call control services and events needed by a Voice Browser application. Level la Voice Browser Profile
48、 (added in ECMA-269 5th edition): Provides support for answering an incoming call, clearing, and moving the call to another endpoint using the Single Step Transfer Call service. The Get Switching Function Capabilities Service is not required to be supported in this profile. Level lb Voice Browser Pr
49、ofile (added in ECMA-269 5th edition): Provides support for answering an incoming call, clearing, and moving the call to another endpoint using the Deflect Call service. The Get Switching Function Capabilities Service is not required to be supported in this profile. Level 2 Voice Browser Profile (added in ECMA-269 5th edition): Provides support for making a call in addition to the services and events required in either the Levella Voice Browser Profile of the Level lb Voice Browser Profile. The Get Switching Function Capabilities Service is required to be supported in this profi
