Devices such as IP phones and gateways registered  to a primary Cisco CallManager server reset and register with the secondary Cisco CallManager server and proceed to failback to the primary after a short period of time

Document

Wed, 07/22/2009 - 19:54
Jun 22nd, 2009
User Badges:
  • Gold, 750 points or more

Core Issue

When you look at the packet capture you see that packets arriving at the Cisco CallManager server are not properly marked for Quality of Service (QoS). The issue is caused when QoS is not set correctly and network utilization causes the traffic to be dropped or delayed.


Resolution

In order to resolve the issue, set QoS trust on the switch port where Cisco CallManager is connected. Setting QoS on the switch port on which Cisco CallManager is connected, alleviates the problem enough for the devices to stop resetting.

For more information, refer to the Phone Resets section of Troubleshooting Guide for Cisco CallManager.

Loading.

Actions

This Document

Related Content