[cisco-voip] Dial plans
Walt Moody
moody at arizona.edu
Mon Feb 15 11:31:11 EST 2010
It's probably not OK in any space to take away DID service if it's
already in place. Beside the "my number" issue, there's also vanity
numbers (e.g. 621-KUAT to reach the Public TV station), and tons of
brochures and stationary. It's not worth alienating all your users for
an ethereal cost savings.
The dial plan we have chosen is designed to emulate the NANP: Seven OR
ten digits internally. Seven OR ten digits to the "home" Area Code.
Ten digits to other Area Codes within the local rate center. Ten
digits for toll bypass (TEHO). Anytime you dial 1 plus ten digits and
your Authorization Level allows the call, it's handed off to an LD
carrier, otherwise the call is blocked. 011+ requires an even higher
Authorization Level and is also handed off to an LD carrier. Seven and
ten digit calls are available to every Authorization Level. 9-1-1 is
dialable from every phone.
We instituted this dial plan after numerous traffic studies and
discussions with telephone users. The traffic studies showed that 2/3
of our originating traffic was off campus, therefore users were dialing
a leading "9" two thirds of the time. There was only one user who was
adamant that he would NEVER! use such a plan. I haven't heard from him
since, so I guess he was true to his word.
Those users who don't wish to use seven digits to reach the person in
the next room can use the Speed Dial or Intercom features. We do not
offer abbreviated dialing.
-walt
On 2/15/2010 7:53 AM, Matthew Saskin wrote:
> 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 ;)
> 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.
>
> Matthew Saskin
> msaskin at gmail.com <mailto:msaskin at gmail.com>
> 203-253-9571
>
> July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run
> Please support the Leukemia & Lyphoma Society
> http://pages.teamintraining.org/nyc/nyctri10/msaskin
>
>
> On Sat, Feb 13, 2010 at 9:51 PM, Lelio Fulgenzi <lelio at uoguelph.ca
> <mailto:lelio at uoguelph.ca>> wrote:
>
> 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?
>
> 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?
>
> 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.
>
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
> - LFJ (with apologies to Mr. Popeil)
>
>
>
> ----- Original Message -----
> From: "george hendrix" <george.hendrix at l-3com.com
> <mailto:george.hendrix at l-3com.com>>
> To: "Jason Fuermann" <JBF005 at shsu.edu <mailto:JBF005 at shsu.edu>>,
> "Syed Ahmed" <sahmed39 at hotmail.com <mailto:sahmed39 at hotmail.com>>,
> "jason aarons" <jason.aarons at us.didata.com
> <mailto:jason.aarons at us.didata.com>>, moody at arizona.edu
> <mailto:moody at arizona.edu>, cisco-voip at puck.nether.net
> <mailto:cisco-voip at puck.nether.net>
> Sent: Saturday, February 13, 2010 9:05:05 PM GMT -05:00 US/Canada
> Eastern
> Subject: Re: [cisco-voip] Dial plans
>
> 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.
>
> Bill Hendrix
>
> L-3 Communications
>
> george.hendrix at l-3com.com <mailto:george.hendrix at l-3com.com>
>
> STRATIS - Horizontal with Tag line
>
> *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:cisco-voip-bounces at puck.nether.net>] *On Behalf Of
> *Fuermann, Jason
> *Sent:* Friday, February 12, 2010 8:28 PM
> *To:* 'Syed Ahmed'; jason.aarons at us.didata.com
> <mailto:jason.aarons at us.didata.com>; moody at arizona.edu
> <mailto:moody at arizona.edu>; cisco-voip at puck.nether.net
> <mailto:cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] Dial plans
>
> 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
>
> *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:cisco-voip-bounces at puck.nether.net>] *On Behalf Of *Syed Ahmed
> *Sent:* Friday, February 12, 2010 6:04 PM
> *To:* jason.aarons at us.didata.com
> <mailto:jason.aarons at us.didata.com>; moody at arizona.edu
> <mailto:moody at arizona.edu>; cisco-voip at puck.nether.net
> <mailto:cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] Dial plans
>
> 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.
>
> Syed
>
> > Date: Fri, 12 Feb 2010 18:06:52 -0500
> > From: jason.aarons at us.didata.com <mailto:jason.aarons at us.didata.com>
> > To: moody at arizona.edu <mailto:moody at arizona.edu>;
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> > Subject: Re: [cisco-voip] Dial plans
> >
> > You really need to look at your DNs/DIDs and map it out carefully.
> That
> > said my generic advice is put 10 digit DNs (or E164 if intl)
> everywhere,
> > then setup 5-digit local translation patterns. This allows Unity
> > UM/UCCX to work across multiple sites. The larger you are the more
> > important it is to plan carefully before deployment and seek
> > professional help to discuss the pros/cons and lab test to avoid
> > interdigit timeout/potential matches exist problems.
> >
> > Search Cisco.com for Deploying Variable-Length On-Net Dial Plans with
> > Flat Addressing
> >
> http://www-uk.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/devmobil.h
> > tml#wp1043929
> >
> >
> > -----Original Message-----
> > 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:cisco-voip-bounces at puck.nether.net>] On Behalf Of Walt Moody
> > Sent: Friday, February 12, 2010 5:00 PM
> > To: cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> > Subject: Re: [cisco-voip] Dial plans
> >
> > Bill,
> >
> > How about 7 digit dialing internally and 7 digit, 10 digit, 1+, and
> > 011+ dialing "outside?"
> >
> > We switched to NANP-style dialing more than 15 years ago and it has
> > really simplified our phone translations. One unanticipated benefit
> > is that our users now know their whole phone number rather than just
> > the last 5 digits. That really helps when you have 40,000+ DID numbers
> > in five area codes.
> >
> > -walt
> >
> > On 2/12/2010 1:58 PM, george.hendrix at l-3com.com
> <mailto:george.hendrix at l-3com.com> wrote:
> > > Hi everyone,
> > >
> > > I was wondering if anyone could tell me the best approach for a dial
> > > plan or of any link you can send me for best practices. Currently we
> > > only have a couple of sites which have 5 digit dialing within each
> > > cluster and also of course internally in each cluster. We are
> > > consolidating into one single cluster. We will also have about 25
> > remote
> > > sites later. Right now, users on the VOIP system dial 9 to dial
> > external
> > > numbers. We have a new site which is assigned numbers where the 6^th
> > > digit is a 9, so for 5 digit dialing, there number is 9XXXX. I
> > > understand that I can simply put the line DN below external route
> > > patterns (but also causes a 15 second delay for those extensions
> to be
> > > dial as the system waits for more digits). However, my concern
> is that
> > > there may be an overlap of extensions later in the system 25 (or
> more)
> > > sites. I don't think it will happen, but I'd also be concerned
> of two
> > > users with the same last 5 digits, even though users are in
> different
> > > area codes.
> > >
> > > Thanks,
> > >
> > > Bill Hendrix
> > >
> > > L-3 Communications
> > >
> > > george.hendrix at l-3com.com <mailto:george.hendrix at l-3com.com>
> <mailto:george.hendrix at l-3com.com <mailto:george.hendrix at l-3com.com>>
> > >
> > > STRATIS - Horizontal with Tag line
> > >
> > >
> > >
> > > _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net <mailto: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 <mailto:cisco-voip at puck.nether.net>
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ------------------------------------------------------------------------
>
> Hotmail: Powerful Free email with security by Microsoft. Get it now.
> <http://clk.atdmt.com/GBL/go/201469230/direct/01/>
>
>
> _______________________________________________ cisco-voip mailing
> list cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto: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
More information about the cisco-voip
mailing list