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
34
This task can only be done in the start of call action because the call technically has not started
when this action occurs.
when this action occurs.
The end of call action is given the special ability to produce a final VoiceXML page to send to
the browser. Even though the caller is no longer connected to the browser by the time the end of
call action is run, some voice browsers will allow for the interpretation of a VoiceXML page sent
back in response to a request triggered by a disconnect or hang-up event. Typically this page will
perform final logging tasks on the browser.
the browser. Even though the caller is no longer connected to the browser by the time the end of
call action is run, some voice browsers will allow for the interpretation of a VoiceXML page sent
back in response to a request triggered by a disconnect or hang-up event. Typically this page will
perform final logging tasks on the browser.
Hotevents
A hotevent is some developer-defined action performed whenever a VoiceXML event is
triggered. Hotevents can take two forms. The first simply moves the caller to a new part of the
call flow when the event is triggered. In this case the hotevent can be defined entirely in the
Builder for Call Studio by the application designer and does not require any additional work by a
developer. The second form of a hotevent executes custom VoiceXML content when the event is
triggered (and may optionally also move to another part of the call flow).
triggered. Hotevents can take two forms. The first simply moves the caller to a new part of the
call flow when the event is triggered. In this case the hotevent can be defined entirely in the
Builder for Call Studio by the application designer and does not require any additional work by a
developer. The second form of a hotevent executes custom VoiceXML content when the event is
triggered (and may optionally also move to another part of the call flow).
The second form requires a Java class that returns the VoiceXML to execute when the event is
triggered. This class is accessed once per call, not when the event is triggered. This is because
hotevents appear in the VoiceXML root document, which is generated when the application is
started or updated. For this reason the API provided to hotevents do not have access to call
information normally given to other components. The purpose of a hotevent is solely to produce
VoiceXML that will execute when the event is triggered.
triggered. This class is accessed once per call, not when the event is triggered. This is because
hotevents appear in the VoiceXML root document, which is generated when the application is
started or updated. For this reason the API provided to hotevents do not have access to call
information normally given to other components. The purpose of a hotevent is solely to produce
VoiceXML that will execute when the event is triggered.
A hotevent can be created to react based on a standard VoiceXML event such as nomatch or
noinput, but a more common use for a hotevent is to be triggered by a developer-specified or a
voice browser-specific event. For example, one can create a hotevent to play audio when a
custom event occurs.
noinput, but a more common use for a hotevent is to be triggered by a developer-specified or a
voice browser-specific event. For example, one can create a hotevent to play audio when a
custom event occurs.
As with any other component that produces VoiceXML, the hotevent utilizes the VFCs and
therefore can only be constructed with the Java API.
therefore can only be constructed with the Java API.
Say It Smart Plugins
In VXML Server, developers can create their own Say It Smart plugins. Similar to custom
elements, Say it Smart plugins are pre-built Java classes that when deployed in the Builder for
Call Studio can be used as a new Say It Smart type. As with custom elements, the level of
integration required with the Unified CVP software restricts the creation of Say It Smart plugins
to the Java API.
elements, Say it Smart plugins are pre-built Java classes that when deployed in the Builder for
Call Studio can be used as a new Say It Smart type. As with custom elements, the level of
integration required with the Unified CVP software restricts the creation of Say It Smart plugins
to the Java API.
Custom Say It Smart plugins can be constructed to read back formatted data not handled by
Unified CVP Say It Smart plugins, such as spelling playback or reading the name of an airport
from its three-digit code. Plugins can also be created to extend the functionality of existing
Unified CVP Say It Smart plugins, such as spelling playback or reading the name of an airport
from its three-digit code. Plugins can also be created to extend the functionality of existing