1、 Access to Additional Content for ECMA-285 4thEdition, Dated: December 2011 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the Copyri
2、ght holder of this document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. ECMA-285 Extra Files Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer for implementations of this standard
3、its edition shall be declared as the protocol version in the PICS. 2.1 Static Requirements To conform to this Standard, a system shall support the transfer syntax (derived from the encoding rules specified in ITU-T X.690) named joint-iso-ccitt asn1(1) basic-encoding(1) ; CSTA APDUs shall be interpre
4、ted according to ITU-T X.680. 2.2 Dynamic Requirements To conform to this Standard, a system shall: a. follow the procedures as specified in this Standard, and ECMA-269, relevant to each CSTA operation that the system claims to implement; and b. satisfy the definitions, as specified in ECMA-269, rel
5、evant to each CSTA service that the system claims to implement. 2.3 PICS Requirement To conform to this Standard, the following shall be stated by the implementer when defining a PICS corresponding to an application or implementation: a. which CSTA operations, as defined in ECMA-269, are supported b
6、y the system for the particular implementation; and b. which optional parameters are supported by the PDUs belonging to the supported operations. A PICS proforma is given in Annex A of this Standard. 2 Ecma International 20113 Normative References The following referenced documents are indispensable
7、 for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ECMA-269, Services for Computer Supported Telecommunications Applications (CSTA), Phase III, 9thEditi
8、on (December 2011) ECMA TR/72, Glossary of Definitions and Terminology for Computer Supported Telecommunications Applications (CSTA) Phase III, 3rdEdition (June 2000) ISO/IEC 8649:1996, Information technology - Open Systems Interconnection Service definition for the Association Control Service Eleme
9、nt (this corresponds to ITU-T Rec. X.217 1995) ISO/IEC 8650-1:1996, Information technology - Open Systems Interconnection - Connection-orientedprotocol for the Association Control Service Element: Protocol specification (this corresponds to ITU-T Rec. X.227 4/95) ISO/IEC 9545:1994, Information techn
10、ology - Open Systems Interconnection Application Layer structure ISO/IEC 13712-1:1995, Information technology - Remote Operations: Concepts, model, and notation (this corresponds to ITU-T Rec. X.880, 1994) ISO/IEC 13712-2:1994, Information technology - Remote Operations: OSI realisations - Remote Op
11、erations Service Element (ROSE) service definition (this corresponds to ITU-T Rec. X.881,1994) ISO/IEC 13712-3:1994, Information technology - Remote Operations: OSI realisations - Remote Operations Service Element (ROSE) protocol specification (this corresponds to ITU-T Rec.X.882, 1994) ITU-T X.680,
12、 Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation ITU-T X.690, Information technology - ASN.1 encoding rules - Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) ITU-T X.694, ASN.1 encoding
13、rules: Mapping W3C XML schema definitions into ASN.1 RFC 4119, A Presence-based GEOPRIV Location Object Format RFC 3966, The tel URI for Telephone Numbers ISO 3166-1, Country Codes 4 Definitions and Abbreviations CSTA-specific terminology is defined in ECMA TR/72. For the purposes of this Standard,
14、the following additional definitions, defined in other standards, shall apply: Remote Operations (as per ISO/IEC 13712-1) Application Association (as per ISO/IEC 8649) Application Context (as per ISO/IEC 8649) 5 CSTA Service Definition Model 5.1 CSTA Application Layer Structure The CSTA Application
15、Layer structure conforms to the model described in ISO/IEC 9545. Ecma International 2011 35.2 Remote Operations The services of CSTA are modeled as Remote Operations as described in ISO/IEC 13712-1. Typically, one entity requests that a particular operation be performed; the other entity attempts to
16、 perform the operation and responds to the requestor. Consequently the operation of the protocol is an elementary request/reply interaction, supported within the OSI Application Layer, and carried out within the context of an application association. The protocol specifications in ECMA-269 determine
17、 the class of the operation. For some of the CSTA services, the entity to which the request is sent generates a reply which can indicate success or failure. For these services, implementations shall use the operations Class 2, defined in ISO/IEC 13712-2 as: Asynchronous, reporting success or failure
18、 (result or error). For some of the CSTA services, the entity to which the request is sent generates a reply which can only indicate failure. For these services, implementations shall use the operations Class 3, defined in ISO/IEC 13712-2 as: Asynchronous, reporting failure (error) only, if any. For
19、 some of the CSTA services, particularly the ongoing reporting of events, no reply is generated. For these services, implementations shall use the operations Class 5, defined in ISO/IEC 13712-2 as: Asynchronous, outcome not reported. Implementations shall correlate the single response, denoting succ
20、ess or failure, with the originating request by using the mechanisms within the ROSE protocol. 5.3 The CSTA Service Response CSTA employs a generic response mechanism which is, in principle, decoupled from the specifics of the switching activity. The following points describe the operation of the CS
21、TA service response: a. Specific services may have an unconfirmed mode where responses to correct requests are not returned. b. The server shall check the correctness of the request (e.g. syntactical checks) before issuing the response. Incorrect requests shall result in an error response, even in t
22、he unconfirmed mode. 5.4 Cross Referencing of Event Reports A computer application process may need to cross reference a CSTAEventReport to one of the following: a. a CSTA Object ID (Call ID or Device ID), b. an earlier Monitor request; or c. one of many Monitor requests (pertaining to the same CSTA
23、 Object). For the above scenarios the necessary cross referencing function may be fulfilled by use of the parameter “MonitorCrossRefID”. The content of MonitorCrossRefID depends upon the context and it may be one of the following: Call ID, Device ID or another independently switch managed static ide
24、ntifier. The independent identifier may have a unique correlation to either: one device, one call, or one monitor request. 4 Ecma International 2011The switching system limit on the number of monitor requests on one CSTA Object (Call or Device) is an implementation option. This Standard does not sti
25、pulate how many monitor requests on one object are to be supported by the switch. If using Static Device or Call identifiers the limit can only be one. 5.5 Handling of Private Data If an entity receives the parameter CSTAPrivateData, and it can not recognize the information contained, the parameter
26、shall be discarded, and the rest of the message shall be processed. 6 Interconnection service boundary The APDUs in this Standard are exchanged in the context of an association and by using the Remote Operations protocol defined in ISO/IEC 13712-3, which assumes that certain services are provided by
27、 the underlying layers. 7 Security The authentication mechanism of ACSE may be used. 8 Association Management The APDUs in this Standard are exchanged in the context of an application association. This application association can be either: an implicit association achieved via off-line agreement; or
28、 a dynamically negotiated association realized through the use of ACSE. 8.1 Implicit association An a-priori agreement exists between switching and computing functions: the application context is implicit, dynamic negotiation is not possible. 8.2 Dynamic association management using ACSE ACSE requir
29、es the use of an application context Name (as defined by ISO 8649). This is an object id that uniquely identifies CSTA independently of the different versions. The CSTA protocol version information is carried within the User Information field of the A-ASSOCIATE request and response PDUs. An applicat
30、ion context is established (using ACSE) as follows: the system generating the A-ASSOCIATE request includes the CSTA application context name and a list of all protocol versions that it is prepared to offer in the User Information field; on receipt of the A-ASSOCIATE request, the receiving system sel
31、ects the protocol version to be used by identifying the highest version that is common to both systems; the protocol version selected is conveyed to the requestor in the User Information field of the A-ASSOCIATE response. Ecma International 2011 5In addition to negotiating the protocol version, it i
32、s necessary for the requesting and responding systems to specify the CSTA services that they support. As with the protocol version information, this is also achieved by carrying additional information in the User Information field of the A-ASSOCIATE request and response PDUs. The application associa
33、tion requestor shall: list the services required from the serving application; list the services it can supply. The responder shall include similar information for the responding application. At this point the association requestor will either accept or reject the association. 8.2.1 Encoding of appl
34、ication context name CSTA-application-context-name iso( 1) identified-organization( 3) icd-ecma( 12) standard( 0) csta( 218) - Common to all CSTA protocol versions 8.2.2 Encoding of application context information CSTA-application-context-information-csta3 iso( 1) identified-organization( 3) icd-ecm
35、a( 12) standard( 0) csta3( 285) application-context-information( 200) DEFINITIONS := BEGIN IMPORTS CSTAFunctionality FROM CSTA-application-context-information iso( 1) identified-organization( 3) icd-ecma( 12) standard( 0) csta2( 218) application-context-information( 200) ; ACSEUserInformationForCSTA
36、 := CHOICE oldDefinition OldACSEUserInformationForCSTA, newDefinition 0 IMPLICIT NewACSEUserInformationForCSTA OldACSEUserInformationForCSTA := SEQUENCE cSTAVersion CSTAVersion, cSTAFunctionsRequiredByApplication CSTAFunctionality, cSTAFunctionsThatCanBeSupplied CSTAFunctionality NewACSEUserInformat
37、ionForCSTA := SEQUENCE cSTAVersion CSTAVersion, - - Note that the following two parameters are defined in ECMA-218 (CSTA Phase II). - They are defined in the context of CSTA Phase II Services and Events for - backward compatibility considerations. - For CSTA Phase III (and later), implementations sh
38、ould use CSTA Capability Exchange - Services to determine the Services and Events supported by a switching function. - cSTAFunctionsRequiredByApplication 0 IMPLICIT CSTAFunctionality OPTIONAL, cSTAFunctionsThatCanBeSupplied 1 IMPLICIT CSTAFunctionality OPTIONAL, cSTAPrivateDataVersionList 2 IMPLICIT
39、 CSTAPrivateDataVersionList OPTIONAL CSTAPrivateDataVersionList := SEQUENCE OF INTEGER 6 Ecma International 2011CSTAVersion := BIT STRING versionOne ( 0), - ECMA-180 versionTwo ( 1), - ECMA-218 versionThree ( 2), - ECMA-285, 1st Edition versionFour ( 3), - ISO/IEC 18052 versionFive ( 4), - ECMA-285,
40、 2nd Edition versionSix ( 5), - ECMA-323 versionSeven ( 6), - ECMA-323, 2nd Edition versionEight ( 7), - ECMA-323, 3rd Edition versionNine ( 8), - ECMA-323, 4th Edition, Tag option versionTen ( 9), - ECMA-323, 4th Edition, short Tag option versionEleven (10), - ECMA-323, 4th Edition, dynamic transfo
41、rmation option versionTwelve (11), - ECMA-323, 5th Edition, Tag option versionThirteen (12), - ECMA-323, 5th Edition, short Tag option versionFourteen (13), - ECMA-323, 5th Edition, dynamic transformation option versionFifteen (14), - ECMA-285, 3rd Edition versionSixteen (15), - ECMA-323, 6th Editio
42、n, Tag option versionSeventeen (16), - ECMA-323, 6th Edition, short Tag option versionEighteen (17), - ECMA-323, 6th Edition, dynamic transformation option versionNineteen (18), - ECMA-285, 4th Edition versionTwenty (19), - Reserved for future use versionTwentyone (20), - Reserved for future use ver
43、sionTwentytwo (21), - Reserved for future use versionTwentythree (22), - Reserved for future use versionTwentyfour (23) - Reserved for future use CallControlServices := BIT STRING acceptCall ( 0), alternateCall ( 1), answerCall ( 2), callBack ( 3), callBackMessage ( 4), campOnCall ( 5), clearCall (
44、6), clearConnection ( 7), conferenceCall ( 8), consultationCall ( 9), deflectCall (10), dialDigits (11), directedPickupCall (12), groupPickupCall (13), holdCall (14), intrudeCall (15), joinCall (16), makeCall (17), makeConnection (25), makePredictiveCall (18), parkCall (19), reconnectCall (20), retr
45、ieveCall (21), sendMessage (26), singleStepConference (22), singleStepTransfer (23), transferCall (24) CallAssociatedServices := BIT STRING associateData ( 0), cancelTelephonyTones ( 1), changeConnectionInformation ( 5), generateDigits ( 2), Ecma International 2011 7generateTelephonyTones ( 3), send
46、UserInformation ( 4) MediaAttachmentServices := BIT STRING attachMediaService ( 0), detachMediaService ( 1) RouteingServices := BIT STRING routeRegister ( 0), routeRegisterCancel ( 1), routeRegisterAbort ( 2), reroute ( 3), routeEnd ( 4), routeReject ( 5), routeRequest ( 6), routeSelect ( 7), routeU
47、sed ( 8) VoiceUnitServices := BIT STRING activate (12), clear (13), concatenateMessage ( 0), deactivate (14), deleteMessage ( 1), playMessage ( 2), queryVoiceAttribute ( 3), recordMessage ( 4), reposition ( 5), resume ( 6), review ( 7), setVoiceAttribute ( 8), stop ( 9), suspend (10), synthesizeMess
48、age (11) LocationServices := BIT STRING getLocationInformation ( 0), setLocationInformation ( 1), locationTrackkingSessionResumed ( 2), locationTrackkingSessionSuspended ( 3), resumeLocationTrackingSession ( 4), locationInformationReport ( 5), startLocationTrackingSession ( 6), stopLocationTrackingSession ( 7), suspendLocationTrackingCapabilities ( 8), locationSessionInfo ( 9) CallControlEvents := BIT STRING bridged (15), callCleared ( 0), conferenced ( 1), connectionCleared ( 2), delivered ( 3), digitsDialed (14), diverted ( 4), e
