-
Notifications
You must be signed in to change notification settings - Fork 18
Error codes
List of error codes, as reported by different appliances to Verboice.
ISDN error codes, based on a list from the International Telecommunication Union. Certain devices will report errors through Asterisk using this codeset.
Unallocated (unassigned) number: This cause indicates that the called party cannot be reached because, although the called party number is in a valid format, it is not currently allocated (assigned).
In outbound calls, this means the network does not recognise the phone number being called. Make sure the phone number is correct and retry the call.
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 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, while it does exist, does not serve the equipment which is sending this cause. This cause is supported on a network-dependent basis.
No route to destination: 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.
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.
Misdialled trunk prefix (national use): This cause indicates the erroneous inclusion of a trunk prefix in the called party number.
Channel unacceptable: This cause indicates that the channel most recently identified is not acceptable to the sending entity for use in this call.
Call awarded and 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 channel already established to that user for similar calls (e.g. packet-mode X.25 virtual calls).
Preemption: This cause indicates that the call is being pre-empted.
Preemption – circuit reserved for reuse: This cause indicates that the call is being pre-empted and the circuit is reserved for reuse by the preempting exchange.
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.
User busy: 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 determine user busy, it is noted that the user equipment is compatible with the call.
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.
If you are using a local modem, this error may occur when Verboice cannot reach the modem. Make sure the modem is powered on, connected to the network, and reachable by Verboice.
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 prescribed period of time. NOTE – This cause is not necessarily generated by Q.931 procedures but may be generated by internal network timers.
This error may also arise if the local modem cannot place the call due to network restrictions, such as having no credit.
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 personal telecommunication user is temporarily not addressable at any usernetwork interface.
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. 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.
Number changed: 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 value, cause No. 1, Unallocated (unassigned) number, shall be used.
Redirection to new destination: This cause is used by a general ISUP protocol mechanism that can be invoked by an exchange that decides that the call should be set-up to a different called number. Such an exchange can invoke a redirection mechanism, by use of this cause value, to request a preceding exchange involved in the call to route the call to the new number.
Exchange – routing error: This cause indicates that the destination indicated by the user cannot be reached, because an intermediate exchange has released the call due to reaching a limit in executing the hop counter procedure. This cause is generated by an intermediate node, which when decrementing the hop counter value, gives the result 0.
Non-selected user clearing: This cause indicates that the user has not been awarded the incoming call.
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 signalling 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.
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. This condition may be determined: – immediately after reception of an end of pulsing (ST) signal; or – on time-out after the last received digit.
In outbound calls, make sure the phone number being called is valid and complete.
Facility rejected: This cause is returned when a supplementary service requested by the user cannot be provided by the network.
Response to STATUS ENQUIRY: This cause is included in the STATUS message when the reason for generating the STATUS message was the prior receipt of a STATUS ENQUIRY message.
Normal, unspecified: This cause is used to report a normal event only when no other cause in the normal class applies. 18 2.2.7.2 Resource unavailable class
No circuit/channel available: This cause indicates that there is no appropriate circuit/channel presently available to handle the call.
If using a local modem, make sure the SIM cards (if applicable) are plugged in, it is connected to the phone network, and the channels are enabled in the modem configuration.
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.
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) (see Annex A/Q.933).
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 (see Annex A/Q.933).
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.
Switching equipment congestion: This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.
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 subaddress, as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic.
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.
Precedence call blocked: This cause indicates that there are no preemptable circuits or that the called user is busy with a call of equal or higher preemptable level.
Resource unavailable, unspecified: This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.
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).
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 which the user is not authorized to use.
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.
Incoming calls barred within CUG: This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls are not allowed to this member of the CUG.
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.
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.
Inconsistency in designated outgoing access information and: subscriber class This cause indicates that there is an inconsistency in the designated outgoing access information and subscriber class.
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.
Bearer capability not implemented: This cause indicates that the equipment sending this cause does not support the bearer capability requested.
Channel type not implemented: This cause indicates that the equipment sending this cause does not support the channel type requested.
Requested facility not implemented: This cause indicates that the equipment sending this cause does not support the requested supplementary service. 20 2.2.7.4.4 Cause No. 70 – Only restricted digital information bearer capability is available (national use) This cause indicates that the calling party has requested an unrestricted bearer service but that the equipment sending this cause only supports the restricted version of the requested bearer capability.
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.
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.
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.
A suspended call exists, but this call identity 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).
Call identity in use: 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.
No call suspended: 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.
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 indicating a suspended call that has in the meantime been cleared while suspended (either by network timeout or by the remote user).
User not 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.
Incompatible destination: 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.
Non-existent CUG: This cause indicates that the specified CUG does not exist.
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.
Invalid message, unspecified: This cause is used to report an invalid message event only when no other cause in the invalid message class applies.
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.
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.
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.
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(s)/parameter(s) not recognized because the information element identifier(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.
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 fields in the information element are coded in such a way which has not been implemented by the equipment sending this cause.
Message not compatible with call state: This cause indicates that a message has been received which is incompatible with the call state.
Recovery on timer expiry: This cause indicates that a procedure has been initiated by the expiry of a timer in association with error handling procedures. 22 2.2.7.6.8 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 recognized because the parameters are not defined or are defined but not implemented by the equipment sending the 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 on unchanged.
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.
Protocol error, unspecified: This cause is used to report a protocol error event only when no other cause in the protocol error class applies.