Avaya

Modular Messaging Help

 Getting Started 
 Administration 
 Maintenance 
 Reference 
 
Home > Administration > System verification > Reports > Overview of traffic reports

Overview of traffic reports

This topic provides an overview of Message Storage Server (MSS) traffic reports.

Traffic reports serve several purposes, including how to:

  • Determine the grade of service (GOS) provided subscribers during the busy hour at your site.
  • Determine the port usage on the messaging system in daily or hourly periods. You need to run these reports periodically to monitor performance and to anticipate your system's needs.
  • Determine if your messaging system is performing at peak efficiency by providing actual usage information that you can compare with the type of usage that was initially forecast for your system.
  • Troubleshoot administration problems that can occur with subscribers and equipment as system usage increases and requirements change.

Messaging traffic reports also provide the following information about subscriber traffic, and feature traffic that help you evaluate system efficiency.

Archiving traffic reports

If you print messaging traffic reports on a regular basis and file them sequentially by date, they can provide an ongoing audit and historical reference of your messaging system. These reports can be useful for analyzing trends and tracking system performance over a period of time. Since traffic records collected for a specific day, hour, or month are retained on the system only for a limited number of days, hours, or months, it is imperative that you run and print the reports on a regular schedule to ensure that you maintain a complete record from one reporting period to the next. See Data retention requirements for more information about how long the system retains traffic records.

Printing traffic reports

To print the contents of any messaging administration screen accessed with the list or display command, type the word print before the command. For example, to print the Alarm Log report, type print display alarm in the command line. The system displays the report and prints it at the same time.

Note: You must have a system printer enabled and available to print screens and reports. If you do not, the print queue fills up with print jobs that cannot be processed. This can slow down system performance.

The types of traffic reports

Each application on the messaging system provides its own set of reports for tracking data relevant and specific to the application itself. The following table lists each traffic report and its purpose. To see more information about a specific report, click the link in the Procedure Link column.

Report Purpose Procedure Link
Messaging
Community Traffic (Hourly/Daily)

Displays the number of messages sent and received by each community.

Running a Community Daily or Hourly Traffic Report
Feature Traffic (Hourly/Daily) Displays traffic information by feature: voice mail and call answer. Running a Feature Daily or Hourly Traffic Report
Load Traffic (Hourly/Daily) Displays the number of calls handled by each active port within a reporting period. Running a Load Daily or Hourly Traffic Report
Subscriber Traffic (Daily/Monthly) Displays traffic information about a specific subscriber. Running a Subscriber Daily or Monthly Traffic Report
Networking
Network Load Traffic
(Hourly/Daily)
Displays the number of calls handled by each active Networking port within a reporting period. Running a Network Load Hourly or Daily Traffic Report
Remote Messages Traffic
(Monthly/Daily)
Displays up to 13 months' worth of information about the traffic load between a local messaging and a specified remote messaging machine. Running a Remote Message Daily or Monthly Traffic Report

Top of page