Kick in the right direction

[asguyas]

Hi guys and gals

I have a definity 3.1.4 and new to Avaya but have been self teaching myself the system over the last 6 months so not a complete noob.

my question is I have a DID number that I want to build what I would call a CCR tree. option 1 goes there, 2 goes there.

Should I build an auto attendent off of that DID or point the DID to a VDN and then a vector. Being a formal Nortel tech I would have used the auto attendent but in the Avaya system I am leaning towards VDN.

Can some one give me the pros and cons of those two options or just flat out say one of them is the best way?

 

[montyzummer]

you need to point the ddi to a vdn and then within the vdn select which vector to use , this is the only way to get this ddi can not route direct to vectors.

APSS (SME)
ACSS (SME)

 

[mojoputter]

VDN and vector is what you want to use, here's an example of a vector I recently setup.

01 wait-time    2   secs hearing ringback
02 goto step    19            if holiday          in     table 1
03 goto step    19            if holiday          in     table 2
04 goto step    19            if time-of-day      is all 17:00 to all 08:00
05 goto step    19            if time-of-day      is fri 16:30 to sat 08:00
06 goto step    19            if time-of-day      is sat 11:00 to mon 08:00
07 wait-time    2   secs hearing ringback
08 collect      1    digits after announcement 1111     for none
09 route-to     number 1217             with cov y if digit           =  1
10 route-to     number 1219             with cov y if digit           =  2
11 route-to     number 1202             with cov y if digit           =  3
12 route-to     number 1203             with cov y if digit           =  4
13 route-to     number 1220             with cov y if digit           =  5
14 wait-time    5   secs hearing silence
15 route-to     number 1219             with cov y if unconditionally
16 stop
17
18
19 route-to     number 98888188181      with cov n if unconditionally

 

[asguyas]

thank you very much