Avaya

Modular Messaging Help

 Getting Started 
 Installation 
 Administration 
 Maintenance 
 Reference 
 
Home > Maintenance > Troubleshooting > General troubleshooting

General troubleshooting

This topic provides information you can use to troubleshoot problems with the system, including:


Note: If the system is not sending calls to a remote service center, see Resetting MSS alarm origination for modem dial out (INADS destination) to restore this service.

 

Keyboard is not operating

Possible cause

Action

Probable fix

The keyboard is not plugged in properly.

Check the keyboard connection.

Disconnect and reconnect the keyboard.

The keyboard is "frozen."

Check the keyboard connection.

Reboot the server. For more information, see Performing an MSS reboot.

The keyboard is not working.

Test the keyboard with another monitor.

Replace the keyboard if it is proven faulty.

Monitor is not operating

Possible cause

Action

Probable fix

The monitor does not show the correct server.

Verify that the keyboard, video, and mouse (KVM) switch for the monitor is set to the server you are trying to view.

Adjust the KVM switch so the monitor shows the correct server. This procedure varies according to the type of KVM switch installed.

The monitor is not turned on.

Check the monitor power switch.

Turn on the monitor.

The monitor brightness was turned down.

Check the monitor brightness knob.

Turn up the brightness.

The monitor was not installed correctly.

1. Verify that the monitor power cord is plugged into a working AC outlet.

2. Verify that the monitor cabling is correct.

1. Plug the AC power cord into a working outlet.

2. Correct the monitor cabling connections. For more information, see Installation and Upgrades (pdf) or Performing hardware maintenance.

The keyboard is not working.

See Keyboard is not operating.

Repair or replace the keyboard.

The monitor is not working.

1. Test the monitor with another system.

2. The video card or controller on the motherboard might have failed.

1. Replace the monitor if it is faulty.

2. Replace the faulty video component. For repair procedures, see Performing hardware maintenance.

Network connection is not working

Possible cause

Action

Probable fix

The physical connection is faulty.

Check the corporate and private LAN cabling, including connections to the Ethernet switch.

1. Reseat and correctly connect the Ethernet cables to each server, both LANs, and the Ethernet switch. more information, see Installation and Upgrades (pdf) or Performing hardware maintenance.

2. Replace the network cable.

The network administration is not correct.

Verify the server networking administration.

For complete information, see Installation and Upgrades (pdf).

Serial modem does not answer

Possible cause

Action

Probable fix

The modem has no power.

Check the power source.

Apply power to the modem.

The modem is not connected.

Verify that the modem is connected properly.

Connect the modem correctly. For more information, see Installation and Upgrades (pdf) or Performing hardware maintenance.

  • For an external modem, check all cables.
  • For an RMB, verify that the RMB-to-COM2 cable is connected to the MSS, as well as an analog line.

Server power light is off

Possible cause

Action

Probable fix

The server has no power.

1. Press the power button on the front of the server.

2. Verify that the AC power cord is plugged into a working AC outlet.

3. For S3400-family servers, verify that the rocker switch for all installed power supplies is on (set to |) at the back of the server.

Apply power to the server.

 

If you plugged in a power cord or turned on a power supply rocker switch, press the power button on the front of the server again.

The power source is faulty.

Check if other components plugged into the same power outlet as the server operate correctly.

Repair or replace the power source as required.

Call answer is not working

Possible cause

Action

Probable fix

Modular Messaging Release 3 is installed on the MSS while Modular Messaging Release 1.1 is installed on the MAS.

It is always recommended that the same release of the Modular Messaging software be installed on the MSS and MAS.

Verify the version of Modular Messaging software installed on the MAS. Click Start > Programs > Avaya Modular Messaging > About. Upgrade the MAS to Release 3. For complete information, see the Installation and Upgrades guide (pdf).

Online help does not display

Possible cause

Action

Probable fix

The computer that you are using to access the Modular Messaging online help has a pop-up blocker installed.

1. Refer to the documentation for your pop-up blocker for information about how to resolve this problem.

2. If you are still unable to view the online help, contact Avaya technical support.

Add the fully qualified domain name (FQDN) of the server on which the application and help files reside to the pop-up blocker's list of allowed sites.

Messaging Application Server (MAS) cannot be started

Possible cause

Action

Probable fix

The Domain Controller was taken out of service by a power failure.

Restore power to the MASs.

Reboot the server on which the Domain Controller resides before rebooting other MASs affected by the power failure.

Note: For an Exchange message store, the Domain Controller does not reside on one of the MASs.

Poor audio quality

Possible cause

Action

Probable fix

The default audio encoding format is set to Microsoft GSM 6.10.

Check the default audio encoding format. For information, see "Audio Encoding Dialog Box" in Messaging Application Server Administration Guide (pdf).

Change the default audio encoding format to G.711 mu-law or G.711 A-law. For more information about audio encoding, see Concepts and Planning Guide (pdf).

Wrong language on fax cover page

Possible cause

Action

Probable fix

The Messaging Application Server (MAS) was not rebooted after the primary language for the Voice Mail Domain was changed.

Using the Voice Mail System Configuration (VMSC) application, verify that the Primary Language field on the Languages Dialog Box is set to the appropriate language. For information about changing the primary language, see "Languages Dialog Box" in Messaging Application Server Administration Guide (pdf).

Reboot the MAS. After changing the primary language setting for a Voice Mail Domain, the MAS must be rebooted for the change to take effect. For information about rebooting an MAS, see "Rebooting MASs for Routine Maintenance" in Messaging Application Server Administration Guide (pdf).

 

Top of page