[cisco-voip] Cancel CallForwardAll wasfailing-CallManager-4.1(3)

[Carter, Bill]

I have seen problems with cancelling CFA when the CM database has
problems.  Specifically, when the publisher had been updated and the
subscriber had not.

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Aman Chugh
Sent: Saturday, April 14, 2007 5:03 AM
To: Muqeemuddin Syed
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Cancel CallForwardAll
wasfailing-CallManager-4.1(3)


Try searching the archieves of this list , they contain usefull
information about the problem you have described below. This is issue is
related to the change notification not working between servers and that
why you not able to remove forwarding from  the phones, several bugs
related to this have been resolved in latest SR for 4.1.3.
 
http://www.archivesat.com/category-55.htm
 
Hope this helps
 
Aman

 
On 4/14/07, Muqeemuddin Syed <muqeems at gmail.com> wrote: 

	We have 7825 running CCM 4.1(3) in a two node cluster, publisher
and subscriber. 
	All IP Phones and end points are registering to the subscriber. 
	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 .
	 
	We had a problem that users were unable to cancel call forward
all. 
	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. 
	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. 
	 
	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).
	All users are now able to cancel call forward all. 
	 
	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. 
	 
	Can anyone confirm if the issue is because our CallManager
Publisher is overloaded. How do we conduct performance monitoring on
Call Managers?

	_______________________________________________
	cisco-voip mailing list 
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip
	
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070416/1cea09ee/attachment.html