Reduce message retention
time by doing the following.
- Log in to the Communication Manager Messaging web page.
- Under Messaging Administration, select Classes-of-Service.
The COS Number
might be any number from 0 through 11. It is strongly recommended
that you modify the cos number that applies to most subscribers.
- Under INCOMING MAILBOX, decrease the number in the
Retention Times (days) New,
Old, and Unopened fields.
- Under
OUTGOING MAILBOX, Decrease the number in the Retention Times (days) File
Cab and Delivered/Nondeliverable fields .
- Click Save.
- If the alarm
is still active,contact your remote support center.
VM AUDIX_FS
2
Description:
The file count reached 80% capacity.
This alarm can escalate to VM AUDIX_FS 0. The system
automatically resolves this alarm when the file count used goes below
75%.
Repair Procedure:
|
Note: After each
step, check for resolved alarms to see if you have freed enough
space. |
- Ask subscribers
to delete unneeded messages. You might want to use the Broadcast
Message feature.
- Remove unused
local and remote subscribers by doing the following:
- Log in to the Communication Manager Messaging web page.
- Under Messaging Administration, select Subscriber Management.
- Click Manage for Local Subscribers or Remote Subscribers.
- Select a subscriber.
- Local Subscriber - Click the Edit/Delete the Selected Subscriber button
- Remote Subscriber - Click the Delete the Selected Subscriber button
- Look at the
Usage
Date field for each remote subscriber and delete those
that are unused.
- Reboot
the system to allow the messaging software to reclaim unused
resources.
- If the alarm
is still active,contact your remote support center.
VM AUDIX_FS
3
Description:
An attempt to restart the messaging software failed because the messaging database is corrupted.
The software is not providing messaging service.
Repair Procedure:
VM AUDIX_FS
4
Description:
The messaging data files are
corrupted. Although the system is providing messaging service,
subscribers might have trouble sending or receiving messages.
Repair Procedure:
VM AUDIX_FS
5
Description:
The messaging data files are
corrupted. Although the system is providing messaging service, subscribers
might have trouble sending or receiving messages.
Repair Procedure:
VM AUDIX_FS
6
Description:
The database might be corrupted.
Although the system is providing messaging service, this condition
could lead to severe problems.
Repair Procedure:
VM AUDIX_FS
7
Description:
The system is experiencing possible
file system corruption. Although the system is providing messaging
service, this condition could lead to severe problems. Nightly and
manual backups usually fail while this alarm is active.
Repair Procedure:
VM AUD_RESTOR
0
Description:
A messaging system-data restore
failed. The messaging application will not initialize.
Repair Procedure:
VM FAXAP
0
Description:
Queries to the FAX Messaging
database fail. This alarm indicates a possible database corruption.
Repair Procedure:
VM
GRAMMAN 001
Description:
The messaging software has lost its connection
to the dialing server because the dialing server is down. The dialing
server was either turned off or had a TCP/IP problem.
Repair Procedure:
You must wait for the remote
support center to fix this problem. The alarm is called in automatically,
unless there is another major alarm still active.
VM
LANINTF 0
Description:
The system has a resource problem.
Repair Procedure:
VM
LANINTF 1
Description:
The system has a resource problem.
Repair Procedure:
VM
LDAPFAIL 0
Description:
An attempt to restart the LDAP
Server for the messaging software failed.
Repair Procedure:
VM
NAMESRESTR 0
Description:
Recorded subscriber names are
not installed on the system.
Repair Procedure:
To repair this alarm:
- Stop
the messaging software (voice system).
- Restore
the messaging names.
- Start
the messaging software (voice system).
VM
NET_CONN 0
Description
A digital networking connection
failure has occurred.
Repair Procedure:
To repair the alarm:
- Verify that the system IP address
is correct:
- Start at the Administration main menu
and select:
Server Administration
Networked Servers
The system displays the Edit Networked Server page.
- Verify that the
IP Address field contains the correct
system IP address.
- If necessary, enter the correct IP address in the
IP Address
field.
- Delete any unnecessary administered remote machines. For example,
delete any unnecessary test machines. See Deleting
Remote Machines for more information.
- If this alarm persists, reboot the
system.
VM NOCUSTANNC
0
Description
The system attempted to restore
custom announcements; however, no custom announcement set is administered.
Repair Procedure:
To repair the alarm:
- Identify
an administrative announcement set.
- Stop
the messaging software (voice system).
- Restore
the custom announcement set.
- Start
the messaging software (voice system).
VM
REORGDB 0
Description:
The system logs this alarm when
messaging initialization fails. System initialization is suspended while
the database is reorganized. This error can occur under the following
circumstances:
- Power supply is interrupted.
- Messaging restarts for a
maintenance reason.
- Someone presses the Reset
button.
The system automatically resolves
this alarm after it reorganizes the database and completes initialization.
|
Note: Do not
press the Reset button. Wait for the system to reorganize the
database and initialize. |
Repair Procedure:
Wait for the alarm to automatically
clear. Clearance can take up to 2 hours. If the alarm does not clear
after this length of time:
VM
REORGDB 1
Description:
The system logs this alarm when
a database repair fails. This alarm occurs in the following circumstances:
- Power supply is interrupted.
- Messaging restarts for a
maintenance reason.
- Someone presses the reset
button.
The system automatically resolves
this alarm after it reorganizes the database and reinitializes.
Repair Procedure:
VM
RPCTEST 001
Description:
The operating system's RPC processes
are not running and cannot be restarted. This problem results in MCAPI
functionality being impaired and Message Manager and
Trusted Server services not being available. Since
messaging services are still provided, subscribers can use the telephone interface
to retrieve messages.
Repair Procedure:
VM
SERVER 900
Description:
A trusted server exceeded the
inactivity timeout period that was administered on the
System Parameters MCAPI-Options screen.
Repair Procedure:
VM
SERVER 901
Description:
A trusted server logged an alarm.
Repair Procedure:
VM
SOFTWARE 0
Description:
A messaging process failed.
Repair Procedure:
When this alarm occurs, the messaging application automatically restarts. This alarm remains active
during the restart and is resolved when the messaging application
successfully restarts.
If the system does not successfully
restart,contact your remote support center.
VM
SOFTWARE 1
Description:
A messaging process failed.
Repair Procedure:
When this alarm occurs, the messaging application automatically restarts. This alarm remains active
during the restart and is resolved when the messaging application
successfully restarts.
If the system does not successfully
restart,contact your remote support center.
VM
SOFTWARE 2
Description:
A messaging process failed.
Repair Procedure:
When this alarm occurs, the messaging application automatically restarts. This alarm remains active
during the restart and is resolved when the messaging application
successfully restarts.
If the system does not successfully
restart,contact your remote support center.
VM
SOFTWARE 100
Description:
A messaging process failed
to restart.
Repair Procedure:
VM
SOFTWARE 101
Description:
Nonstandard system software is
in use.
Repair Procedure:
VM
SOFTWARE 201
Description:
A messaging process could
not initialize. The system might be providing limited messaging
service.
Repair Procedure:
When this alarm occurs, the system
automatically attempts to restart the failed process. The alarm remains
active until the process successfully initializes, and then the alarm
is automatically resolved.
If this alarm fails to resolve,contact your remote support center.
VM
SOFTWARE 202
Description:
A messaging process could
not operate. The system might be providing limited messaging service.
Repair Procedure:
When this alarm occurs, the system
automatically attempts to restart the failed process. The alarm remains
active until the process successfully initializes, and then the alarm
is automatically resolved.
If this alarm remains active,contact your remote support center.
VM
SOFTWARE 203
Description:
A messaging process failed
to initialize. The system might be providing limited messaging
service.
Repair Procedure:
VM
SOFTWARE 204
Description:
A messaging process failed
during operation. The system might be providing limited messaging
service.
Repair Procedure:
VM
SOFTWARE 601
Description:
The system detected nonstandard
system software in use.
Repair Procedure:
VM
SOFTWARE 6000
Description:
A messaging process could
not initialize. The system is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 6001
Description:
A messaging process failed
to operate.
Repair Procedure:
VM
SOFTWARE 6600
Description:
The messaging database automatic
rebuild failed.
The system is not providing messaging service. The messaging application has automatically stopped
its own operation and networking and attempted a restart. During this
restart, the application operates database file checks and performs
a rebuild audit to correct any problems or discrepancies that were
detected. If the rebuild audit is not successful, this system generates
this alarm.
Repair Procedure:
VM
SOFTWARE 6603
Description:
The messaging application
detected file damage during a restart.
The system stops the initialization
and the software attempts to fix the file problems. The system automatically
resolves this alarm after completing the fix and continues initialization.
Repair Procedure:
VM
SOFTWARE 6604
Description:
The system encountered problems
while updating extension length values. Although the system updated
the extension length, the messaging application could not update
its internal tables. This alarm can block administrators from adding
new subscribers.
Repair Procedure:
- Stop
the messaging software (voice system).
- Start
the messaging software (voice system) to synchronize the voice
platform and the messaging application.
- If the alarm
fails to resolve,contact your remote support center.
VM
SOFTWARE 6605
Description:
The automated attendant routing
table contains inconsistent data.
This alarm occurs when a call
to an automated attendant cannot be routed as specified. This alarm
can occur if the routing tables are not updated after voice mailboxes
listed in the table are removed or if file corruption from a system
crash occurs. The system automatically resolves this alarm after the
table is updated.
Repair Procedure:
- Update
the routing tables with correct data.
- If this alarm
persists,contact your remote support center.
VM
SOFTWARE 6606
Description:
An automated attendant software
failure. When this alarm occurs, the messaging application can
restart or shut down.
Repair Procedure:
VM
SOFTWARE 6607
Description:
The system has an inconsistent
holiday or business schedule name. This alarm occurs when a call to
an automated attendant cannot be routed as specified. The system automatically
resolves this alarm after a successful restoration of data and voice
system restart.
Repair Procedure:
VM
SOFTWARE 6608
Description:
The system is experiencing inconsistent
automated attendant software operations.
Repair Procedure:
VM
SOFTWARE 6609
Description:
The system detected inconsistent
automated attendant night service data.
Repair Procedure:
VM
SOFTWARE 6610
Description:
The messaging application
cannot write to the day/night service file. The system is not providing
correct night service operation. This alarm might occur with alarm
VM SOFTWARE 6609.
Repair Procedure:
This alarm is automatically resolved
when the proper night service state is determined.
If this alarm remains active,contact your remote support center.
VM
SOFTWARE 6611
Description:
The messaging application
cannot communicate with the voice platform software. The system is
providing limited or interrupted messaging service.
Repair Procedure:
VM
SOFTWARE 6612
Description:
The messaging outcalling feature
failed.
Repair Procedure:
VM
SOFTWARE 6613
Description:
An error occurred during system
installation, or the system experienced incorrect modifications. System
operation might be impaired.
Repair Procedure:
VM
SOFTWARE 6614
Description:
The system failed to initialize
the messaging application because of insufficient system resources.
The software is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 6615
Description:
During system initialization,
the traffic process is unable to access one of its database files.
Repair Procedure:
VM
SOFTWARE 6616
Description:
The messaging initialization process
detected corrupt traffic data files. The system automatically begins
to correct the corruption.
Repair Procedure:
VM
SOFTWARE 6617
Description:
The messaging software detects
that the LDAP Server is not responding.
Repair Procedure:
The server attempts to restart
the LDAP Server. If the LDAP Server is restarted, the alarm is resolved.
If the LDAP Server does not restart, minor alarm VM
LDAPFAIL0 is then raised.
VM
SOFTWARE 6618
Description:
The system detected a database
problem. Stopping and restarting the voice system automatically repairs
the database.
Repair Procedure:
VM
SOFTWARE 6619
Description:
Call processing detected a problem with the LDAP server.
Repair Procedure:
VM
SOFTWARE 7701
Description:
The system failed to locate all
of the software needed to initialize the messaging application.
The system is not providing messaging service. This failure can
occur after a power hit or when a disk error happens. This alarm is
also sent to the remote support center.
Repair Procedure:
VM
SOFTWARE 7702
Description:
The system found that messaging database files were missing during messaging initialization. The
system is not providing messaging service. This failure can occur
after a power disruption or when a disk error happens.
Repair Procedure:
VM
SOFTWARE 7703
Description:
The system experienced an unexpected
file check failure after a voice system restart or a reboot.
Repair Procedure:
VM
SOFTWARE 7704
Description:
The system restarts too often.
Because of another alarm, the
messaging application has tried to restart itself twice but has
failed. The system is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 7705
Description:
The messaging maintenance
software automatically shut down the messaging application and
attempted a restart.
This alarm can also indicate that
the system attempted too many restarts or that an unexpected error
occurred during the shutdown. The system is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 7706
Description:
The system rebooted too often.
Because of another alarm, voice messaging has tried to restart itself but has failed.
The system is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 7707
Description:
The messaging maintenance
software automatically shut down the messaging application and
attempted a restart.
This alarm can also indicate that
the system attempted too many restarts or that an unexpected error
occurred during shutdown. The system is not providing messaging
service.
Repair Procedure:
VM
SOFTWARE 7708
Description:
The system rebooted too many times.
Because of another alarm, the
messaging application has tried to restart itself but has failed.
The system is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 7709
Description:
The messaging maintenance
software automatically shut down the messaging application and
attempted a restart.
This alarm can also indicate that
the system attempted too many restarts or that an unexpected error
occurred during shutdown. The system is not providing messaging
service.
Repair Procedure:
VM
SOFTWARE 7710
Description:
The maintenance software stopped
messaging operation during a restart. The system is not providing
messaging service.
Repair Procedure:
VM
SOFTWARE 7712
Description:
The maintenance software has automatically
shut down the messaging application and attempted a restart. The
system is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 7713
Description:
The system failed to create a
new voice file system during messaging initialization.
This problem can occur while an
Avaya technician attempts to add additional hours of speech to the
system. The system is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 7714
Description:
The outcalling feature
failed. The system is providing only limited messaging service.
Repair Procedure:
VM
SOFTWARE 7715
Description:
The trusted server
notification feature failed. The system is providing only limited
messaging service.
Repair Procedure:
VM
SOFTWARE 7716
Description:
The system failed to find the
external security password file. Any usage of the old, external security
password will fail. If you have one or more external trusted servers,
administer a new external security password.
Repair Procedure:
Do one of the following:
- Log in to the Communication Manager Messaging web page.
- Under Messaging Administration, select MCAPI Password.
The system displays the Change MCAPI-Password page.
- Complete the
Current Password: and New Password:
fields.
- Click Save.
VM
SOFTWARE 7717
Description:
The system failed to find any
announcement sets during messaging initialization. The system
is not providing messaging service.
Repair Procedure:
VM
SOFTWARE 7718
Description:
During the system initialization,
the messaging database integrity check failed. The system is not providing
service.
Repair Procedure:
VM
SOFTWARE 7719
Description:
This alarm tells you that the
outcalling database is corrupted.
Repair Procedure:
VM TRAFIXFAIL
0
Description:
The automatic file recovery procedure
that was started by VM SOFTWARE 6616 failed.
The system will continue to provide service, but traffic collection
data is incomplete.
Repair Procedure:
VM VM_PT
2
Description:
A messaging port restart
is in progress.
Repair Procedure:
No corrective action is necessary.
VM VM_PT
3
Description:
A messaging port process
failed too many times. The system set the service status of the affected
channel to manually out of service (manoos).
Repair Procedure:
VM VM_PT
4
Description:
An attempt to send or receive
a fax failed. The system generates this alarm after a number of failures
occur.
Repair Procedure:
The system automatically resolves
this alarm if a failure does not reoccur within 5 minutes. If this
alarm continues to remain active,contact your remote support center.
VM VM_PT
5
Description:
An attempt to record or print
a fax failed. The
system generates this alarm after a number of failures occur. This
alarm can indicate a problem with the subscribers' fax equipment or
FAX Messaging administration.
Repair Procedure:
- Verify that
the subscribers' fax equipment is working properly.
- Verify that
FAX Messaging is properly administered.
- If the alarm
remains active,contact your remote support center.
VM VMDIRS
0
Description:
The messaging application
is experiencing problems with a file. Although the system is providing
messagingservice, the system response times might be slow and
the performance poor.
Repair Procedure:
