Cisco Cisco Unified Customer Voice Portal 10.5(1) User Guide
C
HAPTER
2:
Unified CVP
C
OMPONENTS IN
D
ETAIL
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
31
be built using programming languages other than Java. Some more complex and tightly
integrated components can be built only through the Java API, though in most other aspects, the
two APIs are functionally identical. The APIs themselves and the process of building
components using either API is fully detailed in the Javadocs published with the software and in
the Programming Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio.
The two components that do not require the use of high-level programming, XML decisions and
VoiceXML insert elements, are fully explained in this document.
integrated components can be built only through the Java API, though in most other aspects, the
two APIs are functionally identical. The APIs themselves and the process of building
components using either API is fully detailed in the Javadocs published with the software and in
the Programming Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio.
The two components that do not require the use of high-level programming, XML decisions and
VoiceXML insert elements, are fully explained in this document.
The APIs are used to interface with VXML Server in order to retrieve data or change
information. The API provided to each component has slightly different functionality reflecting
each component’s unique abilities. The following lists abilities provided by the API that is
common to most components used within a callflow:
information. The API provided to each component has slightly different functionality reflecting
each component’s unique abilities. The following lists abilities provided by the API that is
common to most components used within a callflow:
•
Getting call information such as the ANI, DNIS, call start time, application name, etc.
•
Getting or setting global data, application data, element data or session data.
•
Getting information about the application’s settings such as the default audio path, voice
browser, etc.
browser, etc.
•
Setting the maintainer and default audio path. Changing the maintainer allows multiple
people to maintain different parts of a single application. Changing the default audio path
allows an application to change the persona or even language of the audio at any time during
the call.
people to maintain different parts of a single application. Changing the default audio path
allows an application to change the persona or even language of the audio at any time during
the call.
•
Sending a custom event to all application loggers (see Chapter 5: VXML Server Logging for
more on logging with VXML Server).
more on logging with VXML Server).
Table 2-2 shows which API can be used to construct the various components listed.
VXML Server Component
Build
With
Java API
With
Java API
Build Using
XML-over-
HTTP API
XML-over-
HTTP API
VoiceXML
Knowledge
Suggested
Knowledge
Suggested
Configurable Action and Decision Elements
Yes
No
No
Configurable Voice Elements
Yes
No
Yes
Standard Elements
Yes
Yes
No
Dynamic Element Configurations
Yes
Yes
No
Start or End of Call Actions
Yes
Yes
No
Hotevents Yes
No
Yes
Say It Smart Plugins
Yes
No
No
Start and End of Application Actions
Yes
No
No
Loggers Yes
No
No
On Error Notification
Yes
No
No
XML Decisions
NA
NA
NA
VoiceXML Insert Elements
NA
NA
Yes
Table 2-2