Cisco Cisco Unified Customer Voice Portal 10.5(1) User Guide
C
HAPTER
2:
V
OICE
XML
S
ERVER
C
OMPONENTS IN
D
ETAIL
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)
36
Inputs
As with any element in the application, an insert element would need to be able to access
information about the call such as element and session data, call data (such as the ANI), and even
information found in the user management database if the application is configured to use one.
Normally, this information is available in the Java or XML API. Since an insert element is
written in VoiceXML, this information must be made available for the insert element to use from
within the VoiceXML.
information about the call such as element and session data, call data (such as the ANI), and even
information found in the user management database if the application is configured to use one.
Normally, this information is available in the Java or XML API. Since an insert element is
written in VoiceXML, this information must be made available for the insert element to use from
within the VoiceXML.
Unified CVP achieves this by creating VoiceXML variables in the root document containing all
the desired information. The variable names conform to a naming convention so the Insert
element developer can refer to them appropriately. This is one reason why Unified CVP requires
the use of the VoiceXML Server-generated root document.
the desired information. The variable names conform to a naming convention so the Insert
element developer can refer to them appropriately. This is one reason why Unified CVP requires
the use of the VoiceXML Server-generated root document.
In order to cut down on the number of variables appearing in the root document, the application
designer is given the option of choosing which input groups are passed to the insert element.
Additionally, the designer can individually choose which element and session data to pass. By
minimizing the inputs to only the data required by the insert element, the overhead involved in
using an Insert element is minimized.
designer is given the option of choosing which input groups are passed to the insert element.
Additionally, the designer can individually choose which element and session data to pass. By
minimizing the inputs to only the data required by the insert element, the overhead involved in
using an Insert element is minimized.
Each input type is listed below:
Telephony
. This information deals with telephony data. The inputs start with
“audium_telephony_”.
o
audium_telephony_ani.
The phone number of the caller or “NA” if not sent.
o
audium_telephony_dnis
. The DNIS or “NA” if not sent.
o
audium_telephony_iidigits
. The IIDIGITS or “NA” if not sent.
o
audium_telephony_uui
. The UUI or “NA” if not sent.
o
audium_telephony_area_code
. The area code of the caller’s phone number. Will not
appear if the ANI is “NA”.
o
audium_telephony_exchange
. The exchange. Will not appear if the ANI is “NA”.
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 timezone (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 timezone (e.g. “EDT”), and
YEAR is the four-digit year.
o
audium_call_application
. The name of the current application.