ECMA-348 3 rd Edition / December 2006 Web Services Description Language (WSDL) for CSTA Phase III
Standard ECMA-348 3 rd Edition / December 2006 Web Services Description Language (WSDL) for CSTA Phase III Ecma International Rue du Rhône 114 CH-1204 Geneva T/F: +41 22 849 6000/01 www.ecma-international.org P ECMA-348.doc 12-Dec-06 5:13 PM
.
Brief history This Standard defines a Web Services Description Language (WSDL) 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 upon the practical experience of Ecma member companies and each one represents a pragmatic and widely based consensus. This 3 rd Edition of ECMA-348 is fully aligned with ECMA-269 7 th Edition and it imports the CSTA XML schemata from ECMA-323 4 th Edition. This Ecma Standard has been adopted by the General Assembly of December 2006.
WSDL Tools Acknowledgement The WSDL specified in this Standard has been checked using the XML SPY tool.
Table of contents 1 Scope 1 2 Conformance 1 3 References 1 3.1 Ecma References 1 3.2 World Wide Web Consortium References 1 4 Definitions 2 5 Web Services Overview 2 6 WSDL Overview 3 6.1 Namespaces 3 6.2 Data Types 3 6.3 Messages 3 6.3.1 Message Names 4 6.3.2 Message Parts 4 6.3.3 Example 4 6.4 Operations 4 6.4.1 Request-response Operation Type 4 6.4.2 One-way Operation Type 5 6.4.3 Solicit-response Operation Type 5 6.4.4 Notification Operation Type 6 6.4.5 Summary of CSTA Request/Response & Event Models and WSDL Operation Types 6 6.5 Port Types 7 6.5.1 Example 7 6.6 Bindings 8 6.7 Port 8 6.8 Service 9 7 Capability Exchange Services Messages and Operations 10 7.1 Messages 10 7.2 Operations 13 8 System Services Messages and Operations 15 8.1 Messages 15 - i -
8.2 Operations 19 9 Monitoring Services Messages and Operations 22 9.1 Messages 22 9.2 Operations 24 10 Snapshot Services Messages and Operations 25 10.1 Messages 25 10.2 Operations 27 11 Call Control Features Messages and Operations 28 11.1 Messages 28 11.2 Operations 43 12 Call Associated Features - Messages and Operations 52 12.1 Messages 52 12.2 Operations 56 13 Media Attachment Features - Messages and Operations 58 13.1 Messages 58 13.2 Operations 60 14 Routeing Features - Messages and Operations 61 14.1 Messages 61 14.2 Operations 64 15 Physical Device Features - Messages and Operations 66 15.1 Messages 66 15.2 Operations 78 16 Logical Device Features - Messages and Operations 85 16.1 Messages 85 16.2 Operations 96 17 Device Maintenance Events - Messages and Operations 103 17.1 Messages 103 17.2 Operations 104 18 I/O Services Features - Messages and Operations 105 18.1 Messages 105 18.2 Operations 111 - ii -
19 Data Collection Features - Messages and Operations 115 19.1 Messages 115 19.2 Operations 118 20 Voice Features - Messages and Operations 120 20.1 Messages 120 20.2 Operations 131 21 Call Data Recording Features - Messages and Operations 138 21.1 Messages 138 21.2 Operations 141 22 Vendor Specific Features - Messages and Operations 143 22.1 Messages 143 22.2 Operations 146 23 Basic Telephony Profile Port Type 148 24 Routeing Profile - Port Type 151 25 Level 1a Voice Browser Profile - Port Type 152 26 Level 1b Voice Browser Profile - Port Type 154 27 Level 2a Voice Browser Profile - Port Type 156 28 Level 2b Voice Browser Profile - Port Type 159 29 Minimal uacsta Call Control Profile Port Type 162 30 Basic uacsta Call Control Profile Port Type 164 31 Advanced uacsta Call Control Profile Port Type 168 32 Conferencing uacsta with Basic Call Control Profile Port Type 173 33 Conferencing uacsta with Advanced Call Control Profile Port Type 177 34 Basic uacsta Device Feature with Basic Call Control Profile Port Type 183 35 Basic uacsta Device Feature with Advanced Call Control Profile Port Type 188 36 Speaker uacsta Device Feature with Basic Call Control Profile Port Type194 - iii -
37 Speaker uacsta Device Feature with Advanced Call Control Profile Port Type 199 Annex A (informative) Example SOAP 1.1/HTTP Bindings 205 Annex B (informative) WSDL Considerations 207 Annex C (informative) Summary of Changes in this Edition 209 - iv -
1 Scope Web Services Description Language (WSDL) is an XML schema for describing Web services and how they can be accessed by Web based applications. WSDL facilitates the creation and deployment of web based applications. For example, by using WSDL with many industry Web services development environments, a web services developer can access features provided by an implementation without knowing details of the network or underlying transport protocols. This Standard specifies a WSDL for ECMA-269, Services for Computer Supported Telecommunications Applications (CSTA) Phase III. All CSTA features (e.g., services and events) specified in ECMA-269 are specified in this Standard. This Standard specifies port types for all the profiles specified in ECMA-269. A full WSDL document contains both abstract definitions (WSDL messages and port type elements) and concrete protocol specific definitions (WSDL bindings, ports, and service elements). This CSTA WSDL Standard specifies only the abstract definitions of a WSDL document. The concrete and protocol specific definitions are implementation specific and are outside the scope of this Standard. One example transport illustrated in this Standard is SOAP over HTTP. WSDL is defined in XML and XML Schemata. This Standard builds upon the XML data types and imports all message formats specified in ECMA-323. 2 Conformance In addition to the conformance requirements specified in Clause 2 of ECMA-269 and Clause 2 of ECMA-323, a conformant implementation supports at least one of the port types defined in this Standard. Each port type in this Standard corresponds to a profile specified in 2.3.1 of ECMA-269. To support one of these port types, an implementation must support all the WSDL operations specified in the port type. A conformant implementation supports an operation by adhering to the corresponding service definition in ECMA-269 and by using the message formats and data types as specified in ECMA-323. 3 References 3.1 Ecma References ECMA-269 Services for Computer Supported Telecommunications Applications (CSTA) Phase III, 7 th Edition (December 2006) ECMA-323 XML Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III, 4 th Edition (December 2006) ECMA TR/72 Glossary of Definitions and Terminology for Computer Supported Telecommunications Applications (CSTA) Phase III, 3 rd Edition (June 2000) 3.2 World Wide Web Consortium References SOAP 1.1 Simple Object Access Protocol (SOAP) 1.1, W3C Note 08 May 2000 XML 1.0 Extensible Markup Language (XML) 1.0 (Second Edition), W3C Recommendation 06 October 2000 XML Schema 1.0 XML Schema Language Part 1: Structures. W3C Recommendation 2 May 2001 and XML Schema Language Part 2: Datatypes. W3C Recommendation 2 May 2001 WSDL 1.1 Web Services Description Language (WSDL) 1.1, W3C Note 15 March 2001-1 -
4 Definitions CSTA-specific terminology is defined in ECMA TR/72. 5 Web Services Overview A Web service is the name for a service that is accessed by applications over the Internet. Conceptually this corresponds to a CSTA application (client) invoking services provided by a CSTA implementation (server) in a distributed environment. Web services are more formally defined as: encapsulated, loosely coupled contracted functions offered via standard protocols where: Encapsulated means the implementation of the function is never seen from the outside Loosely coupled means changing the implementation of one function does not require a change of the invoking function and Contracted means there are publicly available descriptions of the function s behaviour, how to bind to the function as well as its and s. The goal of Web services is a seamless integration of services across the different technologies (networks, software, hardware, etc.) available on the Internet. Web services require: 1. A standard way to represent data 2. A common, extensible message format 3. A common, extensible service description language 4. A common way to discover service providers The first two requirements, a standard way to represent data and a common extensible message format, have already been achieved with ECMA-323. The ECMA-323 Standard includes extensible XML schemas for all of the categories of services defined in ECMA-269. NOTE This Standard satisfies the third requirement, a common, extensible service description language, by providing a WSDL for CSTA. UDDI (Universal Discovery, Description, and Integration Registry) and other procedures to satisfy the forth requirement are outside the scope of this Standard. There are three components that are involved with Web services: Service Requester provides the following major functions: 1) optionally queries a Service Broker for where to find a suitable Service Provider and 2) binds and interacts with a Service Provider. Service Provider provides the following major functions: 1) publishes its services (e.g. WSDL document) and 2) interacts with a Service Requester. Service Broker acts as a look up service between a Service Provider and a Service Requester. A Service Broker is an optional component of a Web service. For the purposes of this Standard: A CSTA Service Requester is a Service Requester. A CSTA Service Provider is a Service Provider. A Service Broker is outside the scope of this Standard. - 2 -
6 WSDL Overview WSDL enables applications to communicate with each other in an automated way. A WSDL document describes Web services both in an abstract (network independent) and concrete (with network protocol bindings, e.g. SOAP) way. A WSDL document consists of sets of definitions. There are six major elements in a WSDL document: types provides the data type definitions used to describe the messages exchanged message defines the messages contents operation defines how and messages are associated with a logical operation porttype groups a set of operations together binding specifies concrete protocol and data format specifications for the operations and messages for a particular porttype port specifies an address for a binding service used to group a set of related ports 6.1 Namespaces There are two CSTA specific namespaces used in this Standard: http://www.ecma-international.org/standards/ecma-323/csta/ed4 - this namespace, for which csta is a shorthand, contains all of the CSTA XML messages specified in ECMA-323, 4 th Edition. See 6.2. http://www.ecma-international.org/standards/ecma-348/csta-wsdl/ed3 - this namespace, for which tns is a shorthand, contains the CSTA WSDL schema definitions specified in this Standard. NOTE The namespace for csta is appropriate for all of the XML Tag Options specified in ECMA-323. There are also several other namespaces referenced by the CSTA WSDL schema such as: http://schemas.xmlsoap.org/wsdl/ - this contains the W3C WSDL 1.1 schema http://schemas.xmlsoap.org/wsdl/soap - this contains the W3C SOAP bindings for WSDL 1.1 http://schemas.xmlsoap.org/wsdl/http - this contains the W3C SOAP bindings for WSDL 1.1 http://www.w3.org/2001/xmlschema - this contains the W3C XML Schema Definition 6.2 Data Types Data types describe the format of the XML elements in a message. Examples of data types are integers and strings. This Standard imports the CSTA XML data types standardized in ECMA-323. 6.3 Messages Message definitions specify the contents of an XML message. The message definitions are used in a WSDL operation where they will be typed as an or message in the context of the WSDL operation. This Standard imports the CSTA XML elements specified in ECMA-323. - 3 -
An example of an XML element specified in ECMA-323 is: <xsd:element name="answercall"> <xsd:complextype> <xsd:sequence> <xsd:element name="calltobeanswered" type="csta:connectionid"/> <xsd:element ref="csta:correlatordata" minoccurs="0"/> <xsd:element ref="csta:userdata" minoccurs="0"/> <xsd:element ref="csta:extensions" minoccurs="0"/> </xsd:sequence> </xsd:complextype> </xsd:element> The above definition, along with all ECMA-323 message definitions, is imported by the CSTA WSDL schema and is available in the http://www.ecma-international.org/standards/ecma- 323/csta/ed4 namespace. 6.3.1 Message Names The WSDL message element specifies the name of a message that is referenced in a WSDL operation element. The naming convention used in this Standard is to derive the WSDL message element name from the corresponding ECMA-323 element name. A lower case letter is used to differentiate the WSDL message name from the ECMA-323 element name. For example, the ECMA-323 element name AnswerCall is used in the definition of the CSTA WSDL answercall message name. 6.3.2 Message Parts The WSDL message part element is used to define the actual format of the message. Although there can be multiple in a WSDL message, CSTA WSDL uses only one part and therefore can always use the same name (i.e. ) for the message part name. The element type refers to an element defined in ECMA-323. 6.3.3 Example The following example defines a WSDL message element definition for the ECMA-323 AnswerCall request message. Its name answercall will be used to define the AnswerCall Operation. <message name="answercall"> <part name="" element="csta:answercall"/> 6.4 Operations A WSDL operation specifies the message (if any), the message (if any), and the message (if any) that is associated with the WSDL operation. This formalizes the relationship between the CSTA XML elements standardized in ECMA-323. Although a person can determine the relationship between messages associated with an operation in ECMA-323 by its logical place in the ECMA-323 Standard and in some cases by naming conventions, CSTA WSDL specifies this relationship in a formal notation that can be understood by applications. The operation name is derived from the feature name as specified in ECMA-323 and the message names are defined by the WSDL message element names. The following subsections describe the types of WSDL operations used in CSTA WSDL. 6.4.1 Request-response Operation Type A request-response operation type is used when a service provider receives a message and responds with a corresponding message. It is defined using one message, one message, and a message. - 4 -
The CSTA Answer Call service uses this type of operation. The operation for CSTA Answer Call is shown below. <operation name="csta-answer-call"> < message="tns:answercall"/> < message="tns:answercallresponse"/> < name="faultname" message=""/> The following notation is used to describe a WSDL request-response operation type: CSTA-Answer-Call tns:answercall tns:answercallresponse 6.4.2 One-way Operation Type A one-way operation type is used when a service provider receives a message and does not respond to the message. This type of WSDL operation is defined using one message. The CSTA-Route-Select service uses this type of operation. The operation for CSTA-Route- Select is shown below. <operation name="csta-route-select"> < message="tns:routeselect"/> The following notation is used to describe a WSDL one-way operation type: CSTA-Route-Select tns:routeselect WSDL 1.1 does not specify a message with a one-way operation type, however ECMA-269 specifies that a negative acknowledgement can be sent for certain services that do not specify a positive acknowledgement. Therefore a separate WSDL operation is specified in this Standard that provides a negative acknowledgement. It is not required to send a negative acknowledgement in these cases. <operation name="csta-fault-one-way"> < message=""/> 6.4.3 Solicit-response Operation Type A solicit-response operation type is used when a service provider sends a message and receives a corresponding response to the message. It is defined using one message, one message, and a message. The CSTA Call Detail Record Report service uses this type of operation. The operation is shown below. <operation name="csta-cdr-report"> < message="tns:cdrreport"/> < message="tns:cdrreportresponse"/> < name="faultname" message=""/> - 5 -
The following notation is used to describe a WSDL solicit-response operation type: CSTA-CDR-Report tns:cdrreport tns:cdrreportresponse 6.4.4 Notification Operation Type A notification operation type is used when a service provider sends a message and does not receive a response to the message. This type of WSDL operation is defined using one message. The CSTA-Delivered-Event uses this type of operation. The operation for the CSTA-Delivered- Event is shown below. <operation name="csta-delivered-event"> < message="tns:deliveredevent"/> The following notation is used to describe a WSDL notification operation type: CSTA-Delivered-event tns:deliveredevent The CSTA-Route-Request service also uses this type of operation. The operation for CSTA- Route-Request is shown below. <operation name="csta-route-request"> < message="tns:routerequest"/> The following notation is another example of a WSDL notification operation type: CSTA-Route-Request tns:routerequest WSDL 1.1 does not specify a message with a notification operation type, however ECMA-269 specifies that a negative acknowledgement can be sent for certain services that do not specify a positive acknowledgement. Therefore a separate WSDL operation is specified in this Standard that provides a negative acknowledgement. It is not required to send a negative acknowledgement in these cases. <operation name="csta-fault-notification"> < message=""/> 6.4.5 Summary of CSTA Request/Response & Event Models and WSDL Operation Types The following list shows how the CSTA request/response models and events are represented with WSDL operation types: CSTA Services initiated by a CSTA Service Requester o o With positive ack. uses WSDL Request-response operation type. With no positive ack uses WSDL One-way operation type. CSTA Event Reports sent by a CSTA Service Provider o Uses WSDL Notification operation type. - 6 -
CSTA Services initiated by a CSTA Service Provider o o With positive ack. Uses WSDL Solicit-response operation type. With no positive ack Uses WSDL Notification operation type. WSDL 1.1 does not allow a element on One-way and Notification operation types. 6.5 Port Types A WSDL port type is a collection of WSDL operations. The WSDL port type will be used to bind to one or more specific protocols and transport data formats. Each port type specified in this Standard (beginning in Clause 23) corresponds to a profile specified in 2.1.3 of ECMA-269. A Service Provider may support other operations in addition to the operations specified in the port types. 6.5.1 Example An example port type with three CSTA WSDL operations follows: <porttype name="sampleporttype"> <operation name="csta-answer-call"> < message="tns:answercall"/> < message="tns:answercallresponse"/> < name="faultname" message=""/> <operation name="csta-clear-connection"> < message="tns:clearconnection"/> < message="tns:clearconnectionresponse"/> < name="faultname" message=""/> <operation name="csta-make-call"> < message="tns:makecall"/> < message="tns:makecallresponse"/> < name="faultname" message=""/> </porttype> - 7 -
The following notation is used to describe a porttype: porttype sampleporttype operations CSTA-Answer-Call tns:answercall tns:answercallresponse CSTA-Clear-Connection tns:clearconnection tns:clearconnectionresponse CSTA-Make-Call tns:makecall tns:makecallresponse <porttype name="sampleporttype"> <operation name="csta-answer-call"> < message="tns:answercall"/> < message="tns:answercallresponse"/> < name="faultname" message=""/> <operation name="csta-clear-connection"> < message="tns:clearconnection"/> < message="tns:clearconnectionresponse"/> < name="faultname" message=""/> <operation name="csta-make-call"> < message="tns:makecall"/> < message="tns:makecallresponse"/> < name="faultname" message=""/> </porttype> 6.6 Bindings A binding associates one concrete protocol and transport data format specification to a port type. This Standard allows any type of binding and binding extensions for the CSTA WSDL port types specified in this Standard. NOTE Although the base WSDL 1.1 specification supports all of the WSDL operation types defined in 6.3, WSDL 1.1 only defines bindings for Request-response and One-way operation types. Binding extensions are necessary to support the CSTA WSDL Solicit-response and Notification operation types defined in this Standard. An example of a SOAP 1.1/HTTP binding is provided in Annex A. 6.7 Port A port is a single endpoint defined as a combination of a binding and a network address. - 8 -
An example of how a port is used in a WSDL document is provided in Annex A. 6.8 Service A service is a collection of related ports. An example of how a service is used in a WSDL document is provided in Annex A. - 9 -
7 Capability Exchange Services Messages and Operations This Clause specifies the WSDL messages and operations for the CSTA capability exchange services and messages. 7.1 Messages message getcstafeatures element csta:getcstafeatures <message name="getcstafeatures"> <part name="" element="csta:getcstafeatures"/> message getcstafeaturesresponse element csta:getcstafeaturesresponse <message name="getcstafeaturesresponse"> <part name="" element="csta:getcstafeaturesresponse"/> message getlogicaldeviceinformation element csta:getlogicaldeviceinformation <message name="getlogicaldeviceinformation"> <part name="" element="csta:getlogicaldeviceinformation"/> message getlogicaldeviceinformationresponse element csta:getlogicaldeviceinformationresponse <message name="getlogicaldeviceinformationresponse"> <part name="" element="csta:getlogicaldeviceinformationresponse"/> - 10 -
message getphysicaldeviceinformation element csta:getphysicaldeviceinformation <message name="getphysicaldeviceinformation"> <part name="" element="csta:getphysicaldeviceinformation"/> message getphysicaldeviceinformationresponse element csta:getphysicaldeviceinformationresponse <message name="getphysicaldeviceinformationresponse"> <part name="" element="csta:getphysicaldeviceinformationresponse"/> message getswitchingfunctioncaps element csta:getswitchingfunctioncaps <message name="getswitchingfunctioncaps"> <part name="" element="csta:getswitchingfunctioncaps"/> message getswitchingfunctioncapsresponse element csta:getswitchingfunctioncapsresponse <message name="getswitchingfunctioncapsresponse"> <part name="" element="csta:getswitchingfunctioncapsresponse"/> message getswitchingfunctiondevices element csta:getswitchingfunctiondevices <message name="getswitchingfunctiondevices"> <part name="" element="csta:getswitchingfunctiondevices"/> - 11 -
message getswitchingfunctiondevicesresponse element csta:getswitchingfunctiondevicesresponse <message name="getswitchingfunctiondevicesresponse"> <part name="" element="csta:getswitchingfunctiondevicesresponse"/> message switchingfunctiondevices element csta:switchingfunctiondevices <message name="switchingfunctiondevices"> <part name="" element="csta:switchingfunctiondevices"/> - 12 -
7.2 Operations operations CSTA-Get-CSTA-Features tns:getcstafeatures tns:getcstafeaturesresponse CSTA-Get-Logical-Device-Information tns:getlogicaldeviceinformation tns:getlogicaldeviceinformationresponse CSTA-Get-Physical-Device-Information tns:getphysicaldeviceinformation tns:getphysicaldeviceinformationresponse CSTA-Get-Switching-Function-Capabilities tns:getswitchingfunctioncaps tns:getswitchingfunctioncapsresponse CSTA-Get-Switching-Function-Devices tns:getswitchingfunctiondevices tns:getswitchingfunctiondevicesresponse CSTA-Switching-Function-Devices tns:switchingfunctiondevices <operation name="csta-get-csta-features"> < message="tns:getcstafeatures"/> < message="tns:getcstafeaturesresponse"/> < name="faultname" message=""/> <operation name="csta-get-logical-device-information"> < message="tns:getlogicaldeviceinformation"/> < message="tns:getlogicaldeviceinformationresponse"/> < name="faultname" message=""/> <operation name="csta-get-physical-device-information"> < message="tns:getphysicaldeviceinformation"/> < message="tns:getphysicaldeviceinformationresponse"/> < name="faultname" message=""/> <operation name="csta-get-switching-function-capabilities"> < message="tns:getswitchingfunctioncaps"/> < message="tns:getswitchingfunctioncapsresponse"/> - 13 -
< name="faultname" message=""/> <operation name="csta-get-switching-function-devices"> < message="tns:getswitchingfunctiondevices"/> < message="tns:getswitchingfunctiondevicesresponse"/> < name="faultname" message=""/> <operation name="csta-switching-function-devices"> < message="tns:switchingfunctiondevices"/> - 14 -
8 System Services Messages and Operations This Clause specifies the WSDL messages and operations for the CSTA system services. 8.1 Messages message changesystemstatfilter element csta:changesysstatfilter <message name="changesystemstatfilter"> <part name="" element="csta:changesysstatfilter"/> message changesysstatfilterresponse element csta:changesysstatfilterresponse <message name="changesysstatfilterresponse"> <part name="" element="csta:changesysstatfilterresponse"/> message systemregister element csta:systemregister <message name="systemregister"> <part name="" element="csta:systemregister"/> message systemregisterresponse element csta:systemregisterresponse <message name="systemregisterresponse"> <part name="" element="csta:systemregisterresponse"/> - 15 -
message systemregisterabort element csta:systemregisterabort <message name="systemregisterabort"> <part name="" element="csta:systemregisterabort"/> message systemregistercancel element csta:systemregistercancel <message name="systemregistercancel"> <part name="" element="csta:systemregistercancel"/> message systemregistercancelresponse element csta:systemregistercancelresponse <message name="systemregistercancelresponse"> <part name="" element="csta:systemregistercancelresponse"/> message requestsystemstatus element csta:requestsystemstatus <message name="requestsystemstatus"> <part name="" element="csta:requestsystemstatus"/> message requestsystemstatusresponse element csta:requestsystemstatusresponse <message name="requestsystemstatusresponse"> <part name="" element="csta:requestsystemstatusresponse"/> - 16 -
message systemstatus element csta:systemstatus <message name="systemstatus"> <part name="" element="csta:systemstatus"/> message systemstatusresponse element csta:systemstatusresponse <message name="systemstatusresponse"> <part name="" element="csta:systemstatusresponse"/> message swfunctioncapschanged element csta:swfunctioncapschanged <message name="swfunctioncapschanged"> <part name="" element="csta:swfunctioncapschanged"/> message swfunctioncapschangedresponse element csta:swfunctioncapschangedresponse <message name="swfunctioncapschangedresponse"> <part name="" element="csta:swfunctioncapschangedresponse"/> message swfunctiondeviceschanged element csta:swfunctiondeviceschanged <message name="swfunctiondeviceschanged"> <part name="" element="csta:swfunctiondeviceschanged"/> - 17 -
message swfunctiondeviceschangedresponse element csta:swfunctiondeviceschangedresponse <message name="swfunctiondeviceschangedresponse"> <part name="" element="csta:swfunctiondeviceschangedresponse"/> - 18 -
8.2 Operations operations CSTA-Change-System-Status-Filter tns:changesystemstatfilter tns:changesysstatfilterresponse CSTA-System-Register tns:systemregister tns:systemregisterresponse CSTA-System-Register-Abort tns:systemregisterabort CSTA-System-Register-Cancel tns:systemregistercancel tns:systemregistercancelresponse CSTA-Request-System-Status-as- tns:requestsystemstatus tns:requestsystemstatusresponse CSTA-Request-System-Status-as- tns:requestsystemstatus tns:requestsystemstatusresponse CSTA-System-Status-as- tns:systemstatus tns:systemstatusresponse CSTA-System-Status-as- tns:systemstatus tns:systemstatusresponse CSTA-SF-Capabilities-Changed tns:swfunctioncapschanged tns:swfunctioncapschangedresponse - 19 -
CSTA-SF-Devices-Changed tns:swfunctiondeviceschanged tns:swfunctiondeviceschangedresponse <operation name="csta-change-system-status-filter"> < message="tns:changesystemstatfilter"/> < message="tns:changesysstatfilterresponse"/> < name="faultname" message=""/> <operation name="csta-system-register"> < message="tns:systemregister"/> < message="tns:systemregisterresponse"/> < name="faultname" message=""/> <operation name="csta-system-register-abort"> < message="tns:systemregisterabort"/> <operation name="csta-system-register-cancel"> < message="tns:systemregistercancel"/> < message="tns:systemregistercancelresponse"/> < name="faultname" message=""/> <operation name="csta-request-system-status-as-"> < message="tns:requestsystemstatus"/> < message="tns:requestsystemstatusresponse"/> < name="faultname" message=""/> <operation name="csta-request-system-status-as-"> < message="tns:requestsystemstatus"/> < message="tns:requestsystemstatusresponse"/> < name="faultname" message=""/> <operation name="csta-system-status-as-"> < message="tns:systemstatus"/> < message="tns:systemstatusresponse"/> < name="faultname" message=""/> <operation name="csta-system-status-as-"> < message="tns:systemstatus"/> < message="tns:systemstatusresponse"/> < name="faultname" message=""/> <operation name="csta-sf-capabilities-changed"> < message="tns:swfunctioncapschanged"/> - 20 -
< message="tns:swfunctioncapschangedresponse"/> < name="faultname" message=""/> <operation name="csta-sf-devices-changed"> < message="tns:swfunctiondeviceschanged"/> < message="tns:swfunctiondeviceschangedresponse"/> < name="faultname" message=""/> - 21 -
9 Monitoring Services Messages and Operations This Clause specifies the WSDL messages and operations for the CSTA monitoring services. 9.1 Messages message changemonitorfilter element csta:changemonitorfilter <message name="changemonitorfilter"> <part name="" element="csta:changemonitorfilter"/> message changemonitorfilterresponse element csta:changemonitorfilterresponse <message name="changemonitorfilterresponse"> <part name="" element="csta:changemonitorfilterresponse"/> message monitorstart element csta:monitorstart <message name="monitorstart"> <part name="" element="csta:monitorstart"/> message monitorstartresponse element csta:monitorstartresponse <message name="monitorstartresponse"> <part name="" element="csta:monitorstartresponse"/> - 22 -
message monitorstop element csta:monitorstop <message name="monitorstop"> <part name="" element="csta:monitorstop"/> message monitorstopresponse element csta:monitorstopresponse <message name="monitorstopresponse"> <part name="" element="csta:monitorstopresponse"/> - 23 -
9.2 Operations operations CSTA-Change-Monitor-Filter tns:changemonitorfilter tns:changemonitorfilterresponse CSTA-Monitor-Start tns:monitorstart tns:monitorstartresponse CSTA-Monitor-Stop-as- tns:monitorstop tns:monitorstopresponse CSTA-Monitor-Stop-as- tns:monitorstop tns:monitorstopresponse <operation name="csta-change-monitor-filter"> < message="tns:changemonitorfilter"/> < message="tns:changemonitorfilterresponse"/> < name="faultname" message=""/> <operation name="csta-monitor-start"> < message="tns:monitorstart"/> < message="tns:monitorstartresponse"/> < name="faultname" message=""/> <operation name="csta-monitor-stop-as-"> < message="tns:monitorstop"/> < message="tns:monitorstopresponse"/> < name="faultname" message=""/> <operation name="csta-monitor-stop-as-"> < message="tns:monitorstop"/> < message="tns:monitorstopresponse"/> < name="faultname" message=""/> - 24 -
10 Snapshot Services Messages and Operations This Clause specifies the WSDL messages and operations for the CSTA snapshot services. 10.1 Messages message snapshotcall element csta:snapshotcall <message name="snapshotcall"> <part name="" element="csta:snapshotcall"/> message snapshotcallresponse element csta:snapshotcallresponse <message name="snapshotcallresponse"> <part name="" element="csta:snapshotcallresponse"/> message snapshotdevice element csta:snapshotdevice <message name="snapshotdevice"> <part name="" element="csta:snapshotdevice"/> message snapshotdeviceresponse element csta:snapshotdeviceresponse <message name="snapshotdeviceresponse"> <part name="" element="csta:snapshotdeviceresponse"/> - 25 -
message snapshotcalldata element csta:snapshotcalldata <message name="snapshotcalldata"> <part name="" element="csta:snapshotcalldata"/> message snapshotdevicedata element csta:snapshotdevicedata <message name="snapshotdevicedata"> <part name="" element="csta:snapshotdevicedata"/> - 26 -
10.2 Operations operations CSTA-Snapshot-Call tns:snapshotcall tns:snapshotcallresponse CSTA-Snapshot-Device tns:snapshotdevice tns:snapshotdeviceresponse CSTA-Snapshot-Call-Data tns:snapshotcalldata CSTA-Snapshot-Device-Data tns:snapshotdevicedata <operation name="csta-snapshot-call"> < message="tns:snapshotcall"/> < message="tns:snapshotcallresponse"/> < name="faultname" message=""/> <operation name="csta-snapshot-device"> < message="tns:snapshotdevice"/> < message="tns:snapshotdeviceresponse"/> < name="faultname" message=""/> <operation name="csta-snapshot-call-data"> < message="tns:snapshotcalldata"/> <operation name="csta-snapshot-device-data"> < message="tns:snapshotdevicedata"/> - 27 -
11 Call Control Features Messages and Operations This Clause specifies the WSDL messages and operations for the CSTA call control features. 11.1 Messages message acceptcall element csta:acceptcall <message name="acceptcall"> <part name="" element="csta:acceptcall"/> message acceptcallresponse element csta:acceptcallresponse <message name="acceptcallresponse"> <part name="" element="csta:acceptcallresponse"/> message alternatecall element csta:alternatecall <message name="alternatecall"> <part name="" element="csta:alternatecall"/> message alternatecallresponse element csta:alternatecallresponse <message name="alternatecallresponse"> <part name="" element="csta:alternatecallresponse"/> - 28 -
message answercall element csta:answercall <message name="answercall"> <part name="" element="csta:answercall"/> message answercallresponse element csta:answercallresponse <message name="answercallresponse"> <part name="" element="csta:answercallresponse"/> message callback element csta:callback <message name="callback"> <part name="" element="csta:callback"/> message callbackresponse element csta:callbackresponse <message name="callbackresponse"> <part name="" element="csta:callbackresponse"/> message callbackmessage element csta:callbackmessage <message name="callbackmessage"> <part name="" element="csta:callbackmessage"/> - 29 -
message callbackmessageresponse element csta:callbackmessageresponse <message name="callbackmessageresponse"> <part name="" element="csta:callbackmessageresponse"/> message camponcall element csta:camponcall <message name="camponcall"> <part name="" element="csta:camponcall"/> message camponcallresponse element csta:camponcallresponse <message name="camponcallresponse"> <part name="" element="csta:camponcallresponse"/> message clearcall element csta:clearcall <message name="clearcall"> <part name="" element="csta:clearcall"/> message clearcallresponse element csta:clearcallresponse <message name="clearcallresponse"> <part name="" element="csta:clearcallresponse"/> - 30 -
message clearconnection element csta:clearconnection <message name="clearconnection"> <part name="" element="csta:clearconnection"/> message clearconnectionresponse element csta:clearconnectionresponse <message name="clearconnectionresponse"> <part name="" element="csta:clearconnectionresponse"/> message conferencecall element csta:conferencecall <message name="conferencecall"> <part name="" element="csta:conferencecall"/> message conferencecallresponse element csta:conferencecallresponse <message name="conferencecallresponse"> <part name="" element="csta:conferencecallresponse"/> message consultationcall element csta:consultationcall <message name="consultationcall"> <part name="" element="csta:consultationcall"/> - 31 -
message consultationcallresponse element csta:consultationcallresponse <message name="consultationcallresponse"> <part name="" element="csta:consultationcallresponse"/> message deflectcall element csta:deflectcall <message name="deflectcall"> <part name="" element="csta:deflectcall"/> message deflectcallresponse element csta:deflectcallresponse <message name="deflectcallresponse"> <part name="" element="csta:deflectcallresponse"/> message dialdigits element csta:dialdigits <message name="dialdigits"> <part name="" element="csta:dialdigits"/> message dialdigitsresponse element csta:dialdigitsresponse <message name="dialdigitsresponse"> <part name="" element="csta:dialdigitsresponse"/> - 32 -
message directedpickupcall element csta:directedpickupcall <message name="directedpickupcall"> <part name="" element="csta:directedpickupcall"/> message directedpickupcallresponse element csta:directedpickupcallresponse <message name="directedpickupcallresponse"> <part name="" element="csta:directedpickupcallresponse"/> message grouppickupcall element csta:grouppickupcall <message name="grouppickupcall"> <part name="" element="csta:grouppickupcall"/> message grouppickupcallresponse element csta:grouppickupcallresponse <message name="grouppickupcallresponse"> <part name="" element="csta:grouppickupcallresponse"/> message holdcall element csta:holdcall <message name="holdcall"> <part name="" element="csta:holdcall"/> - 33 -
message holdcallresponse element csta:holdcallresponse <message name="holdcallresponse"> <part name="" element="csta:holdcallresponse"/> message intrudecall element csta:intrudecall <message name="intrudecall"> <part name="" element="csta:intrudecall"/> message intrudecallresponse element csta:intrudecallresponse <message name="intrudecallresponse"> <part name="" element="csta:intrudecallresponse"/> message joincall element csta:joincall <message name="joincall"> <part name="" element="csta:joincall"/> message joincallresponse element csta:joincallresponse <message name="joincallresponse"> <part name="" element="csta:joincallresponse"/> - 34 -
message makecall element csta:makecall <message name="makecall"> <part name="" element="csta:makecall"/> message makecallresponse element csta:makecallresponse <message name="makecallresponse"> <part name="" element="csta:makecallresponse"/> message makepredictivecall element csta:makepredictivecall <message name="makepredictivecall"> <part name="" element="csta:makepredictivecall"/> message makepredictivecallresponse element csta:makepredictivecallresponse <message name="makepredictivecallresponse"> <part name="" element="csta:makepredictivecallresponse"/> message parkcall element csta:parkcall <message name="parkcall"> <part name="" element="csta:parkcall"/> - 35 -
message parkcallresponse element csta:parkcallresponse <message name="parkcallresponse"> <part name="" element="csta:parkcallresponse"/> message reconnectcall element csta:reconnectcall <message name="reconnectcall"> <part name="" element="csta:reconnectcall"/> message reconnectcallresponse element csta:reconnectcallresponse <message name="reconnectcallresponse"> <part name="" element="csta:reconnectcallresponse"/> message retrievecall element csta:retrievecall <message name="retrievecall"> <part name="" element="csta:retrievecall"/> message retrievecallresponse element csta:retrievecallresponse <message name="retrievecallresponse"> <part name="" element="csta:retrievecallresponse"/> - 36 -
message sendmessage element csta:sendmessage <message name="sendmessage"> <part name="" element="csta:sendmessage"/> message sendmessageresponse element csta:sendmessageresponse <message name="sendmessageresponse"> <part name="" element="csta:sendmessageresponse"/> message singlestepconferencecall element csta:singlestepconferencecall <message name="singlestepconferencecall"> <part name="" element="csta:singlestepconferencecall"/> message singlestepconferencecallresponse element csta:singlestepconferencecallresponse <message name="singlestepconferencecallresponse"> <part name="" element="csta:singlestepconferencecallresponse"/> message singlesteptransfercall element csta:singlesteptransfercall <message name="singlesteptransfercall"> <part name="" element="csta:singlesteptransfercall"/> - 37 -
message singlesteptransfercallresponse element csta:singlesteptransfercallresponse <message name="singlesteptransfercallresponse"> <part name="" element="csta:singlesteptransfercallresponse"/> message transfercall element csta:transfercall <message name="transfercall"> <part name="" element="csta:transfercall"/> message transfercallresponse element csta:transfercallresponse <message name="transfercallresponse"> <part name="" element="csta:transfercallresponse"/> message bridgedevent element csta:bridgedevent <message name="bridgedevent"> <part name="" element="csta:bridgedevent"/> message callclearedevent element csta:callclearedevent <message name="callclearedevent"> <part name="" element="csta:callclearedevent"/> - 38 -
message conferencedevent element csta:conferencedevent <message name="conferencedevent"> <part name="" element="csta:conferencedevent"/> message connectionclearedevent element csta:connectionclearedevent <message name="connectionclearedevent"> <part name="" element="csta:connectionclearedevent"/> message deliveredevent element csta:deliveredevent <message name="deliveredevent"> <part name="" element="csta:deliveredevent"/> message digitsdialedevent element csta:digitsdialedevent <message name="digitsdialedevent"> <part name="" element="csta:digitsdialedevent"/> message divertedevent element csta:divertedevent <message name="divertedevent"> <part name="" element="csta:divertedevent"/> - 39 -
message establishedevent element csta:establishedevent <message name="establishedevent"> <part name="" element="csta:establishedevent"/> message failedevent element csta:failedevent <message name="failedevent"> <part name="" element="csta:failedevent"/> message heldevent element csta:heldevent <message name="heldevent"> <part name="" element="csta:heldevent"/> message networkcapabilitieschangedevent element csta:networkcapabilitieschangedevent <message name="networkcapabilitieschangedevent"> <part name="" element="csta:networkcapabilitieschangedevent"/> message networkreachedevent element csta:networkreachedevent <message name="networkreachedevent"> <part name="" element="csta:networkreachedevent"/> - 40 -
message offeredevent element csta:offeredevent <message name="offeredevent"> <part name="" element="csta:offeredevent"/> message originatedevent element csta:originatedevent <message name="originatedevent"> <part name="" element="csta:originatedevent"/> message queuedevent element csta:queuedevent <message name="queuedevent"> <part name="" element="csta:queuedevent"/> message retrievedevent element csta:retrievedevent <message name="retrievedevent"> <part name="" element="csta:retrievedevent"/> message serviceinitiatedevent element csta:serviceinitiatedevent <message name="serviceinitiatedevent"> <part name="" element="csta:serviceinitiatedevent"/> - 41 -
message transferedevent element csta:transferedevent <message name="transferedevent"> <part name="" element="csta:transferedevent"/> - 42 -
11.2 Operations operations CSTA-Accept-Call tns:acceptcall tns:acceptcallresponse CSTA-Alternate-Call tns:alternatecall tns:alternatecallresponse CSTA-Answer-Call tns:answercall tns:answercallresponse CSTA-Call-Back-Call-Related tns:callback tns:callbackresponse CSTA-Call-Back-Message-Call-Related tns:callbackmessage tns:callbackmessageresponse CSTA-Camp-On-Call tns:camponcall tns:camponcallresponse CSTA-Clear-Call tns:clearcall tns:clearcallresponse CSTA-Clear-Connection tns:clearconnection tns:clearconnectionresponse CSTA-Conference-Call tns:conferencecall tns:conferencecallresponse - 43 -
CSTA-Consultation-Call tns:consultationcall tns:consultationcallresponse CSTA-Deflect-Call tns:deflectcall tns:deflectcallresponse CSTA-Dial-Digits-Call tns:dialdigits tns:dialdigitsresponse CSTA-Directed-Pickup-Call tns:directedpickupcall tns:directedpickupcallresponse CSTA-Group-Pickup-Call tns:grouppickupcall tns:grouppickupcallresponse CSTA-Hold-Call tns:holdcall tns:holdcallresponse CSTA-Intrude-Call tns:intrudecall tns:intrudecallresponse CSTA-Join-Call tns:joincall tns:joincallresponse CSTA-Make-Call tns:makecall tns:makecallresponse - 44 -
CSTA-Make-Predictive-Call tns:makepredictivecall tns:makepredictivecallresponse CSTA-Park-Call tns:parkcall tns:parkcallresponse CSTA-Reconnect-Call tns:reconnectcall tns:reconnectcallresponse CSTA-Retrieve-Call tns:retrievecall tns:retrievecallresponse CSTA-Send-Message tns:sendmessage tns:sendmessageresponse CSTA-Single-Step-Conference-Call tns:singlestepconferencecall tns:singlestepconferencecallresponse CSTA-Single-Step-Transfer-Call tns:singlesteptransfercall tns:singlesteptransfercallresponse CSTA-Transfer-Call tns:transfercall tns:transfercallresponse CSTA-Bridged-event tns:bridgedevent CSTA-Call-Cleared-event tns:callclearedevent - 45 -
CSTA-Conferenced-event tns:conferencedevent CSTA-Connection-Cleared-event tns:connectionclearedevent CSTA-Delivered-event tns:deliveredevent CSTA-Digits-Dialed-event tns:digitsdialedevent CSTA-Diverted-event tns:divertedevent CSTA-Established-event tns:establishedevent CSTA-Failed-event tns:failedevent CSTA-Held-event tns:heldevent CSTA-Network-Capabilities-Changed-event tns:networkcapabilitieschangedevent CSTA-Network-Reached-event tns:networkreachedevent CSTA-Offered-event tns:offeredevent CSTA-Originated-event tns:originatedevent CSTA-Queued-event tns:queuedevent CSTA-Retrieved-event tns:retrievedevent CSTA-Service-Initiated-event tns:serviceinitiatedevent - 46 -
CSTA-Transferred-event tns:transferedevent <operation name="csta-accept-call"> < message="tns:acceptcall"/> < message="tns:acceptcallresponse"/> < name="faultname" message=""/> <operation name="csta-alternate-call"> < message="tns:alternatecall"/> < message="tns:alternatecallresponse"/> < name="faultname" message=""/> <operation name="csta-answer-call"> < message="tns:answercall"/> < message="tns:answercallresponse"/> < name="faultname" message=""/> <operation name="csta-call-back-call-related"> < message="tns:callback"/> < message="tns:callbackresponse"/> < name="faultname" message=""/> <operation name="csta-call-back-message-call-related"> < message="tns:callbackmessage"/> < message="tns:callbackmessageresponse"/> < name="faultname" message=""/> <operation name="csta-camp-on-call"> < message="tns:camponcall"/> < message="tns:camponcallresponse"/> < name="faultname" message=""/> <operation name="csta-clear-call"> < message="tns:clearcall"/> < message="tns:clearcallresponse"/> < name="faultname" message=""/> <operation name="csta-clear-connection"> < message="tns:clearconnection"/> < message="tns:clearconnectionresponse"/> < name="faultname" message=""/> <operation name="csta-conference-call"> - 47 -
< message="tns:conferencecall"/> < message="tns:conferencecallresponse"/> < name="faultname" message=""/> <operation name="csta-consultation-call"> < message="tns:consultationcall"/> < message="tns:consultationcallresponse"/> < name="faultname" message=""/> <operation name="csta-deflect-call"> < message="tns:deflectcall"/> < message="tns:deflectcallresponse"/> < name="faultname" message=""/> <operation name="csta-dial-digits-call"> < message="tns:dialdigits"/> < message="tns:dialdigitsresponse"/> < name="faultname" message=""/> <operation name="csta-directed-pickup-call"> < message="tns:directedpickupcall"/> < message="tns:directedpickupcallresponse"/> < name="faultname" message=""/> <operation name="csta-group-pickup-call"> < message="tns:grouppickupcall"/> < message="tns:grouppickupcallresponse"/> < name="faultname" message=""/> <operation name="csta-hold-call"> < message="tns:holdcall"/> < message="tns:holdcallresponse"/> < name="faultname" message=""/> <operation name="csta-intrude-call"> < message="tns:intrudecall"/> < message="tns:intrudecallresponse"/> < name="faultname" message=""/> <operation name="csta-join-call"> < message="tns:joincall"/> < message="tns:joincallresponse"/> < name="faultname" message=""/> - 48 -
<operation name="csta-make-call"> < message="tns:makecall"/> < message="tns:makecallresponse"/> < name="faultname" message=""/> <operation name="csta-make-predictive-call"> < message="tns:makepredictivecall"/> < message="tns:makepredictivecallresponse"/> < name="faultname" message=""/> <operation name="csta-park-call"> < message="tns:parkcall"/> < message="tns:parkcallresponse"/> < name="faultname" message=""/> <operation name="csta-reconnect-call"> < message="tns:reconnectcall"/> < message="tns:reconnectcallresponse"/> < name="faultname" message=""/> <operation name="csta-retrieve-call"> < message="tns:retrievecall"/> < message="tns:retrievecallresponse"/> < name="faultname" message=""/> <operation name="csta-send-message"> < message="tns:sendmessage"/> < message="tns:sendmessageresponse"/> < name="faultname" message=""/> <operation name="csta-single-step-conference-call"> < message="tns:singlestepconferencecall"/> < message="tns:singlestepconferencecallresponse"/> < name="faultname" message=""/> <operation name="csta-single-step-transfer-call"> < message="tns:singlesteptransfercall"/> < message="tns:singlesteptransfercallresponse"/> < name="faultname" message=""/> <operation name="csta-transfer-call"> < message="tns:transfercall"/> < message="tns:transfercallresponse"/> < name="faultname" message=""/> - 49 -
<operation name="csta-bridged-event"> < message="tns:bridgedevent"/> <operation name="csta-call-cleared-event"> < message="tns:callclearedevent"/> <operation name="csta-conferenced-event"> < message="tns:conferencedevent"/> <operation name="csta-connection-cleared-event"> < message="tns:connectionclearedevent"/> <operation name="csta-delivered-event"> < message="tns:deliveredevent"/> <operation name="csta-digits-dialed-event"> < message="tns:digitsdialedevent"/> <operation name="csta-diverted-event"> < message="tns:divertedevent"/> <operation name="csta-established-event"> < message="tns:establishedevent"/> <operation name="csta-failed-event"> < message="tns:failedevent"/> <operation name="csta-held-event"> < message="tns:heldevent"/> <operation name="csta-network-capabilities-changed-event"> < message="tns:networkcapabilitieschangedevent"/> <operation name="csta-network-reached-event"> < message="tns:networkreachedevent"/> <operation name="csta-offered-event"> < message="tns:offeredevent"/> <operation name="csta-originated-event"> < message="tns:originatedevent"/> <operation name="csta-queued-event"> - 50 -