Cisco Cisco Unified Customer Voice Portal 10.0(1) Guida Utente
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
69
Administrator functions include the ability to add, update, and remove applications as well as
suspend both an application and Call Services itself. This section describes all functions
available.
suspend both an application and Call Services itself. This section describes all functions
available.
Graceful Administration Activity
Administration functions 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 Call Services 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 Call Services 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, Call Services will perform
any necessary cleanup required to remove the old application configuration. 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 the transition 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, Call Services will perform
any necessary cleanup required to remove the old application configuration. 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 the transition will be handled gracefully.
Due to the interactive nature, when using administration scripts to perform graceful functions,
the script will display a count down of callers that are actively visiting the application as they
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 script will display a count down of callers that are actively visiting the application as they
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.
When using the JMX interface or if the countdown is turned off in the administration script, the
only way to track the number of callers that are still experiencing the old configuration would be
to get the system status..
only way to track the number of callers that are still experiencing the old configuration would be
to get the system status..
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
and creating a new call flow branch. They can involve simple configuration changes or may
involve new or changed Java class files. While most changes are implemented during
development time, there is a requirement to support updating an application at runtime.
renaming an audio file or altering a TTS phrase, or large, such as adding another item to a menu
and creating a new call flow branch. They can involve simple configuration changes or may
involve new or changed Java class files. While most changes are implemented during
development time, there is a requirement to support updating an application at runtime.
The update functionality acts gracefully in that any callers on the system, at the time of update,
continue to experience their calls as if the application had not been updated, while new callers
experience the updated voice application. In this manner, there is no downtime when a change is
implemented for an application, the callers are handled as expected.
continue to experience their calls as if the application had not been updated, while new callers
experience the updated voice application. In this manner, there is no downtime when a change is
implemented for an application, the callers are handled as expected.
Call Services exposes an update function for every application deployed This will updates just
that application. It also has a function that will update all applications at once.
that application. It also has a function that will update all applications at once.
There are a few items to note when updating individual voice applications.