Change TAC/AAR for Interoffice dialing

[homemade88]

Hi

There are 4 sites, 3 with IP offices and 1 with a G450 Communications Manager. I recently setup IP Office #3, which can dial internal extensions for the other 3 sites fine. The G450 CM is also able to dial to the new IP Office #3, however, the only way its able to dial internally to IPO #3 is by dialing the 4 Digit (which is 3 digits too long) TAC number to access that trunk.

When I try to change the TAC number, its telling me to check my dial plan, I want to be able to dial 8 then the 3-digit extension that starts with 4, so a user would press 8406 to reach a person at IPO #3. 8 is currently my FAC for the AAR and in the AAR the following is listed:

405, 406, 407 and 408 are the extensions for the users at IPO #3. When I dial for example 8408, it says on the screen the name of the trunk its trying to route through (which seems to be the correct one) followed by the 4-digit TAC number and a beeping tone. Either way, I know the trunk is working since I can dial through it internally using the TAC to reach IPO #3, but I can't modify it or use the AAR to get through. Feel free to ask about anything I didn't cover here and I'll do what I can to get the answer for you, since I have remote access to them.

 

[avayaguy23]

Issue is with your dial plan on CM.

 

[homemade88]

That's what I've concluded, but I just don't know what to change/modify exactly

 

[avayaguy23]

Post your dial plan

 

[homemade88]

Here's the analysis, hopefully its what you need to see:

 

[Sean655]

How do you call the other IPO sites? I don't see their extensions listed in AAR?
What does route 251 look like?
The route pattern is selecting the trunk so there's no need for a TAC code at that point.

 

[avayaguy23]

You need to change dialed string 8 from a FAC to EXT with a length of 4. You can then use AAR to route the call.

 

[Sean655]

It looks like 8 is the FAC for AAR so that shouldn't have to change.
If you can dial 3 digit to the other IPO's then you should mimic that programming. The uniform dialplan table may come into play.

 

[homemade88]

Today's been crazy busy for me, so I'm just getting back to this and it has my undivided attention now. Anyway...

@Sean655: Just so I'm making things as clear as possible, here's what we have:

IPO #1 Freeport
IPO #2 Abaco
IPO #3 Eleuthera
G450 #4 Nassau

- They currently use 2 to dial out through trunk #18 and reach IPO #1. The extensions at that IPO are 4-digits and start with 35XX, so they dial 235XX to reach the IPO at trunk #18.
- Dialing 2 somehow also allows them to reach the 4-digit extensions on IPO #2, so they dial 260XX to reach them.

Here's the route patterns and trunk groups I'm seeing:

I didn't set up the G450 and I'm now responsible for it so I'm still learning what's been set up in there.

 

[Sean655]

Could you show the first page of the feature codes and of uniform dialplan?
It seems like 2 (and/or 8) is the FAC for AAR and you would have entries for the IPO extension ranges in the AAR table.
Is there a reason you want to dial 8 instead of 2 + ext to reach IPO #3?

 

[homemade88]

Here you go:

I did a "list uniform-dialplan" and it returned the following response "No data in the system to list", so I suppose there aren't any entries in there.

The client claimed they dialed 8 to reach their old PBX before I added the IPO #3, but using 2 for IPO #3 is completely fine if we can get it to work that way.

 

[Sean655]

I missed that 2 was the TAC for Trunk 18, that explains how users were dialing to the other offices.
It looks like all of the programming is in place then. Show a trace of your call when you dial 8 40x.

 

[homemade88]

I won't be able to send the trace until Monday Morning, that's when someone should be at that office to test with me.

 

[homemade88]

So here's the trace from an extension at PBX #4 calling to #3

- The 1st and 2nd photos are of the person dialing 2 then 406
- The 3rd and 4th two photos are of the person dialing 8 then 406

 

[Sean655]

Somehow the TAC is getting inserted into the call string and that is causing the failure. I haven't come across that before and your route pattern is not inserting anything so I'm a little stumped.

 

[homemade88]

Yeah, it's so strange, It's probably something very simple too lol. Anyway, I'll keep working at it and will update this if I find a solution. Let me know if you come up with anything as well. Appreciate the help so far.

 

[kyle555]

anything in aar digit conversion?

 

[homemade88]

Hey Kyle,

Thanks for jumping in and yes, there is:

 

[kyle555]

So you dial 8406. 8 is the aar code
Now you dial 406 - there's a match that sends that to ext

Maybe that has something to do with it.

 

[kyle555]

Hey, do this:

add 406 to aar digit conversion and instead of sending it to ext send it to aar and see what happens