grahekf

I would like to send calls to voicemail after they have been holding for 3 minutes. If I add the step 15 to my vector will that accomplish what I want, or will it send all calls to voicemail if ther is one call that has been in queue for 3 minutes?

01 goto vector 90 @step 1 if staffed-agents in skill 90 > 0
02 goto step 30 if staffed-agents in skill 1st < 1
03 queue-to skill 1st pri l
04 queue-to skill 2nd pri l
05 announcement 2420
...

12 collect 1 digits after announcement 2423 for none
13 goto step 30 if digits = 1
14 wait-time 30 secs hearing music
15 goto step 30 if oldest-call-wait in skill 1st pri l >= 500
16 goto step 12 if unconditionally
17 stop

...

30 stop
31 messaging skill 99 for extension 3417
32 stop

ahays

Nope. Step 15 says goto step 30. Step 30 simply says STOP and will immedaitely HALT all vector processing. Now, if step 15 said goto step 31 then ALL CALLS that reach step 15 will go to voicemail x3417 as long as the oldest call in the vector has been queued in skill 1st for 8 mins and 20 seconds (500 secs) ... not just the oldest call itself, but ALL calls will go to step 31 as long as ANY call queued in skill 1st is >= 500 secs.

regs,

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

PBXtech.info

 

colt45

You could use "EWT for call". Remember, this only works when the "call" is in queue. To divert a call before placing it in queue use "ewt for skill xx pri m >= xx"

...
15 goto step 30 if ewt for call >= 500
...
30 messaging skill xxx for 1234.
31 busy
32 stop

A-Train

I could be wrong here but EWT is expected wait time. So if a call has an expected wait time of over 500 seconds then send it. This is not its actual wait time. So the call could be there for 1 minute, but if the EWT is 3 minutes (for some reason) it will head to VM right away after 1 minute, not wait the actual time.

In the past I have gone low tech with this and just kept doing repeating steps. This will fill up your vector fast, so you may need multiple vectors to accomplish it.

colt45

I'm using CM3.5.1. Expected Wait Time for call, when used in a hold loop, works pretty good.

If you have vector variables, you can also set a variable to 'count' the number of steps the call has traversed in the vector. "goto step xx if count => nn". So if it takes 60 seconds total for each hold loop and that loop contains 3 steps, add the number of steps to get to the loop then the number of steps executed in the number of loops until your time has expired. For example, if it takes 12 steps to get to the loop then you would have 15 at the end of the first loop. Then increment by 3 for each additional loop. After 5 minutes at 60 seconds per loop = 5 x 3 or 15 added to the original 12 for 27. When the variable counter reaches 27 jump out to the VM system.

Keep in mind the counter is the number of steps executed so if you jump over some steps such as time of day, don't count those. It may take a little experimentation to get it right.

One trick to test vector conditions is set the condition to goto a subsequent step that just does a goto back to the step after the condition. No action is taken and vector continues processing. Then use "list trace vector" and place a call. If vector sends you to your test step then the condition is working.

caplink811

Hi,

you should administer a variable (e.g T with type vdntime) and then use this variable in your vector...

15 goto step 31 if T > 180

this is the recommended way when you want to route the call which waits for 180 seconds, and not the next one (ocw > 180).

bye
JrB

PBXtech.info