HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
[hylafax-users] Two more, please. was: Re: Three Configuration Questions . . .
Thank you Matt. Two more questions to clarify.
I have now:
1) edited etc/config.ttyS1, changing:
RingsBeforeAnswer: 30 to
RingsBeforeAnswer: 0
2) checked to ensure that metamail is installed (it is),
added two lines to bin/faxrcvd and now must invite someone
to send me a test fax to ensure that these changes are working;
and
3) deleted the line from /etc/hosts.hfaxd.
As I got in this morning, a broadcast job of over one hundred numbers
was just about to complete. There was no evidence that it had used
ttyS1 at all. Everything ran on ttyS0 from what I have seen -- the
expensive phone line.
Two more questions:
Question #4)
Where would I start looking to determine why a line that has an
etc/config.ttyS1 file and is properly cabled to a phone line has not
shared the work load in getting this fax out?
Since first asking this question this morning (not sure why that
didn't hit the lists), I reran faxaddmodem and then ran faxmodem, as
well. But additional tests have shown on-going problems.
Question #5)
What is the proper syntax for the -h parameter for sendfax:
-h "ttyS1@localhost"?
After some experimentation, it seems to accept this syntax.
I'm using two identical Multi-Tech MT-2834-ZDXb's which can't seem to
speak with each other. I have now had three successful tests of ttyS0
receiving faxes from outside the office and about 90 (of perhaps 110 or
so) successful attempts to send a fax with ttyS0 (the errors not being
obviously attributable to the modem, though). I guess I should next try
to send something to some other machine with ttyS1.
But I'm still getting errors as outlined below.
-------------------------------------------------
Date: Fri, 28 May 2004 18:13:05 -0400
From: uucp <uucp@xxxxxxxxxxxxxxxxxxxx>
To: hesco@xxxxxxxxxx
Subject: facsimile job 220 to 1-404-806-0584 failed
From: uucp <uucp@xxxxxxxxxxxxxxxxxxxx>
To: hesco@xxxxxxxxxx
Subject: facsimile job 220 to 1-404-806-0584 failed
Date: Fri, 28 May 2004 18:13:05 -0400
Your facsimile job to 1-404-806-0584 failed because:
DCS sent 3 times without response; Giving up after 3 attempts to
send same page
---- Transcript of session follows ----
May 28 18:09:04.43: [22368]: SESSION BEGIN 00000223 14048060584
May 28 18:09:04.43: [22368]: HylaFAX (tm) Version 4.1.8
May 28 18:09:04.43: [22368]: SEND FAX: JOB 220 DEST 1-404-806-0584
COMMID 00000223 DEVICE '/dev/ttyS1'
May 28 18:09:14.02: [22368]: STATE CHANGE: RUNNING -> SENDING
May 28 18:13:05.24: [22368]: SEND: DCS sent 3 times without response;
Giving up after 3 attempts to send same page "docq/doc10.ps;30", dirnum
0
May 28 18:13:05.50: [22368]: STATE CHANGE: SENDING -> MODEMWAIT (timeout
5)
May 28 18:13:05.50: [22368]: SESSION END
---- Unsent job status ----
Destination: 1-404-806-0584
JobID: 220
GroupID: 220
Sender: hesco
Mailaddr: hesco@xxxxxxxxxx
CommID: 00000223
Modem: ttyS1
Submitted From: localhost
Page Width: 215 (mm)
Page Length: 279 (mm)
Resolution: 98 (lpi)
Status: DCS sent 3 times without response; Giving up after 3
attempts to send same page
Dialogs: 3 (exchanges with remote device)
Dials: 0 (consecutive failed calls to destination)
Calls: 3 (total phone calls placed)
Pages: 0 (pages transmitted)
TotPages: 2 (total pages to transmit)
Attempts: 3 (attempts to send current page)
Dirnum: 0 (directory of next page to send)
---- Documents submitted for transmission ----
The following documents were submitted for transmission and are
available on the server for reuse until they are automatically
purged when this job is removed. Documents may also be manually
removed using the faxrm command; consult faxrm(1) for information.
Filename Size Type
docq/doc10.ps 0 PostScript
--------------------------------
Any and all ideas are appreciated.
-- Hugh Esco
On Fri, 28 May 2004 11:01:01 +0100
Matt <mathfretwell@xxxxxxxxxxxxxxxx> wrote:
> > Question #1)
> > How do I accomplish this modem-by-modem configuration? Should I use
> > `faxstate -s down ttyS0` to avoid using the costly phone line, and
> > then`faxstate -s ready ttyS0` when the job is complete? If I do
> > this, does that disable it from being able to answer an incoming
> > fax? Is this a toggle I have to manually switch every time. The
> > perl script builds the job and hands it off to the hylafax server.
> > If I switch the faxstate back to ready as a part of the perl script,
> > it won't affect the jobs when the server starts faxing the job out.
> > How about making sure that the modem on ttyS1 never answers the
> > incoming voice calls. What does that take?
> >
>
> RingsBeforeAnswer: 0 in appropriate modem config file will disable
> reception. sendfax option (-h [modem@]host[:port]) for specific modem
> for outgoing.
>
> >
> > Question #2)
> > How would I accomplish this? Will adding this line to
> > etc/FaxDispatch handle the email part?
>
> SENDTO=hesco@xxxxxxxxxx;
> FILETYPE=pdf; # all faxes as .pdf'
>
> Metamail has to be installed for pdf emails.
>
> > Where in the faxrcvd script would I add the print command? Do I
> > need to frame that print command as a pipe that converts the
> > incoming tiff to ps to pdf to get it prepared for the printer?
> >
>
> Last line in faxrcvd, something along the lines of:
> /usr/local/bin/tiff2ps -a -h11.30 -w7.95 -H11.80 -L0.5 $* | lpr
>
> >
> > Question #3)
> > Can I just delete the extra line with the password-less user in
> > etc/hosts.hfaxd without corrupting the installation, somehow?
> >
>
> Yes.
> Matt
--
+---------------------------------------------
| Hugh Esco, <hesco@xxxxxxxxxx> 404-806-0480
| Political Coordinator, Georgia Green Party
| Post Office Box 5332; Atlanta GA 31107
| http://www.greens.org/georgia/
+---------------------------------------------
____________________ 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@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*