Important message

1 administrator 16-11-2012 14:59:31

Administrator
Offline
Cause No. 1 unassigned (unallocated) number (UMTS specific cause values for call control)

This cause indicates that the destination requested by the mobile station cannot be reached because,
Cause value = 2 IMSI unknown in HLR (Causes related to MS identification)

This cause is sent to the MS if the MS is not known (registered) in the HLR. This cause code does not a

Cause value = 3 Illegal MS (Causes related to MS identification) This cause is sent to the MS when the

Cause No. 3 no route to destination (UMTS specific cause values for call control) This cause indicates

Cause value = 4 IMSI unknown in VLR (Causes related to MS identification) This cause is sent to the M

Cause value = 5 IMEI not accepted (Causes related to MS identification) This cause is sent to the MS if
Cause value = 6 Illegal ME (Causes related to MS identification) This cause is sent to the MS if the ME

Cause No. 6 channel unacceptable (UMTS specific cause values for call control) This cause indicates

Cause value = 7 GPRS services not allowed (Additional cause codes for GMM) This cause is sent to the
Cause value = 8 GPRS services and non-GPRS services not allowed (Additional cause codes for GMM)

Cause No. 8 operator determined barring (GPRS specific cause values for session management) This
Cause value = 9 MS identity cannot be derived by the network (Additional cause codes for GMM) This

Cause value = 10 Implicitly detached (Additional cause codes for GMM) This cause is sent to the MS e

Cause value = 11 PLMN not allowed (Cause related to subscription options) This cause is sent to the M

Cause value = 12 Location Area not allowed (Cause related to subscription options) This cause is sent

Cause value = 13 Roaming not allowed in this location area (Cause related to subscription options) Th

Cause value = 14 GPRS services not allowed in this PLMN (Additional cause codes for GMM) This cause

Cause value = 15 No Suitable Cells In Location Area (Cause related to subscription options) This cause

NOTE: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the MS to search fo

Cause No.16 normal call clearing (UMTS specific cause values for call control) This cause indicates th

