Important message

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, although the number is in a valid format, it is not currently assigned (allocated).

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 affect operation of the GPRS service, although is may be used by a GMM procedure.

Cause value = 3 Illegal MS (Causes related to MS identification) This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is not acceptable to the network or because the MS does not pass the authentication check, i.e. the SRES received from the MS is different from that generated by the network. When used by an MM procedure, except the authentication procedure, this cause does not affect operation of the GPRS service.

Cause No. 3 “no route to destination” (UMTS specific cause values for call control) This cause indicates that the called user cannot be reached because the network through which the call has been routed does not serve the destination desired.

Cause value = 4 IMSI unknown in VLR (Causes related to MS identification) This cause is sent to the MS when the given IMSI is not known at the VLR.

Cause value = 5 IMEI not accepted (Causes related to MS identification) This cause is sent to the MS if the network does not accept emergency call establishment using an IMEI.

Cause value = 6 Illegal ME (Causes related to MS identification) This cause is sent to the MS if the ME used is not acceptable to the network, e.g. blacklisted. When used by an MM procedure, this cause does not affect operation of the GPRS service.

Cause No. 6 “channel unacceptable” (UMTS specific cause values for call control) This cause indicates the channel most recently identified is not acceptable to the sending entity for use in this call.

Cause value = 7 GPRS services not allowed (Additional cause codes for GMM) This cause is sent to the MS if it requests an IMSI attach for GPRS services, but is not allowed to operate GPRS services.

Cause value = 8 GPRS services and non-GPRS services not allowed (Additional cause codes for GMM) This cause is sent to the MS if it requests a combined IMSI attach for GPRS and non-GPRS services, but is not allowed to operate either of them.

Cause No. 8 “operator determined barring” (GPRS specific cause values for session management) This cause indicates that the MS has tried to access a service that the MS’s network operator or service provider is not prepared to allow.

Cause value = 9 MS identity cannot be derived by the network (Additional cause codes for GMM) This cause is sent to the MS when the network cannot derive the MS’s identity from the P-TMSI in case of inter-SGSN routing area update.

Cause value = 10 Implicitly detached (Additional cause codes for GMM) This cause is sent to the MS either if the network has implicitly detached the MS, e.g. some while after the Mobile reachable timer has expired, or if the GMM context data related to the subscription dose not exist in the SGSN e.g. because of a SGSN restart.

Cause value = 11 PLMN not allowed (Cause related to subscription options) This cause is sent to the MS if it requests location updating in a PLMN where the MS, by subscription or due to operator determined barring is not allowed to operate.

Cause value = 12 Location Area not allowed (Cause related to subscription options) This cause is sent to the MS if it requests location updating in a location area where the MS, by subscription, is not allowed to operate.

Cause value = 13 Roaming not allowed in this location area (Cause related to subscription options) This cause is sent to an MS which requests location updating in a location area of a PLMN which offers roaming to that MS in that Location Area, by subscription.

Cause value = 14 GPRS services not allowed in this PLMN (Additional cause codes for GMM) This cause is sent to the MS which requests GPRS service in a PLMN which does not offer roaming for GPRS services to that MS.

Cause value = 15 No Suitable Cells In Location Area (Cause related to subscription options) This cause is sent to the MS if it requests location updating in a location area where the MS, by subscription, is not allowed to operate, but when it should find another allowed location area in the same PLMN.

NOTE: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the MS to search for another allowed location area on the same PLMN.

Cause No.16 “normal call clearing” (UMTS specific cause values for call control) 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 value = 16 MSC temporarily not reachable” (Additional cause codes for GMM) This cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a PLMN where the MSC is temporarily not reachable via the GPRS part of the GSM network.

Cause value = 17 “Network failure” (Causes related to PLMN specific network failures and congestion / Authentication Failures) This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g. problems in MAP.

Cause No.17 “user busy” (UMTS specific cause values for call control) This cause is used when the called user has indicated the inability to accept another call. It is noted that the user equipment is compatible with the call.

Cause No. 18 “no user responding” (UMTS specific cause values for call control) This cause is used when a user does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated (defined by the expiry of either timer T303 or T310).

Cause No. 19 “user alerting, no answer” (UMTS specific cause values for call control) This cause is used when a user has provided an alerting indication but has not provided a connect indication within a prescribed period of time.

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

