Cisco Cisco Unified Customer Voice Portal 10.0(1) User Guide
C
HAPTER
5:
VXML Server
C
ONFIGURATION
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
120
Figure 6-1 displays the DTD diagram of the
global_config.xml
file. The elements in the XML
document are:
•
administration_port
– This tag defines the port on which administration activity takes place
and can be any positive integer. By default, the port is set to 10100. See Chapter 3:
Administration for more on administration activities.
Administration for more on administration activities.
•
error_class
– This tag defines the fully qualified Java class name of a class to execute when
an error occurs for notification purposes. By default no class is defined. See the
Programming Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio for
more on how to write the On Error Notification class.
Programming Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio for
more on how to write the On Error Notification class.
•
default_browser
– This tag defines the real name of the gateway adapter that should be used
by default when VXML Server needs to produce a VoiceXML page in a scenario where the
current application is unknown and therefore the gateway adapter for that application is
unknown. One such scenario is an error where the VXML Server session is unrecognized.
The reason this exists is because some gateways require the VoiceXML to be formatted in a
specific way (such as requiring an XML namespace to appear in the document) that if the
VoiceXML page were produced in a different format would cause an error on the gateway.
An application lists its gateway in its settings and normally this is available to VXML Server
to produce the correct VoiceXML. However in rare cases, an error occurs and VXML Server
does not have access to the session and hence the application that the call belonged to and
would need to know which gateway to have the resulting VoiceXML page conform to. By
default, if left blank in
current application is unknown and therefore the gateway adapter for that application is
unknown. One such scenario is an error where the VXML Server session is unrecognized.
The reason this exists is because some gateways require the VoiceXML to be formatted in a
specific way (such as requiring an XML namespace to appear in the document) that if the
VoiceXML page were produced in a different format would cause an error on the gateway.
An application lists its gateway in its settings and normally this is available to VXML Server
to produce the correct VoiceXML. However in rare cases, an error occurs and VXML Server
does not have access to the session and hence the application that the call belonged to and
would need to know which gateway to have the resulting VoiceXML page conform to. By
default, if left blank in
global_config.xml
, VXML Server will search through the directory
of installed gateway adapters and use the first one it finds.
•
default_subdialog
– This tag defines whether to treat a call that is not associated with an
application as if it were a VoiceXML subdialog and whose possible values are
true
and
false
. Some gateways (such as Cisco gateways) call all VXML Server applications as
VoiceXML subdialogs. VXML Server must be aware of this because it determines how the
VoiceXML it produces looks and if not produced correctly would cause an error on the
gateway. Typically, a call is made to an application which defines in its settings whether to
treat the application as a subdialog. However in rare cases, an error occurs and VXML Server
does not have access to the session and hence the application that the call belonged to and
would need to know whether to treat the call as a subdialog. By default, if left blank in
VoiceXML it produces looks and if not produced correctly would cause an error on the
gateway. Typically, a call is made to an application which defines in its settings whether to
treat the application as a subdialog. However in rare cases, an error occurs and VXML Server
does not have access to the session and hence the application that the call belonged to and
would need to know whether to treat the call as a subdialog. By default, if left blank in
global_config.xml
, VXML Server will consider a call to the application to not be a
subdialog.
•
session_invalidation_delay
– This tag defines the amount of time in seconds that VXML
Server will wait for after a call session ends before actually invalidating that session (this can
be any integer greater than or equal to 0). This configuration option is needed because there
may be various activities taken by loggers and end of call classes that require the session to
remain alive to access data within it (such as element or session data) and if the session were
invalidated would cause errors to occur when attempting to access the data. If this value were
too small (such as 0 seconds), many errors could occur for routine actions like logging at the
end of a call. If this value were too high, too many sessions would remain in memory for too
be any integer greater than or equal to 0). This configuration option is needed because there
may be various activities taken by loggers and end of call classes that require the session to
remain alive to access data within it (such as element or session data) and if the session were
invalidated would cause errors to occur when attempting to access the data. If this value were
too small (such as 0 seconds), many errors could occur for routine actions like logging at the
end of a call. If this value were too high, too many sessions would remain in memory for too