Cisco Cisco Unified Customer Voice Portal 10.0(1) Betriebsanweisung
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
82
could also help determine if the maximum response time was an isolated event or an
indication of a trend. For example if the maximum response time were 500ms which
occurred near the present, the average was 400ms, the fact that the peak was 500ms is not
alarming, because the average is so high. In this situation the administrator may choose to
throttle down the calls being handled by the system to bring the response times back down to
more acceptable levels.
indication of a trend. For example if the maximum response time were 500ms which
occurred near the present, the average was 400ms, the fact that the peak was 500ms is not
alarming, because the average is so high. In this situation the administrator may choose to
throttle down the calls being handled by the system to bring the response times back down to
more acceptable levels.
•
timeoutCallsInLast
– Returns the total number of calls that ended with a timeout in the last X
minutes where X is entered by the administrator. 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. Under normal circumstances a call should never time out. Many different
types of conditions can yield session timeouts on VXML Server and so knowing if there are
timeouts in the last period of time would tell the administrator how widespread these issues
are.
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. Under normal circumstances a call should never time out. Many different
types of conditions can yield session timeouts on VXML Server and so knowing if there are
timeouts in the last period of time would tell the administrator how widespread these issues
are.
•
failedCallsInLast
– Returns the total number of calls that ended with an error in the last X
minutes where X is entered by the administrator. 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 helps the administrator determine how widespread a bug or other
issue that caused a call to end in an error is. For example, if the last 60 minutes yielded only
one failed call, while the issue should be investigated, it may not be a symptom of a larger
more prevalent issue.
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 helps the administrator determine how widespread a bug or other
issue that caused a call to end in an error is. For example, if the last 60 minutes yielded only
one failed call, while the issue should be investigated, it may not be a symptom of a larger
more prevalent issue.
•
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
an explanation of the logger queue, see the section titled Tuning Logger Options earlier in