Dailplan analysis table question.

[skk391]

Hi all.

Fairly new to CM and Avaya products.

I have a question about my dailplan, we currently use 0 for our attd, I'm planning to change it to 12 but need to keep one location on 0. I thought I could do this by changing the dialplan ana table - add/change the following entry,

Overall, what I am trying to get working is that I would like all but one of my locations to use 12 or any other 2 digit number for the attd but then for one location only to use 0. Is this possible?


Dialed Total Call Dialed Total Call Dialed Total Call
String Length Type String Length Type String Length Type
12 2 attd 55 4 ext 86 5 ext

The original table
Dialed Total Call Dialed Total Call Dialed Total Call
String Length Type String Length Type String Length Type
0 1 attd 55 4 ext 86 5 ext
1 4 ext 56 4 ext 87 5 ext
1 5 ext 57 4 ext 88 4 dac
1 7 ext 59 4 ext 89 5 ext
2 4 ext 6 4 ext 9 1 fac
2 5 ext 6 5 ext * 3 fac
2 7 ext 6 7 ext *4 2 fac
3 4 ext 7 4 ext # 3 fac
3 5 ext 7 5 ext
3 7 ext 80 5 ext
4 4 ext 81 5 ext
4 7 ext 82 5 ext
5 4 ext 83 5 ext
5 7 ext 84 5 ext
54 4 ext 85 5 ext

When I try to make the change I get the following error message,

'One or more extensions exist with the same leading digits as this entry '

I can't see where the problem is, yes, we have extensions starting with 1 but they a total length of 4, so the system should wait for 4 digits, shouldn't it?

BTW I have just entered in 7 for the DS and TL of 2 for the attd and it has taken it??

Can someone shed some light in this for me please.

By plan of attack on this was to then change the ' change dialplan analysis location ' so that this entry is looked at before the global dialplan anan table above, I wanted a location to remain using 0 for the attd. The call type I can enter is udp, so I take it that the system will then send the call to the - uniform-dailplan.

I have then tried to enter in


Matching Insert Node
Pattern Len Del Digits Net Conv Num

0 1 0 n

I cant enter in this because Im getting an error message but the length needs to be greater then 1 or use L'x'.

Unable what to do after that.

Can anyone guide me please?

 

[AvayaTier3]

keep 0 attd
for other locations add dialplan 2 digit ext 6
create extension 62 and make it virtual with cover path to attd


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[skk391]

Thanks for the reply, I'm still learning all the tricks so the virtual extension and coverage path seems like a good idea, I am going to need a little more information if possible , mainly for my understanding more than anything.

I have around 250 locations, all but one will would like to use anything other than 0. The main reason is that people are forgetting to press 9 when trying to dial out , they are just pressing 0 and attempting to dial the number (uk)

The attendant vectoring VDN in the tenant config is set to a VDN and skill, the skill ends up getting all these 'nuisance' calls, so we are trying to stop this. These sites don't actually use a attd console so I could change the attd number once I've got a good understanding of the dialplan ana table.

My problem seems to be that I have one location which uses a slightly different config, the attendant vectoring on this goes to a vdn and a vector which does use a traditional attd group.

Users here would still like to use 0 to get to the attd, I thought I could use the change dialplan analysis location to 'overwite' the global dialplan analysis table so that calls made to 0 would be routed to 0, leaving all other locations to use the new attd number in the dialplan ana table.

How are the locations and tenant linked back together? Try to understand it in my head before making any changes.

Hope this makes sense.

 

[skk391]

Just thinking out loud, is there anyway that I could route the call within a vector, get rid of 0 = attd in the dialplan ana table. Then setup a new number 71 for example.
Send 71 to a VDN and then state if the call came from tenant X route to attd-group, otherwise send call to vdn X ??