Cisco Cisco Customer Voice Portal Downloads 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)
52
Application and System Status
Unified CVP VoiceXML Server provides scripts named
status.bat
for Windows and
status.sh
for Linux/Solaris users for reporting the status of a specific voice application or all
voice applications running on the system. The global status script is found in the
admin
folder of
VXMLServer
while the application-specific status script is found in the
admin
folder of that
application.
The application status script reports the following information:
Whether the application is running, suspended, or has been suspended before being slated for
removal.
How many active sessions are currently visiting the application. Active sessions are defined
as the number of callers that are interacting with the application at the time the status script is
called.
called.
How many sessions are waiting to end. When an active caller ends their application visit, the
VoiceXML Server delays the closing of the corresponding session to allow final logger and
end of call class actions needing access to the session the time to complete. A session waiting
to end does not take up a license port. The amount of time a session remains open after a call
ends is configurable by editing the
end of call class actions needing access to the session the time to complete. A session waiting
to end does not take up a license port. The amount of time a session remains open after a call
ends is configurable by editing the
global_conf.xml
found in the
conf
directory of
VXMLServer
.
How many open sessions are experiencing the most recent past version of the application.
Open sessions are the sum of active callers visiting the application and those sessions that are
in the process of ending. The reason open sessions are listed here is because both active and
ending sessions do need access to session information and an administrator would need to
know when it is safe to disable any systems referenced by the old configuration. Listing
active callers instead could raise the prospect that an ending session's loggers may attempt to
access systems that are no longer available. The administrator would use the status script to
get this information if they interrupted the
in the process of ending. The reason open sessions are listed here is because both active and
ending sessions do need access to session information and an administrator would need to
know when it is safe to disable any systems referenced by the old configuration. Listing
active callers instead could raise the prospect that an ending session's loggers may attempt to
access systems that are no longer available. The administrator would use the status script to
get this information if they interrupted the
updateApp
script while it was counting down the
open sessions.
How many callers are on hold waiting to get into the application. A call that is received when
the system has used up all the allowed sessions defined in the license are played a message
asking them to stay on the line. This call then checks if a license session has become
available and then lets the call into the application.
asking them to stay on the line. This call then checks if a license session has become
available and then lets the call into the application.
The global status script provides an easy to read report with the following information:
The total number of concurrent active callers visiting applications on this instance of the
VoiceXML Server, how many concurrent sessions the license allows, the number of
available ports (the license sessions minus the active callers), and the number of callers on
hold (which would only appear if the number of current callers exceeds the number of license
sessions).
available ports (the license sessions minus the active callers), and the number of callers on
hold (which would only appear if the number of current callers exceeds the number of license
sessions).