<br><font size=2 face="sans-serif">Not the case here as this Subscriber
has many other phones registered is the US with no problems. As Wes
said,I suspect a network issue, but I was hoping to change the keepalive
timer for those phones to decrease the chance that a single missed keepalive
would cause the message to appear and invoke a failover. This way
when a someone hangs up the phone a failover would not be invoked automatically.
That's my understanding of the process anyway......</font>
<br>
<br><font size=2 face="sans-serif">Carlos</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Robert Kulagowski <rkulagow@gmail.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: cisco-voip-bounces@puck.nether.net</font>
<p><font size=1 face="sans-serif">02/05/2008 11:50 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">cisco-voip@puck.nether.net</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [cisco-voip] Phone Keepalives</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Wes Sisk wrote:<br>
> sccp keepalive interval is a cluster wide parameter.<br>
> <br>
> Sounds like you definitely have spotty network connectivity. Have
to <br>
> stabilize that.<br>
<br>
But couldn't it also be a runaway process that's hogging CPU? I just
<br>
ran into a situation where a javaw process was spiking to 100% often <br>
enough that phones connected to that subscriber were showing "CM Down".<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</tt></font>
<br>