<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <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<br>
<b>Subject:</b> Re: [cisco-voip] DST Issues - UCM 7.0(2)<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>Hi Justin,<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"><jsteinberg@gmail.com></a> wrote:<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'>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>
<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-left:.5in'>On Sun, Mar 8, 2009 at 6:57 PM, Wes
Sisk <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-left:.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> <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-left:.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>
<o:p></o:p></p>
<pre style='margin-left:.5in'>Is it worth opening a case for this if you run into it, or just start<o:p></o:p></pre><pre
style='margin-left:.5in'>applying the work around and keep an eye on the bug id? I seem to be<o:p></o:p></pre><pre
style='margin-left:.5in'>hitting it also on cm 5.1.3.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.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:<o:p></o:p></pre><pre
style='margin-left:.5in'> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre style='margin-left:
.5in'>Investigation is in progress under CSCsy25150.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>/Wes<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>On Sunday, March 08, 2009 3:54:33 PM, Erick Bergquist <a
href="mailto:erickbee@gmail.com" target="_blank"><erickbee@gmail.com></a><o:p></o:p></pre><pre
style='margin-left:.5in'>wrote:<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'>Well, I've done the old date/time group offset workaround for one<o:p></o:p></pre><pre
style='margin-left:.5in'>phone which fixed the one while I work with TAC on this before doing<o:p></o:p></pre><pre
style='margin-left:.5in'>the old workaround for the rest.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.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:<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'>Probably, and I thought we would be past all these DST issues on newer<o:p></o:p></pre><pre
style='margin-left:.5in'>6.x and 7.x versions... I might have to do the date/time group offset<o:p></o:p></pre><pre
style='margin-left:.5in'>fix here shortly as a workaround.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>On Sun, Mar 8, 2009 at 2:06 PM, Matthew Linsemier<o:p></o:p></pre><pre
style='margin-left:.5in'><a href="mailto:mlinsemier@apassurance.com"
target="_blank"><mlinsemier@apassurance.com></a> wrote:<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'>Sounds like we have the same issues... I went through similar steps, reset<o:p></o:p></pre><pre
style='margin-left:.5in'>the phones, did a hard power of some test phones, and still the same issues.<o:p></o:p></pre><pre
style='margin-left:.5in'>Resetting the servers didn't resolve the issue either. I am assuming it's a<o:p></o:p></pre><pre
style='margin-left:.5in'>CallManager issue, as all of the other 7960 phones we have on our old<o:p></o:p></pre><pre
style='margin-left:.5in'>CallManager 4.1(3) Cluster running the same version of firmware are the<o:p></o:p></pre><pre
style='margin-left:.5in'>correct time.<o:p></o:p></pre><pre style='margin-left:
.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Matt<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'>On 3/8/09 1:00 PM, "Erick Bergquist" <a
href="mailto:erickbee@gmail.com" target="_blank"><erickbee@gmail.com></a> wrote:<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>The 7960/7940 model phones get their time directly from the Call<o:p></o:p></pre><pre
style='margin-left:.5in'>Manager server (those early models don't do NTP or figure the timezone<o:p></o:p></pre><pre
style='margin-left:.5in'>out on their own like the newer generation phones). I have the same<o:p></o:p></pre><pre
style='margin-left:.5in'>issue on a 6.1.2.1000-13 system with 7940/7960s I am trying to figure<o:p></o:p></pre><pre
style='margin-left:.5in'>out. I have not reset the servers yet but the time and timezone on the<o:p></o:p></pre><pre
style='margin-left:.5in'>servers is correct and date/time group is right and resetting the<o:p></o:p></pre><pre
style='margin-left:.5in'>phones so far hasn't made a difference.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>On Sun, Mar 8, 2009 at 12:38 PM, Matthew Linsemier<o:p></o:p></pre><pre
style='margin-left:.5in'><a href="mailto:mlinsemier@apassurance.com"
target="_blank"><mlinsemier@apassurance.com></a> wrote:<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'>All,<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'>This morning after the DST changes last evening, I have noticed that the<o:p></o:p></pre><pre
style='margin-left:.5in'>time on my UCM 7.0(2) phones are off by an hour. The time on our<o:p></o:p></pre><pre
style='margin-left:.5in'>CallManager 4.1(3) phones are all correct (we are currently in the middle of<o:p></o:p></pre><pre
style='margin-left:.5in'>a migration).<o:p></o:p></pre><pre style='margin-left:
.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>I have verified that the NTP settings are correct on the UCM 7.0(2) cluster<o:p></o:p></pre><pre
style='margin-left:.5in'>and the servers are showing the correct time when you run system settings<o:p></o:p></pre><pre
style='margin-left:.5in'>under OS serviceability, but the phones not syncing up. I have verified all<o:p></o:p></pre><pre
style='margin-left:.5in'>of the date/time groups and made sure that they also have an NTP reference.<o:p></o:p></pre><pre
style='margin-left:.5in'> The phones in question are all 7960šs running the latest firmware. I have<o:p></o:p></pre><pre
style='margin-left:.5in'>not had a chance to test the few 7965šs that we have. As a last resort I<o:p></o:p></pre><pre
style='margin-left:.5in'>restarted both of the servers in the cluster, but no change.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Does anyone have any ideas on what could be going on before I give TAC a<o:p></o:p></pre><pre
style='margin-left:.5in'>call. I figured I would ask if anyone had any ideas here.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Thanks,<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Matt<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>________________________________<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>CONFIDENTIALITY STATEMENT<o:p></o:p></pre><pre
style='margin-left:.5in'>This communication and any attachments are CONFIDENTIAL and may be protected<o:p></o:p></pre><pre
style='margin-left:.5in'>by one or more legal privileges. It is intended solely for the use of the<o:p></o:p></pre><pre
style='margin-left:.5in'>addressee identified above. If you are not the intended recipient, any use,<o:p></o:p></pre><pre
style='margin-left:.5in'>disclosure, copying or distribution of this communication is UNAUTHORIZED.<o:p></o:p></pre><pre
style='margin-left:.5in'>Neither this information block, the typed name of the sender, nor anything<o:p></o:p></pre><pre
style='margin-left:.5in'>else in this message is intended to constitute an electronic signature<o:p></o:p></pre><pre
style='margin-left:.5in'>unless a specific statement to the contrary is included in this message. If<o:p></o:p></pre><pre
style='margin-left:.5in'>you have received this communication in error, please immediately contact me<o:p></o:p></pre><pre
style='margin-left:.5in'>and delete this communication from your computer. Thank you.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>________________________________<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>_______________________________________________<o:p></o:p></pre><pre
style='margin-left:.5in'>cisco-voip mailing list<o:p></o:p></pre><pre
style='margin-left:.5in'><a href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre
style='margin-left:.5in'><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'>CONFIDENTIALITY STATEMENT<o:p></o:p></pre><pre
style='margin-left:.5in'>This communication and any attachments are CONFIDENTIAL and may<o:p></o:p></pre><pre
style='margin-left:.5in'>be protected by one or more legal privileges. It is intended<o:p></o:p></pre><pre
style='margin-left:.5in'>solely for the use of the addressee identified above. If you<o:p></o:p></pre><pre
style='margin-left:.5in'>are not the intended recipient, any use, disclosure, copying<o:p></o:p></pre><pre
style='margin-left:.5in'>or distribution of this communication is UNAUTHORIZED. Neither<o:p></o:p></pre><pre
style='margin-left:.5in'>this information block, the typed name of the sender, nor<o:p></o:p></pre><pre
style='margin-left:.5in'>anything else in this message is intended to constitute an<o:p></o:p></pre><pre
style='margin-left:.5in'>electronic signature unless a specific statement to the<o:p></o:p></pre><pre
style='margin-left:.5in'>contrary is included in this message. If you have received this<o:p></o:p></pre><pre
style='margin-left:.5in'>communication in error, please immediately contact me and delete<o:p></o:p></pre><pre
style='margin-left:.5in'>this communication from your computer. Thank you.<o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>_______________________________________________<o:p></o:p></pre><pre
style='margin-left:.5in'>cisco-voip mailing list<o:p></o:p></pre><pre
style='margin-left:.5in'><a href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre
style='margin-left:.5in'><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'>_______________________________________________<o:p></o:p></pre><pre
style='margin-left:.5in'>cisco-voip mailing list<o:p></o:p></pre><pre
style='margin-left:.5in'><a href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre
style='margin-left:.5in'><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre
style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre
style='margin-left:.5in'> <o:p></o:p></pre></blockquote>
<pre style='margin-left:.5in'> <o:p></o:p></pre>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><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><o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
</div>
<br><br><table bgcolor=white style="color:black"><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></table></body>
</html>