Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
99
This cause indicates that the equipment sending this cause has received a message which includes inform-
ation 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 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.
ation 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 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.
100
This cause indicates that the equipment sending this cause has received and information element which it has
implemented; however, one or several fields in the information elements are coded in such a way which has
not been implemented by the equipment sending this cause.
implemented; however, one or several fields in the information elements are coded in such a way which has
not been implemented by the equipment sending this cause.
101
This cause indicates that a message has been received which is incompatible with the call state.
102
This cause indicates that a procedure has been initiated by the expiry of a timer in association with Q.931
error handling procedures.
error handling procedures.
103
This cause indicates that the equipment sending this cause has received a message which includes para-
meters not recognized because the parameters are not defined or are defined but not implemented by the
equipment sending this cause.
meters not recognized because the parameters are not defined or are defined but not implemented by the
equipment sending this cause.
110
This cause indicates that the equipment sending this cause has discarded a received message which
includes a parameter that is not recognized.
includes a parameter that is not recognized.
111
This cause is used to report a protocol error event only when no other cause in the protocol error class
applies.
applies.
127
This cause indicates that there has been internetworking which does not provide causes for actions. The pre-
cise cause for a message being sent is not known.
cise cause for a message being sent is not known.
128
This cause is used when the called user has indicated the inability to accept another call.
129
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.
have accepted the call because the equipment sending this cause is neither busy nor incompatible.
130
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.
the number is in a valid format, it is not currently assigned.
131
This cause indicates that the destination can not be reached caused by an unknown reason.
132
This cause indicates that the destination can not be reached caused by a generic error.
133
This cause indicates that the gatekeeper rejected the call.
134
This cause indicates that the gatekeeper could not find the number.
135
This cause indicates that the gatekeeper timed out the call.
136
This cause indicates that the gatekeeper is not active.
255
Cisco specific. Not part of ITU-T standard.
1000
range
range
Used for mapping TC & TE codes. Cisco TMS adds 1000 to the number sent by the endpoint. For standard
cause codes this corresponds to the numbers for the cause codes listed above.
cause codes this corresponds to the numbers for the cause codes listed above.
Table 176 Cause codes based on the ITU-T standard (continued)
Revision History
Date
Revision
Description
August 2015
01
Updated folder permission information for a scheduled conference.
Table 177 Cisco TMS Administrator Guide revision history
286
Cisco TelePresence Management Suite Administrator Guide
Revision History