<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceName"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:blue;
        text-decoration:underline;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I like that idea too. Like CCIE’s
can open a P2 case on line, puck.nether.net users can open a P1 case =)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Scott<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Jonathan Charles<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, March 19, 2007 8:07
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Ryan Ratliff<br>
<b><span style='font-weight:bold'>Cc:</span></b> cisco-voip@puck.nether.net;
Corbett Enders<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] Do you
have phones (7970) still withincorrecttime? READ ME</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>But you can do cool
tricks with the hole (hide stuff...)<br>
<br>
Ah, it is nice to hear that Cisco TAC has minions that handle the crappy
stuff... (I have dealt with such minions before, these are the guys in IPCC who
say it is a CCM issue when the script fails...) <br>
<br>
Could we open a new section on the Cisco Voice downloads for "Members of <a
href="http://Puck.nether.net">Puck.nether.net</a> who were told to apply an
ES"? Cuz we are special.<br>
<br>
<br>
<br>
<br>
Jonathan <o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><span class=gmailquote><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>On 3/19/07, <b><span style='font-weight:bold'>Ryan
Ratliff</span></b> <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>>
wrote:</span></font></span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>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-<br>
run the CM DST patch to fix their non-3rd gen phones. It was decided
<br>
that rather than give customer's the loaded gun with instructions<br>
saying "point at foot, pull trigger, yell at me later" we'd just make<br>
you yell at us without putting a hole in your foot first. <br>
<br>
-Ryan<br>
<br>
On Mar 19, 2007, at 10:49 AM, Jonathan Charles wrote:<br>
<br>
Couldn't Cisco automate this?<br>
<br>
I only ask because it seems that it could be easier to acquire...<br>
(and find out that the ES exists)... maybe a web form where you say, <br>
'hey, I am hitting this bugID, and it says to apply this ES, download<br>
now...' Maybe a link on the bugID itself, that way you could track<br>
who is hitting it (have us fill out a questionnaire indicating that <br>
we are hitting that specific bug and then letting us download it).<br>
<br>
This would also act to alleviate some of the more annoying TAC cases<br>
from you guys (seriously, don't you find it tedious to deal with a<br>
ticket that just says, 'give me ES35'?)<br>
<br>
<br>
<br>
<br>
<br>
Jonathan<br>
<br>
<br>
<br>
<br>
On 3/19/07, Ryan Ratliff <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>>
wrote: Because it is an<br>
ES load that has not undergone the full testing to <br>
warrant posting to <a href="http://cisco.com">cisco.com</a>. If you
want the ES, open a TAC SR. If<br>
you can't do this then wait for 8.2(2) which is supposed to post this<br>
week.<br>
<br>
Opening the TAC SR gives us hard data to go back to development and <br>
say X number of customers were impacted directly by this problem.<br>
<br>
-Ryan<br>
<br>
On Mar 18, 2007, at 12:17 PM, Jonathan Charles wrote:<br>
<br>
So, here's a question.<br>
<br>
Cisco has a confirmed bug, with a fix. <br>
<br>
Why do we need to open a TAC case to get the fix? Why doesn't Cisco<br>
just publish it?<br>
<br>
I know this is going to sound a bit mean, but from the customer's<br>
perspective, Cisco has bungled this DST thing horribly. And the <br>
partners are looking like Monkeys 'having unlawful carnal knowledge<br>
of' a football.<br>
<br>
<br>
<br>
<br>
Jonathan<br>
<br>
On 3/16/07, Johnson, Ken < <a href="mailto:kenjohnson@letu.edu">kenjohnson@letu.edu</a>
> wrote: Ok - I guess<br>
sometimes all you have to do is send off an email and<br>
suddelyn everything you wrote in it becomes moot. Literally seconds<br>
after sending the last email my TAC engineer contacted me and said he <br>
had good news that the ES was available and he'd publish it.<br>
<br>
Sorry for the list noise :-)<br>
<br>
Ken Johnson<br>
Mgr. Network Services,<br>
Information Technology<br>
<st1:place w:st="on"><st1:PlaceName w:st="on">LeTourneau</st1:PlaceName>
<st1:PlaceType w:st="on">University</st1:PlaceType></st1:place><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: Johnson, Ken<br>
Sent: Friday, March 16, 2007 1:48 PM<br>
To: 'Ryan Ratliff'; Corbett Enders <br>
Cc: <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>
Glad to see I wasn't the only one with this issue. I tried asking for <br>
8.2(1)ES5 this morning but was told that neither it nor 8.2(2) was<br>
released and I'd need to wait for 8.2(2) to come out next Thursday.<br>
<br>
I guess that's fine - but if anyone has success getting the ES load I'd <br>
like to know so I could ask again :-)<br>
<br>
Ken Johnson<br>
Mgr. Network Services,<br>
Information Technology<br>
<st1:place w:st="on"><st1:PlaceName w:st="on">LeTourneau</st1:PlaceName>
<st1:PlaceType w:st="on">University</st1:PlaceType></st1:place><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: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
[mailto: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Ryan Ratliff<br>
Sent: Thursday, March 15, 2007 1:49 PM<br>
To: Corbett Enders<br>
Cc: <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>
I'm glad they finally got the field notice updated. Also see my<br>
email from this morning indicating that a new phone load is available<br>
that fixes this problem. If you do not want to wait for 8.2(2) next<br>
week then open a TAC SR and request 8.2(1)ES5 be posted for you.<br>
<br>
-Ryan<br>
<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>
<br>
<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>