23487285-isdn-cause-codes.pdf

8/14/2019 23487285-ISDN-Cause-Codes.pdf

1/7

ISDN Cause Codes

Cause No. 0

This is usually given by the router when none of the other codes apply. This cause usually

occurs in the same type of situations as cause 1, cause 88, and cause 100.

Cause No. l - Unallocated (unassigned) number.

This cause indicates that the destination requested by the calling user cannot be reachedbecause, although the number is in a valid format, it is not currently assigned (allocated).

hat it usually means!

1. The "#$%" may be incorrectly entered in the router or the Telco switch, giving a"#$% failure in the router logs.

&. The $"%' phone number being dialed by the router is invalid and the telco switchcannot locate the number to complete the call, as it is invalid.

. n long distance calls, the call cannot be properly routed to its destination.

Cause No. 2 - No route to specified transit networ (national use).This cause indicates that the equipment sending this cause has received a request to routethe call through a particular transit networ* which it does not recogni+e. The equipmentsending this cause does not recogni+e the transit networ* either because the transit networ*does not eist or because that particular transit networ* not serve the equipment which issending this cause.

Cause No. ! - No route to destination.

This cause indicates that the called party cannot be reached because the networ* through

which the call has been routed does not serve the destination desired. This cause issupported on a networ* dependent basis.

Cause No. " - send special information tone.

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

Cause No. # - misdialed trun prefi$ (national use).

This cause indicates the erroneous inclusion of a trun* prefi in the called party number. Thisnumber is to sniped from the dialed number being sent to the networ* by the customer

premises equipment.

Cause No. % - c&annel unacceptable.

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

Cause No. ' - call awarded. being deliered in an establis&ed c&annel.

This cause indicates that the user has been awarded the incoming call and that the incomingcall is being connected to a channel already established to that user for similar calls (e.g.pac*et-mode .& virtual calls).

Cause No. - preemption.

This cause indicates the call is being preempted.

Cause No. * - preemption - circuit resered for reuse.

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

Cause No. +% - normal call clearing.

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.


2/7


3/7

Cause No. 2 - inalid number format (address incomplete).

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

Cause No. 2* - facilities reected.

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

provide by the networ*.

Cause No. !0 - response to S/US INUI1.

This cause is included in the "T;T6" message when the reason for generating the "T;T6"message was the prior receipt of a "T;T6" $'76$


4/7

or sub-address as indicated in the diagnostic. $t is noted that the particular type of accessinformation discarded is optionally included in the diagnostic.

Cause No. "" - re4uested circuit3c&annel not aailable.

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

Cause No. "% - precedence call bloced.

This cause indicates that there are no predictable circuits or that the called user is busy witha call of equal or higher preventable level.

Cause No. "' - resource unaailable5 unspecified.

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

Cause No. "* - ualit, of Serice not aailable.

This cause is used to report that the requested 7uality of "ervice, as defined in

ecommendation ?.&1. cannot be provided (e.g., throughput of transit delay cannot besupported).

Cause No. #0 - re4uested facilit, not subscribed.

This cause indicates that the user has requested a supplementary service which isimplemented by the equipment which generated this cause but the user is not authori+ed touse.

hat it means!The switch loo*s at the number being dialed and thin*s it is for another service rather than$"%'. $f the phone number is put in the correct format, the call should be placed properly.There are no standards for this, all Telcos have their own system for programming thenumber formats that the switches will recogni+e. "ome systems want to see @ digits, some10, and others 11.

Cause No. #2 - outgoing calls barred.

Cause No. #! - outgoing calls barred wit&in CU6.

This cause indicates that although the calling party is a member of the 56A for the outgoing56A call. utgoing calls are not allowed for this member of the 56A.

Cause No. #" - incoming calls barred

Cause No. ## - incoming calls barred wit&in CU6.

This cause indicates that although the calling party is a member of the 56A for the incoming56A call. $ncoming calls are not allowed for this member of the 56A.

Cause No. #' - bearer capabilit, not aut&ori7ed.

This cause indicates that the user has requested a bearer capability which is implemented bythe equipment which generated this cause but the user is not authori+ed to use.

Cause No. # - bearer capabilit, not presentl, aailable.

This cause indicates that the user has requested a bearer capability which is implemented bythe equipment which generated this cause but which is not available at this time.

Cause No. %2 - inconsistenc, in outgoing information element.

This cause indicates an inconsistency in the designated outgoing access information andsubscriber class.

Cause No. %! - serice or option not aailable. unspecified.

This cause is used to report a service or option not available event only when no other causein the service or option not available class applies.


5/7

Cause No. %# - bearer capabilit, not implemented.

This cause indicates that the equipment sending this cause does not support the bearercapability requested.

hat it means!

1. $n most cases, the number being called is not an $"%' number but an analogdestination.

&. The equipment is dialing at a faster rate than the circuitry allows, for eample,dialing at B3C when only BC is supported.

