|
Hylafax Receive Problem
I'm using a USR 2977 Fax/Modem FCLASS 1 With the HylaFax, the latest stable version on Suse 9.2
It's been a long day of running back and forth to the fax machine and I still can't get Hylafax to successfully complete a transaction.
I am starting to doubt the HP fax machine/printer I'm using, but the phone line is for sure not the problem, and I don't believe the modem is at fault because I have two of them in two servers and both are giving me the same results.
I searched all over the net for some answers and didn't come up with anything.
Here is my log file for a typical 1 page fax session.
Mar 18 22:09:50.41: [ 3901]: SESSION BEGIN 000000016 17029870120
Mar 18 22:09:50.41: [ 3901]: HylaFAX (tm) Version 4.2.1
Mar 18 22:09:50.41: [ 3901]: <-- [13:AT+FCLASS=1A\r]
Mar 18 22:09:55.69: [ 3901]: --> [7:CONNECT]
Mar 18 22:09:55.69: [ 3901]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS14'
Mar 18 22:09:55.69: [ 3901]: RECV FAX: begin
Mar 18 22:09:55.69: [ 3901]: <-- data [32]
Mar 18 22:09:55.69: [ 3901]: <-- data [2]
Mar 18 22:09:55.75: [ 3901]: --> [7:CONNECT]
Mar 18 22:09:55.75: [ 3901]: <-- data [23]
Mar 18 22:09:55.75: [ 3901]: <-- data [2]
Mar 18 22:09:56.47: [ 3901]: --> [7:CONNECT]
Mar 18 22:09:56.47: [ 3901]: <-- data [10]
Mar 18 22:09:56.47: [ 3901]: <-- data [2]
Mar 18 22:09:58.66: [ 3901]: --> [2:OK]
Mar 18 22:09:58.66: [ 3901]: <-- [9:AT+FRH=3\r]
Mar 18 22:09:59.75: [ 3901]: --> [7:CONNECT]
Mar 18 22:10:01.28: [ 3901]: --> [2:OK]
Mar 18 22:10:01.28: [ 3901]: REMOTE TSI "7023651133"
Mar 18 22:10:01.28: [ 3901]: <-- [9:AT+FRH=3\r]
Mar 18 22:10:01.29: [ 3901]: --> [7:CONNECT]
Mar 18 22:10:01.63: [ 3901]: --> [2:OK]
Mar 18 22:10:01.63: [ 3901]: REMOTE wants 14400 bit/s
Mar 18 22:10:01.63: [ 3901]: REMOTE wants A4 page width (215 mm)
Mar 18 22:10:01.63: [ 3901]: REMOTE wants unlimited page length
Mar 18 22:10:01.63: [ 3901]: REMOTE wants 7.7 line/mm
Mar 18 22:10:01.63: [ 3901]: REMOTE wants 2-D MMR
Mar 18 22:10:01.63: [ 3901]: REMOTE wants T.30 Annex A, 256-byte ECM
Mar 18 22:10:01.63: [ 3901]: RECV training at v.17 14400 bit/s
Mar 18 22:10:01.63: [ 3901]: <-- [11:AT+FRM=145\r]
Mar 18 22:10:03.33: [ 3901]: --> [7:CONNECT]
Mar 18 22:10:04.84: [ 3901]: RECV: TCF 2722 bytes, 1% non-zero, 2676 zero-run
Mar 18 22:10:04.85: [ 3901]: --> [10:NO CARRIER]
Mar 18 22:10:04.85: [ 3901]: DELAY 75 ms
Mar 18 22:10:04.92: [ 3901]: TRAINING succeeded
Mar 18 22:10:04.92: [ 3901]: <-- [9:AT+FTH=3\r]
Mar 18 22:10:05.12: [ 3901]: --> [7:CONNECT]
Mar 18 22:10:05.12: [ 3901]: <-- data [3]
Mar 18 22:10:05.12: [ 3901]: <-- data [2]
Mar 18 22:10:06.29: [ 3901]: --> [2:OK]
Mar 18 22:10:06.29: [ 3901]: <-- [11:AT+FRM=146\r]
Mar 18 22:10:07.60: [ 3901]: --> [7:CONNECT]
Mar 18 22:10:11.50: [ 3901]: RECV received frame number 0
Mar 18 22:10:11.65: [ 3901]: RECV received frame number 1
Mar 18 22:10:11.79: [ 3901]: RECV received frame number 2
Mar 18 22:10:11.93: [ 3901]: RECV received frame number 3
Mar 18 22:10:12.07: [ 3901]: RECV received frame number 4
Mar 18 22:10:12.28: [ 3901]: RECV received frame number 5
Mar 18 22:10:12.42: [ 3901]: RECV received frame number 6
Mar 18 22:10:12.65: [ 3901]: RECV received frame number 7
Mar 18 22:10:12.65: [ 3901]: HDLC frame not byte-oriented. Trailing byte: 0
Mar 18 22:10:12.65: [ 3901]: RECV assumed RCP frame with block end
Mar 18 22:10:12.65: [ 3901]: --> [10:NO CARRIER]
Mar 18 22:10:12.65: [ 3901]: <-- [9:AT+FRH=3\r]
Mar 18 22:10:19.65: [ 3901]: --> [0:]
Mar 18 22:10:19.65: [ 3901]: MODEM <Empty line>
Mar 18 22:10:19.65: [ 3901]: <-- data [1]
Mar 18 22:10:19.66: [ 3901]: --> [2:OK]
Mar 18 22:10:19.66: [ 3901]: RECV keeping unconfirmed page
Mar 18 22:10:19.66: [ 3901]: RECV: 2048 bytes of data, 228 total lines
Mar 18 22:10:19.66: [ 3901]: <-- [9:AT+FRS=7\r]
Mar 18 22:10:26.42: [ 3901]: --> [2:OK]
Mar 18 22:10:26.42: [ 3901]: RECV FAX (000000016): from 7023651133, page 1 in 0:22, INF, 7.7 line/mm, 2-D MMR, 14400 bit/s
Mar 18 22:10:26.43: [ 3901]: RECV FAX (000000016): recvq/fax000000016.tif from 7023651133, route to <unspecified>, 1 pages in 0:31
Mar 18 22:10:26.43: [ 3901]: RECV FAX: T.30 T2 timeout, expected signal not received
Mar 18 22:10:26.43: [ 3901]: <-- [9:AT+FTH=3\r]
Mar 18 22:10:26.46: [ 3901]: --> [7:CONNECT]
Mar 18 22:10:26.46: [ 3901]: <-- data [3]
Mar 18 22:10:26.46: [ 3901]: <-- data [2]
Mar 18 22:10:27.63: [ 3901]: --> [2:OK]
Mar 18 22:10:27.64: [ 3901]: RECV FAX (000000016): session with 7023651133 terminated abnormally: T.30 T2 timeout, expected signal not received
Mar 18 22:10:27.64: [ 3901]: RECV FAX: bin/faxrcvd "recvq/fax000000016.tif" "ttyS14" "000000016" "T.30 T2 timeout, expected signal not received" "" ""
Mar 18 22:10:27.64: [ 3901]: RECV FAX: end
Mar 18 22:10:27.64: [ 3901]: SESSION END
----------------------------------------------
Config file
--------------------------------------------
CountryCode: 1
AreaCode: 702
FAXNumber: 1.702.555.5555
LongDistancePrefix: 1
InternationalPrefix: 011
DialStringRules: etc/dialrules
ServerTracing: 1
#TracingMask: 0x11
#SessionTracing: 0xFFF
SessionTracing: 11
RecvFileMode: 0600
LogFileMode: 0600
DeviceMode: 0600
RingsBeforeAnswer: 1
SpeakerVolume: off
GettyArgs: "-h %l dx_%s"
LocalIdentifier: BlueFoxHire
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%P of %%T"
MaxRecvPages: 25
#ClocalAsRoot yes
#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType: Class1 # use class 1 interface
ModemRate: 19200 # rate for DCE-DTE communication
ModemFlowControl: xonxoff # software flow control
#
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
I don't know what a T.30 T2 timeout is but I'm sure it's the key to this problem. Is it something in the modem? It outputs a partial Tiff file and in some cases it's readable. In multiple page fax sessions often the first 2 pages will be retrievable out of 4 total.
I would greatly appreciate some help with this.
I had this working once before with the same modem, but earlier versions of Suse & Hylafax. Same boards, cpus & hd's too.
Thanks,
Tony
|
