Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Converse Vector with 2 Collect Steps.

Status
Not open for further replies.

brb5548

IS-IT--Management
Feb 26, 2003
14
US
Hi all,
I would like to create a vector that did a converse-on to a IVR skill and then had two collect steps. The first collect step would accept the transfer destination logic and the second collect step would be additional information about the caller, like an account number. This is how I would like to build the vector:
01 converse-on skill 5 pri m passing none and none
02 collect 1 digit after annoucement none for A
03 collect 12 digits after annoucment none for B
04 goto step 7 if A = 1
05 goto step 8 if A = 2
06 route to number 3800 with cov n if unconditionally
07 route to number 3990 with cov n if unconditionally
08 route to number 3991 with cov n if unconditionally

I am not sure if I should use the feature access code for converse data 1 or converse data 2, or how this should work.

I would assume that IVR would outpulse the converse data return feature access code followed by the collect string. eg; 1#123456789012

Can anyone tell me if I am on the right path here?
 
brb5548,

no need to make it that complicated. collect digits step will only get specified number of digits, so you can use as much consecutive collect digits steps after converse-on as you need. in short, you don't need to bother with hashes in ivr output or like that, just outpulse as much digits as you want and then use collect digits steps. an example you posted above won't work because of hash sign. first collect digits step will get only one digit which is 1, and the second collect digits step will get null string because hash is an end-of-digits sign. therefore the rest of the digit string will remain in digit buffer and not passed to variable B.
from an ivr side you need to outpulse converse data return feature access code and then digit string without hashes.
 
So just to clarify, the only thing I need to change is the way the ivr outpulses the digits by removing the # character. eg; 1123456789012

Also, if I remember any of your other postings, you have some knowledge with cti... As a side question, can a vector populate a UUI-IE variable and if so will the be visible from an asai link? I am going to test in a minute to verify but I thought I would ask.

Thanks!
 
brb5548,

yes, exactly. remove hash sign from the output and you should be fine. except one thing: if you want the second part of the digit string to be displayed on agents' phone screens, you need to collect it into common digit buffer, not variable.

if you have cm3 you can assign an asaiuui type variable and use it in vectors. i can't say exactly if it can be changed from a vector but nothing in the manual says it can't be. i haven't tried to set or change it myself, only check it for this or that value. i guess that's the commonest use for it. however, nothing keeps you from trying and seeing whether it's possible or not. and of course it will be visible from asai link. there's just one uui information element associated with a call so if you change it in vector and then use adjunct-route step to pass data to asai adjunct it will get the modified uui. the same way it can be modified on the adjunct side and passed back to be checked in a vector. you can pass it back and forth as many times as you need.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top