Cause No. %% - c&annel t,pe not implemented.

This cause indicates that the equipment sending this cause does not support the channeltype requested.

Cause No. %* - re4uested facilit, not implemented.

This cause indicates that the equipment sending this cause does not support the requestedsupplementary services.

Cause No. '0 - onl, restricted digital information bearer capabilit, is aailable.This cause indicates that the calling party has requested an unrestricted bearer service butthe equipment sending this cause only supports the restricted version of the requested

bearer capability.

Cause No. '* - serice or option not implemented unspecified.

This cause is used to report a service or option not implemented event only when no othercause in the service or option not implemented class applies.

Cause No. + - inalid call reference alue.

This cause indicates that the equipment sending this cause has received a message with a

call reference which is not currently in use on the user-networ* interface.

Cause No. 2 - identified c&annel does not e$ist.This cause indicates that the equipment sending this cause has received a request to use achannel not activated on the interface for a call. Dor eample, if a user has subscribed tothose channels on a primary rate interface numbered from l to 1& and the user equipment orthe networ* attempts to use channels through &, this cause is generated.

Cause No. ! - a suspended call e$ists5 but t&is call identif, does not.This cause indicates that acall resume has been attempted with a call identity which differs from that in use for any

presently suspended call(s).

Cause No. " - call identit, in use.

This cause indicates that the networ* has received a call suspended request containing a callidentity (including the null call identity) which is already in use for a suspended call within

the domain of interfaces over which the call might be resumed.

Cause No. # - no call suspended.

This cause indicates that the networ* has received a call resume request containing a callidentityinformation element which presently does not indicate any suspended call within the

domain of interfaces over which calls may be resumed.

Cause No. % - call &aing t&e re4uested call identit, &as been cleared.

This cause indicates that the networ* has received a call resume request containing a callidentityinformation element indicating a suspended call that has in the meantime beencleared while suspended (either by networ* time-out or by the remote user).

Cause No. ' - user not a member of CU6.

This cause indicates that the called user for the incoming 56A call is not a member of thespecified 56A or that the calling user is an ordinary subscriber calling a 56A subscriber.


6/7

Cause No. - incompatible destination.

This cause indicates that the equipment sending this cause has received a request toestablish a call which has low layer compatibility. high layer compatibility or other

compatibility attributes (e.g., data rate) which cannot be accommodated.

hat it means!

1. This usually means that the 'umber To %ial in the 5onnection #rofile is in the wrongformat.


7/7

hat it means!Ei*e cause 1 and cause 88, this usually indicates that the $"%' number being dialed is in aformat that is not understood by the equipment processing the call. "#$%s will sometimes failto initiali+e with a 5ause 100, or a call will fail with this cause.

Cause No. +0+ - message not compatible wit& call state.

This cause indicates that a message has been received which is incompatible with the callstate.

Cause No. +02 - recoer, on timer e$pir,.

This cause indicates that a procedure has been initiated by the epiration of a timer inassociation with error handling procedures.

hat it means!

This is seen in situations where ;5 (;lternate 5all ffering) is being used. ith this type ofcall pre-emption, the Telco switch operates a timer. Dor eample, when an analog call is

placed to a 'etopia router that has two %ata 5hannels in place, the router relinquishes thesecond channel, but if it doesn2t happen in the time allotted by the switch programming, the

call will not ring through and will be discarded by the switch.

Cause No. +0! - parameter non-e$istent or not implemented - passed on (national use).

This cause indicates that the equipment sending this cause has received a message whichincludes parameters not recogni+ed because the parameters are not defined or are definedbut not implemented by the equipment sending this cause. The cause indicates that theparameter(s) were ignored. $n addition, if the equipment sending this cause is anintermediate point, then this cause indicates that the parameter(s) were passed unchanged.

Cause No. ++0 - message wit& unrecogni7ed parameter discarded.

This cause indicates that the equipment sending this cause has discarded a receivedmessage which includes a parameter that is not recogni+ed.

Cause No. +++ - protocol error5 unspecified.

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

Cause No. +2' - Intel-woring5 unspecified.

This cause indicates that an interwor*ing call (usually a call to B service) has ended.

Notes about Cause Codes oer +2

5ause code values of 1&8 and higher aren2t sent over the networ*. ; terminal displaying avalue 1&8 or higher and claiming it is a cause code arguably has a bug or is implementingsome proprietary diagnostic code (not necessarily bad). "ome commendation has causecodes listed with numbers higher than 1&8, but at this time they are proprietary in nature.

The #$ equipment vendors are the most li*ely to use these codes as they have been using

proprietary messages in the facilities data lin* for some time now (there is an as yetundefined area in the D%E which is big enough to carry small datagrams or messages). $t istypically used to pass proprietary control or maintenance messages between multipleers.

23487285-isdn-cause-codes.pdf

Documents