When you interpret reports, consider the following guidelines:
|
Find out your system size. |
Know your system’s disk capacity and the number of channels that are installed. Use this information to identify when you are reaching resource limits and to plan for future upgrades. |
|
Establish a baseline. |
Learn what is normal or average behavior for your system. Establish a baseline to help you differentiate between normal system activities and unusual or suspicious activities. |
|
Consider external factors. |
If your reports show unusual system activities, consider external events. For example, an extremely low volume of traffic for a Monday afternoon can be the result of a national holiday. |
|
Observe day-to-day system use. |
Learn how your organization operates on a day-to-day basis. The information contained in reports often relates directly to your company’s routines and schedules. For example, if a large number of employees are working overtime, your reports may indicate a high percentage of after-hours logons. If you do not know how the organization functions, find someone who can help to interpret your report. |
|
Consult users. |
Consult the users of the system for further insight into your reports. Find out if the system is working for the users and if they have any problems to report. Some system problems result from improper use of the system (perhaps due to a lack of end-user training). |
|
Consider new features or services. |
Consider how long a feature or service has been in operation. If users are curious about a new feature, it may generate more traffic than usual. If users are not familiar with the feature, it may generate less traffic. |
Changes to the server time affect the accuracy of reports. When a report is generated that includes a date on which the server time was changed, the data generated for that time can be inaccurate.
The server time can change for various reasons:
daylight saving time
server battery change
server resynchronized with switch time
If the server time has been advanced by one hour, the generated data of calls made during that time shows time lengths increased by one hour. Totals and averages of call sessions displayed in reports covering the time change are also increased.
Server time is advanced by one hour due to daylight saving time. Calls in progress when the time was changed are increased by one hour.
Actual call length: 5 minutes
Report data shows: 1 hour 5 minutes
If the server time has been decreased by one hour, the generated data of calls made during that time can show negative time lengths. Totals and averages of call sessions displayed in reports covering the time change are also decreased.
Server time is decreased by one hour due to daylight saving time. Calls in progress when the time was changed are decreased by one hour.
Actual call length: 5 minutes
Report data shows: -55 minutes