<div>I think you've stumbled upon a cost savings measure that is OK in the education space but wouldn't fly under any circumstances in the corporate world - I can't think of any of my customers with enough DID's to make an impact on the budget that would actually consider giving them up ;)</div>
<div> </div>
<div>As far as scalable dial plans, I'm a big fan of either 10-digit (NANP only) or country code + DID (E164 without the +) assigned as phone DN's - guaranteed global uniqueness which assists for shared services such as voicemail. For sites without DID's, typically a shortened internal only number is used and a list is maintained for within the organization. Site-to-site dialing with a single site or campus can be shortened using translation patterns to allow for 4/5/6/x digit dialing. If you intend to route enterprise calls on-net, dialing the full DID number without an access code can route across the network, dialing anything with a prefix of 9 (or 8, or whatever...) goes out the PSTN.</div>
<div><br clear="all">Matthew Saskin<br><a href="mailto:msaskin@gmail.com">msaskin@gmail.com</a><br>203-253-9571<br><br>July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run<br>Please support the Leukemia & Lyphoma Society<br>
<a href="http://pages.teamintraining.org/nyc/nyctri10/msaskin">http://pages.teamintraining.org/nyc/nyctri10/msaskin</a><br><br><br></div>
<div class="gmail_quote">On Sat, Feb 13, 2010 at 9:51 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Verdana">Two questions come to mind: how many office extensions do you really need, and how long until "budget cuts" require you to move from DIDs to an auto-attendant?<br>
<br>With a five digit dial plan and removing 0 and 9 as the first digit, you have over 50,000 possible extensions. Is that not enough?<br><br>Also, how much are you paying for DIDs? Even at a $1/mo and 5,000 DIDs, that's 60 grand per year. We've never had DIDs except for the odd one out for special purposes, so I can't really speak to the efficacy of them, but auto-attendants seem to do the job around here.<br>
<br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)
<div>
<div></div>
<div class="h5"><br><br><br>----- Original Message -----<br>From: "george hendrix" <<a href="mailto:george.hendrix@l-3com.com" target="_blank">george.hendrix@l-3com.com</a>><br>To: "Jason Fuermann" <<a href="mailto:JBF005@shsu.edu" target="_blank">JBF005@shsu.edu</a>>, "Syed Ahmed" <<a href="mailto:sahmed39@hotmail.com" target="_blank">sahmed39@hotmail.com</a>>, "jason aarons" <<a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>>, <a href="mailto:moody@arizona.edu" target="_blank">moody@arizona.edu</a>, <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
Sent: Saturday, February 13, 2010 9:05:05 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] Dial plans<br><br>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt; COLOR: rgb(31,73,125)">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.</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt; COLOR: rgb(31,73,125)"> </span></p>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt; COLOR: rgb(31,73,125)">Bill Hendrix</span><span style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt; COLOR: rgb(31,73,125)">L-3 Communications</span><span style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt; COLOR: rgb(31,73,125)"><a href="mailto:george.hendrix@l-3com.com" target="_blank">george.hendrix@l-3com.com</a></span><span style="FONT-SIZE: 11pt; COLOR: blue"> </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: red"><img height="68" alt="STRATIS - Horizontal with Tag line" width="234" border="0"></span><span style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"></span></p></div>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt; COLOR: rgb(31,73,125)"> </span></p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: rgb(181,196,223) 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt">From:</span></b><span style="FONT-SIZE: 10pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Fuermann, Jason<br>
<b>Sent:</b> Friday, February 12, 2010 8:28 PM<br><b>To:</b> 'Syed Ahmed'; <a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>; <a href="mailto:moody@arizona.edu" target="_blank">moody@arizona.edu</a>; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Dial plans</span></p></div></div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)">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</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125)"> </span></p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: rgb(181,196,223) 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt">From:</span></b><span style="FONT-SIZE: 10pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Syed Ahmed<br>
<b>Sent:</b> Friday, February 12, 2010 6:04 PM<br><b>To:</b> <a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>; <a href="mailto:moody@arizona.edu" target="_blank">moody@arizona.edu</a>; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Dial plans</span></p></div></div>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="MARGIN-BOTTOM: 12pt"><span style="FONT-SIZE: 10pt">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: <a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a><br>> To: <a href="mailto:moody@arizona.edu" target="_blank">moody@arizona.edu</a>; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><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>> <a href="http://www-uk.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/devmobil.h" target="_blank">http://www-uk.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/devmobil.h</a><br>
> tml#wp1043929<br>> <br>> <br>> -----Original Message-----<br>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a><br>> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Walt Moody<br>
> Sent: Friday, February 12, 2010 5:00 PM<br>> To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><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, <a href="mailto:george.hendrix@l-3com.com" target="_blank">george.hendrix@l-3com.com</a> 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>> > <a href="mailto:george.hendrix@l-3com.com" target="_blank">george.hendrix@l-3com.com</a> <mailto:<a href="mailto:george.hendrix@l-3com.com" target="_blank">george.hendrix@l-3com.com</a>><br>
> ><br>> > STRATIS - Horizontal with Tag line<br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > cisco-voip mailing list<br>> > <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> _______________________________________________<br>> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><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>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span></p>
<div class="MsoNormal" style="TEXT-ALIGN: center" align="center"><span style="FONT-SIZE: 10pt">
<hr align="center" width="100%" size="2">
</span></div>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt">Hotmail: Powerful Free email with security by Microsoft. <a href="http://clk.atdmt.com/GBL/go/201469230/direct/01/" target="_blank">Get it now.</a></span></p></div><br></div>
</div>_______________________________________________ cisco-voip mailing list <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a> </div>
</div><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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>