03-18-2003 05:58 AM - edited 03-12-2019 11:06 PM
CCM 3.1.3(a), Unity 3.1.5 with Exchange 2000 off-box, Unity TSP v. 6.0.2(b), dual integration with CCM and SMDI.
Just recently we have had several situations where users will press the "Messages" button on their IP phone to dial into Unity, and all they see is a flashing cursor; it seems to hang and will not dial voicemail.
Upon checking Unity, I see errors stating that MWI lamp lighting failed, and ports disconnecting and reconnecting to the CCM. I then check the CCM, and the CPU is spiked at 100%. Rebooting the CCM will fix the issue.
I don't quite know which box is causing the problem, but in my reading up on the issue, it seems that we might need to upgrade our TSP to 7.0. We recently upgraded Unity to 3.1.5, and haven't had any other problems besides this one.
Any advice would be appreciated.
TMH
03-18-2003 09:01 AM
I'd recommend gathering AvSkinnyTsp traces and CCM traces during the time that there's a problem to diagnose the issue. Any number of things could be going on and I'd hate to speculate.
03-18-2003 10:56 AM
I didn't have the Skinny traces turned on the last time it happened; they're on now. I did take a glance in the CCM traces, and all I saw was digit analysis timeout (DATimeout) errors.
I'll wait and see if it happens again now that I have the skinny traces turned on.
TMH
03-19-2003 06:36 PM
The most likely reason for the DATimeout errors is die to the CPU utilization on your CallMaanger(s).
You can start by using Task Manager on your CallManger to view the process to see which one is spiking the CPU. Make sure you have the "Show processes from all users" checked.
This could also be causing the Unity ports to unregister and many other issues with your CallManager such as delayed dial tone. This is where I would start looking. You may want to look at the Application Event log on the CallManager as well.
03-21-2003 04:20 AM
I think I've figured out what is going on, and I don't think it has anything to do with Unity...
Got a call the other morning about one of our WebAttendants being down...got onto the CCM, and noticed that the CPU usage was all over the place, and eventually spiked at 100%. Stopping and starting the TCD service cleared out the problem. I think I'm experiencing CSCdy32786; I have already made plans to upgrade to Attendant Console for my version of Call Manager.
TMH
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: