ATIS 1000650-1995 Integrated Services Digital Network (ISDN) C Usage of the Cause Information Element in Digital Subscriber Signaling System Number 1 (DSS1).pdf

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000650.1995(R2015) Integrated Services Digital Network (ISDN) Usage of the Cause Information Element in Digital Subscriber Signaling System Number 1 (DSS1) As a leading technology and solutions development organization, ATIS brings together th

2、e top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing su

3、pport, operations, and more. These priorities follow a fast-track development lifecycle from design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National

4、Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of

5、the Inter-American Telecommunication Commission (CITEL). For more information, visit . AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards develop

6、er. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all vie

7、ws and objections be considered, and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchas

8、ing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue

9、 an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be r

10、evised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the

11、American National Standards Institute. Notice of Disclaimer their existence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American Nationa

12、l Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institu

13、te. Requests for interpretations should be ad-dressed to the secretariat or sponsor whose name appears on the title pageof this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that act

14、ion be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.Published byAmerican National Standards Institute11 West 42nd Street, New

15、 York, New York 10036Copyright 1996 by Alliance for Telecommunications Industry SolutionsAll rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of the publisher.Printed in the United States of Amer

16、icainsert code hereiForeword ii1 Scope, purpose, and application.12 Normative references.13 Definitions .24 Cause information element.2Table1 Cause values.5Figures1 Format of cause information element 32 Coding of the diagnostics field for causes 57, 58, and 65 .9AnnexesA Examples of cause values an

17、d location for busy or congestion conditions.19B Bibliography 21ContentsPageiiForeword (This foreword is not part of American National Standard T1.650-1995.)The Digital Subscriber Signaling System Number 1 (DSS1) is a suite of pro-tocols that provides the means for users to invoke the full range of

18、servicesand capabilities available from the Integrated Services Digital Network(ISDN). The structure of DSS1 is consistent with the seven-layer modeldescribed in CCITT Recommendation I.320. The complete suite of Layer 3DSS1 protocols encompasses a set of several standards, one addressingits own aspe

19、ct of the suite. This standard specifies the usage, format andencoding of the cause information element, which is used throughout thesuite of Layer 3 DSS1 protocol standards. It also defines the meaning ofspecific cause values, and the usage of the location and diagnostic fields.Manufacturers of use

20、r and network equipment that use ISDN can applythis standard to the design and development of their products.This standard contains 2 informative annexes which are not consideredpart of this standard.This standard was developed by Working Group T1S1.1 of AccreditedStandards Committee T1 Telecommunic

21、ations.Suggestions for improvement of this standard will be welcome. Theseshould be sent to the Alliance for Telecommunications Industry Solutions,T1 Secretariat, 1200 G Street, NW, Suite 500, Washington DC 20005.This standard was processed and approved for submittal to ANSI byAccredited Standards C

22、ommittee on Telecommunications, T1. Committeeapproval of the standard does not imply that all committee members votedfor its approval. At the time it approved this standard, AccreditedStandards Committee T1 had the following members:A. K. Reilly, ChairmanG. H. Peterson, Vice-ChairmanO. J. Gusella, S

23、ecretaryWayne Zeuch, Senior EditorDavid Vander Meiden, Technical EditorOrganization Represented Name of RepresentativeEXCHANGE CARRIERSAmeritech Services, Inc. Laurence A. Young Stephen P. Murphy (Alt.)Bell Atlantic.John W. SeazholtzRoger Nucho (Alt.)Bellcore.James C. StaatsE. R. Hapeman (Alt.)BellS

24、outh Telecommunications, Inc. William J. McNamara, IIIMalcolm Threlkeld, Jr. (Alt.)Cincinnati Bell Telephone Thomas C. GrimesRenee W. Cagle (Alt.)GTE Telephone Operations .Bernard J. HarrisRichard L. Cochran (Alt.)National Telephone Cooperative Association .Joseph M. FlaniganNYNEX .James F. BaskinJi

25、m Papadopoulos (Alt.)Pacific Bell Sal R. TesoroPuerto Rico Telephone Company.Segundo RuizAlberto E. Morales (Alt.)Southwestern Bell Corporation C. C. BaileyJoseph Mendoza (Alt.)iiiSprint Local Telecommunications Division.Robert P. McCabeHarold L. Fuller (Alt.)US WESTJames L. EitelDarryl Debault (Alt

26、.)US Telephone Association (USTA) Dennis ByrnePaul Hart (Alt.)INEREXCHANGE CARRIERSAT e.g., a physical layer or data link layer failure atthe remote user, or user equipment off-line.4.4.2.22 Cause 28 “invalid number format (address incomplete)“This cause indicates that the called user cannot be reac

27、hed because the called party number is not avalid format or is not complete.4.4.2.23 Cause 29 “facility rejected“This cause is returned when a facility requested by the user can not be provided by the network.The Facility identification diagnostic may optionally be included with this cause.4.4.2.24

28、Cause 30 “response to STATUS ENQUIRY“This cause is included in the STATUS message when the reason for generating the STATUS messagewas the prior receipt of a STATUS ENQUIRY message.ANSI T1.650-1995144.4.2.25 Cause 31 “normal, unspecified“This cause is used to report a normal event only when no other

29、 cause in the normal class applies.4.4.3 Resource unavailable class4.4.3.1 Cause 34 “no circuit or channel available“This cause indicates that there is no appropriate circuit or channel presently available to handle the call.4.4.3.2 Cause 38 “network out of order“This cause indicates that the networ

