[cisco-voip] Companies using something other than E.64 dial plan

Matthew Saskin matt at saskin.net
Mon Jul 28 14:35:07 EDT 2008


Off the top of my head, almost all of my clients that are global in 
scope use E.164 across the board.  Two in particular that I'm thinking 
of have 10K and 30K handsets across 150 and 300+ sites respectively.

-matt

Bielecki, Matthew wrote:
> Thanks to all for the replies so far!
> 
>  
> 
> The 6 digit plan sounds like it might be a good compromise – if we can 
> get the 5 digit people to migrate to that.
> 
>  
> 
> This brings up another good question.  Are there any international 
> companies out there using a purely E.164 dial plan?
> 
>  
> 
> Thanks,
> 
>  
> 
> Matt
> 
>  
> 
>  
> 
>  
> 
> -----Original Message-----
> From: Dustin S. Fowler [mailto:dustin.s.fowler at gmail.com]
> Sent: Monday, July 28, 2008 11:12 AM
> To: Bielecki, Matthew
> Cc: cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] Companies using something other than E.64 dial 
> plan
> 
>  
> 
> Matthew,
> 
>  
> 
> I have dealt with some interesting dial plan solutions. One was a hybrid six
> 
> digit dialing structure and it worked very well. Here is a run down.
> 
>  
> 
> XYYZZZ
> 
>  
> 
> X - Region code - Only used if leaving the Region like a timezone
> 
> YY - Store number - this leaves 99 stores per region if you use a beginning
> 
> '0'
> 
> ZZZ - Individual stations. You could make this a 2 digit number if need be.
> 
>  
> 
> In this scenario with being a pretty large retailer, they only had 6 DID's
> 
> per location. This left it pretty much wide open to use any number sequence
> 
> we wanted. Unfortunately to this point I have not worked on a deployment
> 
> where I could have used E164 addressing throughout.
> 
>  
> 
> I have another deployment just in the US that uses 10-digit dialing. That
> 
> was cake.
> 
>  
> 
> Semper Fidelis,
> 
>  
> 
> Dustin Fowler
> 
> Senior Cisco Consultant
> 
>  
> 
> Email: dustin.s.fowler at gmail.com
> 
> "KEEPING YOUR BUSINESS HIGHLY AVAILABLE"
> 
>  
> 
>  
> 
> -----Original Message-----
> 
> From: cisco-voip-bounces at puck.nether.net
> 
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bielecki, Matthew
> 
> Sent: Monday, July 28, 2008 11:03 AM
> 
> To: Jonathan Charles
> 
> Cc: cisco-voip at puck.nether.net
> 
> Subject: Re: [cisco-voip] Companies using something other than E.64 dial
> 
> plan
> 
>  
> 
> Right, that is what I thought and of course, 5 digits plus a site code
> 
> is no longer 5 digits from an end user standpoint.  And a 2 digit site
> 
> code isn't enough digits for 125 sites which bumps us up even higher.
> 
>  
> 
> So does anyone know of large companies that has had to convert from, or
> 
> got stuck using, some hybrid dial plan?
> 
>  
> 
> I would like to site the name of the company in a report to my boss in
> 
> support of sticking to our original E.164 dial plan and to not allow 5
> 
> digit dialing for some sites on a whim.
> 
>  
> 
> Thanks,
> 
>  
> 
> Matt
> 
>  
> 
>  
> 
> -----Original Message-----
> 
> From: Jonathan Charles [mailto:jonvoip at gmail.com]
> 
> Sent: Monday, July 28, 2008 10:54 AM
> 
> To: Bielecki, Matthew
> 
> Cc: Matthew Saskin; cisco-voip at puck.nether.net
> 
> Subject: Re: [cisco-voip] Companies using something other than E.64 dial
> 
> plan
> 
>  
> 
> Yes, they do.
> 
>  
> 
> Your solution is access/site codes
> 
>  
> 
> so, Dallas gets a 87+4-digit extension
> 
>  
> 
> The 87 translates with a CSS to include that 4-digit range
> 
>  
> 
> Sucks, but it will work
> 
>  
> 
>  
> 
>  
> 
> Jonathan
> 
>  
> 
> On Mon, Jul 28, 2008 at 9:38 AM, Bielecki, Matthew
> 
> <MBIELECK at steelcase.com> wrote:
> 
>>  Thank you for the reply!
> 
>> 
> 
>> 
> 
>> 
> 
>>  That clears up half of my problem.
> 
>> 
> 
>> 
> 
>> 
> 
>>  Here's my scenario.  I have 125 sites, and everyone wants to be able
> 
> to dial
> 
>>  the other sites via 5 digit dialing.
> 
>> 
> 
>> 
> 
>> 
> 
>>  At some point, certain 5 digit numbers will overlap.  So if both LV
> 
> and NY
> 
>>  have 33xxx extensions, and Dallas wants to call LV, things seem to get
> 
>>  really complicated.
> 
>> 
> 
>> 
> 
>> 
> 
>>  Matt
> 
>> 
> 
>> 
> 
>> 
> 
>> 
> 
>> 
> 
>>  -----Original Message-----
> 
>>  From: Matthew Saskin [mailto:matt at saskin.net]
> 
>>  Sent: Monday, July 28, 2008 10:21 AM
> 
>>  To: Bielecki, Matthew
> 
>>  Cc: cisco-voip at puck.nether.net
> 
>>  Subject: Re: [cisco-voip] Companies using something other than E.64
> 
> dial
> 
>>  plan
> 
>> 
> 
>> 
> 
>> 
> 
>>  What Wes is describing is essentially as follows:
> 
>> 
> 
>> 
> 
>> 
> 
>>  -All DN's on phones are E.164 or equivalent (for north america, all
> 
>> 
> 
>>  phones would get 10-digit DN's).
> 
>> 
> 
>>  -Example site in New York is 212555xxxx and a site in Las Vegas is
> 
>> 
> 
>>  702555xxxx
> 
>> 
> 
>>  -For 4-digit dial within a site, you'd set up an XXXX translation
> 
>> 
> 
>>  pattern within a site-specific partition (or reachable via a
> 
>> 
> 
>>  site-specific CSS) that prefixes the necessary digits to expand
> 
> 4-digits
> 
>> 
> 
>>  to 10-digits.
> 
>> 
> 
>> 
> 
>> 
> 
>>  Example:
> 
>> 
> 
>>  NY-Xlate would have a pattern of XXXX with a prefix of 212555
> 
>> 
> 
>>  LV-Xlate would have a pattern of XXXX with a prefix of 702555
> 
>> 
> 
>> 
> 
>> 
> 
>>  -matt
> 
>> 
> 
>> 
> 
>> 
> 
>> 
> 
>> 
> 
>>  Bielecki, Matthew wrote:
> 
>> 
> 
>> > I've been trying to find large companies that use something other
> 
> than
> 
>> 
> 
>> > the complete E.164 dial plan for their company and I ran across a
> 
> post
> 
>> 
> 
>> > Wes made here:
> 
>> > http://www.gossamer-threads.com/lists/cisco/voip/53729#53729
> 
>> 
> 
>> > 
> 
>> 
> 
>> > Could someone outline what he means a little bit more?
> 
>> 
> 
>> > 
> 
>> 
> 
>> > Also, has anyone been stuck having to use 5 digit dialing when their
> 
>> 
> 
>> > overall strategy is to use the E.164 dial plan?
> 
>> 
> 
>> > 
> 
>> 
> 
>> > Thanks for your help,
> 
>> 
> 
>> > 
> 
>> 
> 
>> > Matt
> 
>> 
> 
>> > 
> 
>> 
> 
>> > 
> 
>> 
> 
>> > 
> 
>> 
> 
>> > 
> 
>> 
> 
>> > 
> 
> ------------------------------------------------------------------------
> 
>> 
> 
>> > 
> 
>> 
> 
>> > _______________________________________________
> 
>> 
> 
>> > cisco-voip mailing list
> 
>> 
> 
>> > 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
> 
>> 
> 
>> 
> 
> _______________________________________________
> 
> cisco-voip mailing list
> 
> 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