Cisco Cisco Customer Voice Portal 8.0(1) User Guide

C

HAPTER 

1:

 

I

NTRODUCTION

 

 

V

OICE

XML

 

S

ERVER 

U

SER 

G

UIDE 

 

 

 

FOR 

C

ISCO 

U

NIFIED 

C

USTOMER 

V

OICE 

P

ORTAL 

R

ELEASE 

4.0(1) 

 

 

 

 

 

10

   

, as described in the previous section, allow voice elements to set or use element or 

session data. Many voice elements use element data to store information captured from a 
caller, though voice element configurations can also define additional variables. 

Finally, a voice element's configuration can be either fixed or dynamic. 

   

 are XML files containing the desired settings, VoiceXML properties, 

audio groups, and variables that are then loaded by the VoiceXML Server. The same 
configuration is applied each time the voice element is called.  

    The configuration of some voice elements can only be determined at runtime. In these cases a 

 is used. As described previously, the Java API and XML API can be 

used to create dynamic configurations. 

For a complete list of the voice elements included in Unified CVP, refer to the VoiceXML 
Element Specification  for Cisco Unified Customer Voice Portal document. 

There are certain situations in a voice application where a developer may wish to include pre-
written VoiceXML into their Unified CVP application. The developer may desire fine-level 
control over a specific voice function at the VoiceXML tag level without having to get involved 
with constructing a custom configurable element in Java. Additionally, the developer may wish 
to integrate VoiceXML content that has already be created and tested into a Unified CVP 
application. These situations are handled by a VoiceXML insert element. 

VoiceXML insert elements contain VoiceXML code that the developer makes available as the 
content of a VoiceXML 

<subdialog>

. The content can be in the form of static VoiceXML files, 

JSP templates, or even dynamically generated by a separate application server. A framework is 
provided to allow seamless integration of VoiceXML insert elements with the rest of the call 
flow. 

The use of VoiceXML insert elements has its consequences such as the loss of being able to 
seamlessly switch between different voice browsers, some greater processing overhead involved 
with integration with the rest of the call flow, as well as the added complexity of dealing with 
VoiceXML itself rather than creating an application with easy to use configurable elements. 

VoiceXML insert elements can have as many exit states as the developer requires, with a 
minimum of one.