TANDBERG 6000MXP - Manual (Page 217)

217
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
Cause No. 81 - Invalid Call Reference Value
This cause indicates that the equipment sending this cause has re-
ceived 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
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 the user only subscribed to channels 1 to 12
and channel 13 through 23 is requested by either side, 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).
Cause No. 84 - Call Identity In Use
This cause indicates that the network has received a call resume
request. The call resume request contained a call identity information
element which presently does not indicate any suspended call within
the domain of interfaces over which calls may be resumed.
Cause No. 85 - 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.
Cause No. 86 - Call Having The Requested Call Identity Has Been
Cleared
This cause indicates that the network has received a call resume re-
quest. The request contained a call identity information element which
once indicated a suspended call, however, that the call was cleared
while suspended (either a network time-out or remote user).
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 ordi-
nary subscriber calling a CUG subscriber.
Cause No. 88 - 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.
Cause No. 90 - Non-Existent CUG
This cause indicates that the specified CUG does not exist.
Cause No. 91 - Invalid Transit Network Selection
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 class applies.
Cause No, 96 - Mandatory Information Element Is Missing
This cause indicates that the equipment sending this cause has re-
ceived a message which is missing an information element which must
be present in the message before that message can be processed.
Cause 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 of defined but not implemented
by the equipment sending this cause.
Cause 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 No. 99 - Information Element / Parameter Non-Existent Or Not
Implemented
This cause indicates that the equipment sending this cause has re-
ceived 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 equip-
ment 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.
Cause No. 100 - Invalid Information Element Contents
This cause indicates that the equipment sending this cause has
received and information element which it has implemented; however,
one or more fields in the information elements are coded in such a way
which has not been implemented by the equipment sending this cause.
Cause No. 101 - Message Not Compatible With Call State
This cause indicates that a message has been received which is incom-
patible with the 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 Q.931 error handling procedures.
Cause No. 103 - Parameter Non-Existent Or Not Implemented
- Passed On
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.
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 - Interworking, Unspecified
This cause indicates that there has been internetworking which does
not provide causes for actions. The precise cause for a message being
sent is not known.
Status Information – xhistory / xhistory.xml
Call - DisconnectCauseValue (3:3)