Re: [hylafax-users] Problem with USR 56K

["Jay R. Ashworth" <jra@baylink.com>]

On Wed, Oct 03, 2001 at 03:11:43PM +0200, Antonio Gabelli wrote:
> I've some problem with a modem USR 56K. When I send a fax faxstat -s tell me
> in status field:
> RSPREC error/got DCN.
> WHFC report the same error but .... faxes are sent and received with an
> error.
> My linux is REDHAT 7.1 with Hylafax 4.1-1
> 
> HELP ME!
> Thanks a lot
> 
> Antonio Gabelli
> antonio.gabelli@libero.it
> 
> My  /var/log/messages

Looks *very* broken...

> ****************************************************************************
> *************************************************************
> ott  3 14:04:03 linux FaxSend[3775]: HylaFAX (tm) Version 4.1
> ott  3 14:04:03 linux FaxSend[3775]: SEND FAX: JOB 11 DEST 0521981690 COMMID
> 00000027
> ott  3 14:04:03 linux FaxSend[3775]: DEVICE '/dev/ttyS0'
> ott  3 14:04:38 linux FaxSend[3775]: SEND: Communication failure during
> Phase B/C; Giving up after 3 attempts to send same pa
> ott  3 14:04:38 linux FaxQueuer[972]: JOB 11 (active dest +39521981690 pri
> 125 tts 0:00 killtime 2:54:27): CMD DONE: exit sta
> ott  3 14:04:38 linux FaxQueuer[972]: JOB 11 (done dest +39521981690 pri 125
> tts 0:00 killtime 2:54:27): SEND DONE: 0:45
> Oct  3 14:04:56s 56K FAXxGetty[1030]: MODEM set DTR OFF
> Oct  3 14:04:56 linux FaxGetty[1030]: MODEM set DTR ON
> Oct  3 14:04:59 linux FaxGetty[1030]: MODEM set baud rate: 38400 baud, input
> flow RTS/CTS, output flow RTS/CTS
> Oct  3 14:04:59 linux FaxGetty[1030]: MODEM flush i/o
> Oct  3 14:04:59 linux FaxGetty[1030]: <-- [4:ATZ\r]
> Oct  3 14:04:59 linux FaxGetty[1030]: --> [2:OK]
> Oct  3 14:04:59 linux FaxGetty[1030]: <-- [5:ATE0\r]
> Oct  3 14:04:59 linux FaxGetty[1030]: --> [4:ATE0]
> Oct  3 14:04:59IOS verFaxGetty[1030]: --> [2:OK]
> Oct  3 14:04:59ng kswaFaxGetty[1030]: <-- [5:ATV1\r]
> Oct  3 14:04:5956 UnixFaxGetty[1030]: --> [2:OK]
> Oct  3 14:04:59 queuedFaxGetty[1030]: <-- [7:ATQ0X4\r]
> Oct  3 14:04:59K driveFaxGetty[1030]: --> [2:OK]
> Oct  3 14:04:59m MultiFaxGetty[1030]: <-- [7:ATS0=0\r]
> Oct  3 14:05:00ssumingFaxGetty[1030]: --> [2:OK]
> Oct  5 14:05:003: IDE FaxGetty[1030]: <-- [7:ATS8=2\r]
> Oct  5 14:05:00ardcodeFaxGetty[1030]: --> [2:OK]
> Oct  5 14:05:003: chipFaxGetty[1030]: <-- [8:ATS7=60\r]
> Oct  5 14:05:003: not suxGetty[1030]: --> [2:OK]
> Oct  3614:05:00e0: BM-suxGetty[1030]: <-- [12:AT&H1&I0&R2\r]
> Oct  3614:05:00e1: BM-FaxGetty[1030]: --> [2:OK]
> Oct  3614:05:00UANTUM FaxGetty[1030]: <-- [11:ATS13=1&D2\r]
> Oct  3614:05:00ssumingFaxGetty[1030]: --> [2:OK]
> Oct8:4714:05:00REATIVEFaxGetty[1030]: <-- [6:AT&C1\r]
> Oct8:4714:05:00t 0x1f0FaxGetty[1030]: --> [2:OK]
> Oct8:5714:05:00t 0x170FaxGetty[1030]: <-- [12:AT+FCLASS=?\r]
> Oct8:5814:05:000066251FaxGetty[1030]: --> [7:0,1,2.0]
> Oct8:5814:05:00ion cheFaxGetty[1030]: --> [2:OK]
> Oct8:5814:05:00hda1 hdFaxGetty[1030]: MODEM Supports "Data"
> Oce8:5814:05:00 drive(FaxGetty[1030]: MODEM Supports "Class 1"
> Oct9:0014:05:00is a poFaxGetty[1030]: MODEM Supports "Class 2.0"

I'm not sure what's going on there, but I suspect you have some fairly
fundamental problems if your syslog looks that borken.  Whether they're
syslog, kernel, or HylaFAX I'm not sure... but the syslog simply isn't
supposed to look like that...

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra@baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 804 5015

   "Usenet: it's enough to make you loose your mind."
     -- me


____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null