VDN ARS ANA Routing

[Stinney]

I've seen a few postings, but no clear answer to this.

It appears that VDNs don't follow the location ARS ANA based on the TN assigned to the VDN and will only use the default ARS ANA when we send the call to a vector and do a route-to 91xxxxxxxxxx. At least that's what we're experiencing.

The other issue with this is that I want the call to route out based on what site takes the call. I want the call to go out the local site's trunking if they handle the call, not the core PBX trunks. If I can get VDNs to follow the location ARS, I could assign a different VDN for the site to transfer to so it routes out their local trunks.

- Stinney

“The man who asks a question is a fool for a minute, the man who does not ask is a fool for life.” - Confucius

 

[joe2938]

Does the VDN have the correct cor for that location?

 

[Stinney]

COR is in the same TN

- Stinney

“The man who asks a question is a fool for a minute, the man who does not ask is a fool for life.” - Confucius

 

[DAVIDPAYNE]

Do you have the number you are dialing out to in the ARS location on the TN? You may want to try to have the full number in the location.

 

[Stinney]

Yes, we put the full 11 digit dialing in the location routing for that TN.

- Stinney

“The man who asks a question is a fool for a minute, the man who does not ask is a fool for life.” - Confucius

 

[dialtonebone]

Just to be clear here, the TN has nothing to do with the call routing. The location field however does. You'll see this in both the ip-network-region for the phone if IP based or the media-gateway or cabinet information if this is a wired telephone.

In the case of a VDN like yours, I'm not sure if there is a way to make it route based upon the location it came in on. The same problem also exists with remote coverage where it will always default to the ALL table.

 

[dialtonebone]

update: Check out "cha sys cov" and look at the option for "Location for Covered..." and then "VDN/Hunt Group Location:". You can choose "ALL" or "Caller". This might help.

 

[szuperk]

VDNs will use the ARS/AAR table that matches the caller's location. For incoming trunk callers it is the trunk's location (location of MG for legacy trunks, location assigned to far-end NR in signaling group for IP trunks). In case the trunk has an empty location ARS/AAR table, it will use the ALL table.
When chossing between the ALL or the location-based table, the same better-match selection applied just like for normal calls.

 

[Stinney]

szuperk,

I'll have to look into that. This is a SIP trunk and the far end of the signaling group for that trunk is assigned to a network region that doesn't have a location defined, so to me that means it would follow the default ars ana.

- Stinney

“The man who asks a question is a fool for a minute, the man who does not ask is a fool for life.” - Confucius

 

[szuperk]

Exactly. Unfortunately the implications are tremendous: besides the fact a solution cannot be tested internally without preparation, calls arriving on different trunks may select different ARS tables, also there are the internally transferred, covered, forwarded, etc scenarios if you want to be on the safe side. And still there is the route with cov Y and N scenarios which behaves totally differently for external routing, especially for SIP trunks.