ECMA 218-1994 Protocol for Computer Supported Telecommunications Applications (CSTA) Phase II《计算机支持的电信应用(CSTA)第II阶段用协议 勘误表 1996年12月11日》.pdf

《ECMA 218-1994 Protocol for Computer Supported Telecommunications Applications (CSTA) Phase II《计算机支持的电信应用(CSTA)第II阶段用协议 勘误表 1996年12月11日》.pdf》由会员分享，可在线阅读，更多相关《ECMA 218-1994 Protocol for Computer Supported Telecommunications Applications (CSTA) Phase II《计算机支持的电信应用(CSTA)第II阶段用协议 勘误表 1996年12月11日》.pdf（228页珍藏版）》请在麦多课文档分享上搜索。

1、Standard ECMA-218December 1994Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chProtocol for ComputerSupported TelecommunicationsApplications (CSTA) Phase II.Standard ECMA-218December 1994Standardizi

2、ng Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chECMA-218.DOC - 12.01.99 08:47Protocol for ComputerSupported TelecommunicationsApplications (CSTA) Phase II.Brief HistoryThis Standard defines Phase II of the Pr

3、otocol for Computer Supported Telecommunications Applications (CSTA) for OSILayer 7 communication between a computing network and a telecommunications network. This Standard and its companionStandard ECMA-217 Services for Computer Supported Telecommunications Applications (CSTA) Phase II reflectagre

4、ements of ECMA member companies on Phase II of the standards for CSTA. Additional phases are anticipated. ThisStandard is based on the practical experience of ECMA member companies and represents a pragmatic and widely-basedconsensus.This Standard takes direction from Technical Report ECMA TR/52 Com

5、puter Supported Telecommunications Applications.Phase II of CSTA extends the previous Phase I standard in major theme directions as well as numerous details. Major areas ofadvancement include: the addition of explicit application context negotiation mechanisms; the addition of I/O services; the addi

6、tion of Special Resource Functions and, particularly, Voice Unit services; new and/or enhanced services and event reports for commonly used call control and monitoring applications; new servicesinclude Single Step Transfer, Single Step Conference, Call Park and Send DTMF Signals.The Phase II CSTA st

7、andards are not fully backwards compatible with the Phase I standards. Although backwardscompatibility is an important consideration and has been maintained whenever possible, the addition of new parameters incertain services and events, as well as the deletion of unused Phase I services and the add

8、ition of entirely new Phase II servicesand events, did not allow complete backwards compatibility.This Standard is dedicated to the memory of Terry Wuerfel.This ECMA Standard has been adopted by the ECMA General Assembly of December 1994.Usage Note regarding removing Year 2000 (Y2K) risksin the CSTA

9、 Phase I and Phase II Protocol Standards1 January 1999In both ITU-T Recs. X.208 (ASN.1 1988) and X.680 (ASN.1 1994), the definition of UTCTime, which is used in the CSTAPhase I and Phase II Protocol Standards (ECMA-180 and ECMA-218 respectively), is not Y2K-safe. The Year field (the YYfield) is repr

10、esented by a two-digit string, with no accompanying text mandating a Y2K-safe interpretation.For the CSTA Phase I and Phase II Protocol Standards, the following interpretation of the Year field is mandated : If the YY component is in the range 00-49, the century is determined to be “20“ (i.e. the ye

11、ar is 2000 to 2049); If the YY component is in the range 50-99, the century is determined to be “19“ (i.e. the year is 1950 to 1999).The risk has been removed in the CSTA Phase III Protocol Standard (ECMA-285) by replacing the references to “UTCTime“with references to “GeneralizedTime“, which is Y2K

12、-safe.List of corrected errata for ECMA-21811 December 1996SummaryFollowing is a summary of the errors detected and corrected in Standard ECMA-218, Protocol for Computer SupportedTelecommunications Applications (CSTA) Phase II. These results were obtained by using the OSS and SNACC ASN.1compilers.Al

13、l definitions Compilers complained about “icd-ecma(0012)” statements, therefore “00” has been removed from the definitionsCorrected:CSTA-application-context-information iso( 1) identified-organization( 3) icd-ecma( 12)standard( 0) csta2( 218) application-context-information( 200) Original:CSTA-appli

