Vector administration supports the vector variable command syntax on Avaya CMS. However, the definition of each variable can only be administered through Communication Manager on the Variables for Vectors administration table.
Note:
The specific commands for which variables are supported, depends on the CMS and Communication Manager release.
Variable failure conditions
When the tested variable conditional is not defined in the variables for vectors administration table, a goto test fails. The call does not branch and processing falls through to the next vector step.
Retention of vector variable values and assignments
The content of a local vector variable exists only while a call is in vector processing. Once a call exits vector processing, the value is cleared. Note that a call that experiences a converse-on vector command remains in vector processing. In addition, a route-to or adjunct routing link step that routes to a local VDN extension also remains in vector processing. Therefore, values that can be obtained by the call related local vector variables (ani, asaiuui, collect, stepcnt, vdn, and vdntime) and the value stored in digits can be used in a subsequent routed-to vector or vector steps for the same call.
The value of a vector variable is not directly passed during an adjunct routing route request operation. The adjunct routing route request operation does pass the value of the digits buffer using the collected digits Information Element (IE). The vector set command can populate the digits buffer. The value determined by or assigned by using vector variables can be written to the digits buffer and become available to an adjunct. The set command can also be used to assign a value to the ASAI UUI string using the asaiuui vector variable type.
Vector Variable Usage Data
Enter the list measurements summary command to view the vector variable usage data on page 4 of the Measurement Summary report.
