Norstar Administration Mike's PBX Tips

Norstar: Cause Codes (Call Clearing Codes)

Useful for diagnostics, Call Clearing Codes show exactly why a call over ISDN has been released. These codes may be turned on by the administrator by going first into System Programming, then Release reasons - Text: Simple - Cause code: Y.

Norstar Cause Codes with a Description of the Event for Convenient Easy Access

 

We have many Nortel, Norstar, ICS Manuals for Download and Meridian Manuals for Download. Additionally, you can find tech Nortel Norstar how-to Instructions. For a List of Nortel Feature Codes.

How to Change Time on Nortel Phone Systems

---

Below we list the Norstar Cause Codes from number 1 to 127 each with name and a description of the event for help with a technician's diagnostics.

Norstar Cause Codes With Definitions

The following list of Cause Codes (Call Clearing Codes) are for a Norstar set when the call has been placed over a PRI circuit. Also known as ISDN Event Cause Codes.

• Cause codes with definitions:
• Cause Code No. 1- 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).
• Cause Code No. 2- No route to specified transit network. 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 network, while it does exist, does not serve the equipment that is sending this cause.
  This cause is supported on a network-dependent basis.
• Cause Code No. 3- No route to destination. 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.
  This cause is supported on a network-dependent basis.
• Cause Code No. 6- Channel unacceptable. This cause indicates that the channel used in this call is not acceptable to the sending entity.
• Cause Code No.7- Call awarded and being delivered in an established channel. This cause indicates that the user is receiving an incoming call, which is being connected to a channel already used by that user for similar calls (e.g., packet-mode X.25 virtual calls).
• Cause Code 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. Under normal situations, the source of this cause is not the network.
• Cause Code No. 17- User busy. 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 call.)
• Cause Code No. 18- No user responding. 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.
• Cause Code No. 19- No answer from user (user alerted). 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. (Note: This cause is not necessarily generated by Q.931 procedures, but may be generated by internal network timers.)

• Cause Code No. 21- Call rejected. 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 Code No. 22- Number changed. This cause is returned to a calling user when the called party number indicated by the calling user 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 Code No. 26- Non-selected user clearing. This cause indicates that the specified user has not been awarded the incoming call.
• Cause Code No. 27- Destination out of order. 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 signaling 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 Code No. 28- Invalid number format (address incomplete). 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 Code No. 29- Facility rejected. This cause is returned when a facility requested by the user cannot be provided by the network.
• Cause Code No. 30- response to STATUS INQUIRY. This cause is included in the STATUS message when the reason for generated the STATUS message was the prior receive of a STATUS INQUIRY message.
• Cause Code No. 31- Normal, unspecified. This cause is used to report a normal even only when no other cause in the normal class applies.
• Cause Code No. 34- No circuit/channel available. This cause indicates that there is no appropriate circuit/channel presently available to handle the call.
• Cause Code 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 reattempting the call is not likely to be successful.
• Cause Code No. 41- Temporary failure. 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 user may wish to try another call attempt almost immediately.
• Cause Code No. 42- Switching equipment congestion. This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.
• Cause Code 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-user information, low layer compatibility, high layer compatibility, or a 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 Code 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 Code 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.
• Cause Code 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 or transit delay cannot be supported).
• Cause Code No. 50- Requested facility not subscribed. This cause indicates that the requested supplementary service could not be provided by the network because the user has not completed the necessary administrative arrangements with its supporting networks.
• Cause Code No 57- Bearer capability not authorized. This cause indicates that the user has requested a bearer capability implemented by the equipment that generated this cause that the user is not authorized to use.
• Cause Code No. 58- Bearer capability not presently available. This cause indicates that the user has requested a bearer capability implemented by the equipment that generated this cause which is not available at this time.
• Cause Code 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 Code No. 65- Bearer capability not implemented. This cause indicates that the equipment sending this cause does not support the bearer capability requested.
• Cause Code No. 66- Channel type not implemented. This cause indicates that the equipment sending this cause does not support the channel type requested.
• Cause Code No. 69- Requested facility not implemented. This cause indicates that the equipment sending this cause does not support the requested supplementary service.
• Cause Code No. 70- Only restricted digital information bearer capability is available. This cause indicates that a device has requested an unrestricted bearer service but the equipment sending this cause only supports the restricted version of the requested bearer capability.
• Cause Code 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 Code 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 Code 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 interface for a call. For example, if a user has subscribed to those channels on a primary rate interface numbered from 1 to 12 and the user equipment or the network attempts to use channels 13 through 23, this cause is generated.
• Cause Code 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).
• Cause Code No. 84- Call identity in use. This cause indicates that the network has received a call suspend request. The call suspend request contained 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.
• Cause Code No. 85- No call suspended. This call indicates that the network has received a call resume request. The call resume request contained a call identity information element that presently does not indicate any suspended call within the domain interfaces over which calls may be resumed.
• Cause Code No. 86- Call having the requested call identity has been cleared. This cause indicates that the network has received a call resume request. The call resume request contained a call identity information element that once indicated a suspended call; however, that suspended call was cleared while suspended (either by network timeout or by remote user).
• Cause Code No. 88- Incompatible destination. This cause indicates that the equipment sending this cause has received a request to establish a call that has a low layer compatibility, high layer compatibility, or other compatibility attributes (e.g., data rate) that cannot be accommodated.
• Cause Code No. 91- Invalid transit network selection. This cause indicates that a transit network identification of an incorrect format as defined in Annex C/Q.931 was received.
• Cause Code 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 Code No. 96- Mandatory information element is missing. This cause indicates that the equipment sending this cause has received a message that is missing an information element that must be present in the message before that message can be processed.
• Cause Code 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 recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.
• Cause Code No. 98- Message not compatible with call state or message type non-existent or not implemented. 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.
• Cause Code No. 99- Information element non-existent or not implemented. This cause indicates that the equipment sending this cause has received a message that 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 Code No. 100- Invalid information element contents. This cause indicates that the equipment sending this cause has received an information element which it has implemented; however, one or more of the fields in the information element are coded in a way that has not been implemented by the equipment sending this.
• Cause Code No 101- Message not compatible with call state. This cause indicates that a message has been received that is incompatible with the call state.
• Cause Code No. 102- Recovery on timer expiry. This cause indicates that a procedure has been initiated by the expiry of a timer in association with Q.931 error handling procedures.
• Cause Code 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 Code No. 127- Interworking, unspecified. This cause indicates there has been interworking with a network that does not provide causes for actions it takes; thus, the precise cause for a message being sent cannot be ascertained.

About Nortel Networks Corp.

Nortel Networks Corporation, first founded as Northern Telecom Limited, is a multinational telecommunications equipment manufacturer headquartered in Toronto, Ontario, Canada. They made many large and small business PBX systems and were for a long time one of the primary leaders in the telecom industry. On January 14, 2009 Nortel filed for bankruptcy protection in order to restructure its debt and financial obligations. Northern Telecom, which bankruptcy lasted until 2013 and was the largest bankruptcy case in Canadian history, was then partially acquired by Avaya.