Cisco Cisco Unified Customer Voice Portal 10.5(1) Mode D'Emploi
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)
48
There are a few items to note when suspending a voice application.
Only when all existing callers have exited the system will the application be officially
suspended. Depending on the average length of calls to the voice application, this may take
some time.
some time.
If changes were made to an application while it was suspended, the application should first
be updated before being resumed (see the previous section on the update administration
function).
function).
The suspension applies only to those resources under the control of the VoiceXML Server.
External resources such as databases, other web servers hosting audio or grammar files, or
servers hosting components via XML documents over HTTP are accessed at runtime by the
VoiceXML Server. If any of these resources become unavailable while there are still pre-
suspension callers on the system, those calls will encounter errors that will interrupt their
sessions. Any maintenance made to backend systems should be initiated after the suspend
script indicates that all pre-suspended callers are finished with their calls.
servers hosting components via XML documents over HTTP are accessed at runtime by the
VoiceXML Server. If any of these resources become unavailable while there are still pre-
suspension callers on the system, those calls will encounter errors that will interrupt their
sessions. Any maintenance made to backend systems should be initiated after the suspend
script indicates that all pre-suspended callers are finished with their calls.
When the suspension occurs, the administration log file will reflect when the suspend script
was run, not when it completed.
If an error occurs during suspension, a description of the error is displayed to the console
window and sent to any loggers listening to the appropriate logger events and the suspend
order is cancelled.
order is cancelled.
Suspending a voice application still requires the VoiceXML Server (and hence the Java
application server) to be running in order to produce the VoiceXML page containing the
suspended message. If the application server itself requires a restart, there are four possible
ways to continue to play the suspended message to callers. Remember to run the suspend
script before any of these actions are taken as this is the prerequisite. The solutions are listed
in order of effectiveness and desirability.
suspended message. If the application server itself requires a restart, there are four possible
ways to continue to play the suspended message to callers. Remember to run the suspend
script before any of these actions are taken as this is the prerequisite. The solutions are listed
in order of effectiveness and desirability.
o
Load balance multiple instances of the VoiceXML Server
. In a load-balanced environment,
one machine can be shut down, restarted, or reconfigured while the rest continue serving
new calls. Once removed from the load balance cluster, a machine will not receive new
call requests. Eventually, all existing callers will complete their sessions, leaving no calls
on the machine removed from the cluster. That machine can then be safely taken down
without affecting new or existing callers.
new calls. Once removed from the load balance cluster, a machine will not receive new
call requests. Eventually, all existing callers will complete their sessions, leaving no calls
on the machine removed from the cluster. That machine can then be safely taken down
without affecting new or existing callers.
o
Use a web server as a proxy.
In a smaller environment, a web server can be used as a
proxy for an application server so that when that application server becomes unreachable,
the web server itself can return a static VoiceXML page containing the suspended
message to the voice browser. The web server need not be on the same machine as the
application server. Once the web server is configured, the VoiceXML Server can be
suspended to flush out all existing callers, then the application server can be taken down
and the proxy server will take over producing the suspended message VoiceXML page.
The disadvantage of this approach is that the web server setup is done outside of Unified
CVP and if the suspended message changes it would need to be changed in both the
Unified CVP VoiceXML Studio and the web server configuration.
the web server itself can return a static VoiceXML page containing the suspended
message to the voice browser. The web server need not be on the same machine as the
application server. Once the web server is configured, the VoiceXML Server can be
suspended to flush out all existing callers, then the application server can be taken down
and the proxy server will take over producing the suspended message VoiceXML page.
The disadvantage of this approach is that the web server setup is done outside of Unified
CVP and if the suspended message changes it would need to be changed in both the
Unified CVP VoiceXML Studio and the web server configuration.