Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Cause Codes
Code Description
0
Cisco specific. Not part of ITU-T standard.
1
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.
although the number is in a valid format, it is not currently assigned.
2
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.
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.
3
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.
has been routed does not serve the destination desired. This cause is supported on a network dependent
basis.
5
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.
supposed to be stripped from the dialed number being sent to the network by the customer premises
equipment.
6
This cause indicates that the channel most recently identified is not acceptable to the sending party for use
in this call.
in this call.
7
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 (for example packet-mode x.25
virtual calls.
connected to a channel already established to that user for similar calls (for example packet-mode x.25
virtual calls.
8
This cause indicates the call is being pre-empted.
9
This cause indicates that the call is being pre-empted and the circuit is reserved for reuse by the pre-
empting exchange.
empting exchange.
16
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.
requested that the call be cleared.
17
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 compatible
with the call.
may be generated by the called user or by the network. Please note that the use equipment is compatible
with the call.
18
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.
alerting or connect indication within the prescribed period of time allocated (in Q.931 by the expiry of
either time T303 or T310.
19
This cause is used when a user as provided an alerting indication but has not provided a connect
indication within a prescribed period of time.
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.
20
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 user-network
interface.
station or if a personal telecommunication user is temporarily not addressable at any user-network
interface.
21
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.
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.
Cisco TMS Administrator Guide (14.3.2)
Page 336 of 342
Troubleshooting
Cause Codes