Attdndant Vectoring Problem

[samorse]

I have changed 0 in the dialplan to type of EXT and created a VDN with extension 0 that points to Vector 1. When calling in, dialing 0 at the Auto Attendant seems to queue properly in the vector, but when someone on-site dials 0, the queue fails and routes to the covering extension. Maybe coincidence, but the call shouldn't be treated differently, inside vs. out? Any ideas?

CALL VECTOR

Number: 1 Name: Att Vector
Multimedia? n Attendant Vectoring? y Meet-me Conf? n Lock? y
Basic? n EAS? n G3V4 Enhanced? n ANI/II-Digits? n ASAI Routing? n
Prompting? y LAI? n G3V4 Adv Route? n CINFO? n BSR? n Holidays? y
Variables? n
01 wait-time 2 secs hearing ringback
02 queue-to attd-group
03 goto step 8 if queue-fail
04
05
06
07
08 route-to number 5000 with cov y if unconditionally
09 stop

 

[gingersnap1027]

You need to change 0 back to attd in your dialplan, next add a new vdn which follows your normal dialplan to point to the attendant vector. Then change tenant and add in the new vdn to the Attendant Vectoring VDN field. Should all work after that.

 

[samorse]

I don't have tenant partitioning active. I have created a separate VDN that points to the attendant vector, so I am going to test with that, but can't figure why 0 works for the VDN external vs. internal.

 

[samorse]

Update. When the VDN is called internally (8010), the attd-queue always fails and the call routes to extension 5000.

Any clue why that would happen?

Thanks

 

[samorse]

Another update. I have added the Attendant VDN # to the console parameters. Still, internal calls to 8010 (Attendant VDN) never queue, adn go straight to the covering extension.

 

[samorse]

Thanks anyway....

 

[gingersnap1027]

I don't have tenant partitioning on either but I am by default tenant 1 so that should still work