They do, it is called the Bug Toolkit... the problem is that it is not as easily searchable as I would like (for some reason it either returns way too many results or none at all)... it would be cool if you could type in a log error message and get a result...
<br><br>Maybe if Cisco let Google run their Bug search engine....?<br><br><br><br>Jonathan<br><br><div><span class="gmail_quote">On 3/19/07, <b class="gmail_sendername">Johnson, Ken</b> <<a href="mailto:kenjohnson@letu.edu">
kenjohnson@letu.edu</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;">To be honest, when something hasn't been fully tested I understand and
<br>agree with the SR restrictions. I would, however, have concern is that<br>people who don't have access to this list have fewer good ways to<br>determine that Cisco actually has a fix for this. I think there could be
<br>some use to doing something like MS does where they put out a publicly<br>searchable KB article that acknowledges the issue and the fix and then<br>says to contact them if it applies to you. Perhaps just link that on the
<br>firmware download page as a revision note or something (again only for<br>something this major - - not sure it makes sense to clutter up firmware<br>download pages for every issue affecting a small smattering of people -
<br>but this one seems pretty global).<br><br>I have no problem holding back a patch that's not fully tested in the<br>interest of keeping some folks from giving themselves even more problems<br>than they already had - but a way of easily determining that a new load
<br>might be available which patched your problem would be nice.<br><br>The Bug Tool might possibly do this - but not sure how easy it'd be to<br>find without a bug ID....<br><br>Ken Johnson<br> Mgr. Network Services,
<br> Information Technology<br> LeTourneau University<br>_________________________________<br>Join the Cisco IP Telecommunications User Group today<br><a href="http://www.ciptug.org">http://www.ciptug.org</a><br><br>-----Original Message-----
<br>From: Ryan Ratliff [mailto:<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>]<br>Sent: Monday, March 19, 2007 9:57 AM<br>To: Jonathan Charles<br>Cc: Johnson, Ken; Corbett Enders; <a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] Do you have phones (7970) still with<br>incorrecttime? READ ME<br><br>You are implying that an SR like that would come to me :)<br><br>It was proposed putting the load in a new DevPack but unfortunately
<br>anyone who installed the Dev Pack would have had to go back and re- run<br>the CM DST patch to fix their non-3rd gen phones. It was decided that<br>rather than give customer's the loaded gun with instructions saying
<br>"point at foot, pull trigger, yell at me later" we'd just make you yell<br>at us without putting a hole in your foot first.<br><br>-Ryan<br></blockquote></div><br>