Cisco Cisco Customer Voice Portal 8.0(1) User Guide
C
HAPTER
3:
A
DMINISTRATION
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)
45
machine in order to access them. Therefore, accessing these programs is as secure as the remote
login process (such as SSH) and the permissions given to these scripts or the entire
login process (such as SSH) and the permissions given to these scripts or the entire
admin
folder.
Secondly, the VoiceXML Server will only accept commands from the local machine, so even
scripts stored on one machine cannot issue commands to an instance of the VoiceXML Server
running on another machine. These two precautions ensure that only authorized administrators
can access these functions.
scripts stored on one machine cannot issue commands to an instance of the VoiceXML Server
running on another machine. These two precautions ensure that only authorized administrators
can access these functions.
Since the global administration scripts are stored in a different location from application scripts,
each directory can be assigned different permissions. That way an administrator can be given
access to the global administration scripts while still allowing the application scripts to be
accessed by voice application developers.
each directory can be assigned different permissions. That way an administrator can be given
access to the global administration scripts while still allowing the application scripts to be
accessed by voice application developers.
Finally, every administration script can be configured to ask for confirmation before the action is
taken, to prevent the accidental execution of the script. By default the confirmations are on. They
can be turned off by passing the command-line argument “noconfirm” to the script. This can be
useful if the administration scripts are run by automated systems like cron jobs.
taken, to prevent the accidental execution of the script. By default the confirmations are on. They
can be turned off by passing the command-line argument “noconfirm” to the script. This can be
useful if the administration scripts are run by automated systems like cron jobs.
Graceful Administration Functions
Administration scripts are used primarily to alter an application, whether it be to update its
contents or suspend its activity. Whenever changes are made to a live system handling callers, a
concern is how these changes affect live callers. A robust, reliable system should strive for
maximum uptime and minimal disruptions of live calls, and Unified CVP VoiceXML Server
does this by implementing a “graceful” process for managing changes.
contents or suspend its activity. Whenever changes are made to a live system handling callers, a
concern is how these changes affect live callers. A robust, reliable system should strive for
maximum uptime and minimal disruptions of live calls, and Unified CVP VoiceXML Server
does this by implementing a “graceful” process for managing changes.
In the graceful process, existing callers continue to experience the application as it existed before
the change, while new callers experience the change. Only after all existing callers have naturally
ended their calls will the change apply to all live callers. At this time, the VoiceXML Server will
perform any necessary cleanup required to remove the old application configurations. In this
manner, changes can be made to applications at any time, the administrator need not worry about
the impact of the change on live callers as they will be handled gracefully.
the change, while new callers experience the change. Only after all existing callers have naturally
ended their calls will the change apply to all live callers. At this time, the VoiceXML Server will
perform any necessary cleanup required to remove the old application configurations. In this
manner, changes can be made to applications at any time, the administrator need not worry about
the impact of the change on live callers as they will be handled gracefully.
When a graceful administration script is executed, it will keep track of callers that were already
visiting the application and display a count down as those callers naturally end their calls. This is
provided as an aid to the administrator in determining how many callers are still experiencing the
application before the change. Command line arguments passed to the scripts can turn off this
countdown if desired. The information on the number of callers visiting the old and new versions
of the application is still available when obtaining the status of the system.
visiting the application and display a count down as those callers naturally end their calls. This is
provided as an aid to the administrator in determining how many callers are still experiencing the
application before the change. Command line arguments passed to the scripts can turn off this
countdown if desired. The information on the number of callers visiting the old and new versions
of the application is still available when obtaining the status of the system.
The description of the various administration functions listed below will each explain the manner
in which their actions are handled gracefully (if applicable) and any points that need to be
considered when the administration script is run.
in which their actions are handled gracefully (if applicable) and any points that need to be
considered when the administration script is run.
Updating Applications
Occasionally, an application will need to be updated. Possible changes can be small, such as
renaming an audio file or altering a TTS phrase, or large, such as adding another item to a menu
renaming an audio file or altering a TTS phrase, or large, such as adding another item to a menu