Coordinated Dialing Plan

[ParkView]

I am working on deploying BCM50s at about 15 remote locations. I am using VoIP trunking along with MCDN to allow 4 digit dialing between all of these BCM50s. I have determined that I am beginning to have an issue with my coordinate dialing plan.
Remote DN
Location 1 5300-5399
Location 2 5400-5499
Location 3 5500-5599
Etc. Etc.
When I do my starting DN as 5300, on my first BCM50, the DNs that are automatically generated actually overlap into the dialing plan for location 2 and 3. There are two ways I thought of on how I can take care of this problem.
1) Renumber all of the DNs, that extend beyond 5399, to DN numbers that will never be used.
2) Make the starting DN a number that will never be used, including the whole range it generates, and renumber the ones I need to fall into the 5300 range.
I can see good and bad points on doing both. 1) is way more work but the control and prime set relate to DN 5300. 2) Is way less work but the control and prime set end but being on a DN that will not be an active one. All opinions on this will be appreciated as I am really not sure which way to go.

 

[biv343]

Some DN's can't be renumbered (such as hunt groups, etc). Renumbering anything past 5399, 5499, etc may not work for you. You might have a hunt group at 5503 for example, and no amount of prayer or cussing will let you change that hunt group DN without renumbering the whole system.

I'd do what you suggested in option 2 - let the systems come up default (221/2221), and renumber the extensions you'll be using to the appropriate extension for the sites. You can then have common park prefixes, etc, and be confident that you won't have any dialing plan conflicts in the network.

If your lead extension (2221) is renumbered to 5300, the control sets/prime sets will change to 5300 once you've renumbered it - you won't have to manually change them.

 

[AlquestTech]

Well I know you can change a hunt group DN by using the DN Renumber Wizard on the BCM 400, but perhaps the BCM50 is different.

We have the same setup here, but on MICS and BCM 200/400's (by the way - the Norstar also allows you to change the Hunt Group DN so I don't see why the 50 would not, anyway...)

We actually are using the 5000 series as well. We have done it both ways, and by far the easiest was to start everything at 6000 (If you are sure you won't need to access these other stations across the network), and then just renumber the first 100 stations starting at 5300 or 5400 - whatever your group is.

As biv said, the control set should be renumbered as well and target lines should follow.
The only thing is you will manually have to enter the target line numbers.

But still, it is now only 100 lines your are dealing with MAX.

 

[ParkView]

Thanks for the responses. I agree and went back and configured all of my BCM50s to start at DN 4000 and then just renumbered the DNs I needed to the correct range. Worked like a charm and I know exactly how many I have to move. By the way, you can renumber hunt DNs on the BCM50 as well.

 

[AlquestTech]

As I said, I have never worked on the BCM50, but if it is like the Norstars and BCM 200/400 then just go to the Hunt Group Heading and look at Hunt Group 1 DN and the last Hunt Group DN and that will give you your range of numbers.

I believe they are some of the last numbers to be assigned so they are pretty high up...