30、k is not functioning correctly and that the condition is likely to last arelatively long period of time; e.g., immediately re-attempting the call is not likely to be successful.4.4.3.3 Cause 39 “permanent virtual connection out of service“This cause indicates that a permanent established virtual con

31、nection is out of service (e.g., due toequipment or section failure).4.4.3.4 Cause 40 “permanent virtual connection operational“This cause indicates that a permanent established virtual connection is operational and capable ofcarrying user information.4.4.3.5 Cause 41 “temporary failure“This cause i

32、ndicates that the network is not functioning correctly and that the condition is not likely to lasta long period of time; e.g., the user may wish to try another call attempt almost immediately.4.4.3.6 Cause 42 “switching equipment congestion“This cause indicates that the switching equipment generati

33、ng this cause is experiencing a period of hightraffic.4.4.3.7 Cause 43 “access information discarded“This cause indicates that the network could not deliver access information to the remote user asrequested; i.e., useruser information, low-layer compatibility, high-layer compatibility, or subaddress

34、.The information element identifier(s) that identify the particular type of access information discarded mayoptionally be included in the diagnostic field.4.4.3.8 Cause 44 “requested circuit or channel not available“This cause is returned when the circuit or channel indicated by the requesting entit

35、y cannot be providedby the other side of the interface.4.4.3.9 Cause 46 “precedence call blocked“This cause indicates that there are no preemptable circuits or that the called user is busy with a call ofequal or higher precedence level.ANSI T1.650-1995154.4.3.10 Cause 47 “resource unavailable, unspe

36、cified“This cause is used to report a resource unavailable event only when no other cause in the resourceunavailable class applies.4.4.4 Service or option not available class4.4.4.1 Cause 49 “quality of service unavailable“This cause is used to report that the requested quality of service, as define

37、d in CCITT RecommendationX.213, cannot be provided (e.g., throughput or transit delay cannot be supported).The Condition diagnostic may optionally be included with this cause.4.4.4.2 Cause 50 “requested facility not subscribed“This cause indicates that the user has requested a supplementary service

38、that is implemented by theequipment that generated this cause, but the user is not authorized to use.The Facility identification diagnostic may optionally be included with this cause.4.4.4.3 Cause 51 (national) “call type incompatible with service request“This cause indicates that a service request

39、has been received that is incompatible with the call type (e.g.,bearer service).4.4.4.4 Cause 53 (national) “service operation violated“This cause is used to report a service operation violation.The Denial condition diagnostic may optionally be included with this cause.4.4.4.5 Cause 57 “bearer capab

40、ility not authorized“This cause indicates that the user has requested a bearer capability that is implemented by theequipment that generated this cause but the user is not authorized to use.The Attribute identity diagnostic may optionally be included with this cause.4.4.4.6 Cause 58 “bearer capabili

41、ty not presently available“This cause indicates that the user has requested a bearer capability that is implemented by theequipment that generated this cause but that is not available at this time.The Attribute identity diagnostic may optionally be included with this cause.4.4.4.7 Cause 63 “service

42、or option not available, unspecified“This cause is used to report a service or option not available event only when no other cause in theservice or option not available class applies.ANSI T1.650-1995164.4.5 Service or option not implemented class4.4.5.1 Cause 65 “bearer capability not implemented“Th

43、is cause indicates that the equipment sending this cause does not support the bearer capabilityrequested.The Attribute identity diagnostic may optionally be included with this cause.4.4.5.2 Cause 66 “channel type not implemented“This cause indicates that the equipment sending this cause does not sup

44、port the channel type requested.The Channel type diagnostic may optionally be included with this cause.4.4.5.3 Cause 69 “requested facility not implemented“This cause indicates that the equipment sending this cause does not support the requestedsupplementary service.The Facility identification diagn

45、ostic may optionally be included with this cause.4.4.5.4 Cause 70 “only restricted digital information bearer capability is available“This cause indicates that equipment has requested an unrestricted bearer service but that the equipmentsending this cause only supports the restricted version of the

46、requested bearer capability.4.4.5.5 Cause 79 “service or option not implemented, unspecified“This cause is used to report a service or option not implemented event only when no other cause in theservice or option not implemented class applies.4.4.6 Invalid message (e.g., parameter out of range) clas

47、s4.4.6.1 Cause 81 “invalid call reference value“This cause indicates that the equipment sending this cause has received a message with a call referencethat is not currently in use on the usernetwork interface.4.4.6.2 Cause 82 “identified channel does not exist“This cause indicates that the equipment

48、 sending this cause has received a request to use a channel notactivated on the interface for a call. For example, if a user has subscribed to those channels on a primaryrate interface numbered from 1 to 12 and the user equipment or the network attempts to use channels 13through 23, this cause is ge

49、nerated.The Channel type diagnostic may optionally be included with this cause.4.4.6.3 Cause 88 “incompatible destination“This cause indicates that the equipment sending this cause has received a request to establish a call thathas low layer compatibility, high layer compatibility, or other compatibility attributes (e.g., data rate) thatcannot be accommodated.The Incompatible parameter diagnostic may optionally be included with this cause.ANSI T1.650-1995174.4.6.4 Cause 91 “invalid transit network selection“This cause indicates that a transit network identification was received th