[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: Re: [efax-users] faxmodem not communicating]

To: efax-users <efax-users@xxxxxxx>
From: Ed Fix <edfix@xxxxxxxxxxx>
Subject: [Fwd: Re: [efax-users] faxmodem not communicating]
Date: Mon, 14 Dec 2009 14:18:54 -0500

Well, some developments, none good.

I tried to use the development efax version (efax-0.9a-001114.tar.gz, I
had a copy from an earlier installation).  Compiled and installed it.
"fax receive" seemed to set up ok (haven't received a fax yet), but when
I tried to send a fax, I got a segmentation fault

mtrr: type mismatch for c0000000,10000000 old: write-back new:
write-combining
efax[4644]: segfault at 00000000000000ff rip 00000035046796d0 rsp
00007fffdea52698 error 4

I'd guess there's a problem compiling in a 64 bit environment.
I replaced efax with the 64-bit binary rpm and tried setting both:

FCINIT='FBO=0'
and
FCINIT='FBO=1'

When I set up the fax receive to wait for a ring, the modem immediately
went off-hook, waited a few seconds, generated an error, reset, and kept
cycling through until I stopped it.

I even tried un-commenting the FCINIT command that was there for some
USR modems, but no change.  I get the same error as in the original
message.  Do I need to invest in a different modem?

Ed

--- Begin Message ---

To: Ed Fix <edfix@xxxxxxxxxxx>
From: Ed Casas <edc@xxxxxxx>
Subject: Re: [efax-users] faxmodem not communicating
Date: Sun, 13 Dec 2009 21:01:22 -0800

Hi Ed Fix,

The problem is that the modem responded with an 'ERROR' response
after efax sent it data.  This means the modem did not get enough
data or the data was not properly delimited.  This could be some
sort of problem with flow control or it could be a problem with
bit order.

Initialize the bit order by adding a +FBO=0 option in the FCINIT
variable (see FCINIT in the fax script).  If this doesn't work
try using +FBO=1 (because some fax modems reverse the
interpretation of the +FBO command).  efax can correct for
reversed bit order when receiving but can't detect the bit order
used when sending.  

If you can compile from source, you can also try the
"development" version available at:

http://www.cce.com/efax/download/

there were some changes to the way it deals with flow control and
it tends to work better with USB modems.

-- 
Ed Casas  edc@xxxxxxx


>I have just installed efax on a new CentOS Linux machine, and have a US
>Robotics USB modem connected (I used a winmodem before, but decided that
>was too much work for the new, 64-bit machine).  efax seems to work, but
>the modems are not communicating.  The other machine answered, and the
>fax and my modem seem to be communicating, but then everything stops.
>Using the old winmodem, I have successfully communicated with this
>machine before.  I don't know enough about fax protocols to figure out
>what's happening, but here's the log of a failed attempt to fax a doc.
>Any help appreciated.
>-------------------------------------------------------------------
>/usr/bin/efax: Sat Dec 12 15:15:18 2009 efax v 0.9 Copyright 1999 Ed
>Casas
>efax: 15:18 compiled Sep 26 2009 13:50:27
>efax: 15:18 TIFF version 4.2 file (little-endian)
>efax: 15:18 TIFF directory at 8 with 20 tags, last image.
>efax: 15:18 page 1 : /tmp/0m2cox.001 + 338 : 1728x2156 @ 204x196 dpi
>TIFF/FAX
>efax: 15:18 argv[0]=/usr/bin/efax
>efax: 15:18 argv[1]=-v
>efax: 15:18 argv[2]=ewin
>efax: 15:18 argv[3]=-v
>efax: 15:18 argv[4]=chewmainrxtf
>efax: 15:18 argv[5]=-d/dev/ttyACM0
>efax: 15:18 argv[6]=-x
>efax: 15:18 argv[7]=/var/lock/LCK..ttyACM0
>efax: 15:18 argv[8]=-iZ
>efax: 15:18 argv[9]=-i&FE&D2S7=120
>efax: 15:18 argv[10]=-i&C0
>efax: 15:18 argv[11]=-iM1L0
>efax: 15:18 argv[12]=-l
>efax: 15:18 argv[13]=myfaxnumber
>efax: 15:18 argv[14]=-kZ
>efax: 15:18 argv[15]=-h
>efax: 15:18 argv[16]=2009/12/12 15:15     myfaxnumber      Me     p. %
>d/%d
>efax: 15:18 argv[17]=-t
>efax: 15:18 argv[18]=Tnumber
>efax: 15:18 argv[19]=/tmp/0m2cox.001
>efax: 15:18 created text lock file /var/lock/LCK..ttyACM0
>efax: 15:18 opened /dev/ttyACM0
>efax: 15:18 command  "Q0V1"
>efax: 15:18 waiting 2.0 s
>efax: 15:18 .890 [<CR><LF>OK<CR><LF>]
>efax: 15:18 response "OK"
>efax: 15:18 command  "Z"
>efax: 15:18 waiting 5.0 s
>efax: 15:19 .509 [<CR><LF>OK<CR><LF>]
>efax: 15:19 response "OK"
>efax: 15:19 command  "&FE&D2S7=120"
>efax: 15:19 waiting 5.0 s
>efax: 15:19 .819 [AT&FE&D2S7=120<CR><CR><LF>]
>efax: 15:19 .819 [OK<CR><LF>]
>efax: 15:19 response "OK"
>efax: 15:19 command  "&C0"
>efax: 15:19 waiting 5.0 s
>efax: 15:19 .920 [<CR><LF>OK<CR><LF>]
>efax: 15:19 response "OK"
>efax: 15:20 command  "M1L0"
>efax: 15:20 waiting 5.0 s
>efax: 15:20 .023 [<CR><LF>OK<CR><LF>]
>efax: 15:20 response "OK"
>efax: 15:20 command  "E0"
>efax: 15:20 waiting 5.0 s
>efax: 15:20 .124 [<CR><LF>OK<CR><LF>]
>efax: 15:20 response "OK"
>efax: 15:20 command  "I3"
>efax: 15:20 waiting 5.0 s
>efax: 15:20 .228 [<CR><LF>U.S. Robotics 56K FAX USB V1.1.0<CR><LF>]
>efax: 15:20 .228 [<CR><LF>OK<CR><LF>]
>efax: 15:20 response "OK"
>efax: 15:20 command  "+FCLASS=?"
>efax: 15:20 waiting 5.0 s
>efax: 15:20 .329 [<CR><LF>0,1<CR><LF>]
>efax: 15:20 .329 [<CR><LF>OK<CR><LF>]
>efax: 15:20 response "OK"
>efax: 15:20 command  "+FCLASS=1"
>efax: 15:20 waiting 5.0 s
>efax: 15:20 .432 [<CR><LF>OK<CR><LF>]
>efax: 15:20 response "OK"
>efax: 15:20 using U.S. Robotics 56K FAX USB V1.1.0 in class 1
>efax: 15:20 command  "+FTM=?"
>efax: 15:20 waiting 5.0 s
>efax: 15:20 .534
>[<CR><LF>3,24,48,72,73,74,96,97,98,121,122,145,146<CR><LF>]
>efax: 15:20 .534 [<CR><LF>OK<CR><LF>]
>efax: 15:20 response "OK"
>efax: 15:20 dialing Tnumber
>efax: 15:20 command  "DTnumber"
>efax: 15:20 waiting 120.0 s
>efax: 15:49 .667 [<CR><LF>CONNECT<CR><LF>]
>efax: 15:49 response "CONNECT"
>efax: 15:49 connected
>efax: 15:51 waiting 2.0 s
>efax: 15:51 .133 [<CR><LF>OK<CR><LF>]
>efax: 15:51 response "OK"
>efax: 15:51 Warning: bit-reversed HDLC frame, reversing bit order
>efax: 15:51 received 16 bytes:
>efax: 15:51  ff c0 04 00 00 6a aa aa 00 11 09 01 fa 00 a8 8a
>efax: 15:51 received NSF - answering features
>efax: 15:51 command  "+FRH=3"
>efax: 15:51 waiting 35.0 s
>efax: 15:51 .136 [<CR><LF>CONNECT<CR><LF>]
>efax: 15:51 response "CONNECT"
>efax: 15:51 waiting 2.0 s
>efax: 15:51 .833 [<CR><LF>OK<CR><LF>]
>efax: 15:51 response "OK"
>efax: 15:51 received 25 bytes:
>efax: 15:51  ff c0 02 1c 9c ec ec 2c 1c 1c ec cc 9c 04 04 04
>efax: 15:51  04 04 04 04 04 04 04 a3 4d
>efax: 15:51 received CSI - answering ID
>efax: 15:51 remote ID ->           number
>efax: 15:51 command  "+FRH=3"
>efax: 15:51 waiting 35.0 s
>efax: 15:51 .835 [<CR><LF>CONNECT<CR><LF>]
>efax: 15:51 response "CONNECT"
>efax: 15:52 waiting 2.0 s
>efax: 15:52 .159 [<CR><LF>OK<CR><LF>]
>efax: 15:52 response "OK"
>efax: 15:52 received 11 bytes:
>efax: 15:52  ff c8 01 00 72 1d 21 01 88 2f 39
>efax: 15:52 received DIS - answering capabilities
>efax: 15:52 remote has no document(s) to send, and can receive
>efax: 15:52 local   196lpi 14.4kbps 8.5"/215mm  any   1D    -     -  0ms
>efax: 15:52 remote  196lpi  9600bps 8.5"/215mm  any   1D ECM-64   -
>20/10ms
>efax: 15:52 session 196lpi  9600bps 8.5"/215mm  any   1D    -     -
>10ms
>efax: 15:52 command  "+FTH=3"
>efax: 15:52 waiting 3.1 s
>efax: 15:52 .963 [<CR><LF>CONNECT<CR><LF>]
>efax: 15:52 response "CONNECT"
>efax: 15:52 sent 23 bytes:
>efax: 15:52  ff c0 c2 4c ec ac 1c 04 8c cc 2c 04 ec cc 9c 04
>efax: 15:52  8c 04 04 04 04 04 04
>efax: 15:52 sent TSI - caller ID
>efax: 15:52 waiting 13.6 s
>efax: 15:52 .965 [<CR><LF>CONNECT<CR><LF>]
>efax: 15:52 response "CONNECT"
>efax: 15:52 sent 6 bytes: ff c8 c1 00 62 14
>efax: 15:52 sent DCS - session format
>efax: 15:52 waiting 13.6 s
>efax: 15:54 .063 [<CR><LF>OK<CR><LF>]
>efax: 15:54 response "OK"
>efax: 15:54 command  "+FTS=8"
>efax: 15:54 waiting 3.0 s
>efax: 15:54 .125 [<CR><LF>OK<CR><LF>]
>efax: 15:54 response "OK"
>efax: 15:54 command  "+FTM=96"
>efax: 15:54 waiting 3.1 s
>efax: 15:54 .129 [<CR><LF>CONNECT<CR><LF>]
>efax: 15:54 response "CONNECT"
>efax: 15:54 waiting 30.0 s
>efax: 16:00 .843 [<CR><LF>ERROR<CR><LF>]
>efax: 16:00 response "ERROR"
>efax: 16:00 Error: wrong response after waiting 
>efax: 16:00 sent TCF - channel check of 1800 bytes
>efax: 16:00 local   196lpi 14.4kbps 8.5"/215mm  any   1D    -     -  0ms
>efax: 16:00 remote  196lpi  9600bps 8.5"/215mm  any   1D ECM-64   -
>20/10ms
>efax: 16:00 session 196lpi  9600bps 8.5"/215mm  any   1D    -     -
>10ms
>efax: 16:00 command  "+FTS=8"
>efax: 16:00 waiting 3.0 s
>efax: 16:00 .905 [<CR><LF>OK<CR><LF>]
>efax: 16:00 response "OK"
>efax: 16:00 local   196lpi 14.4kbps 8.5"/215mm  any   1D    -     -  0ms
>efax: 16:00 remote  196lpi  9600bps 8.5"/215mm  any   1D ECM-64   -
>20/10ms
>efax: 16:00 session 196lpi  9600bps 8.5"/215mm  any   1D    -     -
>10ms
>efax: 16:00 command  "+FTS=8"
>efax: 16:00 waiting 3.0 s
>efax: 16:00 .966 [<CR><LF>OK<CR><LF>]
>efax: 16:00 response "OK"
>efax: 16:00 Error: no command/response from remote
>efax: 16:00 command  "+FTH=3"
>efax: 16:00 waiting 3.1 s
>efax: 16:01 .769 [<CR><LF>CONNECT<CR><LF>]
>efax: 16:01 response "CONNECT"
>efax: 16:01 sent 3 bytes: ff c8 5f
>efax: 16:01 sent DCN - disconnect
>efax: 16:01 waiting 13.6 s
>efax: 16:02 .089 [<CR><LF>OK<CR><LF>]
>efax: 16:02 response "OK"
>efax: 16:02 command  "H"
>efax: 16:02 waiting 5.0 s
>efax: 16:02 .814 [<CR><LF>OK<CR><LF>]
>efax: 16:02 response "OK"
>efax: 16:02 failed -> /tmp/0m2cox.001
>efax: 16:02 command  "Q0V1"
>efax: 16:02 waiting 2.0 s
>efax: 16:02 .915 [<CR><LF>OK<CR><LF>]
>efax: 16:02 response "OK"
>efax: 16:03 command  "Z"
>efax: 16:03 waiting 5.0 s
>efax: 16:03 .534 [<CR><LF>OK<CR><LF>]
>efax: 16:03 response "OK"
>efax: 16:03 read HDB pid 13648 [     13648<LF>]
>from /var/lock/LCK..ttyACM0 (our pid)
>efax: 16:03 removed lock file /var/lock/LCK..ttyACM0
>efax: 16:03 done, returning 3 (invalid modem response)
>
>

--- End Message ---

Prev by Date: Re: [efax-users] faxmodem not communicating
Next by Date: Re: [efax-users] faxmodem not communicating
Previous by thread: Re: [efax-users] faxmodem not communicating
Next by thread: Re: [efax-users] faxmodem not communicating
Index(es):
- Date
- Thread