logo itpoint.cz

Přehled kódů IV. část stavových hlášení - dobrá pomůcka při řešení problémů se spojením euroISDN telefonu

pokračování ...

Máte-li problém s např. s euroISDN telefonem, přinášíme Vám přehled kódů stavových hlášení, která se mohou objevovat na displeji přístroje. Tyto kódy nejsou podle našich zkušeností běžně dostupné, jejich znění přinášíme v originále - tedy v angličtině.

ISDN Cause Codes and Descriptions (127762-AW96)

Unlimited right to copy this document is granted to anyone as long as the document is copied in its entirety, including this title page. AHK & Associates provides sophisticated network access consulting, design, and project implementation services throughout the United States. Our consultants custom design integrated network access solutions utilizing ISDN and other digital technologies to create a heterogeneous network fabric for voice, data, and video in the enterprise network. We sell just the equipment for the self-sufficient telecom department, and provide no charge evaluations and design for equipment only customers.

Disclaimer: This information is available "as is" and no guarantee as to its accuracy or usefulness us implied. I have heard that some switch manufacturers do not report the same values for each code. I have not had a big problem here (that I know of, that is). These cause codes are from field experience in North America. If you have an addition or correction please send it me at ISDN Cause Code Update@ahk.com.

Cause No. 1 - Unallocated (unassigned) number [Q.850]

This cause indicates that the called party cannot be reached because, although the called party number is in a valid format, it is not currently allocated (assigned).

Cause No. 2 - No route to specified transit network (national use) [Q.850]

This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network that it does not recognize. The equipment sending this cause does not recognize the transit network either because the transit network does not exist or because that particular transit network, while it does exist, does not serve the equipment that is sending this cause.

Cause No. 3 - No route to destination [Q.850]

This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network dependent basis.

Cause No. 4 - send special information tone [Q.850]

This cause indicates that the called party cannot be reached for reasons that are of a long term nature and that the special information tone should be returned to the calling party.

Cause No. 5 - misdialed trunk prefix (national use) [Q.850]

This cause indicates the erroneous inclusion of a trunk prefix in the called party number. This number is to be stripped from the dialed number being sent to the network by the customer premises equipment.

Cause No. 6 - channel unacceptable [Q.850]

This cause indicates that the channel most recently identified is not acceptable to the sending entity for use in this call.

Cause No. 7 - call awarded, being delivered in an established channel [Q.850]

This cause indicates that the user has been awarded the incoming call, and that the incoming call is being connected to a channel already established to that user for similar calls (for example, packet-mode x.25 virtual calls).

Cause No. 8 - preemption [Q.850]

This cause indicates the call is being preempted.

Cause No. 9 - preemption - circuit reserved for reuse [Q.850]

This cause indicates that the call is being preempted and the circuit is reserved for reuse by the preempting exchange.

Cause No. 16 - normal call clearing [Q.850]

This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network.

Cause No. 17 - user busy [Q.850]

This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determined user busy it is noted that the user equipment is compatible with the call.

Cause No. 18 - no user responding [Q.850]

This cause is used when a called party does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated.

Cause No. 19 - no answer from user (user alerted) [Q.850]

This cause is used when the called party has been alerted but does not respond with a connect indication within a prescribed period of time.

Note: This cause is not necessarily generated by Q.931 procedures but may be generated by internal network timers.

Cause No. 20 - subscriber absent [Q.850]

This cause value is used when a mobile station has logged off, radio contact is not obtained with a mobile station or if a personal telecommunication user is temporarily not addressable at any user-network interface.

Cause No. 21 - call rejected [Q.850]

This cause indicates that the equipment sending this cause does not want to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible. This cause may also be generated by the network, indicating that the call was cleared due to a supplementaryservice constraint. The diagnostic field may contain additional information about the supplementary service and reason for rejection.

Cause No. 22 - number changed [Q.850]

This cause is returned to a calling party when the called party number indicated by the calling party is no longer assigned, the new called party number may optionally be included in the diagnostic field. If a network does not support this cause, cause no: 1, unallocated (unassigned) number shall be used.

Cause No. 26 - nonselected user clearing [Q.850]

This cause indicates that the user has not been awarded the incoming call.

Cause No. 27 - destination out of order [Q.850]

This cause indicates that the destination indicated by the user cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signal message was unable to be delivered to the remote party; for example, a physical layer or data link layer failure at the remote party, or user equipment off-line.

Cause No. 28 - invalid number format (address incomplete) [Q.850]

This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete.

Cause No. 29 - facilities rejected [Q.850]

This cause is returned when a supplementary service requested by the user cannot be provided by the network.

Cause No. 30 - response to STATUS INQUIRY [Q.850]

This cause is included in the STATUS message when the reason for generating the STATUS message was the prior receipt of a STATUS INQUIRY.

Cause No. 31 - normal, unspecified [Q.850]

This cause is used to report a normal event only when no other cause in the normal class applies.

Cause No. 34 - no circuit/channel available [Q.850]

This cause indicates that there is no appropriate circuit/channel presently available to handle the call.

Cause No. 35 - Call Queued [Q.850]

Cause No. 38 - network out of order [Q.850]

This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time, for example, immediately reattempting the call is not likely to be successful.

Cause No. 39 - permanent frame mode connection out-of-service [Q.850]

This cause is included in a STATUS message to indicate that a permanently established frame mode connection is out-of-service (for example, due to equipment or section failure) [see Annex A/Q.933].

Cause No. 40 - permanent frame mode connection operational [Q.850]

This cause is included in a STATUS message to indicate that a permanently established frame mode connection is operational and capable of carrying user information. [see Annex A/Q.933]

Cause No. 41 - temporary failure [Q.850]

This cause indicates that the network is not functioning correctly and that the condition is no likely to last a long period of time; for example, the user may want to try another call attempt almost immediately.

Cause No. 42 - switching equipment congestion [Q.850]

This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.

Cause No. 43 - access information discarded [Q.850]

This cause indicates that the network could not deliver access information to the remote user as requested, that is, user-to-user information, low layer compatibility, high layer compatibility or subaddress as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic.

Cause No. 44 - requested circuit/channel not available [Q.850]

This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.

Cause No. 46 - precedence call blocked [Q.850]

This cause indicates that there are no preemptable circuits or that the called user is busy with a call of equal or higher preemptable level.

Cause No. 47 - resource unavailable, unspecified [Q.850]

This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.

Cause No. 49 - Quality of Service not available [Q.850]

This cause is used to report that the requested Quality of Service, as defined in Recommendation X.213, cannot be provided (for example, throughput of transit delay cannot be supported).

Článek ze dne 17. ledna 2001 - středa

Acronis True Image 2019