Modular Messaging Help

Home | Search | Site Index Print | Back | Fwd | Legal | Close

MAS Auditing Overview

The MM Audit Service is installed to run on each MAS in the voice mail domain, including the supplementary server. For more information, see MAS - Modular Messaging (MM) Services.

To activate Messaging Application Server (MAS) Auditing, the service on one MAS in the voice mail domain must be assigned to be the MM Audit Server. This is configured in the Voice Mail System Configuration (VMSC) application’s Auditing dialog box. For more information, see VMSC - VMD - Auditing Dialog Box.

With MAS Auditing, an audit event is logged whenever a role-controlled administrative operation is attempted by an MAS or supplementary server. For more information, see VMSC - VMD - Security Roles Dialog Box.

User-friendly information is logged as well as the typical system data. For example, the name of a caller application is logged, as well the Globally Unique Identifier (GUID).

Only the usage of Modular Messaging administrative applications is audited. Other usage is not logged.

What Type of Data is Not Logged?

Data Storage

Audit logs can be configured to purge any events that are older than a specified number of days, automatically.

If the MM Audit Server has been assigned, logged audit events are eventually stored, even if the audit server is temporarily out of service.

The Modular Messaging system optionally sends syslog messages, if a receiver has been configured. This allows third-party system administration tools to be used.

These settings are configured in the VMSC application’s Auditing dialog box. For more information, see VMSC - VMD - Auditing Dialog Box.

Viewing the Data

You can use the MM Audit Log Viewer to view the audit log data. See MAS - Aud - MM Audit Log Viewer Window.

Reporting on the Data

In the MM Audit Log Viewer, you can use the Action > Export List... command to export audit event lists, then open them into Excel or a similar application.

Top of page