Including a vector variable in the converse-on command as a data item to pass (outpulse) to the VRU or IVR allows forwarding of additional data that is not currently a supported data type. You can define the variable as any of the existing variable types, such as collect, value, tod, doy, dow, and asaiuui. You can use the asaiuui type to forward data provided by a remote site or local ASAI interfaced application or with assignment using the set command. For this example, variable D forwards numerical account code data of up to 6 digits provided by an ASAI application.
Variable |
Description |
Type |
Scope |
Length |
Start |
D |
ASAI provided data |
asaiuui |
L |
6 |
1 |
The ASAI application uses adjunct routing to reach VDN2 that is assigned to the following vector. The data is included as ASAI UUI in the route-select message that routes the call to VDN2. The VRU interfaced through the converse-on command performs further interactive processing of the call based on the account code provided in the ASAI UUI and indicates where to next route the call.
1. wait-time 0 secs hearing music
2. converse-on skill 30 pri l passing vdn and D
3. collect 5 digits after announcement none for
4. route-to digits with coverage y
The collect command at step 3 collects the 5-digit destination provided by the VRU using the data return function. Step 4 routes the call to that destination.
From Avaya Aura® Call Center Elite 7.1 onwards, vectoring supports the ability to pass the Last Agent Login ID, using the agent variable, as a parameter in the converse-on vector command in the VDN Return Destination (VRD) vector.
01 converse-on skill 801 pri l passing LA and none [LA – 'agent' variable]