RE: Help getting efax to receive?
1. As a troubleshooting measure you might try hylafax instead
2. I've had horrible experience with USR modems wrt faxing. The only
good fax modems I've found are the more expensive multitech models
(~$300) but they work very reliably and never screw up.
> -----Original Message-----
> From: Kevin Beauchamp [SMTP:Kevin.Beauchamp@ualberta.ca]
> Sent: Tuesday, November 20, 2001 10:48 AM
> To: Debian Users mailing list
> Subject: Help getting efax to receive?
>
> Hello:
>
> I'm not sure if this is the right forum for this type of question. If
> not,
> I apologize.
>
> I'm just starting with Debian and want to use it to run a fax and
> print
> service in our location on a P90 machine with Debian 2.2r3
> loaded. I've loaded efax 0.9-4 from the Debian web site (I couldn't
> find it on the CDs I have) and configured it to run and attach to
> /dev/ttyS1. I can get efax to send faxes and print TIFF files, but
> not receive faxes.
>
> I've tried two modems (USR Sportster, USR Courier)
> and have gotten slightly different results. In both cases,
> efax will answer the incoming call, and will successfully
> retrieve the originating fax's ID and phone number, but
> the session fails when it tries to receive the document.
>
> Here's a snippet of a session log with the Sportster (Type 1 fax):
>
> efax: 23:00 received DCS - session format
> efax: 23:00 session 98lpi 9600bps 8.5"/215mm any 1D - -
> 0ms
> efax: 23:00 command "+FTS=1"
> efax: 23:00 waiting 3.0 s
> efax: 23:00 .798 [<CR><LF>OK<CR><LF>]
> efax: 23:00 response "OK"
> efax: 23:00 command "+FRM=96"
> efax: 23:00 waiting 6.0 s
> efax: 23:01 .098 [<CR><LF>CONNECT<CR><LF>]
> efax: 23:01 response "CONNECT"
> efax: 23:01 waiting 2.0 s
> efax: 23:01 .148 [<CR><LF>NO CARRIER<CR><LF>]
> efax: 23:01 response "NO CARRIER"
> efax: 23:01 received TCF - channel check (not OK: run of 0 in 57)
>
> And here's a piece of the log using the Courier (Type 2 fax):
>
> efax: 11:25 session 98lpi 9600bps 8.5"/215mm any 1D - -
> 0ms
> efax: 11:25 command "+FDR"
> efax: 11:25 waiting 60.0 s
> efax: 11:27 .858 [<CR><LF>+FCS:0,3,0,2,0,0,0,0<CR><LF>]
> efax: 11:29 .598 [<CR><LF>CONNECT<CR><LF>]
> efax: 11:29 response "CONNECT"
> efax: 11:29 session 98lpi 9600bps 8.5"/215mm any 1D - -
> 0ms
>
> [- snip: long error line -]
>
> efax: 12:09 Warning: 113 reception errors
> efax: 12:09 received 113 lines, 113 errors
>
> I've read the man page, checked out the script, visited the
> web page and sent email to efax's author. The author suggested
> trying manual receive (same results) and checking to make sure
> that all programs accessing the serial port use the same files
> for locking (I'm pretty sure efax is the only one accessing the
> serial port: mouse is the only other serial peripheral I know of,
> and its on its own PS/2-style port).
>
> At this point I'm fairly certain that efax is set up basically
> correctly,
> but I'm not sure about what else may or may not be trying to lock the
> serial port, or how I can test my modem(s) to make sure they're
> properly configured.
>
> One web page (the Fax-Server mini-HOWTO) mentions a fax test
> script, but trying the command it suggests isn't recognized on my
> system.
>
> Can anyone suggest a solution, or have any experience with
> this type of application?
>
> TIA
> Kevin B.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
Reply to: