<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Abebe,<div><br></div><div>Note that change the TCP algorithm will only attempts to conceal underlying network issues. If a user attempts to use the phone while network is down they will have a suboptimal user experience. In my experience most users expect very responsive phones even though they are willing to refresh or retry web pages and checking email. Consider pursuing the network issue.</div><div><br></div><div>Otherwise, TCP retransmit algorithm is on the device configuration page:</div><div><img id="792d1919-db92-4c60-aa99-9dec93d7c7ff" height="55" width="637" apple-width="yes" apple-height="yes" src="cid:B2EEE12D-34AB-4782-B5A4-FE99839C8C26@cisco.com"></div><div><br></div><div><br></div><div>Detect Unified CM Connection Failure: This field determines the sensitivity that the phone has for detecting a connection failure to Cisco Unified Communications Manager (Unified CM), which is the first step before device failover to a backup Unified CM/SRST occurs. Valid values specify Normal (detection of a Unified CM connection failure occurs at the standard system rate) or Delayed (detection of a Unified CM connection failover occurs approximately four times slower than Normal). For faster recognition of a Unified CM connection failure, choose Normal. If you prefer failover to be delayed slightly to give the connection the opportunity to reestablish, choose Delayed. Note that the precise time difference between Normal and Delayed connection failure detection depends on many variables that are constantly changing. Default = Normal This is a required field. Default: Normal</div><div><br></div><div>Regards,</div><div>Wes</div><div><br><div><div>On Sep 16, 2011, at 10:33 AM, Abebe Amare wrote:</div><br class="Apple-interchange-newline">Hi Wes, thanks for your customary brilliant assistance.<br><br>How can I enable Geometric TCP failover?<br><br>best regards,<br><br>Abebe<br><br><div class="gmail_quote">On Fri, Sep 16, 2011 at 5:29 PM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;">Last=TCP-timeout<div><br></div><div>That seems pretty clear. Phone tried to send a message to CUCM and never received TCP ACK. Most likely over a poor network connection (wireless?). Possibly this phone has geometric TCP enabled where others have it disabled?</div>
<div><br></div><div>CSCsm81227 Allow Geometric TCP phone failover to be configurable</div><div><br></div><div>This affects the rate and timing of TCP retries.</div><div><br></div><div>regards,</div><div>Wes</div><div>
<br>
<div><div><div></div><div class="h5"><div>On Sep 16, 2011, at 9:43 AM, Abebe Amare wrote:</div><br>Dears,<br><br>I have included the debug message from one of the phones<br><br> 15:44:19 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br>
14:00:24 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
14:01:05 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 14:01:05 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 14:00:30 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
14:01:01 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 14:01:01 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 18:23:29 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
18:24:30 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br> 18:35:57 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 18:35:57 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout: CTFFile.tlv<br>
18:35:57 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br> 18:35:57 17: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=KeepaliveTO<br> 18:37:22 14: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=UCM-closed-TCP<br>
18:37:22 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br> 18:37:22 14: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=UCM-closed-TCP<br> 18:38:38 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br>
18:41:22 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 18:42:22 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br> 18:42:47 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
18:42:47 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 18:43:53 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br> 18:48:24 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
18:49:20 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 18:49:47 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 18:49:51 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br>
18:50:39 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br> 18:52:16 7: Name=SEP00230432DB6D Load= SCCP75.8-4-2S TFTP Timeout<br> 19:01:44 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
19:02:21 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 19:02:21 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 20:51:25 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
20:51:57 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 20:51:57 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 13:19:45 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
13:20:16 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 13:20:16 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 15:35:48 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
15:36:18 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 15:36:18 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 19:40:18 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
19:40:48 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 19:40:48 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 11:07:04 23: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Reset-Restart<br>
19:20:44 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 19:21:15 18: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Failback<br> 10:18:31 23: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Reset-Restart<br>
14:00:32 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br> 14:00:36 23: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=Reset-Restart<br> 15:51:29 10: Name=SEP00230432DB6D Load= SCCP75.8-4-2S Last=TCP-timeout<br>
<br>regards,<br><br>Abebe<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Abebe Amare</b> <span dir="ltr"><<a href="mailto:abucho@gmail.com" target="_blank">abucho@gmail.com</a>></span><br>
Date: Fri, Sep 16, 2011 at 4:02 PM<br>Subject: 7975 reset problem<br>To: cisco voip <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br><br><br>Dears,<br><br>I have few 7975 IP Phones which reset by themselves randomly. They reside in an office which has a wireless connection to the Call Manager location. All other phones (7911, 7941 and 7962) in the same office don't exhibit the same problem. Could this be a firmware issue?<br>
<br>CM version : 6.1.3.1000-16<br>Device firmware: SCCP75.8-4-2S<br><br>best regards,<br><font color="#888888"><br>Abebe Amare<br><br><br>
</font></div><br></div></div>
_______________________________________________<br>cisco-voip mailing list<div class="im"><br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br></div><div class="im"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div><br></div></div></blockquote></div><br>
</div><br></div></body></html>