1、 ETSI TR 102 348 V1.1.1 (2004-09)Technical Report Using CSTA for SIP Phone User Agents (uaCSTA)ETSI ETSI TR 102 348 V1.1.1 (2004-09) 2 Reference DTR/ECMA-00292 Keywords CSTA, transport, user ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65
2、47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, ple
5、ase send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunica
6、tions Standards Institute 2004. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registe
7、red for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 348 V1.1.1 (2004-09) 3 Contents Intellectual Property Rights6 Foreword.6 Brief history6 1 Scope 7 2 Purpose.7 3 References 7 4 Terminology.8 4.1 General terms .8 4.2 SIP/CSTA Terminology Mappings 8 5 Example
8、 environments for uaCSTA 9 5.1 Controlling and Observing a SIP Phone.9 5.2 Controlling and Observing a SIP Phone by Augmenting B2BUA Functionality.9 5.3 Controlling a PBX Phone .10 6 Example User Agent Configurations .10 6.1 Single Line Phone UA10 6.2 Multi Line Phone UA.11 6.3 Bridged Appearance Ph
9、one and other Advanced UA Configurations11 7 SIP Transport Mechanism for CSTA Messages.12 7.1 Establishing a CSTA Application Session .12 7.2 Transporting CSTA Service Requests and Responses .13 7.3 Starting a Monitor and Transporting CSTA Events .13 8 uaCSTA Profiles 14 8.1 Minimal uaCSTA Call Cont
10、rol Profile.15 8.1.1 Services.15 8.1.2 Events .15 8.2 Basic uaCSTA Call Control Profile15 8.2.1 Services.15 8.2.2 Events .15 8.3 Advanced uaCSTA Call Control Profile 16 8.3.1 Services.16 8.3.2 Events .16 8.4 Conferencing uaCSTA Call Control Feature Profile17 8.4.1 Services.17 8.4.2 Events .17 8.5 Ba
11、sic uaCSTA Device Feature Profile .17 8.5.1 Services.17 8.5.2 Events .17 8.6 Speaker uaCSTA Device Feature Profile .18 8.6.1 Services.18 8.6.2 Events .18 9 CSTA Calls and Connections.18 9.1 CSTA Connection State Model18 9.2 Connection State Transitions for CSTA Calls19 9.2.1 Incoming Call .19 9.2.2
12、Outgoing Call19 10 Call Control20 10.1 Alternate Call .20 10.1.1 Service Request 20 10.1.2 Positive Service Response 20 10.1.3 Negative Service Response.21 10.2 Answer Call21 ETSI ETSI TR 102 348 V1.1.1 (2004-09) 4 10.2.1 Service Request 21 10.2.2 Positive Service Response 22 10.2.3 Negative Service
13、 Response.22 10.3 Clear Connection22 10.3.1 Service Request 23 10.3.2 Positive Service Response 23 10.3.3 Negative Service Response.23 10.4 Consultation Call24 10.4.1 Service Request 24 10.4.2 Positive Service Response 24 10.4.3 Negative Service Response.24 10.5 Deflect Call 25 10.5.1 Service Reques
14、t 25 10.5.2 Positive Service Response 26 10.5.3 Negative Service Response.26 10.6 Generate Digits.26 10.6.1 Service Request 27 10.6.2 Positive Service Response 27 10.6.3 Negative Service Response.27 10.7 Hold Call 28 10.7.1 Service Request 28 10.7.2 Positive Service Response 28 10.7.3 Negative Servi
15、ce Response.28 10.8 Make Call .29 10.8.1 Service Request 29 10.8.2 Positive Service Response 30 10.8.3 Negative Service Response.30 10.9 Reconnect Call .30 10.9.1 Service Request 31 10.9.2 Positive Service Response 31 10.9.3 Negative Service Response.31 10.10 Retrieve Call.32 10.10.1 Service Request
16、 32 10.10.2 Positive Service Response 32 10.10.3 Negative Service Response.32 10.11 Single Step Transfer Call .33 10.11.1 Service Request 33 10.11.2 Positive Service Response 34 10.11.3 Negative Service Response.34 10.12 Transfer Call.34 10.12.1 Service Request 35 10.12.2 Positive Service Response 3
17、5 10.12.3 Negative Service Response.35 11 Physical Phone Features.36 11.1 Get Message Waiting Indicator37 11.1.1 Service Request 37 11.1.2 Service Response 37 11.2 Set Message Waiting Indicator.37 11.2.1 Service Request 37 11.2.2 Service Response 38 11.3 Get Speaker Mute.38 11.3.1 Service Request 38
18、 11.3.2 Service Response 38 11.4 Set Speaker Mute39 11.4.1 Service Request 39 11.4.2 Service Response 39 11.5 Get Speaker Volume 39 11.5.1 Service Request 39 11.5.2 Service Response 40 11.6 Set Speaker Volume .40 11.6.1 Service Request 40 ETSI ETSI TR 102 348 V1.1.1 (2004-09) 5 11.6.2 Service Respon
19、se 41 12 Logical Phone Features 41 12.1 Get Do Not Disturb 41 12.1.1 Service Request 41 12.1.2 Service Response 41 12.2 Set Do Not Disturb.42 12.2.1 Service Request 42 12.2.2 Service Response 42 12.3 Get Forwarding 42 12.3.1 Service Request 42 12.3.2 Service Response 43 12.4 Set Forwarding .43 12.4.
20、1 Service Request 43 12.4.2 Service Response 44 13 Monitoring Services and Events.44 13.1 Monitor Start 44 13.1.1 Service Request 44 13.1.2 Positive Service Response 45 13.1.3 Negative Service Response.45 13.2 Monitor Stop 46 13.2.1 Service Request 46 13.2.2 Positive Service Response 46 13.2.3 Negat
21、ive Service Response.46 13.3 Events.47 14 Snapshot Services.47 14.1 Snapshot Device.47 14.1.1 Service Request 47 14.1.2 Positive Service Response 47 14.1.3 Negative Service Response.49 15 Discovery and System Status Services.50 15.1 Get CSTA Features 50 15.1.1 Service Request 50 15.1.2 Service Respo
22、nse 50 15.1.3 Negative Service Response.51 15.2 Request System Status51 15.2.1 Service Request 51 15.2.2 Service Response 52 15.2.3 Negative Service Response.52 15.3 System Status .52 15.3.1 Service Request 52 15.3.2 Positive Service Response 53 15.3.3 Negative Service Response.53 16 ECMA-323 Illust
23、rative Examples 53 16.1 Controlling a SIP UA .53 16.1.1 Creating an Application Session, Establishing a Monitor for a SIP Phone.53 16.1.2 Creating a Call from a SIP UA, Clearing a Call at a SIP UA .55 16.1.3 Answering and Clearing an Incoming Call at a UA .58 16.1.4 Answering an Incoming Call at a U
24、A (no CSTA monitor or CSTA events)60 16.1.5 Examples of Exception Conditions at a SIP UA.62 16.2 Controlling a PBX Phone .63 16.2.1 Creating an Application Session, Establishing a Monitor for a PBX Phone.64 16.2.2 Creating a Call from a PBX Phone, Clearing a Call at a PBX Phone.65 16.2.3 Answering a
25、nd Clearing an Incoming Call at a PBX Phone.69 16.2.4 Examples of Exception Conditions at a PBX Phone 71 Annex A: Example use of SIP and TEL URIs .73 History 75 ETSI ETSI TR 102 348 V1.1.1 (2004-09) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may ha
26、ve 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 (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI stand
27、ards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of oth
28、er IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ECMA on behalf of its members and those of the European Telecommunications Standards Inst
29、itute (ETSI). Brief history This Technical Report illustrates how CSTA can be used over a SIP session to control and observe SIP user agents (uaCSTA). This Technical Report is part of a suite of Ecma CSTA Phase III Standards and Technical Reports. All of the Standards and Technical Reports in this s
30、uite are based upon the practical experience of Ecma member companies and each one represents a pragmatic and widely based consensus. ETSI ETSI TR 102 348 V1.1.1 (2004-09) 7 1 Scope The Session Initiation Protocol (SIP) is a control (signalling) protocol for creating, modifying, and terminating sess
31、ions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. CSTA standardizes a very powerful and flexible set of application services to observe and control voice and non-voice media calls as well as control and observe n
32、on-call related features. This Ecma Technical Report describes how CSTA can be used to provide a subset of CSTA call control functionality, called 1stparty call control, for SIP user agents. The term uaCSTA (for user agent CSTA) refers to transporting ECMA-323 (CSTA XML) messages over a SIP session.
33、 uaCSTA leverages SIP mechanisms to provide a highly featured, robust, and extensible set of features to support applications in the Enterprise environment. uaCSTA can be implemented by several different types of SIP user agents: directly by a SIP user agent on a SIP phone. uaCSTA can also be implem
34、ented by a SIP B2BUA to augment 3PCC functionality. by a proxy server that is front-ending a PBX. 2 Purpose Describe the relevant portions of the CSTA Standards - The two primary CSTA Standards, Services for Computer Supported Telecommunications Applications (ECMA-269) and the XML Protocol for CSTA
35、(ECMA-323), are relatively large standards (combined over 1 100 pages). Due to their size it is sometimes difficult for SIP developers without prior knowledge of CSTA standards to quickly find the relevant parts of the CSTA standards needed to implement basic features. The present document shows the
36、 relevant CSTA concepts and how they can be used to implement a CSTA-based application protocol without having to read all of the CSTA Standards. Terminology - Although many of the concepts are similar, different terms are used in SIP and CSTA to describe the same concepts. Since CSTA is designed to
37、 be protocol independent, it is helpful to show how the abstract terminology of CSTA is mapped to SIP specific terminology. Extensibility - A SIP phone that is being developed to support a specific application may initially need to only support a small subset of the features standardized in CSTA. As
38、 the types and complexity of applications using these devices increase, it is expected that these devices will need to support additional, more advanced, features standardized by CSTA, similar to features supported by other types of phones in Enterprise environments. The present document shows how b
39、asic features can be extended to support a rich standards-based feature set for applications. Interoperability - In order to encourage interoperability of applications and phones supporting this application protocol, additional CSTA Profiles, which include minimal sets of CSTA functionality, are des
40、cribed. These profiles can be extended by implementations to provide a more complete set of call and devices features commonly used by Enterprise applications. 3 References The present document provides informative examples of how to use CSTA concepts as an application protocol for SIP user agents.
41、The following Ecma Standards should be used as the definitive references for CSTA. ECMA-269 Services for Computer Supported Telecommunications Applications (CSTA) Phase III, 6thedition (June 2004). ETSI ETSI TR 102 348 V1.1.1 (2004-09) 8 ECMA-323 XML Protocol for Computer Supported Telecommunication
42、s Applications (CSTA) Phase III, 3rdedition (June 2004). The following IETF references provide information on the SIP features referenced in the present document: IETF RFC 3261 SIP: Session Initiation Protocol, Rosenberg, J. et al, IETF, June 2002. 4 Terminology 4.1 General terms The following table
43、 summarizes some of the commonly used terminologies used in the present document. application Refers to all components that control and observe uaCSTA instances that may be present in an application/computing domain such as an application residing on any type of computing device (desktop PC, mobile
44、computing device, CTI middleware, SIP B2BUA, SIP UA, etc.). uaCSTA user agent CSTA - This refers the mechanism to transport CSTA messages over a SIP session, and the type of call control, called 1stparty call control, that allows an application to control and observe only the device or devices it is
45、 directly involved with. A desktop application controlling its associated phone, for example. uaCSTA device Refers to a SIP UA, such as a SIP or PBX phone, that supports the CSTA features over SIP as described in the present document. phone A SIP UA that supports calls. It is also a PBX device that
46、supports calls. Examples of the types of phones that can be supported by this application protocol are described in clause 6. B2BUA A back-to-back-user-agent is a type of user agent that acts both as a user agent server (receives requests) and acts as a user agent client (generates requests). B2BUA
47、is used to implement SIP third party call control (3PCC) features. uaCSTA could be used to augment the existing B2BUA functionality for enhanced call control. 4.2 SIP/CSTA Terminology Mappings The following table shows some of the common SIP terms and how they are referenced using CSTA and vice vers
48、a. SIP Term CSTA Term Notes User Agent or UA device A SIP UA can be modelled as a type of CSTA device. Whenever the term device is used in the present document, it is referring to a SIP UA. SIP URI device identifier or deviceID A SIP URI can be used to address a SIP UA or a PBX phone in the same way
49、 that a CSTA device identifier can be used to address a CSTA device. One of the formats of a Device Identifier is URI. Whenever the term DeviceID is used in the present document, it is referring to a URI format of CSTA deviceID. Refer to annex A for a description of the ways to represent a user and a users device with a URI. TEL URI device identifier or deviceID A TEL URI can be used to address a device or a dialled number in the same way that a CSTA device identifier can be used to address a CSTA device. Refer to annex A for a description of the ways to represent