14、cation-context-information iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0) csta2( 218) application-context-information( 200) Multiple definitions Many of the definitions referred to “ECMA-180” instead of “ECMA-218”Corrected:CSTA-route-end-request iso( 1) identified-organization( 3) i

15、cd-ecma( 12)standard( 0) csta2( 218) route-end-request( 85) CSTACommonArguments, CSTAPrivateData FROM CSTA-extension-types iso( 1) identified-organization( 3) icd-ecma( 12)standard( 0) csta2( 218) extension-types( 129) ;CSTA-change-monitor-filter iso( 1) identified-organization( 3) icd-ecma( 12)stan

16、dard( 0) csta2( 218) change-monitor-filter( 102) CSTAObject FROM CSTA-switching-function-objects iso( 1) identified-organization( 3) icd-ecma( 12)standard( 0) csta2( 218) switching-function-objects( 122) CSTA-switching-function-objects iso( 1) identified-organization( 3) icd-ecma( 12)standard( 0) cs

17、ta2( 218)switching-function-objects( 122) Original:CSTA-route-end-request iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0) csta( 180) route-end-request( 85) CSTACommonArguments, CSTAPrivateData FROM CSTA-extension-types iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0) c

18、sta( 180) version1(1) extension-types( 129) ;CSTA-change-monitor-filter iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0) csta( 180) version1 ( 1) change-monitor-filter( 102) CSTAObject FROM CSTA-switching-function-objects iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0)

19、 csta( 180) switching-function-objects( 122) CSTA-switching-function-objects iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0) csta( 180) switching-function-objects( 122) Multiple Sections “BITSTRING” should be “BIT STRING”Corrected:CSTAVersion := BIT STRINGSwitchingFunctionServices :=

20、 BIT STRINGEventReportServices := BIT STRINGComputingFunctionServices := BIT STRINGBidirectionalServices := BIT STRINGStatusReportingServices := BIT STRINGInputOutputServices := BIT STRINGVoiceUnitServices := BIT STRINGDeviceClass := BIT STRINGOriginal:CSTAVersion := BITSTRINGSwitchingFunctionServic

21、es := BITSTRINGEventReportServices := BITSTRINGComputingFunctionServices := BITSTRINGBidirectionalServices := BITSTRINGStatusReportingServices := BITSTRINGInputOutputServices := BITSTRINGVoiceUnitServices := BITSTRINGDeviceClass := BITSTRINGSection 8.2.1, Encoding of application context information

22、Comma missing after reRouteRequestCorrected:ComputingFunctionServices := BIT STRINGrouteRequest (0),reRouteRequest (1),routeSelectRequest (2),routeUsedRequest (3),routeEndRequest (4) Original:ComputingFunctionServices := BIT STRINGrouteRequest (0),reRouteRequest (1)routeSelectRequest (2),routeUsedRe

23、quest (3),routeEndRequest (4) Section 9.3, Associate data AssociateDataArgument/Correlator Data misspelled Extra brace at end of SEQUENCE statement for AssociateDataArgumentCorrected:correlatorData 2 IMPLICIT CorrelatorData OPTIONAL,extensions CSTACommonArguments OPTIONALOriginal:correlatorData 2 IM

24、PLICIT CorellatorData OPTIONAL,extensions CSTACommonArguments OPTIONAL Section 9.8, Consultation call Missing comma after AuthCodeCorrected:AccountInfo, AuthCode, CorrelatorData, DeviceProfile FROM CSTA-device-feature-typesOriginal:AccountInfo, AuthCode CorrelatorData, DeviceProfile FROM CSTA-device

25、-feature-typesSection 9.17, Send DTMF tones Removed specific characters from IA5String type (or need to define a new type of just thesecharacters)Corrected:connectionToSendTones ConnectionID,charactersToSend IA5String,toneDuration 0 IMPLICIT INTEGER OPTIONAL,Original:connectionToSendTones Connection

26、ID,charactersToSend IA5String 0,1,2,3,4,5,6,7,8,9,*,#,A,B,C,D,toneDuration 0 IMPLICIT INTEGER OPTIONAL,Section 9.20, Single step transfer SingleStepTransResult should be SEQUENCECorrected:SingleStepTransResult :=SEQUENCEtransferedCall ConnectionID OPTIONAL,Original:SingleStepTransResult :=transfered

