TANDBERG 6000MXP - Manual (Page 215)

215
TANDBERG 3000 MXP & 6000 MXP
REFERENCE GUIDE FOR SYSTEM INTEGRATORS
D 13887.08
MAY 2008
Status information followed by a
*
will not be shown unless Detailed Level has been set to 2 – see XACLI – Special commands – xpreferences
Call - DisconnectCauseValue (1:3)
The DisconnectCauseValue may show as a result of the xhistory Call com-
mand and contains additional information to the DisconnectCause result.
See
Call for an overview of the xhistory Call command.
See DisconnectCause for an overview of the disconnect causes.
Disconnect Cause Codes
You can also find the list of disconnect causes by opening a web browser
and enter the IP address of the MPS followed by the filename:
causecd.htm.
Example:
http:///causecd.htm
http://192.168.10.2/causecd.htm
Cause Codes
Cause 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.
Cause 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 transit network, while it does
exist, does not serve the equipment which is sending this cause.
Cause No. 3 - No Route To Destination
This cause indicates that the called party cannot be reached because
the network through which the call has been routed does not serve the
destination desired. This cause is supported on a network dependent
basis.
Cause No. 4 - Send Special Information Tone (Five One Zero NT)
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
This cause indicates the erroneous inclusion of a trunk prefix in the
called party number. This number is supposed to be stripped 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 party for use in this call.
Cause No. 7 - call awarded, being delivered in an established chan-
nel
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).
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.
Cause No. 16/4 or 17 - User Busy
This cause is used when the called user has indicated the inability to
accept another call. This cause code may be generated by the called
user or by the network. Please note that the use equipment is compat-
ible with the call.
Cause No. 16/3 or 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 (in Q.931 by the expiry of
either time 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. Note: This cause is not necessarily generated by the customer
premise equipment, but may be generated by internal network timers.
Cause No. 20 - Subscriber Absent
This cause value is used when a mobile station has logged off, radio
contact is not obtained with a mobile station or if a personal telecom-
munication user is temporarily not addressable at any user-network
interface.
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 incom-
patible. 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 sup-
plementary service and reason for rejection.
Cause No. 22 - Number Changed
This cause is returned to a calling party when the called party number
indicated by the calling party is no longer assigned. The new called
party number may optionally be included in the diagnostic field. If the
network does not support this cause, cause no: 1, unallocated (unas-
signed) will be used instead.
Cause No. 26 - Non-Selected User Clearing
This cause indicates that the user has not been awarded the incoming
call.
Cause No. 27 - Destination Out Of Order
This cause indicates that the destination cannot be reached because
the interface to the destination is not functioning correctly. The signal-
ing message was unable to be delivered due to a hardware failure.
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 facility requested by the user cannot be
provide by the network.
Cause No. 30 - Response To Status Inquiry
This cause is included in the STATUS message when the reason for
generating the STATUS message was the prior receipt of a STATUS
ENQUIRY.
Status Information – xhistory / xhistory.xml