Re: High Traffic Call Try Your Again Later. Have solution?
You'll see that message displayed on your IP phones when trying to make a call if you are experiencing a "CodeYellow". This indicates a resource issue likely due to high CPU that causes the CallManager service to throttle calls (block them) until the CodeYellow condition exits. Usually this is caused by a call loop to a gateway or trunk. When you see the message on your IP phone, use the Real-Time Monitoring Tool (RTMT) to collect the Event Viewer - Application Logs and CallManager logs you should be able to find the time stamp of when the CodeYellow started and then find the same time in the CallManager traces to try and identify if there is a particular call that caused the problem.
Cisco 7900 series IP Phone users do not receive a dial tone from Cisco CallManager, and the High Traffic Try Again Later error messages appears on the phone display when they go off-hook. This document discusses how to troubleshoot this issue.
Cisco 7900 IP Phones do not receive a dial tone from Cisco CallManager and instead receive a reorder/busy tone when the phone goes off-hook. The High Traffic Try Again Later error message appears on the LCD display of the IP Phone.
The High Traffic Try Again Later error message that appears on the IP Phones indicates this issue:
Whenever the LowPriorityQueueThrottlingFlag Cisco CallManager service parameter is set to TRUE and the Low Priority queue is over the limit specified by the LowPriorityQueueThrottlingMaxCount Cisco CallManager service parameter, the High Traffic Try Again Later error message appears on the LCD display of any IP Phone that is registered to this Cisco CallManager server and that attempts to go off-hook and make a new call. By default, this message appears on the phone if the Low Priority queue gets deeper than 20 signals.
Generally, the Cisco CallManager works fine as long as the Low Priority queue does not get higher than 100. Therefore, if you never see the Low Priority queue go higher than 75, you can configure the LowPriorityQueueThrottlingMaxCount = 100 Cisco CallManager service parameter in order to overcome this issue.
It is also recommended to check the CPU utilization and the disk space usage. If they are high, you need to clear the hard disk space and shrink the CDR/CAR database.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...