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:
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)
16
Application data is typically used to store application-specific information that does not change
on a per call basis and is to be available to all calls. For example, the location of a database to
use for the application.
on a per call basis and is to be available to all calls. For example, the location of a database to
use for the application.
Session Data
Session data variables are accessible and modifiable from a single call session. Session data
variables in one call cannot be accessed by components handling another call. Each session has
its own session data namespace - session data set by one component will overwrite existing
session data that has the same name. Session data can hold any data, including a Java data
structure. The lifetime of session data is the lifetime of the session or the call. When the call
ends, the session data is deleted.
variables in one call cannot be accessed by components handling another call. Each session has
its own session data namespace - session data set by one component will overwrite existing
session data that has the same name. Session data can hold any data, including a Java data
structure. The lifetime of session data is the lifetime of the session or the call. When the call
ends, the session data is deleted.
Any component accessed within a call session, including elements, can create, modify and delete
session data. Session data can even be created automatically by the system in two ways:
session data. Session data can even be created automatically by the system in two ways:
If the voice browser passes additional arguments to Unified CVP VoiceXML Server when
the call is first received, these additional arguments will be added as session data with the
arguments’ name/value pairs translated to the session data name and value (both as
arguments’ name/value pairs translated to the session data name and value (both as
String
s).
For example, if the voice browser calls the URL:
http://myserver.com/CVP/Server?application=MyApp&SomeData=1234
this will create session data named “SomeData” with a value of “1234” in every call session
of the application “MyApp” that starts via this URL.
If a Unified CVP voice application performs an application transfer to another application
and the developer has chosen to pass data from the source application to the destination
application, then this data will appear as session data in the destination application (the data
is renamed before it is passed to the destination application). Please refer to the Unified CVP
VoiceXML Studio documentation for more information on application transfers.
application, then this data will appear as session data in the destination application (the data
is renamed before it is passed to the destination application). Please refer to the Unified CVP
VoiceXML Studio documentation for more information on application transfers.
Element Data
Element data variables are accessible from a single call session and modifiable from a single
element within that call session. As the name suggests, element data can only be created by
elements (excluding start and end of call events, the global error handler, hotevents, and XML
decisions). Dynamic configurations are technically part of an element since they are responsible
for configuring an element, so they can also create element data. Only the element that created an
element data variable can modify or delete it, though it can be read by all other components. Due
to the fact that the variable belongs to the element, the variable namespace is contained within
the element, meaning two elements can define element data with the same name without
interfering with each other. To uniquely identify an element data variable, both the name of the
element and the name of the variable must be used. Like session data, the lifetime of session data
is the lifetime of the session or the call. When the call ends, the element data is deleted.
element within that call session. As the name suggests, element data can only be created by
elements (excluding start and end of call events, the global error handler, hotevents, and XML
decisions). Dynamic configurations are technically part of an element since they are responsible
for configuring an element, so they can also create element data. Only the element that created an
element data variable can modify or delete it, though it can be read by all other components. Due
to the fact that the variable belongs to the element, the variable namespace is contained within
the element, meaning two elements can define element data with the same name without
interfering with each other. To uniquely identify an element data variable, both the name of the
element and the name of the variable must be used. Like session data, the lifetime of session data
is the lifetime of the session or the call. When the call ends, the element data is deleted.