Reports provide indications of data validity by showing the number of observations for a particular metric. As a rule, the greater the number of observations, the higher the validity of the statistics for a metric. The pool of performance data is based on the number of calls placed (calls originated) or the number of call minutes.
The following table describes the observation units for Call Performance reports:
|
Unit |
Type of Metric |
Description |
|---|---|---|
|
Calls Originated |
Call setup |
One call = one call leg. The number of calls from endpoints at a given Location. The term Originated helps identify the direction of the call leg. Call setup metrics apply to one direction for a VoIP call. Only the applicable call legs are included in the Calls Originated count for call setup. |
|
Call Minutes |
Call quality |
One call minute = 60 seconds of time that a telephone was off-hook and sending data. Call minutes are computed as follows: (total seconds of all call data)/60 Normal rounding of seconds into minutes is then applied, but partial minutes are reported. |
The observation units correspond to the units used in configuring performance thresholds. Administrators can set the minimum number of calls originated or call minutes that must be collected before an incident is created.
Observations are taken continuously and reported to the management console, but observed data is not immediately reflected in Call Performance reports. No data about a call is reported until the call ends. When it ends, all data from that call is reported during the next five-minute reporting interval. A call that lasts 42 minutes, for example, reports no data until the ninth reporting interval. At which point, the updated Call Performance Overview adds the entire 42 call minutes to the total number of call minute observations.
The number of observations is a helpful means of judging whether relatively heavy usage played a role in performance issues.
|
Copyright © 2012 CA.
All rights reserved.
|
|