Avaya PARTNER Installation And Use Manual page 405

Possible Cause 2: The data link (ATM or Frame Relay) is not established.
What to do: Follow these steps to check the data link connection.
1. Check the status of the data link. If the Data Link is established, one of the following appears
on the terminal screen:
For ATM—SDSL ATM Interface ONLINE: Data Rate = 2320 kbps
For Frame Relay—SDSL Frame Relay Interface ONLINE: Data Rate = 2320 kbps
Slower speed connections show a different speed.
2. If neither of these messages appears a short time after the SDSL light transitions from flashing
to solid, the data link has not been established. Do the following:
a. Verify that the data link protocol is what the service provider specified (from the Main
Menu, select "5," then "1," and then "1"). The data link protocol appears next to the label
"Current Data Link Protocol." It is set for Frame Relay or ATM.
b. Verify the DLCI (frame relay) or VCI/VPI settings are identical to those that the service
provider provided.
c. Verify the Encapsulation settings (Frame Relay and ATM), PCR (ATM), and Service (ATM)
are those provided by the service provider.
d. If you are running ATM as a data link protocol and the network provider has established a
third PVC for OAM, create this in the ATM Configuration Menu. (From the Main Menu,
press "5," "1," "4," and "2.") After performing a cold-start of the system, attempt an OAM
loopback to verify the ATM connection has been established.
3. If the 1600 DSL module still does not work properly, go to Possible Cause 3.
Possible Cause 3: The voice gateway connection is not established.
What to do: Follow these steps to check the voice gateway connection.
1. Seize any of the lines assigned to the 1600 DSL module.
2. If dial tone is not received on any of the lines assigned to the 1600 DSL module, do the
following:
a. Confirm the gateway manufacturer.
b. Confirm with the service provider which of the DLCIs (Frame Relay) or PVCs (ATM) are
associated with the gateway. There will be two provided—one for voice and one for data.
Make sure the correct DLCI/PVC is associated with the voice.
c. For systems with Lucent Pathstar, verify the Router settings for the voice DLCI/PVC. Also
verify the MGCP/NCS client settings that are found in the "Manage MGCP/NCS
Embedded Client" section of the Main Menu.
3. If the 1600 DSL module still does not work properly, go to Possible Cause 4.
Troubleshooting
Problems with the 1600 DSL Module
11-19