<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16890" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=234213313-28092009><FONT face=Arial
color=#0000ff size=2>Greetings, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=234213313-28092009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=234213313-28092009><FONT face=Arial
color=#0000ff size=2>I also upgraded to 6.1.4 SU1 this past Saturday
with no issues--so far anyway. I did it to avoid DST issues and because of
this field notice I received Thurs last week. Had to do it a week
earlier than I was planning:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=234213313-28092009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=234213313-28092009><BR>Cisco Notification
Service Alert:
<BR>________________________________________________________________________________<BR><BR>Cisco
Notification Alert -7800 MCS Servers_Daily-09/24/2009 08:29 GMT<BR><BR><BR>Field
Notices-Cisco 7800 Series Media Convergence Servers-09/23/2009 08:13
GMT-09/24/2009 07:30 GMT<BR><BR><BR>Title: Field Notice: FN - 63255 -
MCS-7825-I2 & IBM x306m, BIOS 1.42 & 1.43 error prevents a system from
booting if rebooted after October 1, 2009 [Cisco 7800 Series Media
Convergence Servers]<BR>Url: <A
title=blocked::http://www.cisco.com/en/US/customer/ts/fn/632/fn63255.html
href="blocked::http://www.cisco.com/en/US/customer/ts/fn/632/fn63255.html">http://www.cisco.com/en/US/customer/ts/fn/632/fn63255.html</A><BR>Description:
A defect in the HostRAID BIOS 2106 (included with System BIOS version 1.42 and
1.43) will prevent a server from booting successfully if the server is rebooted
after October 1, 2009. This is caused by a defect in the IBM BIOS and is
documented in IBM RETAIN Tip: H182636 <BR>Date: 2009-09-23
06:55:21.0<BR><BR></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Stu
Packett<BR><B>Sent:</B> Friday, September 25, 2009 8:58 PM<BR><B>To:</B> Scott
Voll<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] anyone upgraded to Cm 6.1.4a?<BR></FONT><BR></DIV>
<DIV></DIV>I upgraded from 6.1.2 to 6.1.4 SU1 last weekend and have not had any
technical problems with it. I too upgraded to avoid DST issues. The
only calls we got were from color phone users noticing that the gray bar on
their name was gone and some that felt the phone display looked "funny" during a
call. It's all a cosmetic adjustment for your color phone users.<BR><BR>
<DIV class=gmail_quote>On Fri, Sep 25, 2009 at 3:03 PM, Scott Voll <SPAN
dir=ltr><<A href="mailto:svoll.voip@gmail.com"
target=_blank>svoll.voip@gmail.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">I'm
still on 6.1.2.1106 and don't want to deal with DST issues.
<DIV><BR></DIV>
<DIV>So I'm looking at 6.1.4a. any comments?</DIV>
<DIV><BR></DIV><FONT color=#888888>
<DIV>Scott</DIV></FONT><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><DIV> </DIV>CONFIDENTIALITY NOTICE: The information contained in this email including attachments is intended for the specific delivery to and use by the individual(s) to whom it is addressed, and includes information which should be considered as private and confidential. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you have received this message in error, please reply to the sender immediately and delete the original message and any copy of it from your computer system. Thank you.</BODY></HTML>