[cisco-voip] Cisco Voice Implementation Checklist

Fri Oct 5 16:53:39 EDT 2012

It’s sort of addicting, that’s for sure.

James Buchanan | Sr. Network Engineer
Presidio | www.presidio.com<http://www.presidio.com>
12 Cadillac Drive Suite 130, Brentwood, TN 37027
D: 615.866.5729 | C: 931.797.2326 | F: 615.866.5781 | jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>

[Be Secure In The Knowledge]<http://www.presidio.com>

[Follow Presidio on Twitter]<http://www.twitter.com/presidio>

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Rittenhouse, Robert (LACA)
Sent: Friday, October 05, 2012 8:36 PM
To: Nick Parece; cisco-voip (cisco-voip at puck.nether.net)
Subject: Re: [cisco-voip] Cisco Voice Implementation Checklist

Hah. Thanks Nick for the response and the warm welcoming.

I attempted a checklist yesterday to guide me on my first implementation. I think after a few implementations/migrations it will become second nature but I’ve tried to make some forms that ask just the right questions so I can have a complete list of project requirements. It just cuts down on the amount of communication that I need to do. I feel if a company kept calling you back for details, it would appear to me that they don’t have their things in order. Any extra work could throw things off quite a bit depending on what questions I didn’t ask during the initial meetings.

Next up is making documentation templates that can be filled out and handed to a customer after implementation. Later, I will give them a dashboard where they can look at a high-level overview of their hosted phone system.

Who would have thought that voice could be so awesome? ;) Everybody seems to despise it and give it the cold shoulder.

Thanks again,

Robert Rittenhouse
Network Coordinator
Licking Area Computer Association (LACA)
(740) 345-3400 ext. 220
rrittenhouse at laca.org<mailto:rrittenhouse at laca.org>

From: Nick Parece [mailto:nparece at vistaprint.com]<mailto:[mailto:nparece at vistaprint.com]>
Sent: Thursday, October 04, 2012 1:08 PM
To: Rittenhouse, Robert (LACA); cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: RE: Cisco Voice Implementation Checklist

Hi Robert,

Welcome to the fun and exciting world of Cisco implementations… You pose a tough question as there are SO very many deployment options for the complete solution. The CUCM deployment guide has a great set of steps to follow, but there’s also the different options and platforms for gateways, analog devices, TFTP options, dial-plan, licensing(!) and more. It’s hard to have a generic one work for many different customers.

With all of that said, I’d recommend taking a stab at it and sharing it with the list. I’m sure there will be a lot of input on anything you may have missed.

Best regards,

Nick

Nick Parece
Corporate Voice Lead, Capabilities Operations
E: nparece at vistaprint.com<mailto:nparece at vistaprint.com>
T: 1.781.652.6383
M: 1.781.708.5402
AIM: njparece at gmail.com<mailto:njparece at gmail.com>
Vistaprint Make an Impression.

Business Cards are FREE at www.vistaprint.com<http://www.vistaprint.com/>!

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net]<mailto:[mailto:cisco-voip-bounces at puck.nether.net]> On Behalf Of Rittenhouse, Robert (LACA)
Sent: Thursday, October 04, 2012 8:56 AM
To: cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: [cisco-voip] Cisco Voice Implementation Checklist

I’m starting to make an ordered checklist that can be followed for a basic Cisco voice implementation. Now, before I go and possibly re-create the wheel, does Cisco (or someone else) already provide such a checklist? I’ve searched the Internet over and I haven’t found anything too promising. I am at the point where I am probably going to just develop one for my purposes and release it.

I also had the thought of making a web form that would first step you through asking the basic questions for an implementation. Then it could allow you to fill out all of the gory details for each building in the entire project and then build a PDF of the entire implementation as a TODO check-list. Would releasing something like this even be useful for others I wonder? I’m rather new to the Cisco voice implementation scene and that might be part of my want to over-prepare but I think that it could be a useful guide.

Thanks,

Robert Rittenhouse
Network Coordinator
Licking Area Computer Association (LACA)
(740) 345-3400 ext. 220
rrittenhouse at laca.org<mailto:rrittenhouse at laca.org>
________________________________
PLEASE NOTE: This message and any response to it may constitute a public record, and therefore may be available upon request in accordance with Ohio public records law. (ORC 149.43)
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain private, confidential, and/or privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, employee, or agent responsible for delivering this message, please contact the sender by reply e-mail and destroy all copies of the original e-mail message.
________________________________
PLEASE NOTE: This message and any response to it may constitute a public record, and therefore may be available upon request in accordance with Ohio public records law. (ORC 149.43)
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain private, confidential, and/or privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, employee, or agent responsible for delivering this message, please contact the sender by reply e-mail and destroy all copies of the original e-mail message.
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121005/c75a61a7/attachment.html>