![background image](http://html.mh-extra.com/html/zoom/comstar-svd/comstar-svd_owners-manual_938200035.webp)
Chapter 3 Problems and Solutions
35
(the comma is part of the code) or the other code as a prefix with
the telephone numbers in the software’s dialing directory. Or you
can add *70, or the correct code to the dial string (be sure to
include the comma). Note that this helps with outgoing but not
incoming calls.
Your modem does not make a connection.
If your modem places calls but never makes a connection, make
sure you are dialing the right number.
The remote modem may be turned off.
You receive bursts of errors occasionally, but otherwise
data quality is good.
The connection may have been established on poor-quality or
noisy telephone lines. Hang up and place the call again to try to
obtain a better connection.
Someone may be picking up an extension connected to the line
that your modem is using. If the modem is sharing a telephone
line with other telephones, inform the other users when you will be
making a data call.
Your telephone line may have a Call Waiting feature and a call is
being received. See Call Waiting discussion above.
Random errors occur or data is missing in transmitted data.
Use the MNP or V.42 protocol if the remote modem supports one
of these protocols. See the table on page 34 for more
information.
Select a lower baud rate in your communications software and
place the call again.
If both modems are using the MNP or V.42 protocol, the only way
this can occur is if your modem and communications software are
not using the appropriate flow control. Configure your
communications software for RTS/CTS (hardware) flow control.
Your computer will now pause for the transmission to be stored.
Data appears garbled on the screen
Your communications software character setup (start bit, data
bits, stop bits, and parity bit) does not match that of the remote
system. Check your settings against those used by the remote
system and make sure they match. Pay particular attention to the