27、Call ConnectionID OPTIONAL,Section 10.1.10, Originated OriginatingDevice (SubjectDeviceID) missingCorrected:CalledDeviceID, CallingDeviceID, SubjectDeviceID FROM CSTA-device-identifiersOriginal:CalledDeviceID, CallingDeviceID FROM CSTA-device-identifiersSection 10.3.1, Agent busy Missing agentGroup

28、from AgentBusyEvent sequenceCorrected:Add to IMPORTS:AgentID, AgentGroup FROM CSTA-device-feature-typesAgentBusyEvent :=SEQUENCEagentDevice SubjectDeviceID,agentID 10 IMPLICIT AgentID OPTIONAL,agentGroup AgentGroup OPTIONAL,cause EventCause OPTIONALOriginal:AgentBusyEvent :=SEQUENCEagentDevice Subje

29、ctDeviceID,agentID AgentID OPTIONAL,cause EventCause OPTIONALSections 10.3.2 and 10.3.3, Agent logged on and Agent logged off Conflict between tag for agentID and DeviceID, dialingNumberCorrected:SEQUENCEagentDevice SubjectDeviceID,agentID 10 IMPLICIT AgentID OPTIONAL,agentGroup AgentGroup OPTIONAL,

30、Original:SEQUENCEagentDevice SubjectDeviceID,agentID 0 IMPLICIT AgentID OPTIONAL,agentGroup AgentGroup OPTIONAL,Section 10.3.6, Agent working after call Missing agentGroup from WorkingAfterCallEvent sequenceCorrected:Add to IMPORTS:AgentID, AgentGroup FROM CSTA-device-feature-typesWorkingAfterCallEv

31、ent :=SEQUENCEagentDevice SubjectDeviceID,agentID 10 IMPLICIT AgentID OPTIONAL,agentGroup AgentGroup OPTIONAL,cause EventCause OPTIONALOriginal:WorkingAfterCallEvent :=SEQUENCEagentDevice SubjectDeviceID,agentID AgentID OPTIONAL,cause EventCause OPTIONALSection 11.1, Route request DeviceProfile miss

32、ing from IMPORTSCorrected:CorrelatorData, DeviceClass, DeviceProfile, SelectValue, PriorityValue, RoutingCrossRefIDOriginal:CorrelatorData, DeviceClass, SelectValue, PriorityValue, RoutingCrossRefIDSection 12.1, Escape “CSTA-escape-service” should be “escape-service” in headerCorrected: iso( 1) iden

33、tified-organization( 3) icd-ecma( 12)standard( 0) csta2( 218) escape-service( 91) Original: iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0) csta2( 218) CSTA-escape-service( 91) Section 13.1, Monitor start CSTACommonArguments misspelledCorrected:extensions CSTACommonArguments OPTIONAL

34、Original:extensions CSTACommomArguments OPTIONALSection 14.1, Start data path “IA5STRING” should be “IA5String”, in argument and resultCorrected:terminationCharacter IA5String OPTIONAL,Original:terminationCharacter IA5STRING OPTIONAL,Section 14.2, Stop data path “RRORS” should be “ERRORS” in stopDat

35、aPathCorrected:ERRORS universalFailureOriginal:RRORS universalFailureSection 15.1, Concatenate Message Tag conflicted between CHOICE elements, because MessageIDList should be marked as IMPLICITCorrected:ConcatenateMessageArgument :=CHOICEmessagesToConcatenate 0IMPLICIT MessageIDList,SEQUENCEmessages

36、ToConcatenate MessageIDList,extensions CSTACommonArguments Original:ConcatenateMessageArgument :=CHOICEmessagesToConcatenate MessageIDList,SEQUENCEmessagesToConcatenate MessageIDList,extensions CSTACommonArguments Section 15.5, Record Message Missing IMPLICIT tags for SEQUENCE elements Extraneous br

37、ace at end of RecordMessageArgumentCorrected:RecordMessageArgument :=SEQUENCEcallToBeRecorded ConnectionID,samplingRate REAL OPTIONAL,encodingAlg 0IMPLICIT ENUMERATEDaDPCM6K (0),aDPCM8K (1),muLawPCM6K (2),aLawPCM6K (3) OPTIONAL,maxDuration 1IMPLICIT INTEGER OPTIONAL,termination 2IMPLICIT Terminating

