Speed or duplex mismatch on ethernet ports. Disable auto-negotiation of these parameters and hard code 100 full duplex on both sides.
High CPU utilization on CallManager. Check CPU utilization on the Cisco CallManager server through the Windows Task Manager. Select Ctl Alt Del then the Performance tab. Check which process is causing the high CPU utilization by selecting the Processes tab.
Note: Although 100 percent CPU of a high-level process can cause sluggish behavior or delayed dial tone, do not infer from this that 100 percent CPU is necessarily always a bad thing. As of CallManager 3.3(1), low priority tasks (such as phone registrations) can consume 100 percent CPU without causing adverse effects to the ability to place or receive calls. Look at the 100 percent CPU as a possible symptom but not necessarily the root cause. In this case, you observe the symptoms of sluggish or delayed dial tone and 100 percent CPU utilization and make a correlation between the two.
To investigate CPU spikes more thoroughly, make use of the Real-Time Monitoring Tool to view the counters in the Cisco CallManager System Performance object to view the status of CallManager system performance objects. Counters available detail which queue level the usage is attributed to, so even when the CPU spikes to 100 percent utilization, you can understand where the spike is occurring and determine whether it results in degraded CallManager performance.
High memory utilization and disk fragmentation on Cisco CallManager. To reduce the impact of memory paging to the hard disk, regularly check for fragmentation on the CallManager volume, particularly if tracing is operational. If the total fragmentation appears to be more than 10 percent or if files have become overly fragmented (more than 500 fragments), it is advisable to defragment the volume.
High bandwidth utilization of remote link between Cisco CallManager and IP phone. Ensure that low latency queuing and Connection Admission Control (CAC) are correctly configured.
For more information, refer to the Call Processing chapter of the IP Telephony Solutions Reference Network Design (SRND) Guides. These design guides are available for difference CallManager releases. This includes detailed information on Cisco CallManager performance, including the CPU and memory consumption of various IP telephony devices.
Hello Team, I have configured Call Back Scrip as below. If all agents are busy, Customer gets an option to enter his 10 Digits Call Back Number. When customer input his Call Back Number it is confirmed by Script and then call terminat...
Hello,We are using UCCX 11.5, and we have 1 user assigned as supervisor of several teams. But in her Finesse, she can only see data of 1 team in Team Summary Report (while she can still see different teams in Team Performance)How can we let the supervisor...
I'd like my C40 on 7.3.3 to load a camera preset when it starts up. I've got a startup script that works when I click Run in the web interface startup scripts page. Unfortunately, application.log seems to show that it runs the script right before pairing ...
hi, we have a cucm and CMS on the central site and we have sx 80 on the central site and 9 other sites , other sites have 6 or 2 mbps, the problem is that the video quality isn't good with a 3 way video, so i'm pretty sure if it's a 10 way video...
Call flow:Ingress GW -> CVP -> Label 20480(in routing script) -> CVP -> CUBE If i send call asis, then CUBE answer "486 Busy here" but CVP send to IngressGW "302 Moved Temporarily"If i modify Remote-Party-ID to "--CVP <sip:aaa@bbb>"...