|
This topic provides information about the Message Storage Server
(MSS) Voice Messaging Database Audits.
During normal operation, the messaging 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 messaging system, other databases
might 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 performed on demand. For information about performing
audits on demand, see Performing Voice Messaging
Database Audits.
Voice messaging database audit types
The table below lists the different types of MSS Voice Messaging
Database Audits, the function of each audit, and the frequency of
when each audit automatically runs.
| 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 MSS's 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 |
| 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 |
Top of page
|
