To be honest, when something hasn't been fully tested I understand and
agree with the SR restrictions.  I would, however, have concern is that
people who don't have access to this list have fewer good ways to
determine that cisco actually has a fix for this. I think there could be
some use to doing something like MS does where they put out a publicly
searchable KB article that acknowledges the issue and the fix and then
says to contact them if it applies to you. Perhaps just link that on the
firmware download page as a revision note or something (again only for
something this major - - not sure it makes sense to clutter up firmware
download pages for every issue affecting a small smattering of people -
but this one seems pretty global).

I have no problem holding back a patch that's not fully tested in the
interest of keeping some folks from giving themselves even more problems
than they already had - but a way of easily determining that a new load
might be available which patched your problem would be nice.

The Bug Tool might possibly do this - but not sure how easy it'd be to
find without a bug ID....

Ken Johnson
Mgr. Network Services,
Information Technology
LeTourneau University
_________________________________
Join the cisco IP Telecommunications User Group today
http://www.ciptug.org

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com]
Sent: Monday, March 19, 2007 9:57 AM
To: Jonathan Charles
Cc: Johnson, Ken; Corbett Enders; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Do you have phones (7970) still with
incorrecttime? READ ME

You are implying that an SR like that would come to me 

It was proposed putting the load in a new DevPack but unfortunately
anyone who installed the Dev Pack would have had to go back and re- run
the CM DST patch to fix their non-3rd gen phones.  It was decided that
rather than give customer's the loaded gun with instructions saying
"point at foot, pull trigger, yell at me later" we'd just make you yell
at us without putting a hole in your foot first.

-Ryan

[ Post a follow-up to this message ]