Cisco Cisco Unified Customer Voice Portal 11.0(1) Release Note
C
HAPTER
3:
A
DMINISTRATION
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
83
•
timeoutCallsSinceStart
– Returns the total number of calls that ended with a timeout since
VXML Server launched. More specifically, this counts calls where the “result” action of the
“end” category is timeout. See Chapter 5: VXML Server Logging in the section entitled The
Application Activity Logger for more on the different results and how ended values. This
information is good to compare with the number of timed out calls in the past X minutes as if
the numbers are close it could mean that the issue that is causing the timeouts is a recent
occurrence. It also gives an indication of the stability of the system and will allow the
administrator to calculate the percentage of calls that had encountered timeouts.
“end” category is timeout. See Chapter 5: VXML Server Logging in the section entitled The
Application Activity Logger for more on the different results and how ended values. This
information is good to compare with the number of timed out calls in the past X minutes as if
the numbers are close it could mean that the issue that is causing the timeouts is a recent
occurrence. It also gives an indication of the stability of the system and will allow the
administrator to calculate the percentage of calls that had encountered timeouts.
•
failedCallsSinceStart
– Returns the total number of calls that ended with an error since
VXML Server launched. More specifically, this counts calls where the “result” action of the
“end” category is error. See Chapter 5: VXML Server Logging in the section entitled The
Application Activity Logger for more on the different results and how ended values. This
information is good to compare with the number of failed calls in the past X minutes as if the
numbers are close it could mean that the issue that is causing the errors is a recent
occurrence. It also gives an indication of the stability of the system is and will allow the
administrator to calculate the percentage of calls that had errors.
“end” category is error. See Chapter 5: VXML Server Logging in the section entitled The
Application Activity Logger for more on the different results and how ended values. This
information is good to compare with the number of failed calls in the past X minutes as if the
numbers are close it could mean that the issue that is causing the errors is a recent
occurrence. It also gives an indication of the stability of the system is and will allow the
administrator to calculate the percentage of calls that had errors.
•
maxLoggerEventQueueSizeInLast
– Returns the largest the logger event queue got in the last
X minutes where X is entered by the administrator and when the maximum was reached. For
an explanation of the logger queue, see the section titled Tuning Logger Options earlier in
this chapter. This value will help the administrator understand, in an abstract way, how much
VXML Server is logging. While it is not unusual for this number to be large, the
administrator can track a trend and if this number continually increases it could be an
indication that the system cannot handle the logger event load and could eventually result in
memory problems. The time when the maximum was reached can help indicate if VXML
Server is able to handle the incoming stream of logger events.
an explanation of the logger queue, see the section titled Tuning Logger Options earlier in
this chapter. This value will help the administrator understand, in an abstract way, how much
VXML Server is logging. While it is not unusual for this number to be large, the
administrator can track a trend and if this number continually increases it could be an
indication that the system cannot handle the logger event load and could eventually result in
memory problems. The time when the maximum was reached can help indicate if VXML
Server is able to handle the incoming stream of logger events.
•
maxLoggerThreadCountInLast
– Returns the most simultaneous threads VXML Server was
using to handle loggers in the last X minutes where X is entered by the administrator and
when the maximum was reached. For an explanation of the logger thread pool, see the
section titled Tuning Logger Options earlier in this chapter. This would be another indication
of whether VXML Server is able to keep up with the stream of logger events as if the number
is close to the maximum thread pool size it is an indication that VXML Server has almost
reached its limit in handling events. When the maximum was reached will help determine if
this is happening recently. Keep in mind that when all the threads in the pool are actively
handling logger events, the logger event queue will rise rapidly. So if this value is at the
maximum thread pool size, then the maxLoggerEventQueueSizeInLast function would
display rapidly increasing queue sizes.
when the maximum was reached. For an explanation of the logger thread pool, see the
section titled Tuning Logger Options earlier in this chapter. This would be another indication
of whether VXML Server is able to keep up with the stream of logger events as if the number
is close to the maximum thread pool size it is an indication that VXML Server has almost
reached its limit in handling events. When the maximum was reached will help determine if
this is happening recently. Keep in mind that when all the threads in the pool are actively
handling logger events, the logger event queue will rise rapidly. So if this value is at the
maximum thread pool size, then the maxLoggerEventQueueSizeInLast function would
display rapidly increasing queue sizes.
•
callTransferRate
– Returns the percentage of calls that ended in a blind telephony transfer.
More specifically, this counts calls where the “how” action of the “end” category is
call_transfer. This could help the administrator determine what percentage of callers decided
to speak to an agent rather than complete the call in the automated voice application.
call_transfer. This could help the administrator determine what percentage of callers decided
to speak to an agent rather than complete the call in the automated voice application.