0 to attendant VDN through Tenant Partition not working...

[ashwebster]

I am trying to configure the 0 option to route to the attendant vectoring vdn for a particular tenant however when running a trace, the call is trying to go to the attd-group rather than the attendant vectoring VDN. I was under the impression that if this field has a VDN number filled in, calls should follow this VDN rather than go to the attd-group.
This is what I have setup:

TENANT 146

Tenant Description: xxxx

Attendant Group: 146

Ext Alert Port (TAAS):

Night Destination:

Music Source: 146

Attendant Vectoring VDN: 465-0000

DISTINCTIVE AUDIBLE ALERTING
Internal: 1 External: 2 Priority: 3
Attendant Originated Calls: external

COS Group: 146



VECTOR DIRECTORY NUMBER

Extension: 465-0000
Name*: xxxx
Destination: Vector Number 117
Attendant Vectoring? y


COR: 45
TN*: 146
Measured: external


CALL VECTOR

Number: 117 Name: Attd
Multimedia? n Attendant Vectoring? y Meet-me Conf? n Lock? y
Basic? y EAS? y G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y
Prompting? y LAI? y G3V4 Adv Route? y CINFO? y BSR? y Holidays? y
Variables? y 3.0 Enhanced? y
01 queue-to attd-group
02 wait-time 5 secs hearing ringback
03 route-to number 4655604 with cov y if unconditionally
04 stop
05

When running the trace, this is what I see:

04:03:03 TRACE STARTED 12/16/2013 CM Release String cold-03.0.124.0-21188
04:03:04 active station 4655501 cid 0x97e
04:03:04 dial 0
04:03:04 busy attendant-group 146 cid 0x97e
04:03:04 G711MU ssff ps:20
rgn:146 [10.132.37.130]:2496
rgn:146 [10.132.37.10]:2058
04:03:07 idle station 4655501 cid 0x97e
04:04:21 TRACE COMPLETE station 4655501 cid 0x0


Have I missed anything out as I can’t see why this isn’t working?

Thanks in advance for any help…


Apple Tree Education specialising in Avaya and Cisco IPT Training

http://www.apple-tree.co.uk

 

[montyzummer]

What entry is in your dial plan analysis for 0 ?

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[ashwebster]

Dialed Total Call
String Length Type
0 1 attd
1 7 ext

not sure if this comes out correct but basically:
dialled string - 0
total length - 1
call type - attd

thanks ash

Apple Tree Education specialising in Avaya and Cisco IPT Training

http://www.apple-tree.co.uk

 

[montyzummer]

So its behaving how its supposed to , guess you could change the attendant to ext in dial plan ana with a length of 1 , the create a vdn with extn 0 that points to your vector.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[ashwebster]

Thanks for the suggestion, the only issue is that this is a multi-site (about a 100 sites). the 0 for each site needs to go to the local reception phone. i'm a bit hesitant about changing the dial plan at this stage.

I thought the Tenant Attendant vectoring VDN was supposed to overcome this? I basically need the 0 option to go to the attendant VDN rather than the attd-group. all the documentation seems to say that if this is filled in, it should go to the VDN but it's definitely not hitting the VDN. it's trying the attd-group straight away rather than going to the VDN

Apple Tree Education specialising in Avaya and Cisco IPT Training

http://www.apple-tree.co.uk

 

[ashwebster]

I have found a solution so thought i'd post it just in case others would like to know.

I entered the VDN extension into the night service field within the tenant form and now 0 goes through to the attendant vectoring VDN rather than going straight to the attendant group.

Apple Tree Education specialising in Avaya and Cisco IPT Training

http://www.apple-tree.co.uk