Data calls do not automatically answer – Verilink Productivity 500 (34-00236) Product Manual User Manual

Page 82

Advertising
background image

Page 82

500 TA

Troubleshooting Guide

Data calls do not automatically answer.

• Check that the rings to answer command S0 is set to a nonzero value. Also,

if the ring count is set too high, the calling device may time out and termi-
nate the call.

Data calls connect but automatically terminate within about 5 seconds.

• Check that the remote device is running the same rate adaption protocol.

• Make sure you are calling the correct device.

Calls to the unit are rejected by the unit or calls from the unit are not accepted
by the switch.

• Verify that the switch type and version settings are for the correct switch.

• Verify that the SPID and DN match the number agreed to at subscription

time with the local telephone company. Also check that the switch options
have been saved in the stored profile and that the network link has been
restarted.

• Verify that the line is configured at the switch to accept the type of call

desired. Data calls need circuit-switched data capability, and voice calls need
circuit-switched voice capability.

When the 500 TA tries to dial or answer data calls, it aborts for no appar-
ent reason.

This can occur if the PC sends any characters to the 500 TA while it is dialing,
answering, or connecting. The 500 TA has a feature called ‘any key abort’ that
aborts if any characters are received from the PC during the connect sequence.

• If this problem occurs in the answer mode on the first ring, the problem may

be that the PC is echoing the RING message back to the 500 TA, causing it
to abort. In this case, you can disable response messages using the ATQ
command.

After a data call connects, the local PC receives bad or garbled data.

This usually indicates a rate adaption problem.

• Verify that both the 500 TA and the remote device are set for the same rate

adaption protocol (e.g. V.120).

• The remote device may be trying to establish a synchronous protocol,

unaware that the 500 TA is set for asynchronous mode. Suspect this problem
if the garbled data consists of long streams of one or two characters. To cor-
rect the problem find out which mode and protocol the remote device is
attempting, and set your 500 TA and PC accordingly.

Advertising