Thanks for the info guys<br><br><div><span class="gmail_quote">On 1/19/07, <b class="gmail_sendername">Erick Bergquist</b> <<a href="mailto:erickbe@yahoo.com">erickbe@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I had opened a case for a client asking about this for IPCC, and there's going to a notice going out in a week or so that covers this. But for IPCC Express/CRS I am being told that 3.5(4)SR2 will have fix, and anything lower will not so you'll need to upgrade. The SR2 will have a JRE update also for the DST changes.
<br><br>IPCC 4.0(1), 4.0(2), 4.0(3), 4.0(4), 4.5(1), 4.5(2) will need the OS update and Sun JRE DST patch.<br>IPCC 4.1(1) won't have to do anything done.<br><br>----- Original Message ----<br>From: Ryan Ratliff <<a href="mailto:rratliff@cisco.com">
rratliff@cisco.com</a>><br>To: "Voll, Scott" <<a href="mailto:Scott.Voll@wesd.org">Scott.Voll@wesd.org</a>><br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Sent: Friday, January 19, 2007 10:00:23 AM
<br>Subject: Re: [cisco-voip] Change date in CallManager<br><br>Yes, the Win2k fix will be included in an OS patch. There should be<br>a notice going out soon with more specifics.<br><br>-Ryan<br><br>On Jan 19, 2007, at 10:46 AM, Voll, Scott wrote:
<br><br>If we are only using one time zone, will that affect us?<br><br>Since M$ isn't going to fix this in patch(windows 2000), will cisco fix<br>it in an OS SR?<br><br>Thanks<br><br>Scott<br><br>-----Original Message-----
<br>From: Ryan Ratliff [mailto:<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>]<br>Sent: Friday, January 19, 2007 7:03 AM<br>To: Ed Leatherman<br>Cc: Voll, Scott; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a><br>Subject: Re: [cisco-voip] Change date in CallManager<br><br>Haven't looked into the CM bug but I assume it is because you can set<br>different time zones in your CM date/time groups. CM will obviously<br>need to adjust those if you have them selected.
<br><br>-Ryan<br><br>On Jan 18, 2007, at 7:49 PM, Ed Leatherman wrote:<br><br>I was going on the assumption that since they had a engineering<br>special for that there was something internal to callmanager<br>application that needed adjusted, on top of the MS update.
<br><br>On 1/18/07, Voll, Scott <<a href="mailto:Scott.Voll@wesd.org">Scott.Voll@wesd.org</a>> wrote:<br>What about using the M$ TZedit? I'm guessing not supported by Cisco<br>TAC?<br><br><br>What does CM have to do with the Time Zone? I thought it used the OS
<br>time / Date.<br><br><br>Scott<br><br><br><a href="http://support.microsoft.com/kb/914387">http://support.microsoft.com/kb/914387</a><br><br><br><br><br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net
</a> [mailto: cisco-voip-<br><a href="mailto:bounces@puck.nether.net">bounces@puck.nether.net</a>] On Behalf Of Ed Leatherman<br>Sent: Thursday, January 18, 2007 1:05 PM<br>To: Robert Kulagowski<br>Cc: <a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] Change date in CallManager<br><br><br>Anyone have an ETA when this will come out as an official SR?<br>Hopefully soon enough that it can sit and stew on CCO for a while
<br>before we have to load it.<br><br>In short we are going to be covered with CallManager versions 3.3(5)ES56<br>4.1(3)ES89.1 4.2(1)ES38 4.2(3)ES11.1<br><br>All the other versions of CallManager will not have this bug fix.
<br>"<br><br>My problem is that I don't like to run a SR until it's been out for a<br>few weeks to ensure that it's not withdrawn the day after I install it.<br> 4.1.3sr4d was looking good, but now it looks like I've got to
<br>wait at<br>least until ES89.1 comes out. The OS side of the fix is already in<br>2000.4.4sr2. It's going to be interesting...<br><br>--<br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations
<br><br><br><br><br>--<br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations<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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br><br><br><br>
<br>____________________________________________________________________________________<br>Never Miss an Email<br>Stay connected with Yahoo! Mail on your mobile. Get started!<br><a href="http://mobile.yahoo.com/services?promote=mail">
http://mobile.yahoo.com/services?promote=mail</a><br><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">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations