Wolfgang Baudler wrote:
Hi,
Thanks for the hints so fare...
I somehow managed to get the right logs for my problem (see below).
...and with this log your problem perhaps can be solved, see
below :-))
Is anybody using an ELSA or TKR modem sucessfully with HylaFAX? Your
config-files could save a lot of time...
And what devices do I have to use for faxgetty and for HylaFAX? /dev/ttyS?
or /dev/cua?
Log:
====
Sep 17 23:02:51 lucutus FaxGetty[1151]: OPEN /dev/ttyS1
Sep 17 23:02:51 lucutus FaxGetty[1151]: MODEM set DTR OFF
Sep 17 23:02:51 lucutus FaxGetty[1151]: DELAY 2600 ms
Sep 17 23:02:54 lucutus FaxGetty[1151]: MODEM set DTR ON
Sep 17 23:02:54 lucutus FaxGetty[1151]: MODEM set baud rate: 38400 baud, input
flow RTS/CTS, output flow RTS/CTS
Sep 17 23:02:54 lucutus FaxGetty[1151]: MODEM flush i/o
Sep 17 23:02:54 lucutus FaxGetty[1151]: <-- [15:ATZE0V1Q0S0=0H\r]
Sep 17 23:02:54 lucutus FaxGetty[1151]: --> [14:ATZE0V1Q0S0=0H]
^^^^^^^^^^^^^^
as you can see the command string contains "E0" but the modem is not
in echo-off mode after the reset-cmd "ATZE0V1Q0S0=0H";
the behaviour of modems regarding the command-buffer after "ATZ"
is undefined; some modems are just cleaning the buffer during ATZ
and don't executing all commands behind ATZ on the command line;
the echo of the commands from the modem are read by faxgetty(1M)
and faxgetty(1M) don't understand them correctly;
don't use "ATZ" in ModemResetCmds: (see also man config(4F));
matthias
Matthias Apitz / guru@softcon.de ; (07:34:58 AM 01/27/97)