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 shown
below 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 that exceed maximum
retention time
|
Daily
|
Clears new, old, and unopened
broadcast-deleted messages from subscriber
mailboxes
|
Daily
|
Verifies that the 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 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:
-
Starting at the Administration
main menu, select:
Global Administration
Messaging Administration
The system displays the SSH
User Authentication dialog box. Enter your login, for example, sa or vm,
in the User name
field and your password in the Password
field. Click Login. The system then displays the AUDIX
Command Prompt screen.
-
Enter the appropriate command from the Voice
Messaging Database Audit Commands table shown
below.
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.
-
Press F3 (Enter).
The system displays the
audit name and Result code R, which indicate that
the audit is running.
-
Wait for the audit to finish or take one of
the following steps:
- Press
F1 (Cancel) to abort the audit and exit the
form.
- Press
F3 (Enter) to put the audit in the background
mode and return to the command line. Enter status
audit to reconnect to the page.
If the audit
fails:
-
Resolve any active alarms and rerun the audit.
-
If the audit fails again, contact the remote
service center.
-
If the system is not providing service and
the remote service center cannot help immediately,
reboot the system.
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.
This audit
is performed automatically at 12:10 am. You might
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 shut down improperly, thus causing
databases to become unsynchronized.
Performing
a User Database Audit
To perform
this audit on demand:
-
Start at the Administration
main menu and select:
Utilities
Platform User Database Audit
The
system displays the Platform User Database page.
-
Click Run Audit.
Note:
The audit takes approximately 60
minutes, depending on the system's load,
and can degrade service.
|
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.
Viewing
Results from a User Database Audit
To view the results of a user
database audit:
- Start at the Administration
main menu and select:
Utilities
Platform User Database Audit
The system displays
the Platform User Database page.
- Click View Result.
The results from the last audit display.