Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
C
HAPTER
2:
U
NIVERSAL
E
DITION
C
OMPONENTS IN
D
ETAIL
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
51
• The insert element cannot define its own root document, a root document generated by Call
Services must be used.
• The variables to return to Call Services, including the exit state, must conform to a strict
naming convention.
• When using the <return> tag, Universal Edition-specified arguments must be returned along
with the custom variables.
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.
Universal Edition 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 Universal Edition
requires the use of the Call Services-generated root document.
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 Universal Edition
requires the use of the Call Services-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”.