Cause value = 16 MSC temporarily not reachable (Additional cause codes for GMM) This cause is sen
Cause value = 17 Network failure (Causes related to PLMN specific network failures and congestion

Cause No.17 user busy (UMTS specific cause values for call control) This cause is used when the cal

Cause No. 18 no user responding (UMTS specific cause values for call control) This cause is used wh

Cause No. 19 user alerting, no answer (UMTS specific cause values for call control) This cause is use

Cause value = 20 MAC failure (Causes related to PLMN specific network failures and congestion/Auth

Cause value = 21 Synch failure (Causes related to PLMN specific network failures and congestion/Au

Cause No. 21 call rejected (UMTS specific cause values for call control) This cause indicates that the

Cause No. 22 number changed (UMTS specific cause values for call control) This cause is returned to

Cause value = 22 Congestion(Causes related to PLMN specific network failures and congestion/Auth

Cause value = 23 GSM authentication unacceptable(Causes related to PLMN specific network failure

Cause No. 25 pre-emption (UMTS specific cause values for call control) This cause is returned to the

Cause value = 25 LLC or SNDCP failure (GSM only) (GPRS specific cause values for session managem
Cause value = 26 Insufficient resources (GPRS specific cause values for session management) This
Cause No. 26 non-selected user clearing (UMTS specific cause values for call control)

Cause No. 27 destination out of order (UMTS specific cause values for call control) This cause indica

Cause value = 27 Unknown or missing access point name (GPRS specific cause values for session m

Cause No. 28 invalid number format (incomplete number) (UMTS specific cause values for call contr

Cause value = 28 Unknown PDP address or PDP type (GPRS specific cause values for session manag

Cause No. 29 facility rejected (UMTS specific cause values for call control) This cause is returned wh

Cause value = 29 User authentication failed (GPRS specific cause values for session management) T

Cause No. 30 response to STATUS ENQUIRY (UMTS specific cause values for call control) This cause i

Cause value = 30 Activation rejected by GGSN (GPRS specific cause values for session management
Cause No. 31 normal, unspecified (UMTS specific cause values for call control) This cause is used to

Cause value = 31 Activation rejected, unspecified (GPRS specific cause values for session managem

Cause value = 32 Service option not supported (GPRS specific cause values for session managemen

Cause value = 33 Requested service option not subscribed(GPRS specific cause values for session m

Cause No. 34 no circuit/channel available (Resource unavailable class) This cause indicates that ther
Cause value = 34 Service option temporarily out of order (Causes related to nature of request) This

Cause value = 35 NSAPI already used (GPRS specific cause values for session management) This ca

Cause value = 36 Regular PDP context deactivation (GPRS specific cause values for session manage

Cause value = 37 QoS not accepted (GPRS specific cause values for session management) This caus
Cause No. 38 network out of order (Resource unavailable class)

This cause indicates that the network is not functioning correctly and that the condition is likely to las
Cause value = 38 Call cannot be identified (Causes related to nature of request)

This cause is sent when the network cannot identify the call associated with a call re-establishment re
Cause value = 38 Network failure (GPRS specific cause values for session management)

This cause code is used by the network to indicate that the PDP context deactivation is caused by an e

Cause value = 39 Reactivation requested (GPRS specific cause values for session management)
This cause code is used by the network to request a PDP context reactivation after a GGSN restart.
Cause value = 40 No PDP context activated (Additional cause codes for GMM)

This cause is sent to the MS if the MS requests an establishment of the radio access bearers for all act
Cause value = 40 Feature not supported (GPRS specific cause values for session management)

This cause code is used by the MS to indicate that the PDP context activation initiated by the network
Cause No. 41 temporary failure (Resource unavailable class)

This cause indicates that the network is not functioning correctly and that the condition is not likely to

Cause value = 41 semantic error in the TFT operation. (GPRS specific cause values for session manag

This cause code is used by the network to indicate that the there is a semantic error in the TFT operat
Cause No. 42 switching equipment congestion (Resource unavailable class)

This cause indicates that the switching equipment generating this cause is experiencing a period of hi

Cause value = 42 syntactical error in the TFT operation. (GPRS specific cause values for session mana

This cause code is used by the network to indicate that there is a syntactical error in the TFT operation
Cause No. 43 access information discarded (Resource unavailable class)

This cause indicates that the network could not deliver access information to the remote user as requ
Cause value = 43 unknown PDP context (GPRS specific cause values for session management)

This cause code is used by the network to indicate that the PDP context identified by the Linked TI IE t
Cause No. 44 requested circuit/channel not available (Resource unavailable class)

This cause is returned when the circuit or channel indicated by the requesting entity cannot be provid

Cause value = 44 semantic errors in packet filter(s) (GPRS specific cause values for session managem

This cause code is used by the network to indicate that there is one or more semantic errors in packet

Cause value = 45 syntactical error in packet filter(s) (GPRS specific cause values for session managem

This cause code is used by the network to indicate that there is one or more syntactical errors in pack

Cause value = 46 PDP context without TFT already activated (GPRS specific cause values for session m

This cause code is used by the network to indicate that the network has already activated a PDP conte
Cause No. 47 resource unavailable, unspecified (Resource unavailable class)

This cause is used to report a resource unavailable event only when no other cause in the resource un
Cause No. 49 quality of service unavailable (Service or option not available class)

This cause indicates to the mobile station that the requested quality of service, as defined in ITU-T Rec
Cause No. 50 Requested facility not subscribed (Service or option not available class)
This cause indicates that the requested supplementary service could not be provided by the network
Cause No. 55 Incoming calls barred within the CUG (Service or option not available class)

This cause indicates that although the called party is a member of the CUG for the incoming CUG call,
Cause No. 57 bearer capability not authorized (Service or option not available class)

This cause indicates that the mobile station has requested a bearer capability which is implemented b

Cause No. 58 bearer capability not presently available (Service or option not available class)

This cause indicates that the mobile station has requested a bearer capability which is implemented b
Cause No. 63 service or option not available, unspecified (Service or option not available class)

This cause is used to report a service or option not available event only when no other cause in the se
Cause No. 68 ACM equal to or greater than ACMmax (Service or option not available class)

This cause is used by the mobile to indicate that call clearing is due to ACM being greater than or equ
Cause No. 65 bearer service not implemented (Service or option not implemented class)

This cause indicates that the equipment sending this cause does not support the bearer capability req
Cause No. 69 Requested facility not implemented (Service or option not implemented class)

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

Cause No. 70 only restricted digital information bearer capability is available (Service or option not i

This cause indicates that one equipment has requested an unrestricted bearer service, but that the eq
Cause No. 79 service or option not implemented, unspecified (Service or option not implemented cl

This cause is used to report a service or option not implemented event only when no other cause in th
Cause No. 81 invalid transaction identifier value (Service or option not implemented class)

This cause indicates that the equipment sending this cause has received a message with a transaction
Cause No. 87 user not member of CUG (Service or option not implemented class)

This cause indicates that the called user for the incoming CUG call is not a member of the specified CU
Cause No. 88 incompatible destination (Service or option not implemented class)

This cause indicates that the equipment sending this cause has received a request to establish a call w
Cause No. 91 invalid transit network selection (Service or option not implemented class)
Cause No. 95 semantically incorrect message (Causes related to invalid messages)
This cause is used to report receipt of a message with semantically incorrect contents (see subclause
Cause No. 96 invalid mandatory information (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message with a non-seman
Cause No. 96 invalid mandatory information (Causes related to invalid messages)
Cause No. 97 message type non-existent or not implemented (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message with a message t
Cause No. 97 message type non-existent or not implemented (Causes related to invalid messages)

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

Cause No. 98 message type not compatible with protocol state (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message not compatible w

Cause No. 98 message type not compatible with protocol state (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message not compatible w

Cause No. 99 information element non-existent or not implemented (Causes related to invalid mess

This cause indicates that the equipment sending this cause has received a message which includes in

Cause No. 100 conditional IE error (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message with conditional I
Cause No. 101 message not compatible with protocol state (Causes related to invalid messages)

This cause indicates that a message has been received which is incompatible with the protocol state o
Cause No. 102 recovery on timer expiry

This cause indicates that a procedure has been initiated by the expiry of a timer in association with 3G
Cause No. 111 protocol error, unspecified (Causes related to invalid messages)

This cause is used to report a protocol error event only when no other cause in the protocol error class
Cause No. 127 interworking, unspecified

This cause indicates that there has been interworking with a network which does not provide causes f

2 mahmood_tareque 12-12-2012 08:17:48

New Member
Offline
wau ..thanks mate ...

Posts: 2
Pages 1
You must login or register to post a reply
Telecom Traffic 3G Cause codes from network.

Similar topics
Planning scrambling codes(easy way)
Planning 3G network base on 2G network
LTE Network Architecture
Core Network Planning
UMTS Network Structure

Powered by PunBB, supported by Telecom Traffic.

ThemeUrban

om that generated by the network. When used by an MM procedure, except the authentication procedure, this c

SGSN restart.

es not support this capability, cause No. 1 unassigned (unallocated) number shall be used.

TICATION REQUEST message.

d XID response , see 3GPP TS 44.065 [78])

ent resources.

ge was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote u

f the access point name could not be resolved.

eived from a R97/R98 network at PDP context activation

ncluded in the diagnostic.

uired to be present in the message in order for the equipment sending the cause to process the message.

inShare5

ntication procedure, this cause does not affect operation of the GPRS service.

er failure at the remote user, user equipment off-line, etc.

ocess the message.

Default SIP-to-SS7 ISUP Cause Codes

ISUP Cause Value
Normal event
1 unallocated number
2 no route to network
3 no route to destination
16 normal call clearing
17 user busy
18 no user responding
19 no answer from the user
20 subscriber absent
21 call rejected
22 number changed (s/ o diagnostic)
22 number changed ( w/ diagnostic)
23 redirection to new destination
26 non-selected user clearing
27 destination out of order
28 address incomplete
29 facility rejected
31 normal unspecified
34 no circuit available
38 network out of order
41 temporary failure
42 switching equipment congestion
47 resource unavailable
55 incoming calls barred within CUG
57 bearer capability not authorized
58 bearer capability not presently available
65 bearer capability not implemented
70 Only restricted digital information bearer
capability is available (National use)
79 service or option not implemented
Invalid message
87 user not member of CUG
88 incompatible destination
102 Call Setup Time-out Failure
111 Protocol Error Unspecified
127 Internal Error - interworking unspecified

(*) ISDN Cause 16 will usually result in a BYE or CANCEL

(+) If the cause location is user than the 6xx code could be given rather than the 4xx code. the cause value re
(=) ANSI procedure

SIP Status Code to ISDN Cause Code Mapping

Response received Cause value in the REL
400 Bad Request 41 Temporary failure
401 Unauthorized 21 Call rejected (*)
402 Payment required 21 Call rejected
403 Forbidden 21 Call rejected
404 Not Found 1 Unallocated number
405 Method not allowed 63 Service or option unavailable
406 Not acceptable 79 Service/option not implemented (+)
407 Proxy authentication required 21 Call rejected (*)
408 Request timeout 102 Recovery on timer expiry
410 Gone 22 Number changed (w/o diagnostic)
413 Request Entity too long 127 Interworking (+)
414 Request URI too long 127 Interworking (+)
415 Unsupported media type 79 Service/option not implemented (+)
416 Unsupported URI Scheme 127 Interworking (+)
402 Bad extension 127 Interworking (+)
421 Extension Required 127 Interworking (+)
423 Interval Too Brief 127 Interworking (+)
480 Temporarily unavailable 18 No user responding
481 Call/Transaction Does not Exist 41 Temporary Failure
482 Loop Detected 25 Exchange routing error
483 Too many hops 25 Exchange routing error
484 Address incomplete 28 Invalid Number Format (+)
485 Ambiguous 1 Unallocated number
486 Busy here 17 User Busy
487 Request Terminated --- (no mapping)
488 Not Acceptable here --- by warning header
500 Server internal error 41 Temporary Failure
501 Not implemented 79 Not implemented, unspecified
502 Bad gateway 38 Network out of order
503 Service unavailable 41 Temporary Failure
504 Service time-out 102 Recovery on timer expiry
505 Version Not supported 127 Interworking (+)
513 Message Too Large 127 Interworking (+)
600 Busy everywhere 17 User busy

603 Decline 21 Call rejected

604 Does not exist anywhere 1 Unallocated number
606 Not acceptable --- by warning header

use Codes
SIP Response
Normal event
404 Not Found
404 Not Found
404 Not Found
--- (*)
486 Busy here
408 Request Timeout
480 Temporarily unavailable
480 Temporarily unavailable
403 Forbidden (+)
410 Gone
301 Moved permanently
410 Gone
404 Not Found (=)
502 Bad Gateway
484 Address incomplete
510 Not implemented
480 Temporarily unavailable Resource unavailable
503 Service unavailable
503 Service unavailable
503 Service unavailable
503 Service unavailable
503 Service unavailable Service or option not available
403 Forbidden
403 Forbidden
503 Service unavailable
488 Not Acceptable here
488 Not Acceptable here
501 Not implemented
403 Forbidden
503 Service unavailable
504 Gateway timeout
500 Server internal error Interworking
500 Server internal error

500 Server internal error (default)

de could be given rather than the 4xx code. the cause value received in the H.225.0 message is unknown in ISUP, the uns

Code Mapping

n unavailable
plemented (+)

on not implemented (+)

orary Failure

age is unknown in ISUP, the unspecified cause value of the class is sent.

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 sit
Cause No. l - Unallocated (unassigned) number.

This cause indicates that the destination requested by the calling user cannot be reached because, although the number
What it usually means:
1. The SPIDS may be incorrectly entered in the router or the Telco switch, giving a SPID failure in the router logs.

2. The ISDN phone number being dialed by the router is invalid and the telco switch cannot locate the number to co
3. On long distance calls, the call cannot be properly routed to its destination.
Cause No. 2 - No route to specified transit network (national use).

This cause indicates that the equipment sending this cause has received a request to route the call through a particular
transit network does not exist or because that particular transit network not serve the equipment which is sending this c

Cause No. 3 - No route to destination.

This cause indicates that the called party cannot be reached because the network through which the call has been route

Cause No. 4 - send special information tone.

This cause indicates that the called party cannot be reached for reasons that are of a long term nature and that the spe
Cause No. 5 - misdialed trunk prefix (national use).
This cause indicates the erroneous inclusion of a trunk prefix in the called party number. This number is to sniped from

Cause No. 6 - channel unacceptable.

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.

This cause indicates that the user has been awarded the incoming call and that the incoming call is being connected to a

Cause No. 8 - preemption.

This cause indicates the call is being preempted.
Cause No. 9 - preemption - circuit reserved for reuse.
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.

This cause indicates that the call is being cleared because one of the users involved in the call has requested that the ca
What it means:

This could be almost anything; it is the vaguest of the cause codes. The call comes down normally, but the reasons for i
1. Bad username or password
2. Router's settings do not match what is expected by the remote end.
3. Telephone line problems.
4. Hung session on remote end.
Cause No. 17 - user busy.
This cause is used to indicate that the called party is unable to accept another call because the user busy condition has
noted that the user equipment is compatible with the call.
What is means:
Calling end is busy.
Cause No. 18 - no user responding.

This cause is used when a called party does not respond to a call establishment message with either an alerting or conn
What it means:

The equipment on the other end does not answer the call. Usually this is a misconfiguration on the equipment being cal
Cause No. 19 - no answer from user (user alerted).

This cause is used when the called party has been alerted but does not respond with a connect indication within a presc

Cause No. 20 - subscriber absent.

This cause value is used when a mobile station has logged off. Radio contact is not obtained with a mobile station or if a

Cause No. 21 - call rejected.

This cause indicates that the equipment sending this cause does not wish to accept this call. although it could have acce
indicating that the call was cleared due to a supplementary service constraint. The diagnostic field may contain addition

What it means:

This is usually a telco issue. The call never reaches the final destination, which can be caused by a bad switch translatio
Cause No. 22 - number changed.

This cause is returned to a calling party when the called party number indicated by the calling party is no longer assigne
unallocated (unassigned) number shall be used.
Cause No. 26 - non-selected user clearing.
This cause indicates that the user has not been awarded the incoming call.
Cause No. 27 - destination out of order.

This cause indicates that the destination indicated by the user cannot be reached because the interface to the destinatio
party; e.g., 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).

This cause indicates that the called party cannot be reached because the called party number is not in a valid format or
Cause No. 29 - facilities rejected.
This cause is returned when a supplementary service requested by the user cannot be provide by the network.
Cause No. 30 - response to STATUS INQUIRY.

This cause is included in the STATUS message when the reason for generating the STATUS message was the prior receip
Cause No. 31 - normal. unspecified.
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.
This cause indicates that there is no appropriate circuit/channel presently available to handle the call.
What it means:

There is no place on the Public Telephone network to place the call; the call never gets to its destiation. This is usually a
Cause No. 35 - Call Queued.
Cause No. 38 - network out of order.

This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long p

Cause No. 39 - permanent frame mode connection out-of-service.

This cause is included in a STATUS message to indicate that a permanently established frame mode connection is out-of
Cause No. 40 - permanent frame mode connection operational.

This cause is included in a STATUS message to indicate that a permanently established frame mode connection is opera
Cause No. 41 - temporary failure.

This cause indicates that the network is not functioning correctly and that the condition is no likely to last a long period

What it means:

This means that there is a temporary failure at the physical layer on the ISDN network. If you remove the ISDN cable fr
Cause No. 42 - switching equipment congestion.
This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.
What it means:
Just too much going on at this point on the ISDN network to get the call through to its destination.
Cause No. 43 - access information discarded.

This cause indicates that the network could not deliver access information to the remote user as requested. i.e., user-to
type of access information discarded is optionally included in the diagnostic.

Cause No. 44 - requested circuit/channel not available.

This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other sid
Cause No. 46 - precedence call blocked.

This cause indicates that there are no predictable circuits or that the called user is busy with a call of equal or higher pre
Cause No. 47 - resource unavailable, unspecified.

This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class ap
Cause No. 49 - Quality of Service not available.

This cause is used to report that the requested Quality of Service, as defined in Recommendation X.213. cannot be prov
Cause No. 50 - requested facility not subscribed.

This cause indicates that the user has requested a supplementary service which is implemented by the equipment which
What it means:

The switch looks at the number being dialed and thinks it is for another service rather than ISDN. If the phone number
programming the number formats that the switches will recognize. Some systems want to see 7 digits, some 10, and ot

Cause No. 52 - outgoing calls barred.

Cause No. 53 - outgoing calls barred within CUG.

This cause indicates that although the calling party is a member of the CUG for the outgoing CUG call. Outgoing calls ar
Cause No. 54 - incoming calls barred
Cause No. 55 - incoming calls barred within CUG.

This cause indicates that although the calling party is a member of the CUG for the incoming CUG call. Incoming calls ar
Cause No. 57 - bearer capability not authorized.

This cause indicates that the user has requested a bearer capability which is implemented by the equipment which gene
Cause No. 58 - bearer capability not presently available.

This cause indicates that the user has requested a bearer capability which is implemented by the equipment which gene
Cause No. 62 - inconsistency in outgoing information element.
This cause indicates an inconsistency in the designated outgoing access information and subscriber class.
Cause No. 63 - service or option not available. unspecified.

This cause is used to report a service or option not available event only when no other cause in the service or option no
Cause No. 65 - bearer capability not implemented.
This cause indicates that the equipment sending this cause does not support the bearer capability requested.
What it means:

1. In most cases, the number being called is not an ISDN number but an analog destination.

2. The equipment is dialing at a faster rate than the circuitry allows, for example, dialing at 64K when only 56K is su
Cause No. 66 - channel type not implemented.
This cause indicates that the equipment sending this cause does not support the channel type requested.
Cause No. 69 - requested facility not implemented.
This cause indicates that the equipment sending this cause does not support the requested supplementary services.
Cause No. 70 - only restricted digital information bearer capability is available.

This cause indicates that the calling party has requested an unrestricted bearer service but the equipment sending this c

Cause No. 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 the service or optio
Cause No. 81 - invalid call reference value.

This cause indicates that the equipment sending this cause has received a message with a call reference which is not cu
Cause No. 82 - identified channel does not exist.

This cause indicates that the equipment sending this cause has received a request to use a channel not activated on the
equipment or the network attempts to use channels 3 through 23, this cause is generated.

Cause No. 83 - a suspended call exists, but this call identify does not. This cause indicates that a call resume has been attempte

Cause No. 84 - call identity in use.

This cause indicates that the network has received a call suspended request containing a call identity (including the null

Cause No. 85 - no call suspended.

This cause indicates that the network has received a call resume request containing a call identity information element w

Cause No. 86 - call having the requested call identity has been cleared.

This cause indicates that the network has received a call resume request containing a call identity information element i

Cause No. 87 - user not a member of CUG.

This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG or that the call
Cause No. 88 - incompatible destination.

This cause indicates that the equipment sending this cause has received a request to establish a call which has low laye

What it means:

1. This usually means that the Number To Dial in the Connection Profile is in the wrong format. You may need to dia
2. This problem may also give a Cause 111.
3. Dialing at the wrong line speed can also give this Cause.
Cause No. 90 - non-existent CUG.
This cause indicates that the specified CUG does not exist.
Cause No. 91 - invalid transit network selection (national use).

This cause indicates that a transit network identification was received which is of an incorrect format as defined in Anne
Cause No. 95 - invalid message, unspecified.
This cause is used to report an invalid message event only when no other cause in the invalid message class applies.
Cause No. 96 - mandatory information element is missing.

This cause indicates that the equipment sending this cause has received a message which is missing an information elem

What it means:
This is rarely seen in North America but usually means that the number that is being dialed is in the wrong format, (sim
between the source and destination of the call.
Cause No. 97 - message type non-existent or not implemented.

This cause indicates that the equipment sending this cause has received a message with a message type it does not rec

Cause No. 98 - message not compatible with call state or message type non-existent.

This cause indicates that the equipment sending this cause has received a message such that the procedures do not ind
state.
Cause No. 99 - Information element / parameter non-existent or not implemented.

This cause indicates that the equipment sending this cause has received a message which includes information element
by the equipment sending the cause. This cause indicates that the information element(s)/parameter(s) were discarded
message.

Cause No. 100 - Invalid information element contents.

This cause indicates that the equipment sending this cause has received and information element which it has implemen
equipment sending this cause.
What it means:

Like cause 1 and cause 88, this usually indicates that the ISDN number being dialed is in a format that is not understoo

Cause No. 101 - message not compatible with call state.

This cause indicates that a message has been received which is incompatible with the call state.
Cause No. 102 - recovery on timer expiry.

This cause indicates that a procedure has been initiated by the expiration of a timer in association with error handling p

What it means:

This is seen in situations where ACO (Alternate Call Offering) is being used. With this type of call pre-emption, the Telco
relinquishes the second channel, but if it doesn't happen in the time allotted by the switch programming, the call will no

Cause No. 103 - parameter non-existent or not implemented - passed on (national use).

This cause indicates that the equipment sending this cause has received a message which includes parameters not reco
that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this

Cause No. 110 - message with unrecognized parameter discarded.

This cause indicates that the equipment sending this cause has discarded a received message which includes a paramet
Cause No. 111 - protocol error, unspecified.
This cause is used to report a protocol error event only when no other cause in the protocol error class applies.
Cause No. 127 - Intel-working, unspecified.
This cause indicates that an interworking call (usually a call to 5W56 service) has ended.
Notes about Cause Codes over 128

Cause code values of 128 and higher aren't sent over the network. A terminal displaying a value 128 or higher and claim
has cause codes listed with numbers higher than 128, but at this time they are proprietary in nature.

The PRI equipment vendors are the most likely to use these codes as they have been using proprietary messages in the
messages). It is typically used to pass proprietary control or maintenance messages between multiplexers.