AVAYA DID Numbers - Different Sites

[BigL1010]

We are in the process of consolidation of employees and buildings where Building A has its own PBX and Building B has its own PBX.........and they both have their own range of DID Numbers

Both PBX systems report back the CORE - which is Building C....

- During the consolidation.....will the DID numbers that were on building A or B still work for those employees moving their new desks in Building C

- Is there any additional steps needed (Porting DID Ranges from the old systems to the CORE) ?

 

[DAVIDPAYNE]

How are the PBX connected? If they are there own system, then you will have to program the extension in the core. If they are just LSP, then they are all ready programmed in the Core.
Please proved more detail on your setup.

 

[BigL1010]

all the PBX are networked back to the core via IP addresses so the core so they are constantly talking to each other so everything is replicated.

alot of times i make changes to the core and it eventually copies it down to that/those PBX system(s)......but this scenario.....THAT or more than one PBX (Building A & Building B) will be discontinued.

where will the DIDs now reside? on the CORE or will i have to port them over from those disconnected telephone systems?

 

[smokinjoe2938]

Port the numbers from A and B onto the Pri at site C, also make sure you program the extensions as well on site C. make sure you have you have no dial plan conflicts.

 

[BigL1010]

Port the Numbers.....that is all LOCAL LEC related....correct? Not PBX related.....

 

[Sean655]

Yes, unless you can move the circuits onto the system at site C. Make sure you have enough circuits to handle call traffic since you're losing two sites with trunks.

 

[BigL1010]

WOW...this is very valuable information.....thinking it was just a shutdown and move.....it seems to be more intricate that that. Thank you all.

 

[Sean655]

There's a lot of things that are being assumed. I'm assuming the DIDs for each site come in only on the circuits at those sites. However, there's even a chance that direct trunk overflow (DTO) is set up on those PRIs so that if they go down, the calls route in on your other PRIs. You'd still want to consider the amount of call traffic you can handle at site C once A and B are consolidated.

It sounds like sites A and B are running as some flavor of survivable servers and if that's the case then you don't need to rebuild any programming because it all exists on your core system. You can use the 'list survivable' command to take a look.

You're not in bad shape if site C has all of your programming, just take care of the carrier stuff. Your account rep for the carrier will be able to help you with understanding your current setup and possible options.

 

[smokinjoe2938]

Yes you will need to work with your line provider to do this, if is not very complicated.

 

[7deedtz]

I guess this is a IP phone deployment

 

[smokinjoe2938]

why would you think ip phones?

 

[7deedtz]

Because we are left to guess that

 

[7deedtz]

@BigL1010, may you please engage with your BP to solution this for you

 

[DAVIDPAYNE]

BigL1010, I asked this before, and you did not answer, but some other stuff you said leads me to believe that you do not have separate PBX at the remote site, you have LSP (local Survivable Processors). you do all the programming the the main system, and that get duplicated to the LSP. LSP can have there own local trunks, and DID ranges. if they get disconnected from the main then they will still function. you main have one setup as and ESS (Enterprise Survivable Server), which would take over if the main sit were to go down. If you do not have a good grasp of what you have, then as 7deedtx said contact and Business Partner to help you. But DID are done at the Line Carrier level, and unless you have the same carrier at all location you may not be able to keep the DID ranges. If you had SIP trunks it would make it a lot s easier.