Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Unity slowly dies once a week

We are running Unity 2.4.5.66 / Call Manager 3.09 and TSP 1.0.0.28 and we have about 200 users. The problem is this, last Monday and today our Unity started to shut down ports around 3 or 4 AM (I found this in the event log). It starts with port 8 and then 7 etc..... During this time our CPU Utilization would climb as well. By lunch time the Unity software would shut down and not be able to restart without a reboot of the server. Has anybody heard of this before? Any help would be greatly appreciated.<br><br>

6 REPLIES
Anonymous
N/A

Re: Unity slowly dies once a week

That doesn't look like a supported configuration. Check out the following link:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/2_46/rel_note/246_135.htm#xtocid2099614

Steve Olivier
Software Engineer
Cisco Systems

New Member

Re: Unity slowly dies once a week

This configuration has been running since late February / early March. How can this all of a sudden start happening just last week?

New Member

Re: Unity slowly dies once a week

Good point. What has changed in your Unity/Exchange/Network in the last few weeks?
Have you been adding subscribers to the Unity box? If so, you might want to run the exchange optimizer.
You said that the CPU usage seems to pick up. Can you track as to which process is taking the most CPU?

New Member

Re: Unity slowly dies once a week

In the past week the Microsoft Security Updates (critical updates only) and about 2 weeks ago service pack 2 was put on.

New Member

Re: Unity slowly dies once a week

Can you track which process is eating up the CPU?

Anonymous
N/A

Re: Unity slowly dies once a week

"Unsupported" doesn't mean that it doesn't work. It means that TAC doesn't support it. Since we often refer people to TAC, I am not going to refer an unsupported configuration to TAC.

Steve Olivier
Software Engineer
Cisco Systems

120
Views
0
Helpful
6
Replies