<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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: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";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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="1026" />
</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:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">We have had to approach our large dial plan a little different. Currently we have about 250 sites on a single cluster none of which have DID (only our corporate
site has DID). All remote sites are very small and have a handful of 1FBs. Each site has an accounting code which we use as a site code. To dial inter-site users must dial 5+<SiteCode>+<LocalExtension>. Xlates have been set up so users can dial *+<SiteCode>
to reach the local receptionist.<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Works pretty good, very scalable.<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Jason<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>Fuermann, Jason<br>
<b>Sent:</b> Friday, February 12, 2010 7: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>
<br>
<hr>
<font face="Arial" color="Gray" size="1">*** NOTICE--The attached communication contains privileged and confidential information. If you are not the intended recipient, DO NOT read, copy, or disseminate this communication. Non-intended recipients are hereby
placed on notice that any unauthorized disclosure, duplication, distribution, or taking of any action in reliance on the contents of these materials is expressly prohibited. If you have received this communication in error, please delete this information in
its entirety and contact the Amedisys Privacy Hotline at 1-866-518-6684. Also, please immediately notify the sender via e-mail that you have received this communication in error. ***<br>
</font>
</body>
</html>