Vector: Want to collect digits twice 3

[kmcglinchey]

G3SiV12/CM 2.1

Using Avaya IP Agent to pop a screen driven by digits collected in a vector. Digits are provided by 3rd-party IVR calling into the Definity (a human is conferenced by the IVR). I want to provide an "out" to voicemail for the human ("Press 1 to leave us a message, press 2 to continue holding"), which I would normally do by a collect digits step. Tried this (see vector below), but if the collect step times-out, I loose the digits collected in the first step. Any thoughts about how to give the human an out without whacking the previously collected digits? Here's the vector:

01 collect 5 digits after announcement none for none
02 queue-to skill 74 pri t
03 wait-time 30 secs hearing music
04 collect 1 digit after announcement 3624 for none ("press 1 to leave a message")
05 goto step 07 if digits = 1
06 goto step 2 if unconditionally
07 route-to number 1931 with cov y if unconditionally (voicemail ext)
08 stop

Thanks

 

[nohuhu]

kmcglinchey,

since you have cm2.1, you can use the new feature called 'variables in vectors'. take a look at it, it's real good.

 

[4merAvaya]

There is only one buffer for the collected digits. By collecting a second time you will overwrite the first set of collected digits.

Kevin

 

[kmcglinchey]

dwalin - Fantastic ... that looks like the ticket. We'll test it tonight and see how it goes. I'm thinking the "viv" feature might come in handy for other things too...

I appreciate the response.

 

[telcomwork]

Where can I find more info on VIV?

 

[kmcglinchey]

On the Avaya support site:

http://support.avaya.com/japple/css/japple?PAGE=avaya.css.TechnicalDatabase

Search for:

07-300302

You should get a .pdf search hit for CM 2.2. Open it and down about page 139 or so, there'll be a chapter on viv.

Have fun...

 

[telcomwork]

I downloaded 2.1 and thought it was in there. I'll try 2.2 now. Thanks!

 

[Tolson]

By the way, in the vector above on line 6 you are gouing to line 2 which will requeue the call, goto line 3 instead. You can only queue the call three times before you will start dequeueing the calls and destroying and valid measurements.

 

[kmcglinchey]

tolson -- interesting. I have been operating under the premise that a particular call queued to the same skill at the same priority would NOT have an impact on the queued state of that call (or any other call).

Does the 4th requeue of the call make it dequeue? Maybe I need to spend some more quality time with the manual referenced above...

 

[yurichan]

CM2.x Variables in Vectors will not directly help with the overwriting of the digits buffer in the 2nd collect step. You would have to play some games with storing the 5 digits from the first collect step into a variable, and then let the 2nd collect step overwrite the digits buffer, and add a converse-on step passing the first 5 collected digits (stored in a variable) to an IVR. That IVR would then "converse-data return" back those same 5 digits (collected in the first collect step, stored in a variable)and are recollected in a 3rd collect step. This 3rd collect step would repopulate the "digits buffer" so when the call is eventually routed, the "info=" will display the 5 collected digits. Just a thought.

By the way, as long as you re-queue to the same split, I believe you don't lose your place in queue and you can do this as often as you like. It is when you try to queue to 4 DIFFERENT queues is when your 4th queuing will fail.