Filter
Top Products
Event Histories F-3
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.
Under normal situations, the source of this cause is not the network.
Cause 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 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 (defined in
Recommendation Q.931 by the expiry of either timer T303 or T310).
Cause 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.
This cause is not necessarily generated by Q.931 procedures but may be generated by internal network timers.
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 accepted the call because the equipment sending this cause is neither
busy nor incompatible.
Cause 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 No. 26: non-selected user clearing. This cause indicates that the specified 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 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 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 No. 29: facility rejected. This cause is returned when a facility requested by the user cannot be
provided by the network.
Cause 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 No. 31: normal, unspecified. This cause is used to report a normal even 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.
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 reattempting the call is not likely
to be successful.
Cause 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.