Avaya Support Forums  

Go Back   Avaya Support Forums > Messaging

Thread Tools Search this Thread Display Modes
Old 01-30-2014, 02:35 PM
marsh108 marsh108 is offline
Join Date: Jan 2014
Posts: 4
marsh108 has 10 reputation points
Default Vector Route-to Audix extension unsuccessful

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?


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*:


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
Reply With Quote
Old 04-11-2014, 08:37 AM
bobby11 bobby11 is offline
Aspiring Member
Join Date: Apr 2014
Posts: 1
bobby11 has 10 reputation points

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
Reply With Quote
Old 04-11-2014, 09:45 AM
barblee07 barblee07 is offline
Hot Shot
Join Date: Mar 2011
Posts: 15
barblee07 has 14 reputation pointsbarblee07 has 14 reputation points

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.
Reply With Quote
Old 04-17-2014, 07:01 AM
richa164 richa164 is offline
Join Date: Oct 2013
Posts: 131
richa164 has 23 reputation pointsricha164 has 23 reputation points

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
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 04:11 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.