Cisco Cisco Unified Customer Voice Portal 11.0(1)

Subdialog_End elements are never filtered from reporting data unless Reporting is disabled
on the VoiceXML Server.

•

The Exclusive Filter takes precedence over the Inclusive Filter. For example, if an application
name is in the Exclusive Filter, then all of the items of that applications are excluded from
reporting data even if a particular field or element is listed in the Inclusive filter.

•

The syntax for Inclusive/Exclusive filters is:

or

Note: This syntax is used to indicate session variables.

•

A semicolon (;) should be used to separate each item in a filter. For example, 

 is valid.

•

A single wildcard (*) can be specified anywhere within the application name, element type,
element name, or field name.

•

Element types, element names, and field names can contain alphanumeric characters,
underscores, and a space character.

•

An application name can contain alphanumeric characters and underscores, but the space
character is not allowed. For example, 

 is valid.

Examples of VoiceXML Filter Wildcard Matching

The table below provides examples of VoiceXML filter wildcard matching.

Matches all voice elements in MyApplication

MyApplication.Voice.*.*

Matches all Voice elements in all applications.

*.Voice.*.*

Matches all fields in MyApplication that start with the string

.

MyApplication.*.*.var*

Matches all fields in MyApplication that end with 

.

MyApplication.*.*.*3

Matches the Company session variable in MyApplication.

MyApplication.*.*.SESSION:Company

Examples of Inclusive and Exclusive VoiceXML Filters for Reporting

The table below provides examples of some different combinations of Inclusive and Exclusive
filters and the resulting data that the VoiceXML Server feeds to the Reporting Server.

Reporting Guide for Cisco Unified Customer Voice Portal Release 4.0(1)