Thanks so much ZeroZeroOne! The removal of the 5900 ldn record and configuration of a vdn in my DID range did the trick. [smile]
Internal calls are still hitting the attendant hunt group as they are supposed to, and the external calls are routed through the auto attendant vector.
Thanks again!
I am not sure what data the CO is sending to the switch for evaluation but would guess we're getting at least 4 digits based on our DID range (DID's not in the ldn table bypass the attendant). I could potentially use the incoming call handling table to manage the routing, but would need...
ISDN/PRI
Group Number 1
Group Type isdn
CDR Reports y
Group Name US-LEC ISDN-PRI
Native Name
Script Tag
COR 11
TN 1
TAC 701
Direction two-way
Outgoing Display n
CESID I Digits Sent
Trunk Signal Type
Dial Access n
Busy Threshold 255
Night Service
CO Type analog
Protocol Type inloc
Queue...
I'm using Avaya CM 3.1 with Hospitality features, BCMS and Attendant Vectoring for a hotel. We've use a single VDN (5991) to route all calls to the attendant hunt group through a simple vector that plays BGM and brand messages and repeats a "please hold" message periodically until the caller is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.