Cause value = 20 “MAC failure” (Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent to the network if the SIM detects that the MAC in the authentication request message is not fresh (see 3GPP TS 33.102).

Cause value = 21 “Synch failure” (Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent to the network if the SIM detects that the SQN in the authentication request message is out of range (see 3GPP TS 33.102).

Cause No. 21 “call rejected” (UMTS specific cause values for call control) This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible.

Cause No. 22 “number changed” (UMTS specific cause values for call control) This cause is returned to a calling mobile station when the called party number indicated by the calling mobile station is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this capability, cause No. 1 “unassigned (unallocated) number” shall be used.

Cause value = 22 “Congestion”(Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility busy/congested etc.).

Cause value = 23 “GSM authentication unacceptable”(Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent to the network in UMTS if the MS supports the UMTS authentication algorithm and there is no Authentication Parameter AUTN IE present in the AUTHENTICATION REQUEST message.

Cause No. 25 “pre-emption” (UMTS specific cause values for call control) This cause is returned to the network when a mobile station clears an active call which is being pre-empted by another call with higher precedence.

Cause value = 25 “LLC or SNDCP failure (GSM only)” (GPRS specific cause values for session management) This cause code is used by the MS indicate that a PDP context is deactivated because of a LLC or SNDCP failure (e.g. if the SM receives a SNSM-STATUS.request message with cause “DM received ” or “ invalid XID response “, see 3GPP TS 44.065 [78])

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 indicates that the destination indicated by the mobile station cannot be reached because the interface to the destination is not functioning correctly. The term “not functioning correctly” indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

Cause value = 27 “Unknown or missing access point name” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included although required or if the access point name could not be resolved.

Cause No. 28 “invalid number format (incomplete number)” (UMTS specific cause values for call control) This cause indicates that the called user cannot be reached because the called party number is not a valid format or is not complete.

Cause value = 28 “Unknown PDP address or PDP type” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the PDP address or type could not be recognised.

Cause No. 29 “facility rejected” (UMTS specific cause values for call control) This cause is returned when a facility requested by user can not be provided by the network.

Cause value = 29 “User authentication failed” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication.

Cause No. 30 “response to STATUS ENQUIRY” (UMTS specific cause values for call control) This cause is included in STATUS messages if the message is sent in response to a STATUS ENQUIRY message. See also subclause 5.5.3.

Cause value = 30 “Activation rejected by GGSN” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the GGSN.

Cause No. 31 “normal, unspecified” (UMTS specific cause values for call control) This cause is used to report a normal event only when no other cause in the normal class applies.

Cause value = 31 “Activation rejected, unspecified” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected due to unspecified reasons.

Cause value = 32 “Service option not supported” (GPRS specific cause values for session management) This cause code is used by the network when the MS requests a service which is not supported by the PLMN.

Cause value = 33 ”Requested service option not subscribed”(GPRS specific cause values for session management) This cause is sent when the MS requests a service option for which it has no subscription.

Cause No. 34 “no circuit/channel available” (Resource unavailable class) This cause indicates that there is no appropriate circuit/channel presently available to handle the call.

Cause value = 34 “Service option temporarily out of order” (Causes related to nature of request) This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service.

Cause value = 35 “NSAPI already used” (GPRS specific cause values for session management) This cause code may be used by a network to indicate that the NSAPI requested by the MS in the PDP context activation request is already used by another active PDP context of this MS. Never to be sent, but can be received from a R97/R98 network at PDP context activation

Cause value = 36 “Regular PDP context deactivation” (GPRS specific cause values for session management) This cause code is used to indicate a regular MS or network initiated PDP context deactivation.

Cause value = 37 “QoS not accepted” (GPRS specific cause values for session management) This cause code is used by the MS if the new QoS cannot be accepted that were indicated by the network in the PDP Context Modification procedure.

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 last a relatively long period of time; e.g., immediately re-attempting the call is not likely to be successful.

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 request.

This cause code is used by the network to indicate that the PDP context deactivation is caused by an error situation in the network.

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 active PDP contexts by sending a SERVICE REQUEST message indicating “data” to the network, but the SGSN does not have any active PDP context(s).

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 is not supported by the MS.

Cause value = 26 “Insufficient resources“ (GPRS specific cause values for session management) This cause code is used by the MS or by the network to indicate that a PDP context activation request, secondary PDP context activation request or PDP context modification request cannot be accepted due to insufficient resources.

Cause value = 38 Network failure (GPRS specific cause values for session management)

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 last a long period of time; e.g., the mobile station may wish to try another call attempt almost immediately.

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

This cause code is used by the network to indicate that the there is a semantic error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification.

Cause No. 42 “switching equipment congestion” (Resource unavailable class)

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

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

This cause code is used by the network to indicate that there is a syntactical error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification.

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 requested; i.e., a user-to-user information, low layer compatibility, high layer compatibility, or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic.

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 the secondary PDP context activation request is not active.

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 provided by the other side of the interface.

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

This cause code is used by the network to indicate that there is one or more semantic errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification.

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

This cause code is used by the network to indicate that there is one or more syntactical errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification.

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

This cause code is used by the network to indicate that the network has already activated a PDP context without TFT.

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 unavailable class applies.

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 Recommendation X.213, cannot be provided.

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 because the user has no completed the necessary administrative arrangements with its supporting networks.

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, incoming calls are not allowed within this CUG.

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 by the equipment which generated this cause but the mobile station is not authorized to use.

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 by the equipment which generated this cause but which is not available at this time.

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 service or option not available class applies.

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 equal to ACMmax.

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 requested.

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 supplementary service.

Cause No. 70 “only restricted digital information bearer capability is available” (Service or option not implemented class)

This cause indicates that one equipment has requested an unrestricted bearer service, but that the equipment sending this cause only supports the restricted version of the requested bearer capability.

Cause No. 79 “service or option not implemented, unspecified” (Service or option not implemented class)

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

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 identifier which is not currently in use on the MS-network interface.

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 CUG.

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 which has low layer compatibility, high layer compatibility, or other compatibility attributes (e.g., data rate) which cannot be accommodated.

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 8.8).

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-semantical mandatory IE error (see subclause 8.5).

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 type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this cause.

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 type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this cause.

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 with the protocol state (subclause 8.4).

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 with the protocol state.

Cause No. 99 “information element non-existent or not implemented” (Causes related to invalid messages)

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

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 IE errors (see subclause 8.7.2).

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 or that a STATUS message has been received indicating an incompatible call state.

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 3GPP TS 24.008 error handling procedures.

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 applies.

Cause No. 127 “interworking, unspecified”

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being sent cannot be ascertained

New Member

Offline

wau ..thanks mate ...

Posts: 2

You must login or register to post a reply

Similar topics

Powered by PunBB, supported by Telecom Traffic.

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

Pages 1

Telecom Traffic → 3G → Cause codes from network.

Planning scrambling codes(easy way)

Planning 3G network base on 2G network

LTE Network Architecture

Core Network Planning

UMTS Network Structure

ThemeUrban

Cause value = 3 Illegal MS (Causes related to MS identification) This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is not acceptable to the network or because the MS does not pass the authentication check, i.e. the SRES received from the MS is different from that generated by the network. When used by an MM procedure, except the authentication procedure, this cause does not affect operation of the GPRS service.

Cause value = 10 Implicitly detached (Additional cause codes for GMM) This cause is sent to the MS either if the network has implicitly detached the MS, e.g. some while after the Mobile reachable timer has expired, or if the GMM context data related to the subscription dose not exist in the SGSN e.g. because of a SGSN restart.

Cause No. 22 “number changed” (UMTS specific cause values for call control) This cause is returned to a calling mobile station when the called party number indicated by the calling mobile station is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this capability, cause No. 1 “unassigned (unallocated) number” shall be used.

Cause value = 23 “GSM authentication unacceptable”(Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent to the network in UMTS if the MS supports the UMTS authentication algorithm and there is no Authentication Parameter AUTN IE present in the AUTHENTICATION REQUEST message.

Cause value = 25 “LLC or SNDCP failure (GSM only)” (GPRS specific cause values for session management) This cause code is used by the MS indicate that a PDP context is deactivated because of a LLC or SNDCP failure (e.g. if the SM receives a SNSM-STATUS.request message with cause “DM received ” or “ invalid XID response “, see 3GPP TS 44.065 [78])

Cause No. 27 “destination out of order” (UMTS specific cause values for call control) This cause indicates that the destination indicated by the mobile station cannot be reached because the interface to the destination is not functioning correctly. The term “not functioning correctly” indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

Cause value = 27 “Unknown or missing access point name” (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included although required or if the access point name could not be resolved.

Cause value = 35 “NSAPI already used” (GPRS specific cause values for session management) This cause code may be used by a network to indicate that the NSAPI requested by the MS in the PDP context activation request is already used by another active PDP context of this MS. Never to be sent, but can be received from a R97/R98 network at PDP context activation

Cause value = 26 “Insufficient resources“ (GPRS specific cause values for session management) This cause code is used by the MS or by the network to indicate that a PDP context activation request, secondary PDP context activation request or PDP context modification request cannot be accepted due to insufficient resources.

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

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

inShare5

Cause value = 3 Illegal MS (Causes related to MS identification) This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is not acceptable to the network or because the MS does not pass the authentication check, i.e. the SRES received from the MS is different from that generated by the network. When used by an MM procedure, except the authentication procedure, this cause does not affect operation of the GPRS service.

Cause No. 27 “destination out of order” (UMTS specific cause values for call control) This cause indicates that the destination indicated by the mobile station cannot be reached because the interface to the destination is not functioning correctly. The term “not functioning correctly” indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

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

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

79 – service or option not implemented

Invalid message

87 – user not member of CUG

88 – incompatible destination

102 – Call Setup Time-out Failure

16 –  normal call clearing

70 – Only restricted digital information bearer capability is available (National use)

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 received in the H.225.0 message is unknown in ISUP, the unspecified cause value of the class is sent.

(=) ANSI procedure

SIP Status Code to ISDN Cause Code MappingResponse received Cause value in the REL

406 – Not acceptable 79 – Service/option not implemented (+)

407 – Proxy authentication required 21 – Call rejected (*)

408 – Request timeout 102 – Recovery on timer expiry

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

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

410 – Gone 22  –  Number changed (w/o diagnostic)

Default SIP-to-SS7 ISUP Cause 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

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

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)

 410 Gone

 503 Service unavailable Service or option not available

(*) 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 received in the H.225.0 message is unknown in ISUP, the unspecified cause value of the class is sent.

SIP Status Code to ISDN Cause Code Mapping

406 – Not acceptable 79 – Service/option not implemented (+)

407 – Proxy authentication required 21 – Call rejected (*)

408 – Request timeout 102 – Recovery on timer expiry

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 (+)

421 – Extension Required 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 (+)

488 – Not Acceptable here --- by warning header

500 – Server internal error 41 – Temporary Failure

501 – Not implemented 79 – Not implemented, unspecified

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 (+)

604 – Does not exist anywhere 1 – Unallocated number

405 –  Method not allowed 63 –  Service or option unavailable

410 – Gone 22  –  Number changed (w/o diagnostic)

(+) If the cause location is ‘user’ than the 6xx code could be given rather than the 4xx code. the cause value received in the H.225.0 message 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 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 reached because, although the number is in a valid format, it is not currently assigned (allocated).

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 complete the call, as it is invalid.

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).

Cause No. 3 - No route to destination.

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 special information tone should be returned to the calling party.

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 the dialed number being sent to the network by the customer premises equipment.

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.

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 call be cleared.

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 it could be:

1. Bad username or password

This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network which 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 not serve the equipment which is sending this cause.

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.

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 (e.g. packet-mode x.25 virtual calls).

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.

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 connect indication within the prescribed period of time allocated.

What it means:

The equipment on the other end does not answer the call. Usually this is a misconfiguration on the equipment being called.

Cause No. 19 - no answer from user (user alerted).

Cause No. 20 - subscriber absent.

Cause No. 21 - call rejected.

What it means:

This is usually a telco issue. The call never reaches the final destination, which can be caused by a bad switch translation, or a misconfiguration on the equipment being called.

Cause No. 22 - number changed.

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.

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 is not complete.

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 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.

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.

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.

This cause indicates that the equipment sending this cause does not wish 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 supplementary service constraint. The diagnostic field may contain additional information about the supplementary service and reason for rejection.

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.

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; e.g., a physical layer or data link layer failure at the remote party or user equipment off-line.

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.

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 temporary problem.

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 period of time e.g., immediately re-attempting the call is not likely to be successful.

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-service (e.g. due to equipment or section failure)

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 operational and capable of carrying user information.

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 of time; e.g., the user may wish to try another call attempt almost immediately.

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 from the Netopia, you would see this. It's usually temporary.

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.

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 side of the interface.

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 preventable level.

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 applies.

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

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 provided (e.g., throughput of transit delay cannot be supported).

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 generated this cause but the user is not authorized to use.

What it means:

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 are not allowed for this member of the CUG.

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 are not allowed for this member of the CUG.

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 generated this cause but the user is not authorized to use.

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 generated this cause but which is not available at this time.

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 not available class applies.

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 supported.

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 cause only supports the restricted version of the requested bearer capability.

The switch looks at the number being dialed and thinks it is for another service rather than ISDN. If 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 the number formats that the switches will recognize. Some systems want to see 7 digits, some 10, and others 11.

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 option not implemented class applies.

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 currently in use on the user-network interface.

Cause No. 82 - identified channel does not exist.

Cause No. 84 - call identity in use.

Cause No. 85 - no call suspended.

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

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 calling user is an ordinary subscriber calling a CUG subscriber.

Cause No. 88 - incompatible destination.

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 dial a 10 or 11 digit number, or dial a 9 in front of the number if it is a Centrex line.

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 Annex C/Q.931

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 element which must be present in the message before that message can be processed.

This cause indicates that the equipment sending this cause has received a request to use a channel not activated on the interface for a call. For example, if a user has subscribed to those channels on a primary rate interface numbered from l to 12 and the user 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 attempted with a call identity which differs from that in use for any presently suspended call(s).

This cause indicates that the network has received a call suspended request containing a call identity (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.

This cause indicates that the network has received a call resume request containing a call identity information element which presently does not indicate any suspended call within the domain of interfaces over which calls may be resumed.

This cause indicates that the network has received a call resume request containing a call identity information element indicating a suspended call that has in the meantime been cleared while suspended (either by network time-out or by the remote user).

This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility. high layer compatibility or other compatibility attributes (e.g., data rate) which cannot be accommodated.

What it means:

Cause No. 97 - message type non-existent or not implemented.

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

Cause No. 99 - Information element / parameter non-existent or not implemented.

Cause No. 100 - Invalid information element contents.

What it means:

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 procedures.

What it means:

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

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 parameter that is not recognized.

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

This is rarely seen in North America but usually means that the number that is being dialed is in the wrong format, (similar to cause 88). Some part of the format being used is not understood by either the remote side equipment or the switching equipment between the source and destination of the call.

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined of defined but not implemented by the equipment sending this cause.

This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the call state, or a STATUS message was received indicating an incompatible call state.

This cause indicates that the equipment sending this cause has received a message which includes information element(s)/parameter(s) not recognized because the information element(s)/parameter name(s) are not defined or are defined but not implemented by the equipment sending the cause. This cause indicates that the information element(s)/parameter(s) were discarded. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

This cause indicates that the equipment sending this cause has received and information element which it has implemented; however, one or more of the fields in the information element are coded in such a way which has not been implemented by the equipment sending this cause.

Like cause 1 and cause 88, this usually indicates that the ISDN number being dialed is in a format that is not understood by the equipment processing the call. SPIDs will sometimes fail to initialize with a Cause 100, or a call will fail with this cause.

This is seen in situations where ACO (Alternate Call Offering) is being used. With this type of call pre-emption, the Telco switch operates a timer. For example, when an analog call is placed to a Netopia router that has two B Data Channels in place, the router relinquishes the second channel, but if it doesn't happen in the time allotted by the switch programming, the call will not ring through and will be discarded by the switch.

This cause indicates that the equipment sending this cause has received a message which includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending this cause. The cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed unchanged.

Cause code values of 128 and higher aren't sent over the network. A terminal displaying a value 128 or higher and claiming it is a cause code arguably has a bug or is implementing some proprietary diagnostic code (not necessarily bad). Some commendation 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 facilities data link for some time now (there is an as yet undefined area in the FDL which is big enough to carry small datagrams or messages). It is typically used to pass proprietary control or maintenance messages between multiplexers.