Cisco Cisco Unified Customer Voice Portal 10.5(1)

and user.microapp.UseVXMLParams is not set to N, the default extension of .vxml is
automatically added.

•

You can only specify the name of a single file in the Peripheral Variable. You cannot set this
value to a name/value pair.

For more information, see the sections on individual micro-applications in this chapter.

Capture (CAP) Micro-Application

The Capture (CAP) micro-application allows you to trigger the storage of current call data at
multiple points in the ICM routing script. The CAP micro-application must be configured as a
VRU script, and it is executed using a RunExternalScript node, just as with any other Unified
CVP micro-application. The VRU Script Name value is "CAP" or "CAP,xxx," where "xxx" is
any arbitrary string to be used if necessary for uniqueness purposes. There is no VRU Script
Config string.

Executing a Capture micro-application causes the ICM PG to produce an intermediate termination
record. Specifically, it writes a record in the Termination_Call_Detail (TCD) table which includes
all current call variables (but not the VRUProgress variable), router call keys, date and time,
caller entered digits, etc. Together with the TCD record, the Capture micro-application writes
a set of records to the Termination_Call_Variable (TCV) table which includes the current values
of all ECC variables.

Unified ICME provides no standard reporting templates for TCD and TCV records. These tables
are very large and minimally indexed, and are optimized for writing rather than querying, in
order to minimally impact call handling throughput. If you plan to report on this data, create
off-hours extract processes which copy rows in their raw format into a database which is external
to ICM. From there you can organize the tables in the way that best supports your querying
requirements.

Some information you need concerning these records:

•

TCD records for a given call may be identified because they contain the same
RouterCallKeyDay and RouterCallKey. Successive TCD records are ordered by incrementing
RouterCallKeySequenceNumber.

•

Intermediate TCD records may be identified because they contain a CallDisposition of 53,
“PartialCall”. Only the last TCD record for the call contains the actual disposition.

•

TCV records corresponding to a particular TCD record may be obtained by joining on
TCV.TCDRecoveryKey. This key matches the RecoveryKey value in the TCD record.

•

As of Unified ICME 6.0(0), the TCD record’s CallTypeId is populated even for VRU
peripherals. This means you can determine the call’s current CallType at the time of each
Capture micro-application invocation, as well as at the end of the call.

•

In Unified CVP Comprehensive call flow models, these records will be associated with the
VRU leg peripheral. If you are doing VRU application reporting, you may want to filter for
TCD records which contain the PeripheralID of the ISN VRU leg.

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