[cisco-voip] Callmanager CFWDAll

[David Winter]

Usually resetting just the DB layer monitor service corrects this. 

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
To: Voll, Scott; Ed Leatherman; cisco-voip at puck-nether.net Voip
Sent: Thu Apr 06 17:03:18 2006
Subject: Re: [cisco-voip] Callmanager CFWDAll

Same here!  All of our CFWDAll database inconsistencies went away after 4.1(3)sr2.  You may want restart your CallManagers in your cluster, and then run dblhelper to check your database.

 

Matt

 

________________________________

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Voll, Scott
Sent: Thursday, April 06, 2006 4:44 PM
To: Ed Leatherman; cisco-voip at puck-nether.net Voip
Subject: Re: [cisco-voip] Callmanager CFWDAll

 

I guess knock on wood, we have not had any of these issues with 4.1.3sr2.

 

Scott

 

________________________________

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ed Leatherman
Sent: Thursday, April 06, 2006 11:35 AM
To: cisco-voip at puck-nether.net Voip
Subject: [cisco-voip] Callmanager CFWDAll

 

Anyone having problems with CFWDAll not working every now and then? I've been having trouble with it ever since we upgraded to 4.0.. albeit they are getting less frequent as I apply various SR's. We just had a burp this morning with it and I had to reload DBL Mon this morning to fix it.. was relatively painless but kinda annoying to still be having these problems. So wondering if anyone else is having it happen. We're running 4.1(3)SR3a now.

-- 
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations 

________________________________

CONFIDENTIALITY STATEMENT

This communication and any attachments are CONFIDENTIAL and may be protected by one or more legal privileges. It is intended solely for the use of the addressee identified above. If you are not the intended recipient, any use, disclosure, copying or distribution of this communication is UNAUTHORIZED. Neither this information block, the typed name of the sender, nor anything else in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. If you have received this communication in error, please immediately contact me and delete this communication from your computer. Thank you.

________________________________