Vector Route-to Audix extension unsuccessful

[marsh108]

I have been searching forums and reading the documentation without any luck so I am hoping someone will be able to help. What I am trying to do seems simple but is not working. I want to setup a VDN in our DID range so that when external callers dial the number it transfers to the Audix system for voicemail access. I know they can call their DID and hit *7 but I want to keep it simple.

My current setup is a VDN that points to a vector. That vector is set to route-to the internal extension for voicemail, the same one our stations dial when hitting the message button on a phone. I set all this up successfully but when it tries to transfer to the audix extension I get "extension not valid". I would like to have it say 'Welcome to Audix" so the user can enter their extension and password to access VM. I assume this is a security feature and I have read that in order for an extension to call audix it needs to be a station. Anyway around this?

VDN

Extension: 8555
Name*: RouteToVM
Destination: Vector Number 3
Attendant Vectoring? n
Meet-me Conferencing? n
Allow VDN Override? n
COR: 1
TN*: 1
Measured: none

VDN of Origin Annc. Extension*:

----------------------------------------------------------------------------------------------
CALL VECTOR

Number: 3 Name: From8555to1999
Multimedia? n Attendant Vectoring? n Meet-me Conf? n Lock? n
Basic? y EAS? n G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y
Prompting? y LAI? n G3V4 Adv Route? y CINFO? y BSR? n Holidays? y
Variables? n 3.0 Enhanced? n
01 wait-time 1 secs hearing silence
02 route-to number 1999 with cov n if unconditionally
03 stop
04
05
06
07

[bobby11]

your audix is in a hunt group whit all your connecting out going ext numbers ? you shouldn't need a vector to do this just make it a hunt group

[barblee07]

On your VDN form, change allow VDN override to "Y".
Also on the vector form, change the cov "n" to cov "y"
This may fix your problem.

[richa164]

Just simply modify the number in your incomming treatment table on the trunk group to hit the VM hunt group , no need for VDN etc