Cisco Cisco Unified Customer Voice Portal 11.0(1)

The user.microapp.metadata ECC variable is structured as follows:

m|con|tr|to|iv|duratn|vruscriptname

The following table shows the values for this variable.

D, V or N – Indicates whether the user responded with Voice (V),
DTMF (D), or not at all (N). (Note that for the Menu

m

micro-application, any successful single digit entry will result in
m being set to V or D, even if the entry was an invalid menu
selection.)

000 to 100 – Indicates the ASR percent confidence level at which
the voice input was finally recognized. This field is only valid if
m is Voice (V).

con

00 to 99 – Indicates how many tries were required. 01 means user
responded successfully after the first prompt.

tr

00 to 99 – Indicates how many timeouts occurred. Does not
include interdigit timeouts.

to

00 to 99 – Indicates how many invalid entries were received,
including interdigit timeouts.

iv

000000 to 999999 – Indicates the micro-application duration in
milliseconds. Duration is defined as the elapsed time between

duratn

entering and exiting the RunExternalScript node, as measured in
the IVR Service.

Full name of the VRU script which was executed. This is the only
variable length field.

vru script name

This ECC variable is optional. If used, you must define it in the Unified ICME Expanded Call
Context Variables configuration tool. The variable length would normally be configured as 62
bytes, but if ECC space is restricted, you can configure it as 21 bytes. This will drop the
vruscriptname subfield. If you do define this variable, its contents get written to the Unified
ICME database with every termination record, and can be used to provide a record of
meta-information about the execution of each input micro-application.

Common Configuration for Differentiating VRUs (Unified CVPs) Based on Dialed Number

The Network VRU configuration instructions in this guide assume that all callers will be routed
to the same VRUs (Unified CVPs) for VRU treatment purposes. Under this assumption, it is
always simplest to rely on the system default Network VRU. However, it is sometimes necessary
to differentiate the VRUs (Unified CVPs) based on dialed number.

Note: This section is only applicable to call flow models which use the SendToVRU node to
transfer the call to Unified CVP's VRU leg (it does not apply to Translation Route transfers).

Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 4.1(1)