38、Conditions OPTIONAL,extensions CSTACommonArguments OPTIONALOriginal:RecordMessageArgument :=SEQUENCEcallToBeRecorded ConnectionID,samplingRate REAL OPTIONAL,encodingAlg ENUMERATEDaDPCM6K (0),aDPCM8K (1),muLawPCM6K (2),aLawPCM6K (3) OPTIONAL,maxDuration INTEGER OPTIONAL,termination TerminatingConditi

39、ons OPTIONAL,extensions CSTACommonArguments OPTIONALSection 15.9, Set voice attribute OPERATION, ERROR imports missingCorrected:IMPORTSOPERATION, ERROR FROM Remote-Operations-Notation joint-iso-ccitt( 2) remote-operations( 4) notation( 0) - Data Types -Original:IMPORTS- Data Types - universalFailure

40、 import missingCorrected:universalFailure FROM CSTA-error-definition iso( 1) identified-organization( 3) icd-ecma( 12)standard( 0) csta2( 218) error-definition( 120) CSTACommonArguments import misingCorrected: iso( 1) identified-organization( 3) icd-ecma( 12)standard( 0) csta2( 218) device-feature-t

41、ypes( 127) CSTACommonArguments FROM CSTA-extension-types iso( 1) identified-organization( 3) icd-ecma( 12)standard( 0) csta2( 218) extension-types( 129) ;Original: iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0) csta2( 218) device-feature-types( 127) ; SetVoiceAttributeArgument missp

42、elled, comma after brace missingCorrected:SetVoiceAttributeArgument :=SEQUENCEconnection ConnectionID,attributeToSet CHOICEspeed 0 IMPLICIT Speed,speakerVolume 1 IMPLICIT INTEGER (0 100),recordingLevel 2 IMPLICIT INTEGER (0 100) ,message MessageID OPTIONAL,extensions CSTACommonArguments OPTIONALOrig

43、inal:SetVoiveAttributeArgument :=SEQUENCEconnection ConnectionID,attributeToSet CHOICEspeed 0 IMPLICIT Speed,speakerVolume 1 IMPLICIT INTEGER (0 100),recordingLevel 2 IMPLICIT INTEGER (0 100) message MessageID OPTIONAL,extensions CSTACommonArguments OPTIONAL setVoiceAttributeResult misspelledCorrect

44、ed:SetVoiceAttributeResult :=CHOICEOriginal:SetVoiveAttributeResult :=CHOICESection 15.10, Stop Opening brace missing in StopArgumentCorrected:StopArgument :=SEQUENCEconnection ConnectionID,Original:StopArgument :=SEQUENCEconnection ConnectionID,Section 15.11, Suspend Opening brace missing in Suspen

45、dArgumentCorrected:SuspendArgument :=SEQUENCEconnection ConnectionID,Original:SuspendArgument :=SEQUENCEconnection ConnectionID,Section 15.12, Synthesize message Opening brace missing in SynthesizeMessageArgumentCorrected:SynthesizeMessageArgument :=SEQUENCEtextToBeSynthesized OCTET STRING,Original:

46、SynthesizeMessageArgument :=SEQUENCEtextToBeSynthesized OCTET STRING,Section 18, CSTA data types Comment line not properly alignedCorrected:-The major parameters have been assigned distinct application tags to facilitate parsing. Thedata is defined in logical-groups in ascending order of application

47、 tag. Application tags used are:Original:-The major parameters have been assigned distinct application tags to facilitate parsing. Thedata is defined in logical -grops in ascending order of application tag. Application tags used are:Section 18.4, Connection states ConnectionIDList should be removed

48、from EXPORTS listCorrected:EXPORTSConnectionList, LocalConnectionState;Original:EXPORTSConnectionList, ConnectionIDList, LocalConnectionState;Section 18.5, Status reporting Extraneous semicolon at end of CSTAObject import statementCorrected: iso( 1) identified-organization( 3) icd-ecma( 12)standard( 0) csta2( 218) switching-function-objects( 122) Original: iso( 1) identified-organization( 3) icd-ecma( 0012)standard( 0) csta2( 218) switching-function-objects( 122) ;Section 18.6, Device and feature types and other parameters IOCrossRefIDList misspelled in