Specifications

6-130
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
MTP/transcoder), and so on, and accordingly calculate the maximum bandwidth that can be allocated
per call involving an MTP/transcoder and take that into consideration when configuring the supported
codecs in the MTPs and transcoders. A good idea is to configure the media devices with all the supported
codecs and set the region bandwidths to restrict too much bandwidth usage (refer to the Unified CM
documentation for details on region and location settings).
Also, there may be codec mismatch between the endpoint and the MTP/transcoders after considering the
region bandwidth between the MTP/transcoder and the endpoint. Increasing the region bandwidth may
be a solution to the problem, but that decision should be made after careful consideration of the amount
of bandwidth you're willing to allocate per call between the set of regions.
Another possible cause that an MTP/transcoder did not get allocated is because there was not enough
available bandwidth for the call. This can happen if the MTP/transcoder and endpoint belong to different
locations and the bandwidth that is set between the locations is already in use by other calls. Examine
the bandwidth requirements in your deployment to determine whether bandwidth between the locations
can be increased. However, note that increasing the bandwidth between these two locations means that
you may need to reduce the bandwidth between other locations.
Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware
that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in
poor voice quality during call. Consider increasing the total amount of network bandwidth. Finally, if
RSVP Agent allocation fails due to MTP/transcoder not supporting RSVP functionality or capability
mismatch or all the resources being in use, consider installing additional MTP or transcoder devices
which support RSVP functionality.
ICTCallThrottlingStart
Cisco CallManager stops handling calls for the indicated H.323 device due to heavy traffic or a route
loop over the H.323 trunk.
Cisco Unified Communications Manager has detected a route loop over the H.323 trunk indicated in this
alarm. As a result, Unified CM has temporarily stopped accepting calls for the indicated H.323 trunk.
It's also possible that a high volume of calls are occurring over the intercluster trunk, which has triggered
throttling.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Error (3)
Parameters
Device Name [String] IP Address [String] Device type. [Optional] [Enum]Device description
[Optional].
[String]
Enum Definitions for DeviceType
125—TRUNK