Use this screen to test your modem and ensure it is working properly. The modem is used to report Avaya media server alarms (see Alarm-reporting options for details). It also enables you to dial in to an interface through which you can fix problems as they occur.
The Test Modem screen allows you to:
Before you test the modem, you must first have an understanding of how to troubleshoot possible modem problems. Knowing what tests to run and when to run them is key to this troubleshooting procedure. This section covers:
To test your modem:
On the main menu under Diagnostics, select Test Modem.
Select one of the following tests by clicking the corresponding radio button:
Performs handshake and offhook tests. Choose this default selection to run both the handshake and the offhook tests.
If these tests fail, run the handshake test and the offhook test individually to determine the reason for the failure. See Troubleshooting modem problems for details.
For more information about each test, see the individual description below.
Resets the modem. Choose this selection to reset the modem.
Performs handshake test. Choose this selection to verify that the modem is connected to the USB port and responding (that is, the drivers are functioning and the modem is sane).
Performs offhook test. Choose this selection to take the modem offhook and search for a dial tone. This test is important because an Avaya S8700 configuration has two modems, one for each server, and the modems share a single analog line.
Click Test Modem.
The Test Modem screen displays the test results. See the Viewing modem test results section for details.
For each test you want to run on the modem, repeat steps 1 through 3.
To verify that your modem is functioning properly, use the following procedure to test for problems.
Run the handshake test.
If the handshake test fails, check the modem connection to the telephone line and the server, make sure the modem is powered on, and then continue with step 2.
Run the handshake test again.
If the handshake test is successful, run the offhook test.
If the offhook test fails, check the modem connection line and hardware, then continue with step 4.
Perform the offhook test again.
If either the handshake or the offhook test fails again, reset the modem.
After you reset the modem, run the handshake and offhook tests again.
If you get an output message stating that the tests were unsuccessful because they failed to open a device (tty), it indicates that some other program is using the modem. In this case, check to see if someone else is using the modem.
If there are no problems with the connection line and hardware, restart the media server.
When you run the modem test, the Test Modem screen displays the following standard output:
Test. This part of the output message shows which test was performed.
Result. This part of the output message indicates whether or not the test was successful. The following results are possible:
Pass
Fail
Abort
Description. This part of the output message provides additional information about the test result. For example:
Did not detect offhook.
Did not detect dial tone.
Device in use. Please try later.
Failed to open device (tty).
In addition to the standard output, you might see the following error messages in the Test Modem screen:
Failed to create socket. This error message displays when the test could not allocate a system resource. If you see this message, check to see if someone else is using the modem.
Failed to connect to SME. This error message displays when the program could not connect to the server maintenance engine (SME) to process the command. Go to the View Process Status screen and make sure that both the Avaya Call Processing (ACP) system and the SME are running.
Failed to send request to SME. This error message displays when a request could not be sent to the SME. Go to the View Process Status screen and make sure that both the ACP system and the SME are running.
Failed to receive response from SME. This error message displays when the test did not receive a response from the SME. The call-processing software may be hung. Go to the View Process Status screen and make sure that the ACP system is running.