<div>ya, but all your 2nd and 3rd gen phone have the wrong time now. Right?</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Sun, Mar 8, 2009 at 8:17 PM, Biffle, Gerrad <span dir="ltr"><<a href="mailto:Gerrad.Biffle@greensboro-nc.gov">Gerrad.Biffle@greensboro-nc.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang="EN-US" bgcolor="white" vlink="purple" link="blue">
<div>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d">I’m running into the same problem here – glad I logged in tonight. What I’ve done and it appears to have worked – was change the TimeZone on my Date/Time group from EST to Atlantic. Reset my phone and it shows the correct time. Seems this saves time from creating new groups/pools, reassigning phones, etc. – and less to change back after a fix is released.</span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p style="MARGIN-LEFT: 0.5in"><b><span style="FONT-SIZE: 10pt; COLOR: windowtext">From:</span></b><span style="FONT-SIZE: 10pt; COLOR: windowtext"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Wes Sisk<br>
<b>Sent:</b> Sunday, March 08, 2009 10:34 PM<br><b>To:</b> Justin Steinberg<br><b>Cc:</b> cisco-voip voyp list
<div class="im"><br><b>Subject:</b> Re: [cisco-voip] DST Issues - UCM 7.0(2)</div></span>
<p></p></p></div></div>
<p style="MARGIN-LEFT: 0.5in"> </p>
<p style="MARGIN-LEFT: 0.5in">Hi Justin,
<div>
<div></div>
<div class="h5"><br><br>Thanks for pointing out the missing information from Cisco.com. I released the RNE so it should be visible in Bug Toolkit after tonight's load.<br><br>Details are still a bit preliminary so I do not want to provide dis-information. At this moment (10:19 EDT) my understating of the options are:<br>
<br>1. do nothing - for 2nd gen phones registered to CUCM time will be correct after next weekend<br>2. create new datetimegroups and devicepools. reassign 2nd gen phones- this will correct the condition for this week but has to be undone next weekend<br>
3. wait for patch - a patch is in progress.<br><br>I will update the list as I learn more.<br><br>/Wes<br><br>On Sunday, March 08, 2009 9:45:44 PM, Justin Steinberg <a href="mailto:jsteinberg@gmail.com" target="_blank"><jsteinberg@gmail.com></a> wrote:<br>
<br></div></div>
<p></p>
<div>
<div></div>
<div class="h5">
<p style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0in">Wes,<br><br>For those who are not opening a TAC case on this, can you please update the list when you receive information related to the permanent fix. At this time, the DDTS information is under review when viewed with my CCO login.<br>
<br>Thank you.<br><br>Justin<br><br></p>
<div>
<p style="MARGIN-LEFT: 0.5in">On Sun, Mar 8, 2009 at 6:57 PM, Wes Sisk <<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>> wrote:</p>
<div>
<p style="MARGIN-LEFT: 0.5in">yes, it's in all 5.x-7.x.<br><br>TAC is only going to step you through the workaround.<br><span style="COLOR: #888888"><br>/Wes</span> </p>
<div>
<div>
<p style="MARGIN-LEFT: 0.5in"><br><br>On Sunday, March 08, 2009 6:48:31 PM, Ed Leatherman <a href="mailto:ealeatherman@gmail.com" target="_blank"><ealeatherman@gmail.com></a> wrote:<br><br></p><pre style="MARGIN-LEFT: 0.5in">
Is it worth opening a case for this if you run into it, or just start</pre><pre style="MARGIN-LEFT: 0.5in">applying the work around and keep an eye on the bug id? I seem to be</pre><pre style="MARGIN-LEFT: 0.5in">hitting it also on cm 5.1.3.</pre>
<pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">On Sun, Mar 8, 2009 at 4:27 PM, Wes Sisk <a href="mailto:wsisk@cisco.com" target="_blank"><wsisk@cisco.com></a> wrote:</pre><pre style="MARGIN-LEFT: 0.5in">
</pre>
<blockquote style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt"><pre style="MARGIN-LEFT: 0.5in">Investigation is in progress under CSCsy25150.</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">/Wes</pre>
<pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">On Sunday, March 08, 2009 3:54:33 PM, Erick Bergquist <a href="mailto:erickbee@gmail.com" target="_blank"><erickbee@gmail.com></a></pre><pre style="MARGIN-LEFT: 0.5in">
wrote:</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">Well, I've done the old date/time group offset workaround for one</pre><pre style="MARGIN-LEFT: 0.5in">phone which fixed the one while I work with TAC on this before doing</pre>
<pre style="MARGIN-LEFT: 0.5in">the old workaround for the rest.</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">On Sun, Mar 8, 2009 at 1:10 PM, Erick Bergquist <a href="mailto:erickbee@gmail.com" target="_blank"><erickbee@gmail.com></a> wrote:</pre>
<pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">Probably, and I thought we would be past all these DST issues on newer</pre><pre style="MARGIN-LEFT: 0.5in">6.x and 7.x versions... I might have to do the date/time group offset</pre>
<pre style="MARGIN-LEFT: 0.5in">fix here shortly as a workaround.</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">On Sun, Mar 8, 2009 at 2:06 PM, Matthew Linsemier</pre><pre style="MARGIN-LEFT: 0.5in">
<a href="mailto:mlinsemier@apassurance.com" target="_blank"><mlinsemier@apassurance.com></a> wrote:</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">
Sounds like we have the same issues... I went through similar steps, reset</pre><pre style="MARGIN-LEFT: 0.5in">the phones, did a hard power of some test phones, and still the same issues.</pre><pre style="MARGIN-LEFT: 0.5in">
Resetting the servers didn't resolve the issue either. I am assuming it's a</pre><pre style="MARGIN-LEFT: 0.5in">CallManager issue, as all of the other 7960 phones we have on our old</pre><pre style="MARGIN-LEFT: 0.5in">
CallManager 4.1(3) Cluster running the same version of firmware are the</pre><pre style="MARGIN-LEFT: 0.5in">correct time.</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">Matt</pre><pre style="MARGIN-LEFT: 0.5in">
</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">On 3/8/09 1:00 PM, "Erick Bergquist" <a href="mailto:erickbee@gmail.com" target="_blank"><erickbee@gmail.com></a> wrote:</pre><pre style="MARGIN-LEFT: 0.5in">
</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">The 7960/7940 model phones get their time directly from the Call</pre><pre style="MARGIN-LEFT: 0.5in">Manager server (those early models don't do NTP or figure the timezone</pre>
<pre style="MARGIN-LEFT: 0.5in">out on their own like the newer generation phones). I have the same</pre><pre style="MARGIN-LEFT: 0.5in">issue on a 6.1.2.1000-13 system with 7940/7960s I am trying to figure</pre><pre style="MARGIN-LEFT: 0.5in">
out. I have not reset the servers yet but the time and timezone on the</pre><pre style="MARGIN-LEFT: 0.5in">servers is correct and date/time group is right and resetting the</pre><pre style="MARGIN-LEFT: 0.5in">phones so far hasn't made a difference.</pre>
<pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">On Sun, Mar 8, 2009 at 12:38 PM, Matthew Linsemier</pre><pre style="MARGIN-LEFT: 0.5in"><a href="mailto:mlinsemier@apassurance.com" target="_blank"><mlinsemier@apassurance.com></a> wrote:</pre>
<pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">All,</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">This morning after the DST changes last evening, I have noticed that the</pre>
<pre style="MARGIN-LEFT: 0.5in">time on my UCM 7.0(2) phones are off by an hour. The time on our</pre><pre style="MARGIN-LEFT: 0.5in">CallManager 4.1(3) phones are all correct (we are currently in the middle of</pre><pre style="MARGIN-LEFT: 0.5in">
a migration).</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">I have verified that the NTP settings are correct on the UCM 7.0(2) cluster</pre><pre style="MARGIN-LEFT: 0.5in">and the servers are showing the correct time when you run system settings</pre>
<pre style="MARGIN-LEFT: 0.5in">under OS serviceability, but the phones not syncing up. I have verified all</pre><pre style="MARGIN-LEFT: 0.5in">of the date/time groups and made sure that they also have an NTP reference.</pre>
<pre style="MARGIN-LEFT: 0.5in"> The phones in question are all 7960¹s running the latest firmware. I have</pre><pre style="MARGIN-LEFT: 0.5in">not had a chance to test the few 7965¹s that we have. As a last resort I</pre>
<pre style="MARGIN-LEFT: 0.5in">restarted both of the servers in the cluster, but no change.</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">Does anyone have any ideas on what could be going on before I give TAC a</pre>
<pre style="MARGIN-LEFT: 0.5in">call. I figured I would ask if anyone had any ideas here.</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">Thanks,</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">
Matt</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">________________________________</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">CONFIDENTIALITY STATEMENT</pre>
<pre style="MARGIN-LEFT: 0.5in">This communication and any attachments are CONFIDENTIAL and may be protected</pre><pre style="MARGIN-LEFT: 0.5in">by one or more legal privileges. It is intended solely for the use of the</pre>
<pre style="MARGIN-LEFT: 0.5in">addressee identified above. If you are not the intended recipient, any use,</pre><pre style="MARGIN-LEFT: 0.5in">disclosure, copying or distribution of this communication is UNAUTHORIZED.</pre>
<pre style="MARGIN-LEFT: 0.5in">Neither this information block, the typed name of the sender, nor anything</pre><pre style="MARGIN-LEFT: 0.5in">else in this message is intended to constitute an electronic signature</pre><pre style="MARGIN-LEFT: 0.5in">
unless a specific statement to the contrary is included in this message. If</pre><pre style="MARGIN-LEFT: 0.5in">you have received this communication in error, please immediately contact me</pre><pre style="MARGIN-LEFT: 0.5in">
and delete this communication from your computer. Thank you.</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">________________________________</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">
_______________________________________________</pre><pre style="MARGIN-LEFT: 0.5in">cisco-voip mailing list</pre><pre style="MARGIN-LEFT: 0.5in"><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></pre>
<pre style="MARGIN-LEFT: 0.5in"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">
</pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">CONFIDENTIALITY STATEMENT</pre><pre style="MARGIN-LEFT: 0.5in">This communication and any attachments are CONFIDENTIAL and may</pre>
<pre style="MARGIN-LEFT: 0.5in">be protected by one or more legal privileges. It is intended</pre><pre style="MARGIN-LEFT: 0.5in">solely for the use of the addressee identified above. If you</pre><pre style="MARGIN-LEFT: 0.5in">
are not the intended recipient, any use, disclosure, copying</pre><pre style="MARGIN-LEFT: 0.5in">or distribution of this communication is UNAUTHORIZED. Neither</pre><pre style="MARGIN-LEFT: 0.5in">this information block, the typed name of the sender, nor</pre>
<pre style="MARGIN-LEFT: 0.5in">anything else in this message is intended to constitute an</pre><pre style="MARGIN-LEFT: 0.5in">electronic signature unless a specific statement to the</pre><pre style="MARGIN-LEFT: 0.5in">
contrary is included in this message. If you have received this</pre><pre style="MARGIN-LEFT: 0.5in">communication in error, please immediately contact me and delete</pre><pre style="MARGIN-LEFT: 0.5in">this communication from your computer. Thank you.</pre>
<pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">_______________________________________________</pre><pre style="MARGIN-LEFT: 0.5in">
cisco-voip mailing list</pre><pre style="MARGIN-LEFT: 0.5in"><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></pre><pre style="MARGIN-LEFT: 0.5in"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></pre>
<pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in">_______________________________________________</pre><pre style="MARGIN-LEFT: 0.5in">cisco-voip mailing list</pre>
<pre style="MARGIN-LEFT: 0.5in"><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></pre><pre style="MARGIN-LEFT: 0.5in"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></pre>
<pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre><pre style="MARGIN-LEFT: 0.5in"> </pre></blockquote><pre style="MARGIN-LEFT: 0.5in"> </pre>
<p style="MARGIN-LEFT: 0.5in"> </p></div></div></div>
<p style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0in"><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></p></div>
<p style="MARGIN-LEFT: 0.5in"> </p>
<p style="MARGIN-LEFT: 0.5in"> </p></div></div></p></div><br><br>
<table style="COLOR: black" bgcolor="white">
<tbody>
<tr>
<td><br>=======================================================<br>Please note that email sent to and from this address is subject <br>to the North Carolina Public Records Law and may be disclosed to <br>third parties.</td>
</tr></tbody></table></div><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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>