Combining sites

[loneWolf9]

I have been asked to work with a vendor on bringing 4 separate CS1000 onto 1 CS1000E HE.
The core will centrally locate at our corporate office, with high speed private networking in between. There will be gateways, and COTS at each site for trunks, and survivability.

Adding to the fact it will communicate directly with a centrally controlled Shortel system that has about 80 locations across the country.

The question is how to best combine the dialing plan with minimal issue to end user.


We are willing to go up to 7 digits.

Ideas that have been thrown out:

Start from scratch, and start a whole new number scheme based off 7 digits.

3 digit access code, based off location followed by 4 digit ext.
ex 1001234
100 = the access code for the corporate office
1234 = the ext at the location.

Any advice on this subject would be appericated.

Thanks

 

[scotthdiv]

Do you mean HS (High Scalability) or are you just combining the 4 CS1000's in to one CS1000E?

As far as what to do with the dial plan, that depends on what you want to do and what you can do based on the existing dial plan.


I'm in the middle of consolidating 10+ CS1000M's/Option 11's in to one. This customer already has a coordinated dial plan, so we are just using the existing dial plan and changing the few DNs that may overlap.

 

[loneWolf9]

Currently these are 4 seperate CS1000M that are completely independant.

They will be moved over to a CS1000E in a campus redundant high availabity system (HA)

Guess I am just looking for some "best practices", or advice from others that may have done something in the past.

The current systems all use eith 4 digit dialing plans. That is why we thought about going to 7. Using the first 3 as a kind of identify means of location.

 

[Firebird Scrambler]

I've done a job last year where I had to combine 4 Option 61 systems onto one CPPM card. It required many hours of homework, but it was done with the use of a few scripts and other programs that I had via TNB printouts split for 500 and digital sets for each site.

There are many factors to consider such as pickup up groups, scl lists, DN conflicts (I had a few to deal with!). Also creating new and changing TN's, because I was using MGXPEC cards.

Is your network using linked numbering?.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[loneWolf9]

Forgive me Firebird I am not familiar with "Linked numbers."

TN's, Scls, and many Dn's will have to change no doubt about
that.

There is also a chance we will have to create several IDC's do to local numbers may not match the new ext. Hoping to keep them as close as we can.

Big fan of the KISS method.

 

[trvlr1]

Why not use the standard NPA-NXX-XXXX configuration. Everyone is familiar with it, so no extra training. Calls between sites, you route over your own network, saving you money (hopefully) and people do not have to learn 2 sets of numbers for all their contacts (dialing internally on your system and dialing from their cell when out of the office for example) If you try to set up codes for every location, you are bound to start overlapping numbers sooner or later with the PSTN using only 7 digits.
If you also intend to use a centralized voice mail system, remember each mailbox will have to use the full number of whatever scheme you decide to deploy.
Why reinvent the wheel?

 

[trvlr1]

One other point, if you lose connectivity between sites, using the PSTN numbering scheme in your set up, allows you to reroute calls through the Telco without having to translate each set of numbers at each site, from non-PSTN scheme to PSTN scheme.

 

[loneWolf9]

7 digits is what we are shooting for. I have just never had to map out something like this before.

I appericate the feedback.