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
50
•
Call
. This information deals with the call. The inputs start with “audium_call_”.
o
audium_call_session_id
. The session ID.
o
audium_call_source
. The name of the application which transferred to this one. Will not
appear if this application is the first application in the call.
o
audium_call_start
. The start time of the call in the format “DAY MNAME MONTH
HH:MM:SS ZONE YEAR” where DAY is the abbreviated day of the week (e.g. “Wed”),
MNAME is the abbreviated name of the month (e.g. “Jun”), HH is the hour (in military
time), MM is the minute, SS is the seconds, ZONE is the time zone (e.g. “EDT”), and
YEAR is the four-digit year.
MNAME is the abbreviated name of the month (e.g. “Jun”), HH is the hour (in military
time), MM is the minute, SS is the seconds, ZONE is the time zone (e.g. “EDT”), and
YEAR is the four-digit year.
o
audium_call_application
. The name of the current application.
•
History
. This information deals with the history of elements visited so far in the call. The
inputs start with “audium_history_”.
o
audium_history
. This entire content of the element history (including exit states) is
contained in this variable. The format is [ELEMENT]:[EXITSTATE]|..|[
ELEMENT]:[EXITSTATE] where ELEMENT is the name of the element and
EXITSTATE is the name of the exit state of this element. The order of the element/exit
state pairs is consistent with the order in which they were visited. This will not appear if
this insert element is the first element in the call.
ELEMENT]:[EXITSTATE] where ELEMENT is the name of the element and
EXITSTATE is the name of the exit state of this element. The order of the element/exit
state pairs is consistent with the order in which they were visited. This will not appear if
this insert element is the first element in the call.
•
Data
. This is the element and session data created so far in the call.
o
audium_[ELEMENT]_[VARNAME]
. This is an element variable where ELEMENT is the
name of the element and VARNAME is the name of the variable. Note that both the
element and variable names will have all spaces replaced with underscores. There may be
no instances of this input if no element variables exist when this insert element is visited.
For example, the variable “audium_MyElement_the_value” is element data named “the
value” from the element “MyElement”.
element and variable names will have all spaces replaced with underscores. There may be
no instances of this input if no element variables exist when this insert element is visited.
For example, the variable “audium_MyElement_the_value” is element data named “the
value” from the element “MyElement”.
o
audium_session_[VARNAME]
. This is a session variable whose name is VARNAME.
Note that the variable name will have all spaces replaced with underscores. The value is
expressed as a string even if the type is not a string (the
expressed as a string even if the type is not a string (the
toString()
method of the Java
class is called). There may be no instances of this input if no session variables exist when
this insert element is visited.
this insert element is visited.
•
User Data
. This element information associated with the caller. It will only appear if the
application has associated the call with a UID and a user management database has been set
up for this application. The data will appear in the input exactly as in the database. The inputs
start with “user_”.
up for this application. The data will appear in the input exactly as in the database. The inputs
start with “user_”.
o
user_uid
. This is the UID of the user.
o
user_account_number
. The account number of the user.
o
user_account_pin
. The PIN of the user.
o
user_demographics_name
. The name of the user.