Audits

Voice Messaging Database Audit Overview

During normal operation the Avaya Intuity system 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 Avaya Intuity 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 Intuity AUDIX Voice Messaging Database Audits table lists the types of voice messaging database audits.

 

Table: Intuity AUDIX Voice Messaging Database Audits

Audit	Function	Frequency
Mailboxes	Checks and deletes new ,old, and unopened messages exceeding maximum retention time.	Daily
	Clears new, old, and unopened broadcast-deleted messages from subscriber mailboxes	Daily
	Verifies that Avaya Intuity 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 not having 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 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, touch-tone, 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:

1. Starting at the Avaya Intuity Main Menu, select:

AUDIX Administration

The system displays the AUDIX Command Prompt Screen.

2. Enter the appropriate command from the Voice Messaging Database Audit Commands table.


 


Table: Voice Messaging Database Audit Commands

To Audit	Enter
Mailboxes	audit mailboxes or au mailb
Mailing lists	audit mailing-lists or au maili
Names	audit names or au na
Network data	audit network-data or au ne Note: This audit is available only if the system has Digital or AMIS Analog Networking.
Personal directories	audit personal-directories or au p
Subscriber data	audit subscriber-data or au su

The system displays an Audit Screen.

3. Press F3 (Enter).
4. The system displays the audit name and Result code R, which indicate that the audit is running.
5. Wait for the audit to finish or take one of the following steps:
• Press F1 (Cancel) to abort the audit and exit the form.

OR

• Press F3 (Enter) to put the audit in the background mode and return to the command line. Enter status audit to reconnect to the screen.

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.

Performing a Networking Database Audit

The networking database audit consists of a series of internal checks which verify, for example, that files are not corrupted and that values within the files are within the proper ranges.

The networking database audit is performed automatically nightly, before the nightly unattended backup. This audit occurs whenever the voice system is restarted or the UNIX system is rebooted. You may want to perform this audit on demand when directed to do so by alarm repair actions.

To perform this audit on demand:

1. Start at the Avaya Intuity Main Menu and select:

Customer/Services Administration
	Database Audits

The system displays the Database Audit Menu.

2. Make sure the cursor is on Networking Audit.
3. Press F8 (Chg-Keys).
4. Press F1 (Run Audit).

The system displays the Confirm Audit Window.

5. Press y
6. Press F8 (Chg-Keys).
7. Press F4 (View_Res).

If the audit is successful the system displays the following message:

Networking Database Audit completed successfully.

If the audit fails, the system displays the following message:

Networking Database Audit failed.

If a failure message appears, look for related alarms such as NW SOFTWARE-1004. Follow the repair actions for any active alarms as appropriate.

Platform User Database Audit Overview

The Avaya Intuity system switch integration database must periodically be synchronized with the applications' databases. The Station Manager Subscriber Database audit performs this synchronization.

The Avaya Intuity system switch integration database monitors the applications with which each subscriber is registered. When the audit is executed, the station manager matches its subscriber's extension and MWL status with each subscriber application database. When successful matches are made, the audit progresses to the next subscriber. If a match is not found, a message is printed in the audit report (see below).

This audit is performed automatically at 12:10 am. You may want to perform this audit on demand when:

• Alarms (SOFTWARE VP-12) indicate that subscribers cannot be found
• Subscribers report message-waiting light problems
• The system was shutdown improperly causing databases to become unsynchronized

Performing a User Database Audit

To perform this audit on demand:

1. Start at the Avaya Intuity Main Menu and select:

Customer/Services Administration
	Database Audits

The system displays the Database Audit Menu.

2. Make sure the cursor is on Platform User Database Audit.
3. Press F8 (Chg-Keys).
4. Press F1 (Run Audit).

The system displays the Confirm Audit Window.

5. Press y to confirm that you want to run the audit.
    
   

   Note: The audit takes approximately 60 minutes, depending on the system's load and may degrade service.

6. Press F8 (Chg-Keys).
7. Press F4 (View_Res).

If the audit is successful, the system displays the following message:

Station Manager Subscriber Audit is successfully done.

If the audit terminates before completion, the system displays the following message:

Station Manager Subscriber Audit is terminated because of <reason>.

If a subscriber exists in the Avaya Intuity system switch integration database but does not exist in any of the registered applications, the system displays the following message:

Station Manager Subscriber Database Audit found an extra subscriber user's extension requesting Station Manager to delete it from database

The subscriber is automatically deleted from the Avaya Intuity system switch integration database.

If a subscriber exists in one of the application databases and not in the Avaya Intuity system switch integration database, the system displays the following message:

Station Manager Subscriber Database Audit found a missing subscriber user's extension requesting Station Manager to add it to database

The subscriber is automatically added to the Avaya Intuity system switch integration database.

If the MWL status in the Avaya Intuity system switch integration database does not match the MWL status in the application databases, the system displays the following message:

Station Manager Subscriber Database Audit found a mismatched subscriber user's extension requesting Station Manager to update its database

The subscriber MWL status is automatically updated in the Avaya Intuity system switch integration database.

http://www.avaya.com Avaya UCS Information Development