<div>We have 7825 running CCM 4.1(3) in a two node cluster, publisher and subscriber. </div>
<div>All IP Phones and end points are registering to the subscriber. </div>
<div>We have recently (2 weeks ago) upgraded from CCM 3.3(5) to 4.1(3) and have been facing several issues evern since then. I presume that the new version needs beefed up servers .</div>
<div> </div>
<div>We had a problem that users were unable to cancel call forward all. </div>
<div>We tried all possible ways, cancel CFwdAll from Call Manager, from the users web interface and even deleted and re-created the IP Phone and the Users profile. All failed. </div>
<div>Finally we looked at a Cisco troubleshooting tip Document ID 91213 and it said that with 7960 phones and call manager version 3.0 and above there could be a problem with low disk space on server and the database layer monitoring service.
</div>
<div> </div>
<div>We restarted the Cisco Database Layer Monitoring service on the subscriber first (no improvement) and then on the publisher (after about 2 minutes it worked fine).</div>
<div>All users are now able to cancel call forward all. </div>
<div> </div>
<div>I noticed that earlier after the users had enabled the CFwdAll, there would be either no change when they press the CFwdAll again or they would get a busy out tone. </div>
<div> </div>
<div>Can anyone confirm if the issue is because our CallManager Publisher is overloaded. How do we conduct performance monitoring on Call Managers?</div>