Audits

Voice Messaging Database Audit Overview

During normal operation, the messaging databases work independently under the direction of a set of software managers. These managers, in tandem with hardware and firmware managers, allow the files, databases, and system hardware to work together.

Because databases are handled separately, it is possible for different databases to contain conflicting information. For example, if a subscriber is removed from the messaging system, other databases may contain messages addressed to that subscriber. In addition, mailing lists that include the deleted subscriber's name could still exist.

To reconcile possible conflicts among databases, software programs called audits run automatically to check for inconsistencies. Audits can also be run on demand by you.

Voice Messaging Database Audit Types

The Voice Messaging Database Audits table shown below lists the types of voice messaging database audits.

Table: Voice Messaging Database Audits

Audit	Function	Frequency
Mailboxes	Checks and deletes new, old, and unopened messages that exceed maximum retention time	Daily
	Clears new, old, and unopened broadcast-deleted messages from subscriber mailboxes	Daily
	Verifies that the Messaging MWL status matches with the switch's MWL status for each subscriber	Daily
	Checks for valid mailbox structure	Weekly
	Makes space-accounting corrections on a per-subscriber and system basis	Daily
	Checks for valid message subscriber IDs	Weekly
Mailing Lists	Counts subscriber lists and entries on a system and per-subscriber basis to ensure that they are not exceeding internal limits	Weekly
	Removes deleted subscribers from lists	Daily
	Removes deleted remote subscribers from local mailing lists	Daily
	Audits delivery manager queues and makes undeliverable entries for deleted subscribers	Daily
Names	Matches each voice name with a valid local or remote subscriber	Weekly
	Logs messages in the administrator's log for the first 20 local subscribers who do not have voiced names	Weekly
Network Data	Deletes subscribers on remote nodes that have been eliminated from the network	Weekly
	Compares internal network files to synchronize information on nodes and subscribers, for example, which node each subscriber belongs to	Weekly
Personal Directories	Removes deleted subscribers (local and remote) from local subscribers' personal directories	Daily
Subscriber Data	Checks delivery lists associated with current outgoing messages	Daily
	Validates fields in class of service templates, subscriber profiles, and automated attendant profiles	Weekly
	Counts subscribers to ensure that the number of subscribers is not exceeding internal limits	Weekly
	Checks the system guest password against individual subscriber passwords and makes appropriate entries in the administration log	Weekly
	Checks subscriber profiles against class of service templates and changes subscribers to class of service	Weekly
	Deletes remote unverified subscribers who have not been on delivery lists in the last 24 hours	Daily
	Deletes remote subscribers with no valid nodes	Weekly
	Deletes unadministered remote subscribers who have not used the system for a specified time period	Daily
	Cross-checks name, extension, touchtone, subscriber directory, and remote node list translations files for consistency with subscriber profiles	Weekly

Performing a Voice Messaging Database Audit

All of the voice messaging database audit types use the same general procedure.

To audit a voice messaging database audit:

1. Log in to the Communication Manager Messaging web page.
2. Under Utilities, select Messaging DB Audits. The system displays the Audits page.
3. Click the appropriate link for a particular audit.


 

Table: Voice Messaging Database Audits

To Audit	Click
View Audit History	History
Mailboxes	Start Mailboxes Audit (Mailboxes, Mailbox Data)
Mailing lists	Start Mailing Lists Audit (Mail Lists, Delivery Data)
Names	Start Voice Names Audit (Voice Names)
Network data	Start Network Data Audit (Machine Translations, Network Translations, Network Data) Note: This audit is available only if the system has Digital Networking.
Personal directories	Start Personal Directory Data (Personal Directories)
Subscriber data	Start Subscriber Data Audit (Subscribers, Delivery Data)
Nightly Audit	Start Subscriber Data Audit (Subscribers, Delivery Data)
Weekly Audit	Start Weekly Audit (Weekly, Delivery Data, Network Data, Mailbox Data)

The system displays the audit name and Result code, which indicate that the audit is running. The system also displays results of in stages depending on how that feature has been designed.

4. Wait for the audit to finish or take one of the following steps:

• Click Abort to partially stop the audit and exit the page.
• Click Back to go to the Audits page.

If the audit fails:

1. Resolve any active alarms and rerun the audit.
2. If the audit fails again, contact the remote service center.
3. If the system is not providing service and the remote service center cannot help immediately, reboot the system.

 

Top of page