Every attempted call is logged in the database. However, to generate call setup metrics for a call performance report, a call must progress far enough to receive a response-time measurement.
UC Monitor bases response time on the time it takes for the call server to send setup information to the calling endpoint. Call server response time is used to calculate the post-dial delay and delay-to-dial-tone metrics.
Call performance data is collected continuously and sent to the management console, but reports are updated every 5 minutes. Call quality metrics are collected when a call completes. The metrics do not appear in reports until they are received at the management console and processed.
A reporting interval is distinct from a monitoring interval: monitoring is continuous, but reporting of call quality and call setup metrics occurs every 5 minutes. Call metrics appear in reports when a call ends during a reporting interval. Several minutes can elapse before the collector reports all data.
Note: For other types of reporting, such as call server and collector incidents, a 15-minute reporting interval applies. Data from a Call Watch is collected every 15 seconds and reported every minute.
A call that fails or is abandoned must actually reach the ringing phase before UC Monitor logs the associated IP address or directory number.
In a few rare cases, a call attempt has no call setup data. The following example explains how the situation occurs:
|
Copyright © 2012 CA.
All rights reserved.
|
|