Cisco MCS-7825-H3-IPC1 Service Manual page 528

Warning-Level Alarms
Enum Definitions
Code
2
3
Recommended Action
For HopCountExceeded alarm, the recommended action is to check that no routing loops exist across the
Unified CM trunk interfaces (PRI, intercluster trunk, and so on) and gateway (H.323) devices related to
the indicated failed call. By examining trace files and CDR data in all Unified CM nodes and route
patterns in gateways (H.323) that are involved in routing of the indicated failed call, you may be able to
detect a translation pattern, route list or other routing mechanism that is part of the loop.
Update the routing mechanism that resulted in the loop, and then if the looping route pattern was on a
Unified CM, reset the affected route list/pattern in an attempt to clear the route loop; if that fails, reset
the affected trunk/gateway or if the looping route pattern was on a H.323 gateway, restart the gateway.
For call failure reason UserUserIEDropped, if the indicated device is an H.323 intercluster trunk then
the recommended action is to verify that the Passing Precedence Level Through UUIE checkbox has
been enabled on the Trunk Configuration window. If the indicated device is an MGCP gateway with
Device Protocol set to Digital Access PRI and Passing Precedence Level Through UUIE is enabled on
the gateway, then verify that the far-end side of the configured PRI trunk interface supports PRI 4ESS
UUIE-based MLPP and sends the UUIE message with IEID value set to USER_USER_IE (126) and the
User specific protocol ID value set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00).
Cisco Unified Communications Manager Managed Services Guide
6-294
Chapter 6
Definition
HopCountExceeded—The hop count field in passing User-to-User IE exceeded
the maximum value of 10. The reason could be the presence of routing loops
across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on). The
recommended action is to check that no routing loops exist across the Unified CM
trunk interfaces (PRI, intercluster trunk, and so on) and gateway (H.323) devices
related to the indicated failed call. By examining trace files and CDR data in all
Unified CM nodes and route patterns in gateways (H.323) that are involved in
routing of the indicated failed call, you may be able to detect a translation pattern,
route list or other routing mechanism that is part of the loop. Update the routing
mechanism that resulted in the loop, and then if the looping route pattern was on
a Unified CM, reset the affected route list/pattern in an attempt to clear the route
loop; if that fails, reset the affected trunk/gateway or if the looping route pattern
was on an H.323 gateway, restart the gateway.
UserUserIEDropped—The passing UserUserIE is dropped. If the indicated device
is an H.323 intercluster trunk then the possible reason could be that the Passing
Precedence Level Through UUIE checkbox in the Trunk Configuration window
in Unified CM is not enabled; the recommended action is to verify that the Passing
Precedence Level Through UUIE checkbox has been enabled. If the indicated
device is an MGCP gateway with Device Protocol set to Digital Access PRI, the
possible reason could be that in the incoming UUIE message, either the IEID is
not set to USER_USER_IE (126) or the User specific protocol ID value is not set
to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00); the recommended action
is to verify that the far-end side of the configured PRI trunk interface supports PRI
4ESS UUIE-based MLPP and sends the UUIE message with IEID value set to
USER_USER_IE (126) and the User specific protocol ID value is set to
PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00).
Cisco Unified Serviceability Alarms and CiscoLog Messages
OL-22523-01