Redesigning dial plan from four/six digit to seven digit extensions
aaron0011
Member Posts: 330
Thought I would post this project that I am working on here for input since their are some knowledgeable Voice guys on the forum.
We're running into overlap with four digit extensions and up to this point have been accommodating using two additional digits for some sites to control the overlap, ie. 1234 and 771234.
We're planning to go to seven digit using the prefix/DID as the new extension. All of our sites are NANP and based on the reports I've run we have zero overlap past three digits. We have approximately 2,000 users in 150 sites but are adding new sites all of the time that aren't on VoIP yet.
Also, looking at the dial peers in CUBE, I'll be able to replace all of my incoming with a single translation pattern, rule 1 /^.*\(.......\)/ /\1/
Anyone here ever done anything similar? Pros/Cons, Anything I am missing?
We're running into overlap with four digit extensions and up to this point have been accommodating using two additional digits for some sites to control the overlap, ie. 1234 and 771234.
We're planning to go to seven digit using the prefix/DID as the new extension. All of our sites are NANP and based on the reports I've run we have zero overlap past three digits. We have approximately 2,000 users in 150 sites but are adding new sites all of the time that aren't on VoIP yet.
Also, looking at the dial peers in CUBE, I'll be able to replace all of my incoming with a single translation pattern, rule 1 /^.*\(.......\)/ /\1/
Anyone here ever done anything similar? Pros/Cons, Anything I am missing?
Comments
On a side note the guy before me must have gotten a deal a sweet deal on DID blocks beginning with “9” because we have a ton of em!
In some cases we do have multiple sites in the same town or area. We have at least 20 extra DIDs per site and in larger ones we have 60+ so expanding sites shouldn't be a problem going forward. In our business we don't have large sites with hundreds of users per except for Corp and we're all good here.
I like the idea of being able to look at someones signature or business card and know their extension right away. Also, we are migrating to click to call via CTI with Lync/Outlook so users having to dial an extra three digits will not be a problem.
CUCM SRND 9x/10, UCCX SRND 10x, QOS SRND, SIP Trunking Guide, anything contact center related
That's my plan (no pun intended)...just hashing out how my DNs will be configured...or are you saying use the full E.164 number as the DN?
This project is also a 6.1.5 to 9.1 upgrade so a lot of changes with call routing with LRGs coming into play. Majority of sites are SIP through CUBE but there are some PRI sites that are mostly H.323, I've only come across a few MGCP so far and plan to get rid of those. Just started a new job and was handed this project with one other guy working with me.
CUCM SRND 9x/10, UCCX SRND 10x, QOS SRND, SIP Trunking Guide, anything contact center related
We have about 150 remote site gateways currently so adding in LRG is going to cut down on the complexity a ton from what is currently in the 6.X cluster.