The following syntax rules apply when you use vector variables with the converse-on command:

converse-on split [hunt group, 1st, 2nd, 3rd] pri [l, m, h, t] 
passing [A-Z, AA-ZZ] and [A-Z, AA-ZZ]
converse-on split [hunt group] 
pri [l, m, h, t] 
passing [A-Z, AA-ZZ] and [A-Z, AA-ZZ]

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 a VDN Return Destination (VRD) vector.

01 converse-on skill 801 pri l passing LA and none [LA – 'agent' variable]

Requirements and considerations

The requirements and considerations for using vector variables with the converse-on command are as follows:

• You can use a variable as a data type in both passing fields. This results in outpulsing the current value of up to 16 digits for each of the specified variables as a DTMF digit stream to the VRU or IVR connected by the converse-on command.

• The normal converse-on command rules for both passing fields apply. If the variable is defined, the passed DTMF digits are the current assignment of the variable followed by a # DTMF digit. If a variable is not defined, or assigned to none or #, a single # DTMF digit is outpulsed for that data item (treated as though the data type is none) and a vector event 38 (variable not defined) or vector event 213 (no digits in variable) is logged.