[cisco-voip] CM5 hardware requirements

Jean-Victor.Brun at ins.com Jean-Victor.Brun at ins.com
Wed Mar 21 18:31:12 EST 2007


Sorry guys!  I did not mean to post on this thread.

________________________________

From: cisco-voip-bounces at puck.nether.net on behalf of Jean-Victor.Brun at ins.com
Sent: Wed 3/21/2007 5:25 PM
To: jonvoip at gmail.com; Matt.Slaga at us.didata.com
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CM5 hardware requirements


Gurus of the VoIP World,
I have a cust who want to do a small survey at the end of everycall.  Two to three questions, yes or no and form 1 to 5 answers.  Anyone has any docs or suggestions?  Thanks!
 
 

________________________________

From: cisco-voip-bounces at puck.nether.net on behalf of Jonathan Charles
Sent: Wed 3/21/2007 4:58 PM
To: Matt Slaga (US)
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CM5 hardware requirements


Yes, but it also means that basic troubleshooting info is hidden from customers...


Jonathan


On 3/21/07, Matt Slaga (US) < Matt.Slaga at us.didata.com <mailto:Matt.Slaga at us.didata.com> > wrote: 

	It's probably because Cisco has always required these systems to be 
	installed by partners.  Hence the focus of technical documentation
	directed at partners.
	
	My 2 cents..
	
	
	Matt
	
	-----Original Message-----
	From: cisco-voip-bounces at puck.nether.net
	[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
	Sent: Wednesday, March 21, 2007 1:55 PM
	To: Robert Kulagowski 
	Cc: cisco-voip at puck.nether.net
	Subject: Re: [cisco-voip] CM5 hardware requirements
	
	Your guess is as good as mine.  That's a trick I learned back in 2000
	when I started at Cisco.  How it got that way was waaay before my time.
	
	-Ryan
	
	On Mar 21, 2007, at 1:45 PM, Robert Kulagowski wrote:
	
	Ryan Ratliff wrote:
	> Change partner to customer and the link usually works. 
	
	Yep, which is what I did.  Should that be in the wiki?  :)
	
	Actually, I don't understand why generic docs like that even _have_ a
	partner version and a customer version; the issue is that the release
	notes for 5.1(1b) point you at a partner URL for the hardware
	requirements rather than a customer URL.
	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip
	_______________________________________________
	cisco-voip mailing list 
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip
	----------------------------------------- 
	Disclaimer:
	
	This e-mail communication and any attachments may contain
	confidential and privileged information and is for use by the
	designated addressee(s) named above only.  If you are not the
	intended addressee, you are hereby notified that you have received 
	this communication in error and that any use or reproduction of
	this email or its contents is strictly prohibited and may be
	unlawful.  If you have received this communication in error, please
	notify us immediately by replying to this message and deleting it 
	from your computer. Thank you.
	
	_______________________________________________
	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/20070321/265df668/attachment-0001.html 


More information about the cisco-voip mailing list