Cisco Cisco Unified Customer Voice Portal 10.5(1)

The Capture (CAP) micro-application is new for CVP 3.0. It has been added to allow 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 
CVP micro-application. The VRU Script Name should be “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 microapplication 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. 

ICM 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, you should 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 ICM 6.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 microapplication 
invocation, as well as at the end of the call.

In CVP Comprehensive Model deployments, 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.

If using the Capture microapplication you should keep in mind that it places a heavy demand on ICM 
resources. Each time you use it, the ICM writes one TCD record and multiple TCV records. Though it 
can conveniently capture the information you need, it is also likely to capture a great deal of extra 
information which you do not require. If you overuse this microapplication, you may end up placing a 
heavy load on the ICM both in terms of processing time and disk space, which despite the minimal 
indexing, may nevertheless impact ICM’s ability to handle the expected call load. Therefore it is 
recommended that you choose carefully where in your scripts you really need to capture information, 
and that you spread data items into as many different call variables as possible in order to maximize the 
usefulness of each invocation.

The Play Media (PM) micro-application simply plays a message contained in a media file. Use the ICM 
Configuration Manager’s Network VRU Script List tool’s Attributes tab to specify parameters.