Re: [hylafax-users] MODEM /dev/ttyS1 appears to be wedged on a linux Redhat 7.1 system

["sachin" <sachindra.nath@iba.com.sg>]

Hi All,
   My problem with the hylafax setup is still un resolved. Could anyone
please point out the mistake ? Also attached here is my config file and the
latest logs with hylafax-4.1.5. Please help. Could anyone help me finding
out, whether its a problem with the configuration I'm using, OS version or
my modem ? I'm now really clueless after breaking my head with this software
for the past five weeks.

Nov  5 16:10:05 linux FaxSend[4288]: MODEM set baud rate: 115200 baud, input
flo
w RTS/CTS, output flow RTS/CTS
Nov  5 16:10:05 linux FaxSend[4288]: DELAY 10 ms
Nov  5 16:10:05 linux FaxSend[4288]: MODEM flush i/o
Nov  5 16:10:05 linux FaxSend[4288]: <-- [4:ATZ\r]
Nov  5 16:10:05 linux FaxSend[4288]: --> [3:ATZ]
Nov  5 16:10:05 linux FaxSend[4288]: --> [2:OK]
Nov  5 16:10:05 linux FaxSend[4288]: DELAY 3000 ms
Nov  5 16:10:08 linux FaxSend[4288]: <-- [5:ATE0\r]
Nov  5 16:10:13 linux FaxSend[4288]: MODEM TIMEOUT: reading line from modem
Nov  5 16:10:13 linux FaxSend[4288]: MODEM <Timeout>
Nov  5 16:10:13 linux FaxSend[4288]: MODEM set DTR OFF
Nov  5 16:10:13 linux FaxSend[4288]: DELAY 75 ms
Nov  5 16:10:13 linux FaxSend[4288]: MODEM set DTR ON
Nov  5 16:10:13 linux FaxSend[4288]: DELAY 2600 ms
Nov  5 16:10:16 linux FaxSend[4288]: MODEM set baud rate: 115200 baud, input
flo
w RTS/CTS, output flow RTS/CTS
Nov  5 16:10:16 linux FaxSend[4288]: DELAY 10 ms
Nov  5 16:10:16 linux FaxSend[4288]: MODEM flush i/o
Nov  5 16:10:16 linux FaxSend[4288]: <-- [4:ATZ\r]
Nov  5 16:10:46 linux FaxSend[4288]: MODEM TIMEOUT: reading line from modem
Nov  5 16:10:46 linux FaxSend[4288]: MODEM <Timeout>
Nov  5 16:10:46 linux FaxSend[4288]: MODEM set DTR OFF
Nov  5 16:10:46 linux FaxSend[4288]: /dev/ttyS1: Can not initialize modem.
Nov  5 16:10:46 linux FaxSend[4288]: STATE CHANGE: BASE -> MODEMWAIT
(timeout 30
)

The configuration file

# $Id: usr-xon,v 1.9 2002/09/13 16:55:15 darren Exp $
#
# HylaFAX Facsimile Software
#
# Copyright (c) 1990-1996 Sam Leffler
# Copyright (c) 1991-1996 Silicon Graphics, Inc.
# HylaFAX is a trademark of Silicon Graphics, Inc.
#
# Permission to use, copy, modify, distribute, and sell this software and
# its documentation for any purpose is hereby granted without fee, provided
# that (i) the above copyright notices and this permission notice appear in
# all copies of the software and related documentation, and (ii) the names
of
# Sam Leffler and Silicon Graphics may not be used in any advertising or
# publicity relating to the software without the specific, prior written
# permission of Sam Leffler and Silicon Graphics.
#
# THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
# EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
# WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
#
# IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
# ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
# OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
# WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
# LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
# OF THIS SOFTWARE.
#

