Problem
How can I determine why my dialer is failing? After enabling the port assigned to my modem, I get errors stating that the dialer has failed, similar to:
***/etc/getty -t60 tty2A m (Mon Sep 22 14:15:22 1997), PID 15888 Dialer failed on line tty2A: Timer Expired (error 62)
- OR -***/etc/getty -t60 tty2A m (Mon Sep 22 14:15:22 1997), PID 15888 Dialer failed on line tty2A: Invalid argument (error 22)
What do these messages mean and how can I correct this problem?
I have created a new dialer that does not work as expected; how can I determine why it is failing?
Cause
Each modem manufacturer and each type of modem has a set of commands
that are used to set options such as error correction, data
compression, and any number of other features that the specific
modem supports. Using an option that the modem does not support can
result in dialer failure and can also cause the modem to fail to
respond as expected. Additionally, there are certain modem commands
that change the modem response in such a way that the dialer cannot
tell whether the configuration of the modem was accepted. The
"Invalid argument (error 22)" indicates that the dialer received
an ERROR response, and the "Timer Expired (error 62)" indicates
that the modem did not respond as expected within the time allotted,
or the modem is powered off or disconnected. Solution
If the modem is off or disconnected, you should also disable the port so that the dialer stops trying to initialize it:
disable tty2AThere are three basic dialer types:1. The first type is the uuchat style of dialer, which stores an
initialization string in the Dialers(F) file. For example:(/usr/lib/uucp/Dialers)hayes2400 =,-, "" ATQ0E0T&D2S0=0X4S2=043\r\c OK\r ATDT\T\r\c Speed2. The second type is the non-atdialer binary dialer that hard codes
the modem setup strings into the dialer itself. For example:/usr/lib/uucp/dialHA24 which is compiled from the C program /usr/lib/uucp/dialHA24.c Your modem manufacture may also provide dialers in this form.
3. The third type is the atdialer(C) style, which is the most common.For the atdialer type of dialer, the modem initialization string is found in the ASCII companion file portion of the dialer.
Dialers are associated to a serial port in the Devices(F) file. Check /usr/lib/uucp/Devices for an ACU-type entry. If you see errors regarding a certain port, tty2A for example, you can determine the dialer used by looking here for lines related to this port. Use:
grep tty2 /usr/lib/uucp/DevicesYou may see lines such as:# ACU tty2A - 1200-2400 hayes2400 \D
ACU tty2A - 9600 /usr/lib/uucp/Courier_9600_V32
Direct tty2a - 9600 direct
# ACU tty2A - 1200 develcon vent ventel
# ACU tty2A - X1200 develcon vent ventel \D
# Develcon tty2A - Any develcon \D
# Direct tty2a - 9600 directAll lines starting with # are commented out and can be ignored.
So, in this example, the dialer associated with tty2A is
/usr/lib/uucp/Courier_9600_V32. The ASCII companion file
containing the initialization string for this dialer is
/usr/lib/uucp/default/Courier_9600_V32, which should contain
lines that look like this:#
# Vendor: U-S-_Robotics-_Inc-
# Modem : Courier 9600 V32
#
MDM_SETUP=AT&F&B1&C1&D2&M4&K1E0Q0V1&A3&H1&R2&I0&M4
MDM_SPEAKER=ATM0
MDM_DIALCMD=ATDT
MDM_HANGUP=ATHThe MDM_SETUP line contains the string. To debug this string you
need to connect directly to the modem and determine which option it
does not understand or which causes the modem to not return an "OK"
response. In the example above there is also a Direct entry for
tty2a. (If you don't have a direct entry for the port in question,
create one by editing Devices(F).) To connect directly to the
modem use the command:cu -l tty2aYou should get a "Connected" response. The initialization string
needs to be tested, one option at a time. The different options
are set with 2- or 3-character codes proceeded by "AT". These codes
are in the format of a letter, a letter and a number, or a special
character followed by a letter and a number, where the special
character is either "$", or "&", and sometimes "%". Once you are
connected to the modem, split the string up into parts and see which
one gives you an error or fails to return OK.# cu -l tty2a Connected AT&F OK AT&B1 OK AT&C1 OK AT&D2 OK AT&M4 ERROR (NOTE: This did not return OK and this indicates that this is not a valid option for your modem.) AT&K1 ERROR ATE0 OK (NOTE: E0 is a code that turns echo off on most modems. This causes you to be unable to see what is being typed. To reset echo to on, issue ATE1, blindly and press <Enter>.)
OKOK
ATQ0 (NOTE: The Q code controls quiet mode for most modems Q0
OK turns quiet mode off. Q1 would cause the modem to stop
responding all together and cause the timer expired
problem.)ATV1 (NOTE: The V code controls Verbal Response for almost all
OK modems. V1 sets Verbal responses and V0 sets Numeric
responses. The dialer expects Verbal responses and will
fail if set to Numeric(V0).)
AT&A3
ERROR
AT&H1
ERROR
AT&R2
ERROR
AT&I0
ERROR
AT&M4
ERROR
(NOTE: None of these last options are compatible with
this modem. Consult the manual for your modem to
determine what each option means and make changes
to the MDM_SETUP string manually with the editor of
your choice. In this case, we would change the string
to look like:MDM_SETUP=AT&F&B1&C1&D2E0Q0V1which eliminates all unrecognized options.)~[systemid]. (NOTE: Issue "~." to exit cu; the system name will
appear on its own. The ~ has to be the first
character of the line.)
#NOTE: Almost every modem uses two specific parameters that control the
modem response settings. The first is the "V?" string. "V0"
turns off verbal response codes on most modems causing the modem
to return numeric responses instead. To fix this, use "V1" instead;
this will generate "OK" instead of "0" (zero). The second parameter
is "Q?". "Q1" turns off response codes altogether on most modems.
To correct this use "Q0" so that the modem does return responses
to commands. See also
TA105764, "How to utilize the extra dialers contained in /usr/lib/uucp/default in 5.0.4."
cu(C), uucp(C), Devices(F)