Cisco Cisco Unified Customer Voice Portal 11.0(1) Release Note
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
52
•
element_log_[VARNAME] / element_nolog_[VARNAME] These create new element data
for this VoiceXML insert element whose name is VARNAME and which either sends a
logging event to log the element data value or not, respectively. The data type will be
assumed to be a string. The variable name cannot include spaces.
for this VoiceXML insert element whose name is VARNAME and which either sends a
logging event to log the element data value or not, respectively. The data type will be
assumed to be a string. The variable name cannot include spaces.
•
session_[VARNAME]. This creates a new session variable whose name is VARNAME. The
data type is assumed to be a string. The variable name cannot include spaces. If the variable
name already exists, the old value will be replaced with this one. If the old data type was not
a string, the new data type will be a string.
data type is assumed to be a string. The variable name cannot include spaces. If the variable
name already exists, the old value will be replaced with this one. If the old data type was not
a string, the new data type will be a string.
•
custom_[NAME]. This sends a custom logging event whose contents is the action named
NAME and the value of the variable being the description.
NAME and the value of the variable being the description.
•
set_uid. This associates the UID passed to the call.
•
audium_hotlink, audium_hotevent, audium_error, audium_action. These four Unified
CVP variables are created in the root document and must be passed along in the return
CVP variables are created in the root document and must be passed along in the return
namelist
. The content of each deals with the occurrence of any global hotlinks, hotevents,
errors, or actions (e.g., a hang-up) while in this insert element. Since the subdialog has its
own context and root document, this data has to be explicitly passed for any of these events
to be recognized by VXML Server. The developer should not alter the contents of these
variables.
own context and root document, this data has to be explicitly passed for any of these events
to be recognized by VXML Server. The developer should not alter the contents of these
variables.
•
audium_vxmlLog. This variable contains the raw content for an interaction logging event.
Adding to the interaction log is not required - the
Adding to the interaction log is not required - the
audium_vxmlLog
variable can be passed
empty. In order for VXML Server to parse the interaction data correctly, a special format is
required for the content of the
required for the content of the
audium_vxmlLog
variable. This format is defined below:
The format for interaction logging is:
“
|||ACTION$$$VALUE^^^ELAPSED
”
where:
•
ACTION is the name of the action. The following lists the possible action names and the
corresponding contents of VALUE:
corresponding contents of VALUE:
o
audio_group.
This is used to indicate that the caller heard an audio group play. VALUE is
the name of the audio group.
o
inputmode.
This is used to report how the caller entered their data, whether by voice or
by DTMF key presses. VALUE should be contents of the
inputmode
VoiceXML shadow
variable.
o
utterance.
This is used to report the utterance as recorded by the speech recognition
engine. VALUE should be the contents of the utterance VoiceXML shadow variable.
o
interpretation.
This is used to report the interpretation as recorded by the speech
recognition engine. VALUE should be the contents of the interpretation VoiceXML
shadow variable.
shadow variable.