[cisco-voip] Do you have phones (7970) still withincorrecttime?READ ME

Carter, Bill bcarter at sentinel.com
Mon Mar 19 14:57:04 EST 2007


Sorry, I'm not allowed to comment on that.
 
BC
CCIE 5022

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
Charles
Sent: Monday, March 19, 2007 12:21 PM
To: Voll, Scott
Cc: Corbett Enders; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Do you have phones (7970) still
withincorrecttime?READ ME


Damned Skippy, at least the Pucksters (still working on a noun for us)
share info... those CCIEs are all 'can't... NDA' blah...




Jonathan


On 3/19/07, Voll, Scott <Scott.Voll at wesd.org> wrote: 

	I like that idea too.  Like CCIE's can open a P2 case on line,
puck.nether.net users can open a P1 case =)

	 

	Scott

	 

	
________________________________


	From: cisco-voip-bounces at puck.nether.net [mailto:
cisco-voip-bounces at puck.nether.net
<mailto:cisco-voip-bounces at puck.nether.net> ] On Behalf Of Jonathan
Charles
	Sent: Monday, March 19, 2007 8:07 AM
	To: Ryan Ratliff
	Cc: cisco-voip at puck.nether.net; Corbett Enders 
	
	Subject: Re: [cisco-voip] Do you have phones (7970) still
withincorrecttime? READ ME

	

	 

	But you can do cool tricks with the hole (hide stuff...)
	
	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...) 
	
	Could we open a new section on the Cisco Voice downloads for
"Members of Puck.nether.net who were told to apply an ES"? Cuz we are
special.
	
	
	
	
	Jonathan 

	On 3/19/07, Ryan Ratliff <rratliff at cisco.com> wrote:

	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
	
	On Mar 19, 2007, at 10:49 AM, Jonathan Charles wrote:
	
	Couldn't Cisco automate this?
	
	I only ask because it seems that it could be easier to
acquire...
	(and find out that the ES exists)... maybe a web form where you
say, 
	'hey, I am hitting this bugID, and it says to apply this ES,
download
	now...' Maybe a link on the bugID itself, that way you could
track
	who is hitting it (have us fill out a questionnaire indicating
that 
	we are hitting that specific bug and then letting us download
it).
	
	This would also act to alleviate some of the more annoying TAC
cases
	from you guys (seriously, don't you find it tedious to deal with
a
	ticket that just says, 'give me ES35'?)
	
	
	
	
	
	Jonathan
	
	
	
	
	On 3/19/07, Ryan Ratliff <rratliff at cisco.com> wrote: Because it
is an
	ES load that has not undergone the full testing to 
	warrant posting to cisco.com.  If you want the ES, open a TAC
SR.  If
	you can't do this then wait for 8.2(2) which is supposed to post
this
	week.
	
	Opening the TAC SR gives us hard data to go back to development
and 
	say X number of customers were impacted directly by this
problem.
	
	-Ryan
	
	On Mar 18, 2007, at 12:17 PM, Jonathan Charles wrote:
	
	So, here's a question.
	
	Cisco has a confirmed bug, with a fix. 
	
	Why do we need to open a TAC case to get the fix? Why doesn't
Cisco
	just publish it?
	
	I know this is going to sound a bit mean, but from the
customer's
	perspective, Cisco has bungled this DST thing horribly. And the 
	partners are looking like Monkeys 'having unlawful carnal
knowledge
	of' a football.
	
	
	
	
	Jonathan
	
	On 3/16/07, Johnson, Ken < kenjohnson at letu.edu > wrote: Ok - I
guess
	sometimes all you have to do is send off an email and
	suddelyn everything you wrote in it becomes moot. Literally
seconds
	after sending the last email my TAC engineer contacted me and
said he 
	had good news that the ES was available and he'd publish it.
	
	Sorry for the list noise :-)
	
	Ken Johnson
	     Mgr. Network Services,
	     Information Technology
	     LeTourneau University
	_________________________________ 
	Join the Cisco IP Telecommunications User Group today
	http://www.ciptug.org
	
	-----Original Message-----
	From: Johnson, Ken
	Sent: Friday, March 16, 2007 1:48 PM
	To: 'Ryan Ratliff'; Corbett Enders 
	Cc: cisco-voip at puck.nether.net
	Subject: RE: [cisco-voip] Do you have phones (7970) still with
	incorrecttime? READ ME
	
	Glad to see I wasn't the only one with this issue. I tried
asking for 
	8.2(1)ES5 this morning but was told that neither it nor 8.2(2)
was
	released and I'd need to wait for 8.2(2) to come out next
Thursday.
	
	I guess that's fine - but if anyone has success getting the ES
load I'd 
	like to know so I could ask again :-)
	
	Ken Johnson
	     Mgr. Network Services,
	     Information Technology
	     LeTourneau University
	_________________________________
	Join the Cisco IP Telecommunications User Group today 
	http://www.ciptug.org
	
	-----Original Message-----
	From: cisco-voip-bounces at puck.nether.net
	[mailto: cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan
Ratliff
	Sent: Thursday, March 15, 2007 1:49 PM
	To: Corbett Enders
	Cc: cisco-voip at puck.nether.net
	Subject: Re: [cisco-voip] Do you have phones (7970) still with 
	incorrecttime? READ ME
	
	I'm glad they finally got the field notice updated.  Also see my
	email from this morning indicating that a new phone load is
available
	that fixes this problem.  If you do not want to wait for 8.2(2)
next
	week then open a TAC SR and request 8.2(1)ES5 be posted for you.
	
	-Ryan
	
	
	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip
	
	

	 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070319/71ac2b44/attachment-0001.html 


More information about the cisco-voip mailing list