#
# Configuration for using the Class 1 command interface with
# a USR Courier or Sportster modem and XON/XOFF flow control.
#
#
#
#
CountryCode:            65
#AreaCode:              415
FAXNumber:              +6568720574
#LongDistancePrefix:    1
#InternationalPrefix:   011
DialStringRules:        /var/spool/hylafax/etc/dialrules
ServerTracing:          0xFFF
SessionTracing:         0xFFF
RecvFileMode:           0600
LogFileMode:            0600
DeviceMode:             0600
RingsBeforeAnswer:      0
SpeakerVolume:          off
GettyArgs:              "-h %l dx_%s"
LocalIdentifier:        "NothingSetup"
TagLineFont:            /var/spool/hylafax/etc/lutRS18.pcf
TagLineFormat:          "From %%l|%c|Page %%P of %%T"
QualifyTSI:             /var/spool/hylafax/etc/lutRS18.pcf
MaxRecvPages:           25
#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType:              Class1          # use class 1 interface
ModemRate:              115200
ModemFlowControl:       rtscts
#
ModemSetupDTRCmd:       ATS13=1&D2      # setup so DTR drop resets modem
ModemSetupDCDCmd:       AT&C1           # setup so DCD reflects carrier (or
not)
ModemNoFlowCmd:         AT&H0&I0&R1     # setup modem for no flow control
ModemHardFlowCmd:       AT&H1&I0&R2     # setup modem for hardware flow
control
ModemSoftFlowCmd:       AT&H2&I2&R1     # setup modem for software flow
control
ModemResultCodesCmd:    ATQ0X4          # enable result codes
#
#ModemMfrQueryCmd:      !USR
ModemModelQueryCmd:     ATI3
ModemRevQueryCmd:       ATI7            # XXX returns a multi-line result
#
# When AT+FCLASS=1 is issued the modem automatically switches
# to software flow control; these parameters let the fax software
# reset flow control as needed after entering Class 1.
#
Class1NFLOCmd:          AT&H0&I0&R1     # setup modem for no flow control
Class1HFLOCmd:          AT&H1&I0&R2     # setup modem for hardware flow
control
Class1SFLOCmd:          ""              # modem does this automatically
#
# This should resolve "DIS/DTC received 3 times" errors:
#
#
Class1ResponseWaitCmd:  AT+FRS=1        # wait after sending TCF for
response
#
# The remainder of this configuration is included so that the
# modem "idles" in Class 0 while not sending or receiving facsimile.
#
ModemSetupAACmd:        AT+FCLASS=0     # leave modem idling in class 0
ModemAnswerCmd:         AT+FCLASS=1A    # answer in Class 1
#
# Disables the reporting of bad frames by the modem.  This
# overcomes a firmware problem in the x2 and V90 Sportsters.
# It is not necessary for the Courier modem.
#
Class2NRCmd:    AT+FNR=1,1,1,0


thanks & regards
Sachin


 -----Original Message-----
From: 	sachin [mailto:sachindra.nath@iba.com.sg]
Sent:	Monday, October 21, 2002 4:09 PM
To:	'hylafax-users@hylafax.org'
Subject:	MODEM /dev/ttyS1 appears to be wedged on a linux Redhat 7.1 system

Hi Guys,
   I urgently need some help to counter this problem, I had been facing for
the last couple of weeks. I have been trying to do a fresh installation of
hylafax 4.1.3 (as well as, later 4.1.4) on a linux redhat 7.1 system, doing
a source build. I am using a Class 1 modem It is a US Robotics 56K FAX EXT
Rev. 11.13.14 ...
I have been continuously getting the message
MODEM /dev/ttyS1 appears to be wedged

On a closer look on the server's trace log, I see that there is a timeout
encountered after Hylafax sends a ATZ message to the device. Attached is the
tracelog.

Oct 18 20:08:51 linux FaxQueuer[19160]: SUBMIT JOB 15
Oct 18 20:08:53 linux FaxSend[19176]: DELAY 75 ms
Oct 18 20:08:53 linux FaxSend[19176]: DELAY 2600 ms
Oct 18 20:08:56 linux FaxSend[19176]: <-- [4:ATZ\r]
Oct 18 20:09:26 linux FaxSend[19176]: MODEM <Timeout>
Oct 18 20:09:26 linux FaxSend[19176]: DELAY 75 ms
Oct 18 20:09:26 linux FaxSend[19176]: DELAY 2600 ms
Oct 18 20:09:28 linux FaxSend[19176]: <-- [4:ATZ\r]
Oct 18 20:09:58 linux FaxSend[19176]: MODEM <Timeout>
Oct 18 20:10:00 linux CROND[19217]: (root) CMD (   /sbin/rmmod -as)
Oct 18 20:10:28 linux FaxSend[19176]: DELAY 75 ms
Oct 18 20:10:29 linux FaxSend[19176]: DELAY 2600 ms
Oct 18 20:10:31 linux FaxSend[19176]: <-- [4:ATZ\r]
Oct 18 20:11:01 linux FaxSend[19176]: MODEM <Timeout>
Oct 18 20:11:01 linux FaxSend[19176]: DELAY 75 ms
Oct 18 20:11:01 linux FaxSend[19176]: DELAY 2600 ms
Oct 18 20:11:04 linux FaxSend[19176]: <-- [4:ATZ\r]
Oct 18 20:11:34 linux FaxSend[19176]: MODEM <Timeout>
Oct 18 20:11:34 linux FaxQueuer[19160]: MODEM /dev/ttyS1 appears to be
wedged
Oct 18 20:11:34 linux FaxQueuer[19160]: MODEM WEDGED: bin/wedged "ttyS1"
"/dev/t
tyS1"
Oct 18 20:11:34 linux FaxSend[19235]: DELAY 75 ms

Sometimes, this call succeeds, but the modem times out when Hylafax sends a
ATE0 message to it. Can someone point out the problem ?

ps: When I try to send these same messages through minicom, it works fine.
All the test commands given in hylafax manual to check the modem, appear to
work fine for me. Could anyone throw some light on this please ?
thanks in advance...
regards
Sachin


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*