<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16414" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=688043501-16042007><FONT face=Arial
color=#0000ff size=2>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.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Aman
Chugh<BR><B>Sent:</B> Saturday, April 14, 2007 5:03 AM<BR><B>To:</B> Muqeemuddin
Syed<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] Cancel CallForwardAll
wasfailing-CallManager-4.1(3)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV><A
href="http://www.archivesat.com/category-55.htm">http://www.archivesat.com/category-55.htm</A></DIV>
<DIV> </DIV>
<DIV>Hope this helps</DIV>
<DIV> </DIV>
<DIV>Aman<BR><BR> </DIV>
<DIV><SPAN class=gmail_quote>On 4/14/07, <B class=gmail_sendername>Muqeemuddin
Syed</B> <<A href="mailto:muqeems@gmail.com">muqeems@gmail.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<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><BR>_______________________________________________<BR>cisco-voip
mailing list <BR><A onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
onclick="return top.js.OpenExtLink(window,event,this)"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR></BLOCKQUOTE></DIV><BR></BODY></HTML>