Fw: flexfax: US Robotics Modem Help - Resolved!!!

["Catherine Doris" <stormie@shaw.wave.ca>]

Well, I finally found the problem that was presenting me from sending faxes.
My problem was that my modem would dial and the remote modem would respond
but my modem would not start the handshaking.  Receives worked fine.

In the config file there is a default entry ATDT%s@.  The @ causes the
connection to be "quite".  However, with a US Robotic modem (at least mine)
there are 4 levels of X messages (X1, X2, X3, or X4).  For X3 and X4 the @
prevents any verbal codes from being relayed back from the modem.  I was
using X4.

By removing the @ the sends are now working fine.  I suppose I could have
accomplished the same thing by changing to X1 or X2 but I haven't tried it.

Gerry

BTW, the correct command is ATDT.  I also made the other correct suggested
in the attached note.


-----Original Message-----
From: a <aandrews@mediswitch.co.za>
To: 'gdoris@shaw.wave.ca' <gdoris@shaw.wave.ca>
Date: December 11, 1998 5:20 AM
Subject: RE: flexfax: US Robotics Modem Help


>
>
>----------
>From: gdoris@shaw.wave.ca[SMTP:gdoris@shaw.wave.ca]
>Sent: Friday, December 11, 1998 2:37 AM
>To: Hylafax
>Subject: flexfax: US Robotics Modem Help
>
>Hi
>My 10 cents worth ...
>Have you checked the user manual for the correct modem commands and matched
them with your config. file.
>I can already see that  class2ncrcmd in your config is "incorrect"
>It "should" be AT+FNR=1,1,1,0   (see the SUSE hylafax page)
>I think your modem dial cmd might be wrong...
>Is it not supposed to be AT&DT.... ?
>Have you tried using your modem as a class 1 modem ?
>Perhaps try use cu or something and actually test the commands you
>issued to the modem prior to the abort.
>Perhaps another process trying to access the modem will hylafax is busy
>because the port is not locking properly?
>cheers
>
>