I am new to Nortel Option 11c. I have a queue 4014 setup and any caller being hold in this queue over 5 minutes suppose be automatically forward to voicemail but it is not. Any idea why?
TYPE ACD
CUST 0
ACDN 4014
MWC NO
DSAC NO
MAXP 32
SDNB NO
BSCW NO
ISAP NO
AACQ NO
RGAI NO
ACAA NO
FRRT 11
FRT 6
SRRT 12
NRRT
FROA NO
NCFW 7000
FNCF NO
FORC NO
RTQT 0
SPCP NO
OBTN NO
RAO NO
CWTH 1
NCWL NO
BYTH 0
OVTH 2047
TOFT 300
HPQ NO
OCN NO
OVDN 7200
IFDN
OVBU LNK LNK LNK LNK
EMRT
MURT 14
RTPC NO
HOML YES
RDNA NO
ACNT
NRAC NO
DAL NO
RPRT YES
RAGT 4
DURT 30
RSND 4
FCTH 20
CRQS 100
IVR NO
CWNT NONE
Cung,
OVTH (Overflow Threshold) is how many calls can be holding in the queue before they overflow to the OVDN. 2047 is the maximum number of calls allow for this feature.
TOFT is the Timed Overflow Threshold. Currently calls to 4014 that are unanswered after 300 seconds should overflow to 7200 unless all agents are logged out of the queue.
What are DN 7000 from the NCFW (Night Call Forward: when all agents are logged out of the queue)
and DN 7200 from the OVDN (Overflow Directory Number)
DN 7000 and 7200 are voicemail. When all agents are not logged in, it goes directly to voicemail which is correct but when there is agent login and is busied, the call should go to voicemail after 5 minutes in the queue and that is not working.
i think that your probelm is that you have srrt=12 and i dont see any seconds for that,delete srrt,because you calls never wait for 5 minuts.they go frrt 11 after 6 secs. gets music,goes to srrt and gets music,goes to srrt and music and so on,so delete srrt then i think it works.
ok sorry i got called aqway ...iff you are still looking for the answer ill try agin....
the book says/// this is for TOFT "before defining the TOFT first delete that OVDN from its source ACD DN then enter the time in seconds that you want a call to wait in q before it overflows to an ovdn"..
Thanks for everyone trying to help. I got to the point where I do not know what to do anymore and ended up calling an expertise outside vendor and have the guy fixed it. It turns out that acd dn 7000 is alreay services 6 active (reaches its limit) acd dn and the tech has to do some programming in the backend to workaround it. Not sure exactly what he did.
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.