<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 12 (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]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Arial Narrow";
panose-1:2 11 6 6 2 2 2 3 2 4;}
@font-face
{font-family:Verdana;
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","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>I have been thinking 10 digit dialing also, due to the fact that
we are going to be hosting users across like 30 different area codes.
Allowing each location to dial users in the same location with 5 or even 4
digits is easy, but I just don’t think 5 digit dialing between locations with
that many different locations is worth the hassle and headache. I have
also seen where you have to plan for the inevitable changes that will occur,
such as new sites stood up, and a host of other things, like we had one site
that actually changed numbers when it was converted from one provider to
another (there was a good reason for it). I like to take the approach “expect
the unexpected”, otherwise you set yourself up for a mess later.
Thanks for all the input and info and especially the dial plan link. It
is really going to help a lot.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Bill Hendrix</span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>L-3 Communications</span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><a href="mailto:george.hendrix@l-3com.com">george.hendrix@l-3com.com</a></span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial Narrow","sans-serif";
color:red'><img border=0 width=234 height=68 id="Picture_x0020_1"
src="cid:image001.jpg@01CAACEE.373478A0"
alt="STRATIS - Horizontal with Tag line"></span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Fuermann, Jason<br>
<b>Sent:</b> Friday, February 12, 2010 8:28 PM<br>
<b>To:</b> 'Syed Ahmed'; jason.aarons@us.didata.com; moody@arizona.edu;
cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Dial plans<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I don’t like the 7 digit dialing, multiple area codes end
up having the same exchanges, then you’re done for. Looks like 10 digit
might be your best bet, due to your limitations<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Syed Ahmed<br>
<b>Sent:</b> Friday, February 12, 2010 6:04 PM<br>
<b>To:</b> jason.aarons@us.didata.com; moody@arizona.edu;
cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Dial plans<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>Totally agree. We had our Cisco CCIE VoIP
verify our dial plan before we deployed it. I do agree with Walt that 7-digit
dialing is a good thing. It is scalable. Do use translation pattern for your
5-digit dialing. <br>
<br>
Syed<br>
<br>
> Date: Fri, 12 Feb 2010 18:06:52 -0500<br>
> From: jason.aarons@us.didata.com<br>
> To: moody@arizona.edu; cisco-voip@puck.nether.net<br>
> Subject: Re: [cisco-voip] Dial plans<br>
> <br>
> You really need to look at your DNs/DIDs and map it out carefully. That<br>
> said my generic advice is put 10 digit DNs (or E164 if intl) everywhere,<br>
> then setup 5-digit local translation patterns. This allows Unity<br>
> UM/UCCX to work across multiple sites. The larger you are the more<br>
> important it is to plan carefully before deployment and seek<br>
> professional help to discuss the pros/cons and lab test to avoid<br>
> interdigit timeout/potential matches exist problems.<br>
> <br>
> Search Cisco.com for Deploying Variable-Length On-Net Dial Plans with<br>
> Flat Addressing<br>
> http://www-uk.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/devmobil.h<br>
> tml#wp1043929<br>
> <br>
> <br>
> -----Original Message-----<br>
> From: cisco-voip-bounces@puck.nether.net<br>
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Walt Moody<br>
> Sent: Friday, February 12, 2010 5:00 PM<br>
> To: cisco-voip@puck.nether.net<br>
> Subject: Re: [cisco-voip] Dial plans<br>
> <br>
> Bill,<br>
> <br>
> How about 7 digit dialing internally and 7 digit, 10 digit, 1+, and<br>
> 011+ dialing "outside?"<br>
> <br>
> We switched to NANP-style dialing more than 15 years ago and it has<br>
> really simplified our phone translations. One unanticipated benefit<br>
> is that our users now know their whole phone number rather than just<br>
> the last 5 digits. That really helps when you have 40,000+ DID numbers<br>
> in five area codes.<br>
> <br>
> -walt<br>
> <br>
> On 2/12/2010 1:58 PM, george.hendrix@l-3com.com wrote:<br>
> > Hi everyone,<br>
> ><br>
> > I was wondering if anyone could tell me the best approach for a dial<br>
> > plan or of any link you can send me for best practices. Currently we<br>
> > only have a couple of sites which have 5 digit dialing within each<br>
> > cluster and also of course internally in each cluster. We are<br>
> > consolidating into one single cluster. We will also have about 25<br>
> remote<br>
> > sites later. Right now, users on the VOIP system dial 9 to dial<br>
> external<br>
> > numbers. We have a new site which is assigned numbers where the 6^th<br>
> > digit is a 9, so for 5 digit dialing, there number is 9XXXX. I<br>
> > understand that I can simply put the line DN below external route<br>
> > patterns (but also causes a 15 second delay for those extensions to
be<br>
> > dial as the system waits for more digits). However, my concern is
that<br>
> > there may be an overlap of extensions later in the system 25 (or
more)<br>
> > sites. I don't think it will happen, but I'd also be concerned of two<br>
> > users with the same last 5 digits, even though users are in different<br>
> > area codes.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Bill Hendrix<br>
> ><br>
> > L-3 Communications<br>
> ><br>
> > george.hendrix@l-3com.com <mailto:george.hendrix@l-3com.com><br>
> ><br>
> > STRATIS - Horizontal with Tag line<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > cisco-voip@puck.nether.net<br>
> > https://puck.nether.net/mailman/listinfo/cisco-voip<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> https://puck.nether.net/mailman/listinfo/cisco-voip<br>
> <br>
> -----------------------------------------<br>
> Disclaimer:<br>
> <br>
> This e-mail communication and any attachments may contain<br>
> confidential and privileged information and is for use by the<br>
> designated addressee(s) named above only. If you are not the<br>
> intended addressee, you are hereby notified that you have received<br>
> this communication in error and that any use or reproduction of<br>
> this email or its contents is strictly prohibited and may be<br>
> unlawful. If you have received this communication in error, please<br>
> notify us immediately by replying to this message and deleting it<br>
> from your computer. Thank you.<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> https://puck.nether.net/mailman/listinfo/cisco-voip<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Hotmail:
Powerful Free email with security by Microsoft. <a
href="http://clk.atdmt.com/GBL/go/201469230/direct/01/" target="_new">Get it
now.</a><o:p></o:p></span></p>
</div>
</body>
</html>