Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Two more, please. was: Re: Three Configuration Questions . . .
On 2004.05.31 06:48 Matt wrote:
> 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?
Part of the problem is that this question is really vague.
You "start looking" by troubleshooting. You send a fax out of the
unused modem. Then you send a couple of test faxes to "all" modems,
you turn on debugging levels of logging and you look at the logs. That
kind of thing.
Your log below is the answer to that question. This modem has a
problem.
I, however, have no idea what could be causing this. This is a problem
better
answered by Lee.
Well, even I am not capable of reading stuff that's not there...
> But I'm still getting errors as outlined below.
> 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
This log contains relatively no information. You've got to set
SessionTracing to 0xFFF for us to see the necessary HDLC frame
communications.
Generally "DCS sent 3 times without response" means that there is some
kind of protocol failure. It will be more common with Class 2 modems,
I believe, than with Class 1.
Lee.
____________________ 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*