<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3059" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>I guess it would be nice if the system could recover from
temporary connectivity issues. ;)</FONT></DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>...there's no such thing as a bad timbit...<BR></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=rratliff@cisco.com href="mailto:rratliff@cisco.com">Ryan Ratliff</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=ealeatherman@gmail.com
href="mailto:ealeatherman@gmail.com">Ed Leatherman</A> ; <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">ciscovoip</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, April 03, 2007 10:19
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] Callforward all
keeps getting stuck</DIV>
<DIV><BR></DIV>/rant on<BR>The ONLY time database replication will cause an
issue is when your <BR>publisher goes away and subs start using their
local database.<BR><BR>AT NO OTHER POINT will it cause issues. This is
especially true for <BR>CFA failures, since if your pub is down CFA is
not going to work anyhow.<BR><BR>You may have connectivity issues where DB
replication failure is a <BR>symptom, but it is just that, a symptom
(and a pretty minor one at <BR>that). If your subs cannot connect
to the pub you've got much bigger <BR>issues than replication.
DBLHelper is nice and all, but all it shows <BR>you is if your SQL jobs
are running (on the replication tab anyway).<BR><BR>I swear a part of my inner
troubleshooter dies a little bit every <BR>time I see somebody bust out
DBLHelper as the first step in <BR>troubleshooting a completely
unrelated problem. "My MOH is broken, <BR>but DBLHelper says
everything is fine!"... "I put this firewall <BR>between my CMs
and now I can't make any calls between those servers, <BR>but DBLHelper
is all smileys!"<BR><BR>/rant off<BR><BR>If you go searching the archives for
this list I've sent several <BR>emails in the past on how to
troubleshoot CFA failures in 4.x. There <BR>were some pretty big
architectural changes that have exposed some <BR>issues with change
notification. Thankfully they go away in 5.x.<BR><BR><BR>-Ryan<BR><BR>On
Apr 3, 2007, at 9:50 AM, Lelio Fulgenzi wrote:<BR><BR>I'm convinced that it
has to do with the replication of databases and <BR>nothing to do with
CallManager version.<BR><BR>Even the dblhelper tool can't illustrate with any
confidence that <BR>your databases are in sync. It might work to show
you that they are <BR>out of sync, but if you see all smiley faces,
don't trust your cat's <BR>life on
it.<BR><BR><BR>------------------------------------------------------------------------
<BR>--------<BR>Lelio Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of
Guelph * Guelph, Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>...there's
no such thing as a bad timbit...<BR>----- Original Message -----<BR>From: Ed
Leatherman<BR>To: ciscovoip<BR>Sent: Tuesday, April 03, 2007 9:46
AM<BR>Subject: [cisco-voip] Callforward all keeps getting
stuck<BR><BR>Hello,<BR><BR>We've had an ongoing problem with the callforward
all feature on the <BR>phones ever since we went from ccm 3.x for 4.x.
usually it would only <BR>happen maybe once every couple months... while
still very annoying we <BR>could live with it. I've probably opened 4
different TAC SR's on it, <BR>with little success in actually fixing
it.<BR><BR>Basically we have people who forward their lines to another number
or <BR>to voicemail, and then they cannot remove the forwarding, nor can
we <BR>do it from CCMadmin.<BR><BR>For some reason the past week i've
had it happen almost everyday. The <BR>work around is very easy, just
restarting the DBL monitor service on <BR>all the nodes in the cluster
fixes the problem. But its still an <BR>interuption of service for alot
of departments. I'm going to open yet <BR>another TAC case on it.. but
does anyone have any suggestions on a <BR>possible cause? I don't
believe we're having a networking problem but <BR>i'm open to
suggestions. Currently running ccm 4.1.3sr4d.<BR><BR>-- <BR>Ed
Leatherman<BR>Senior Voice Engineer<BR>West Virginia
University<BR>Telecommunications and Network
Operations<BR><BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>