btrain2871

This may sound a bit confusing but bear with me..

I have a main site (s8700cm3.1) and then 2 small remote sites that are 1 block away from eachother (s8300/standalone). We have 4 digit dialing setup between each location via an IP trunk that goes back to the main site. the 2 small offices are consolidating into 1. Because of an MPLS network we have that carries our IP trunk traffic I had the DID's of the site that is moving ported over to the circuit at the other location even though the users aren't moving until next week. So what is happening now is the users still make outgoing calls off the PRI that the DID's were ported away from and any incoming call on those ported DID's are coming in at the other location.. seeing that range as a UDP/AAR entry and then routing to the main site over the IP trunk and then to the users. This is working perfect so far.

Next weekend the move of the users is to happen. Since the DID's are already ported do I just need to add the new stations at the 'TO' location and then remove the UDP/AAR entry and make sure in the dialplan that range is specified as an extension??

stubborne

just check your dialplan (display dialplan parameters) to ensure that UDP Ext Search Order = local-extensions-first. Then as your users move over, when you create the new extension for them, calls will be delivered to that local extension before the switch would look to the UDP table..

__________________
Stu

PBXtech.info

 

btrain2871

Ok, but if the DID's are already coming down that circuit and they are 20XX and 2 is an entry in the dialplan as an ext and the udp/aar tables have nothing in them referencing 20 or 20XX then shouldn't it just treat it as local??

martinyoung

Let's pick a station number 2010 for example and that number is currently assigned to the remote switch. You currently have 2010 in your UDP table being routed to the remote system. If your UDP search parameter are to use the UDP table first, a call to 2010 will be sent to the other switch before looking to see if there is a local station.

To stop that from happening you will have to remove each station from UDP when you move it. On the other hand, if your UDP search parameters are to check for a local station first then it will see the new phone and send the call to it before checking the UDP table.

Once everybody has moved you can change the UDP entries. Follow Stubborne's suggestion and you will not need to be concerned with UDP entries until you are done and there will not be any service disruption to the folks moving. That is one less programming step to be concerned with during the move.

__________________
Marty
Retired Avaya DSIC tech

btrain2871

So, on the system and office that is moving I don't have to do anything aside from shutting it down because it's being decomissioned.

The site the users are moving to is existing and in software I just have to build the new stations? The DID's are already on the circuit there. Then in Software I just have to either remove the UDP/AAR entries for that range of #'s and make sure they are listed as extensions in the dialplan?? OR, switch the dialplan parameters on this switch to say local extension first and then make sure in the dialplan the range in ? is listed as an extension no matter what the udp/aar says??

martinyoung

If you tell the switch to look at local numbers first, and it finds a local number, it will completely ignore the UDP table.

The stations are already in your dialplan range or you wouldn't be able to use UDP on them. You assign them just like any other phone you install at that site.

__________________
Marty
Retired Avaya DSIC tech

PBXtech.info

 

btrain2871

understood but I can do it the other way as well? Wouldn't it be better practice to do it the way I mentioned because you keep the dialplan/udp/aar clean?

martinyoung

Yes, you can do it either way. Do it whichever way you are comfortable with.

My choice would be to move the station and let the UDP direct the call to the local station automatically during the move. After all that is done then I can clean up the UDP at my leisure.

You are going to go back and look it over anyway after the move, why do that twice? I will do a better job cleaning it up when I can look it over carefully without the pressure of moving phones too.

__________________
Marty
Retired Avaya DSIC tech

btrain2871

Yea, I'll see during the week how I want to handle it. I'd have to really look thru the dialplan/udp/aar to see if changing it to look at local ext first would cause any other entries to be affected.

But something else is on the site that is moving we have a 4620 IP station setup that resides at someones home via I guess a vpn concentrator etc.. since this switch is going to be just shutdown that IP phone will lose its connectivity. That I imagine will be an issue for my network group to tackle since the connectivity info would have to change on that router/vpn concentrator??

martinyoung

Yes, that phone will need to be rehomed to the new switch. Your network guys will need to replicate the VPN, it might be a good idea to get them to look at how it is setup now unless they are fluent in VPN's now. There will be work in the PBX and at the phone but neither should be traumatic.

__________________
Marty
Retired Avaya DSIC tech

btrain2871

if the phone isn't really accessible due to location how and what needs to be done on the PBX end aside from building the new station?

martinyoung

Unless you can use the same IP address that will need to be changed. If the phone gets it by DHCP then changing the settings in the PBX will require restarting the phone. Unplugging the phone and plugging it back in might accomplish that. If it has a static IP, that will have to be changed at the phone.

If they have a computer using the same link, that will also have to be changed.

Unless Al knows a way, rehoming the IP phone will require some work at the phone. It can't all be done at the PBX.

__________________
Marty
Retired Avaya DSIC tech