Introduction to viewing operation history events

An event is any significant occurrence in the voice mail system that is of interest to an administrator for diagnostic or reporting purposes. Events are generated by the various messaging application server (MAS) components, for example, a Call Waiting state generated by the telephone user interface.

The tracing system includes the following storage areas:

Operation history database

A temporary storage area for events that are generated by the voice mail system. The database is purged periodically. The Operation History Viewer is used for viewing events in this database.

Transaction database

A more permanent storage area for voice mail system activity. The Reporting Tool is used for extracting information from this database. For more information on Reporting Tool, see Reports.

Before you begin

Ensure that operation history collection is enabled for the voice mail domain. For more information see Enabling operation history collection.

Understanding session files

You create a session to restrict the number of events displayed by the Operation History Viewer to only those that meet your criteria. You can use Operation History Viewer to view:

Live events as they are generated and added to the operation history database.

Historical events stored in the operation history database.

You can create two types of session file:

Session file (.ssn)

You create a session file when you want to save only a session's properties. You can modify the properties to create different event viewing scenarios.

Snapshot file (.snp)

You create a snapshot file when you want to save a session's properties and the event data matching these properties. The operation history database is purged periodically. However, by creating a snapshot file you can keep the event data for as long as you require.

Starting Operation History Viewer

Start Operation History Viewer from the Avaya Unified Messenger folder.

If most menus and commands in Operation History Viewer are unavailable on starting, you may need to select a data source. For more information, see Selecting a data source.

Note: It is recommended that you do not run multiple instances of Operation History Viewer at the same time to access the operation history database for a single voice mail domain. This has a detrimental effect on the performance of all Operation History Viewer applications that you are running.