<div>You meant 1st gen phones right Wes?</div>
<div> </div>
<div>When do you think we will see a patch for CM 6.1?</div>
<div> </div>
<div>TIA</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Sun, Mar 8, 2009 at 7:33 PM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div text="#000000" bgcolor="#ffffff">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><font color="#888888"><br>/Wes</font>
<div>
<div></div>
<div class="h5"><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>
<blockquote type="cite">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><br>
<div class="gmail_quote">On Sun, Mar 8, 2009 at 6:57 PM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div text="#000000" bgcolor="#ffffff">yes, it's in all 5.x-7.x.<br><br>TAC is only going to step you through the workaround.<br><font color="#888888"><br>/Wes</font>
<div>
<div><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>
<blockquote type="cite"><pre>Is it worth opening a case for this if you run into it, or just start
applying the work around and keep an eye on the bug id? I seem to be
hitting it also on cm 5.1.3.
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>
<blockquote type="cite"><pre>Investigation is in progress under CSCsy25150.
/Wes
On Sunday, March 08, 2009 3:54:33 PM, Erick Bergquist <a href="mailto:erickbee@gmail.com" target="_blank"><erickbee@gmail.com></a>
wrote:
Well, I've done the old date/time group offset workaround for one
phone which fixed the one while I work with TAC on this before doing
the old workaround for the rest.
On Sun, Mar 8, 2009 at 1:10 PM, Erick Bergquist <a href="mailto:erickbee@gmail.com" target="_blank"><erickbee@gmail.com></a> wrote:
Probably, and I thought we would be past all these DST issues on newer
6.x and 7.x versions... I might have to do the date/time group offset
fix here shortly as a workaround.
On Sun, Mar 8, 2009 at 2:06 PM, Matthew Linsemier
<a href="mailto:mlinsemier@apassurance.com" target="_blank"><mlinsemier@apassurance.com></a> wrote:
Sounds like we have the same issues... I went through similar steps, reset
the phones, did a hard power of some test phones, and still the same issues.
Resetting the servers didn't resolve the issue either. I am assuming it's a
CallManager issue, as all of the other 7960 phones we have on our old
CallManager 4.1(3) Cluster running the same version of firmware are the
correct time.
Matt
On 3/8/09 1:00 PM, "Erick Bergquist" <a href="mailto:erickbee@gmail.com" target="_blank"><erickbee@gmail.com></a> wrote:
The 7960/7940 model phones get their time directly from the Call
Manager server (those early models don't do NTP or figure the timezone
out on their own like the newer generation phones). I have the same
issue on a 6.1.2.1000-13 system with 7940/7960s I am trying to figure
out. I have not reset the servers yet but the time and timezone on the
servers is correct and date/time group is right and resetting the
phones so far hasn't made a difference.
On Sun, Mar 8, 2009 at 12:38 PM, Matthew Linsemier
<a href="mailto:mlinsemier@apassurance.com" target="_blank"><mlinsemier@apassurance.com></a> wrote:
All,
This morning after the DST changes last evening, I have noticed that the
time on my UCM 7.0(2) phones are off by an hour. The time on our
CallManager 4.1(3) phones are all correct (we are currently in the middle of
a migration).
I have verified that the NTP settings are correct on the UCM 7.0(2) cluster
and the servers are showing the correct time when you run system settings
under OS serviceability, but the phones not syncing up. I have verified all
of the date/time groups and made sure that they also have an NTP reference.
The phones in question are all 7960¹s running the latest firmware. I have
not had a chance to test the few 7965¹s that we have. As a last resort I
restarted both of the servers in the cluster, but no change.
Does anyone have any ideas on what could be going on before I give TAC a
call. I figured I would ask if anyone had any ideas here.
Thanks,
Matt
________________________________
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may be protected
by one or more legal privileges. It is intended solely for the use of the
addressee identified above. If you are not the intended recipient, any use,
disclosure, copying or distribution of this communication is UNAUTHORIZED.
Neither this information block, the typed name of the sender, nor anything
else in this message is intended to constitute an electronic signature
unless a specific statement to the contrary is included in this message. If
you have received this communication in error, please immediately contact me
and delete this communication from your computer. Thank you.
________________________________
_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended
solely for the use of the addressee identified above. If you
are not the intended recipient, any use, disclosure, copying
or distribution of this communication is UNAUTHORIZED. Neither
this information block, the typed name of the sender, nor
anything else in this message is intended to constitute an
electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete
this communication from your computer. Thank you.
_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre></blockquote><pre> </pre></blockquote><br></div></div></div><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><br><br></blockquote></div><br></blockquote><br></div></div></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>