Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
C
HAPTER
3:
A
DMINISTRATION
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
68
•
SessionTimeout
– this shows the length of time, in seconds, of inactivity to consider a call
session timed out.
•
SuspendedAudioFile
– The path for the audio file to play to callers when calling into an
application that is suspended.
An administrator may choose to change the default audio path of an application at runtime
should there be a need to change the audio callers hear quicky. One use case would be if the
server that hosts the audio files is being restarted and the administrator wishes all audio to be
fetched from a backup server. Note that the effectiveness of this change will be based on how
consistently the application was designed to use the default audio path and also if the application
explicitly sets the default audio path itself by not enabling the default audio path configuration
setting, which would override the value passed here.
should there be a need to change the audio callers hear quicky. One use case would be if the
server that hosts the audio files is being restarted and the administrator wishes all audio to be
fetched from a backup server. Note that the effectiveness of this change will be based on how
consistently the application was designed to use the default audio path and also if the application
explicitly sets the default audio path itself by not enabling the default audio path configuration
setting, which would override the value passed here.
An administrator may choose to change the session timeout value at runtime as part of the
process of debugging a problem. Under normal circumstances no session should time out
because the voice browser and Call Services should be in constant communication regarding
when a call starts and ends. An administrator expreiancing some sessions timing out may choose
to increase this attribute to see if it resolves the issue and if not, should look into network issues.
The administrator should be careful not to set this value too small because there is a risk that a
normal call could time out due to the caller visiting a particularly large VoiceXML page or
taking their time entering a long DTMF input. Too large a number will mean that sessions that
are no longer valid will remain in memory longer and the administrator would not be able to see
which sessions timed out until the timeout period elapsed.
process of debugging a problem. Under normal circumstances no session should time out
because the voice browser and Call Services should be in constant communication regarding
when a call starts and ends. An administrator expreiancing some sessions timing out may choose
to increase this attribute to see if it resolves the issue and if not, should look into network issues.
The administrator should be careful not to set this value too small because there is a risk that a
normal call could time out due to the caller visiting a particularly large VoiceXML page or
taking their time entering a long DTMF input. Too large a number will mean that sessions that
are no longer valid will remain in memory longer and the administrator would not be able to see
which sessions timed out until the timeout period elapsed.
An administrator may choose to change the suspended audio file at runtime if the application
needed to be suspended due to a specific reason. For example, if a weather event required an
application to be suspended, the administrator could point the suspended audio message to a
recording explaining why the application is suspended rather then just pointing to a generic
message. The administrator is taking advantage of the fact that this change is not persisted since
it is expected that the event that caused the application’s suspension is temporary.
needed to be suspended due to a specific reason. For example, if a weather event required an
application to be suspended, the administrator could point the suspended audio message to a
recording explaining why the application is suspended rather then just pointing to a generic
message. The administrator is taking advantage of the fact that this change is not persisted since
it is expected that the event that caused the application’s suspension is temporary.
Administration Functions
Call Services exposes several functions that allow an administrator to make both small and large
changes to the applications and Call Services at runtime. They are divided into two categories:
those that affect a specific application and those that affect all applications running on Call
Services. An administrator can use the JMX interface as well as administration scripts to execute
these functions.
changes to the applications and Call Services at runtime. They are divided into two categories:
those that affect a specific application and those that affect all applications running on Call
Services. An administrator can use the JMX interface as well as administration scripts to execute
these functions.
Each administrator function, when activated, prompts Call Services to send a logger event
reporting the function and its result so that any loggers listening to these events can log the
information. The logs will then maintain a history of administration activity that can be analyzed
later.
reporting the function and its result so that any loggers listening to these events can log the
information. The logs will then maintain a history of administration activity that can be analyzed
later.