[hylafax-users] Fax error sending from application

[David A Davidson]

Faxes are currently being sent today and working correctly.

We have an application on Sun Solaris Enterprise 450 which submits faxes
to a Linux box running Hylafax 4.3.0, Redhat EL 3.0. Saturday night our
application submitted about 1600 faxes, of which some 1400 didn't get
sent correctly. At this point I don't know why.

For all of the failed faxes in question, I am getting the following
error message in the log file.

Oct 2 11:23:47 mail HylaFAX[32725]: Can not access document file
"docq/cover4500.cover": No such file or directory
Oct 2 11:23:47 mail HylaFAX[32725]: sendq/q4500: line 64: Rejected
document in corrupt job request

In the sendq directory, the actual postscript file exists for the fax,
but no cover page exists. I created a generic fax cover postscript file
that I am going to use to send all of these failed faxes.

As a test, I copy the fax cover page to the sendq directory and called
it cover4501.cover. I chmod the file 640 and set the owner to uucp and
the group to 60002. When I do a faxstat -s I see the fax waiting to be
sent. However I can't use faxalter to force hylafax to send the fax or
even to change the faxes priority.

I also noticed that each fax in the sendq directory had a file named
cover4501;70 or cover4501;f0. Do I need to make these for each of the
failed faxes?

I would like to send these faxes by creating the generic fax coverpage.
Is there any documentation on handling this problem or what might have
caused the problem?

Regards,
David Davidson
Wright Printing


____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Aidan Van Dyk]

Post by David A Davidson
Faxes are currently being sent today and working correctly.
We have an application on Sun Solaris Enterprise 450 which submits faxes
to a Linux box running Hylafax 4.3.0, Redhat EL 3.0. Saturday night our
application submitted about 1600 faxes, of which some 1400 didn't get
sent correctly. At this point I don't know why.
For all of the failed faxes in question, I am getting the following
error message in the log file.
Oct 2 11:23:47 mail HylaFAX[32725]: Can not access document file
"docq/cover4500.cover": No such file or directory
Oct 2 11:23:47 mail HylaFAX[32725]: sendq/q4500: line 64: Rejected
document in corrupt job request

Did *all* jobs start failing at a particular time?

From what you describe below, it seems like all the jobs coverfiles have
disappeard? Can you show us one of the qfiles?

Post by David A Davidson
In the sendq directory, the actual postscript file exists for the fax,
but no cover page exists. I created a generic fax cover postscript file
that I am going to use to send all of these failed faxes.
As a test, I copy the fax cover page to the sendq directory and called
it cover4501.cover. I chmod the file 640 and set the owner to uucp and
the group to 60002. When I do a faxstat -s I see the fax waiting to be
sent. However I can't use faxalter to force hylafax to send the fax or
even to change the faxes priority.
I also noticed that each fax in the sendq directory had a file named
cover4501;70 or cover4501;f0. Do I need to make these for each of the
failed faxes?

I don't know what state the jobs are in. During usual processing, there
will be:
docq/coverXXXX.cover
docq/coverXXXX.cover.JOBID
docq/coverXXXX.cover;ab

The 1st to are hardlinks to the same file. HylaFAX does most of it's
document accounting by looking at the number links to an inode.

The ";ab" format are the "rendered" documents, in the outgoing TIFF
format requried for sending. faxq prepares these as it starts sending a
job.

Post by David A Davidson
I would like to send these faxes by creating the generic fax coverpage.
Is there any documentation on handling this problem or what might have
caused the problem?

The easiest way is probably to "copy" the documents you want to send
out and combine them with some perl/shell to just resubmit them as new
jobs. Just faxrm the current ones before submitting your new batch (but
after copying your documents out).

It should be possible to "fix" the problem only using the client-server
protocol, but without knowing exactly what state the jobs are all in and
what files are around, I can't tell you exactly what you would need to
do.

a.

[David A Davidson]

Here is the copy of a qfile below. Phone and email address blanked out.
As a test, I created a cover4501.cover. Hylafax finally tried to send
the fax but it again removed the cover4501.cover file and complained
about the file being corrupt.

Oct 2 13:42:45 mail HylaFAX[3254]: Can not access document file
"docq/cover4501.cover": No such file or directory
Oct 2 13:42:45 mail HylaFAX[3254]: sendq/q4501: line 64: Rejected
document in corrupt job request


tts:1159677584
killtime:1160887124
retrytime:0
state:5
npages:0
totpages:0
ntries:0
ndials:0
totdials:0
maxdials:12
tottries:0
maxtries:3
pagewidth:215
resolution:98
pagelength:279
priority:200
schedpri:200
minbr:0
desiredbr:13
desiredst:0
desiredec:2
desireddf:3
desiredtl:0
useccover:1
usexvres:0
external:
number:
mailaddr:
sender:tracyu
jobid:4501
jobtag:00269996
pagehandling:
modem:any
faxnumber:
tsi:
receiver:
company:
location:
voice:
fromcompany:
fromlocation:
fromvoice:
regarding:
comments:
cover:
client:192.168.30.1
owner:tdu
groupid:4501
signalrate:
dataformat:
jobtype:facsimile
tagline:
subaddr:
passwd:
doneop:default
commid:
csi:
nsf:
status:
returned:0
notify:none
pagechop:default
chopthreshold:3
postscript:0::docq/cover4501.cover
postscript:0::docq/doc8991.ps.4501

Post by Aidan Van Dyk

Post by David A Davidson
Faxes are currently being sent today and working correctly.
We have an application on Sun Solaris Enterprise 450 which submits faxes
to a Linux box running Hylafax 4.3.0, Redhat EL 3.0. Saturday night our
application submitted about 1600 faxes, of which some 1400 didn't get
sent correctly. At this point I don't know why.
For all of the failed faxes in question, I am getting the following
error message in the log file.
Oct 2 11:23:47 mail HylaFAX[32725]: Can not access document file
"docq/cover4500.cover": No such file or directory
Oct 2 11:23:47 mail HylaFAX[32725]: sendq/q4500: line 64: Rejected
document in corrupt job request

Did *all* jobs start failing at a particular time?
From what you describe below, it seems like all the jobs coverfiles have
disappeard? Can you show us one of the qfiles?

Post by David A Davidson
In the sendq directory, the actual postscript file exists for the fax,
but no cover page exists. I created a generic fax cover postscript file
that I am going to use to send all of these failed faxes.
As a test, I copy the fax cover page to the sendq directory and called
it cover4501.cover. I chmod the file 640 and set the owner to uucp and
the group to 60002. When I do a faxstat -s I see the fax waiting to be
sent. However I can't use faxalter to force hylafax to send the fax or
even to change the faxes priority.
I also noticed that each fax in the sendq directory had a file named
cover4501;70 or cover4501;f0. Do I need to make these for each of the
failed faxes?

I don't know what state the jobs are in. During usual processing, there
docq/coverXXXX.cover
docq/coverXXXX.cover.JOBID
docq/coverXXXX.cover;ab
The 1st to are hardlinks to the same file. HylaFAX does most of it's
document accounting by looking at the number links to an inode.
The ";ab" format are the "rendered" documents, in the outgoing TIFF
format requried for sending. faxq prepares these as it starts sending a
job.

Post by David A Davidson
I would like to send these faxes by creating the generic fax coverpage.
Is there any documentation on handling this problem or what might have
caused the problem?

The easiest way is probably to "copy" the documents you want to send
out and combine them with some perl/shell to just resubmit them as new
jobs. Just faxrm the current ones before submitting your new batch (but
after copying your documents out).
It should be possible to "fix" the problem only using the client-server
protocol, but without knowing exactly what state the jobs are all in and
what files are around, I can't tell you exactly what you would need to
do.
a.

____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Lee Howard]

Post by David A Davidson
Oct 2 11:23:47 mail HylaFAX[32725]: Can not access document file
"docq/cover4500.cover": No such file or directory
Oct 2 11:23:47 mail HylaFAX[32725]: sendq/q4500: line 64: Rejected
document in corrupt job request

It was a faxqclean bug that robbed you of your coverpages and then made
faxq flip out on the fax job (due to the missing cover file).

The attached patch should fix it for you.

Thanks,

Lee.

[David A Davidson]

I installed hylafax from an rpm. So I won't be able to recompile from
source. Has there been a new release of hylafax recently. The rpm I have
installed is hylafax-4.3.0.1-1. It looks like there is a new rpm, would
you know if it contains this fix?

Regards,
David Davidson

Post by Lee Howard

Post by David A Davidson
Oct 2 11:23:47 mail HylaFAX[32725]: Can not access document file
"docq/cover4500.cover": No such file or directory
Oct 2 11:23:47 mail HylaFAX[32725]: sendq/q4500: line 64: Rejected
document in corrupt job request

It was a faxqclean bug that robbed you of your coverpages and then made
faxq flip out on the fax job (due to the missing cover file).
The attached patch should fix it for you.
Thanks,
Lee.
------------------------------------------------------------------------
--- hylafax.orig/faxd/faxQCleanApp.c++ 2006-09-29 16:31:44.000000000 -0700
+++ hylafax/faxd/faxQCleanApp.c++ 2006-10-02 11:02:07.666463472 -0700
@@ -353,7 +353,7 @@
* at the front; look to see if the job still
* exists in the sendq.
*/
- u_int prefix = docDir.length()+1+3;
+ u_int prefix = docDir.length()+1+5;
fxStr qfile = qFilePrefix | file.extract(prefix, l-1-prefix);
if (Sys::stat(qfile, sb) == 0) {
if (trace)

____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Lee Howard]

Post by David A Davidson
I installed hylafax from an rpm. So I won't be able to recompile from
source. Has there been a new release of hylafax recently. The rpm I have
installed is hylafax-4.3.0.1-1. It looks like there is a new rpm, would
you know if it contains this fix?

It is in HylaFAX+ 4.3.0.12. You can download the RPM now from
http://hylafax.sourceforge.net/

Thanks,

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-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[David A Davidson]

Related to my earlier issue of coverpages missing from the fax jobs. Its
probably due to the fax that we sent our faxes out 09/30/2006 at 23:59
because we send customer statements out at the end of the month. As per
Mr. Howards statement that faxclean removed the coverpages and now faxq
is "flipped" out.

Anyways my plan is to merge the qfiles in sendq directory with the
docq directory. I've written a small kornshell script to grep for phone
number, email address, groupid and postscript file name. The script will
run faxcover to generate a new coverpage and resumbit the postscript fax
file using sendfax. And since I have the old fax queue id, I could also
issue the faxrm command using the groupid from the original qfile.

The problem is that I can no longer use faxrm to remove these files. I
get an error that I can't delete job because of a corrupt file...
"500 Cannot kill job 4501; invalid or corrupted job description file."

So I created a new "cover4501.cover", chmod 640 and chown uucp and chgrp
60002, so hylafax doesn't think its corrupt. but then I get the
message... "504 Cannot kill job: Operation not permitted."

Is there anyway to cleanly remove these old files from the send queue?

Regards,
David Davidson

____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Lee Howard]

Post by David A Davidson
The problem is that I can no longer use faxrm to remove these files. I
get an error that I can't delete job because of a corrupt file...
"500 Cannot kill job 4501; invalid or corrupted job description file."
So I created a new "cover4501.cover", chmod 640 and chown uucp and chgrp
60002, so hylafax doesn't think its corrupt. but then I get the
message... "504 Cannot kill job: Operation not permitted."
Is there anyway to cleanly remove these old files from the send queue?

If there is anything worth saving there in your doneq or sendq files
back it up, and then restart faxq. Then you should be fine. In my
testing for the fix I noticed that faxq refused to delete the jobs
because they were corrupted... and that messed stuff up in faxq's
arrays, etc.

So worst-case scenario, just remove the files from docq and from sendq
and then restart faxq.

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-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[David A Davidson]

Thanks, I already have the files copied to another directory away from
the hylafax sendq and docq directories. We will clean out the files
later this evening.

Thanks for your help.
Regards,
David Davidson

Post by Lee Howard

Post by David A Davidson
The problem is that I can no longer use faxrm to remove these files. I
get an error that I can't delete job because of a corrupt file...
"500 Cannot kill job 4501; invalid or corrupted job description file."
So I created a new "cover4501.cover", chmod 640 and chown uucp and chgrp
60002, so hylafax doesn't think its corrupt. but then I get the
message... "504 Cannot kill job: Operation not permitted."
Is there anyway to cleanly remove these old files from the send queue?

If there is anything worth saving there in your doneq or sendq files
back it up, and then restart faxq. Then you should be fine. In my
testing for the fix I noticed that faxq refused to delete the jobs
because they were corrupted... and that messed stuff up in faxq's
arrays, etc.
So worst-case scenario, just remove the files from docq and from sendq
and then restart faxq.
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi

____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Todd Patton]

I just bought a new modem to use with hylafax - an external Trendnet
TFM-560x. Trendnet claims this works with Linux. I installed the modem
but using command probemodem ttyS0, I can't seem to communicate with the
modem. The lights light up when probing speeds but it seems like
probemodem doesn't get a response. This goes for the same faxaddmodem.

Using the -s option reports a stndin > standout error that I don't
understand.

This modem is also suppose to accept hayes standard modem commands. Does
someone have an example config file for this modem that I can try? Could
anything be blocking communications from ttyS0?

Thanks for the responses. - This faxserver is becoming quite a chore!

/Todd



____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Lee Howard]

Post by Todd Patton
I just bought a new modem to use with hylafax - an external Trendnet
TFM-560x. Trendnet claims this works with Linux. I installed the modem
but using command probemodem ttyS0, I can't seem to communicate with the
modem.

I almost always first test the modem with minicom before running
faxaddmodem. Have you tried to use the modem with minicom?

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-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Todd Patton]

Good suggestion.

Installed minicom but cannot dial - It reports that I am already online
and I can't seem to hangup.

Secondly, I got a crap load of messages to faxmaster
subject modem on ttyS0 seems to be wedged

- repeated attempts to initialize the modem have failed

Makes sense since the communication lights seem to be stuck on.

Post by Lee Howard

Post by Todd Patton
I just bought a new modem to use with hylafax - an external Trendnet
TFM-560x. Trendnet claims this works with Linux. I installed the modem
but using command probemodem ttyS0, I can't seem to communicate with the
modem.

I almost always first test the modem with minicom before running
faxaddmodem. Have you tried to use the modem with minicom?
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-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Lee Howard]

Post by Todd Patton
Good suggestion.
Installed minicom but cannot dial - It reports that I am already online
and I can't seem to hangup.
Secondly, I got a crap load of messages to faxmaster
subject modem on ttyS0 seems to be wedged
- repeated attempts to initialize the modem have failed
Makes sense since the communication lights seem to be stuck on.

Stop faxgetty from running. Then try minicom again. Check to make sure
you don't have any other processes using the modem.

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-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Todd Patton]

Post by Lee Howard

Post by Todd Patton
Good suggestion.
Installed minicom but cannot dial - It reports that I am already online
and I can't seem to hangup.
Secondly, I got a crap load of messages to faxmaster
subject modem on ttyS0 seems to be wedged
- repeated attempts to initialize the modem have failed
Makes sense since the communication lights seem to be stuck on.

Stop faxgetty from running. Then try minicom again. Check to make sure
you don't have any other processes using the modem.
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi

Thanks again for your help Lee - I must send you a starbucks card soon.
-
minicom seems to have some kind of <open ready> signal because it shows
the modem is online. However, nothing goes through -h+++ returns
nothing, same with with AT -- gets no response.

ON the modem, the CS,RS,SD,TR,MR lights stay lit constantly. Correct me
if I am wrong but I doubt it should be that way without and action. I
guess I will have to try it on a Windoze machine and verify that this
new modem actually does work.

/todd









____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Lee Howard]

Post by Todd Patton
minicom seems to have some kind of <open ready> signal because it shows
the modem is online. However, nothing goes through -h+++ returns
nothing, same with with AT -- gets no response.
ON the modem, the CS,RS,SD,TR,MR lights stay lit constantly. Correct me
if I am wrong but I doubt it should be that way without and action. I
guess I will have to try it on a Windoze machine and verify that this
new modem actually does work.

Is this a PCI modem? If so what does 'lspci' say?

What does 'dmesg' say?

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-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Todd Patton]

Post by Lee Howard

Post by Todd Patton
minicom seems to have some kind of <open ready> signal because it shows
the modem is online. However, nothing goes through -h+++ returns
nothing, same with with AT -- gets no response.
ON the modem, the CS,RS,SD,TR,MR lights stay lit constantly. Correct me
if I am wrong but I doubt it should be that way without and action. I
guess I will have to try it on a Windoze machine and verify that this
new modem actually does work.

Is this a PCI modem? If so what does 'lspci' say?
What does 'dmesg' say?
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi

After 3 more hours of diagnostics, I determined that the power supply
was faulty. It provided enough current to light the lights but not
enough to actually control the modem. So I replaced the power supply and
wham it probes, answers, and sends. -

Then back to the original problem - the distinctive ring - losing hair
fast -
I determined that the modem will not send a RING1 and RING2, however
while I was RTFM, I tried to understand the ring cadance but I am not
certain I understand the format correctly. I have tried it several
different ways but it won't answer any rings with it set. Do I need to
turn on getty arguments?


CountryCode: 1
AreaCode: 813
FAXNumber: ""
LongDistancePrefix: 1
InternationalPrefix: 011
DialStringRules: etc/dialrules
ServerTracing: 12
SessionTracing: 1
RecvFileMode: 0600
LogFileMode: 0600
DeviceMode: 0600
RingsBeforeAnswer: 0
SpeakerVolume: Medium
GettyArgs: ""
DistictiveRings: V-20,F-4-8-4
DRingOn: DRON=F-4-8-4
DRingOff: DROF=V-20

#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType: Class1 # use this to supply a hint
#ModemRate: 19200 # rate for DCE-DTE communication
#ModemFlowControl: xonxoff # XON/XOFF flow control assumed
#
#ModemSetupDTRCmd: AT&D2 # setup so DTR drop resets modem
#ModemSetupDCDCmd: AT&C1 # setup so DCD follows carrier
#GettyArgs: "-h %l dx_%s" # modem must auto-detect
fax/data
#
# We can append the "@" symbol to the dial string so that
# the modem will wait 5 seconds before attempting to connect
# and return result codes that distinguish between no carrier
# and no answer. This makes it possible to avoid problems with
# repeatedly dialing a number that doesn't have a fax machine
# (kudos to Stuart Lynne for this trick.)
#
# NB: If you need to prefix phone numbers to get through a PBX,
# put it in the ModemDialCmd; e.g. "DT9%s@".
#
#ModemDialCmd: ATDT%s # T for tone dialing
#
# Other possible configuration stuff. The default strings are
# shown below. Only those that are different from the defaults
# need to be included in the configuration file.
#
#ModemResetCmds: "" # stuff to do when modem
is reset
#ModemAnswerCmd: ATA # use this to answer
phone
#ModemNoFlowCmd: AT&K # disable flow control
cmd
#ModemHardFlowCmd: AT&K3 # hardware flow control cmd
#ModemSoftFlowCmd: AT&K4 # software flow control cmd
#ModemNoAutoAnswerCmd: ATS0=0 # disable auto-answer
#
# Set modem speaker volume commands: OFF QUIET LOW MEDIUM HIGH.
# Note that we both turn the speaker on/off and set volume.
#
#ModemSetVolumeCmd: "ATM0 ATL0M1 ATL1M1 ATL2M1 ATL3M1"
#ModemEchoOffCmd: ATE0 # disable command echo
#ModemVerboseResultsCmd: ATV1 # enable verbose command
results#ModemResultCodesCmd: ATQ0 # enable result codes
#ModemOnHookCmd: ATH0 # place phone on hook (hangup)
#ModemSoftResetCmd: ATZ # do soft reset of modem
#ModemSoftResetCmdDelay: 3000 # pause after soft reset
#ModemWaitTimeCmd: ATS7=60 # wait 60 seconds for carrier
#ModemCommaPauseTimeCmd: ATS8=2 # comma pause time is 2 seconds
#ModemRecvFillOrder: LSB2MSB # bit order of received
facsimile
#ModemSendFillOrder: LSB2MSB # bit order modem expects for
transmit
#
Class1Cmd: AT+FCLASS=1 # command to enter class 1
Class1PPMWaitCmd: AT+FTS=7 # command to stop and wait
before PPM
Class1TCFWaitCmd: AT+FTS=7 # command to stop and wait
before TCF
Class1EOPWaitCmd: AT+FTS=9 # command to stop and wait
before EOP
Class1SendMsgDelay: 200 # 75ms delay after training
Class1SwitchingCmd: AT+FRS=7 # silence between HDLC recv and
trans
Class1TrainingRecovery: 1500 # 1.5sec delay after training
failure
Class1RecvAbortOK: 200 # wait 200ms for abort response
Class1FrameOverhead: 4 # 4 byte overhead in recvd HDLC
frames
Class1RecvIdentTimer: 40000 # 35+5secs waiting for ident
frames
Class1TCFMaxNonZero: 10 # max 10% of data may be
non-zero
Class1TCFMinRun: 1000 # min run is 2/3rds of TCF
duration







____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Michael Stowe]

I'd think you'd want to fire up minicom, dial the modem, and see what the
modem is actually reporting -- and then set up a ring cadence string to
match.

Post by Todd Patton
Then back to the original problem - the distinctive ring - losing hair
fast -
I determined that the modem will not send a RING1 and RING2, however
while I was RTFM, I tried to understand the ring cadance but I am not
certain I understand the format correctly. I have tried it several
different ways but it won't answer any rings with it set. Do I need to
turn on getty arguments?

____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Todd Patton]

I can't seem to get minicom to report anything other than OK - perhaps I
don't have it set right. I cranked up the server logging but I am seeing
a cadance of 0,0,0,0,0,0

I wasn't certain on the config file parameters DRON= and DROFF= , along
with the DistinctiveRing V-20,F-8-4-8

When the fax number rings a get 2 short rings instead of 1 long ring.

What is the proper way to have the modem communications displayed in
minicom? I turned on "Echo" but I don't see anything unless it actually
picks up the line.




4) Voice Mercury DP2SH mode-ii SERIAL]
Oct 4 21:55:18 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:55:18 earth FaxGetty[2186]: <-- [9:AT+FTM=?\r]
Oct 4 21:55:18 earth FaxGetty[2186]: -->
[41:3,24,48,72,73,74,96,97,98,121,122, 145,146]
Oct 4 21:55:18 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:55:18 earth FaxGetty[2186]: <-- [9:AT+FRM=?\r]
Oct 4 21:55:18 earth FaxGetty[2186]: -->
[41:3,24,48,72,73,74,96,97,98,121,122, 145,146]
Oct 4 21:55:18 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:55:18 earth FaxGetty[2186]: <-- [7:ATL2M1\r]
Oct 4 21:55:18 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:55:18 earth FaxGetty[2186]: MODEM input buffering disabled
Oct 4 21:55:28 earth FaxGetty[2186]: --> [4:RING]
Oct 4 21:55:28 earth FaxGetty[2186]: WFR: received cadence = 0, 0, 0,
0, 0
Oct 4 21:55:34 earth FaxGetty[2186]: --> [4:RING]
Oct 4 21:55:34 earth FaxGetty[2186]: WFR: received cadence = 0, 0, 0,
0, 0
Oct 4 21:55:40 earth FaxGetty[2186]: --> [4:RING]
Oct 4 21:55:40 earth FaxGetty[2186]: WFR: received cadence = 0, 0, 0,
0, 0
Oct 4 21:55:46 earth FaxGetty[2186]: --> [4:RING]
Oct 4 21:55:46 earth FaxGetty[2186]: WFR: received cadence = 0, 0, 0,
0, 0
Oct 4 21:55:52 earth FaxGetty[2186]: --> [4:RING]
Oct 4 21:55:52 earth FaxGetty[2186]: WFR: received cadence = 0, 0, 0,
0, 0
Oct 4 21:55:58 earth FaxGetty[2186]: --> [4:RING]
Oct 4 21:55:58 earth FaxGetty[2186]: WFR: received cadence = 0, 0, 0,
0, 0
Oct 4 21:56:04 earth FaxGetty[2186]: --> [4:RING]
Oct 4 21:56:04 earth FaxGetty[2186]: WFR: received cadence = 0, 0, 0,
0, 0
Oct 4 21:56:14 earth FaxGetty[2186]: <-- [5:ATH0\r]
Oct 4 21:56:14 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:14 earth FaxGetty[2186]: MODEM set DTR OFF
Oct 4 21:56:15 earth FaxGetty[2186]: MODEM set DTR OFF
Oct 4 21:56:15 earth FaxGetty[2186]: MODEM set DTR ON
Oct 4 21:56:19 earth FaxGetty[2186]: MODEM set baud rate: 19200 baud,
input flo w XON/XOFF, output flow XON/XOFF
Oct 4 21:56:19 earth FaxGetty[2186]: MODEM flush i/o
Oct 4 21:56:19 earth FaxGetty[2186]: <-- [4:ATZ\r]
Oct 4 21:56:19 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: MODEM flush i/o
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [7:ATS0=0\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [6:ATS0=0]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [5:ATE0\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [4:ATE0]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [5:ATV1\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [5:ATQ0\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [7:ATS8=2\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [8:ATS7=60\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [12:AT+FCLASS=?\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [5:0,1,8]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [12:AT+FCLASS=1\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [2:OK]
Oct 4 21:56:22 earth FaxGetty[2186]: <-- [5:ATI3\r]
Oct 4 21:56:22 earth FaxGetty[2186]: --> [71:Agere OCM V.92 Ver2.7a
(Jun 14 200

Post by Michael Stowe
I'd think you'd want to fire up minicom, dial the modem, and see what the
modem is actually reporting -- and then set up a ring cadence string to
match.

Post by Todd Patton
Then back to the original problem - the distinctive ring - losing hair
fast -
I determined that the modem will not send a RING1 and RING2, however
while I was RTFM, I tried to understand the ring cadance but I am not
certain I understand the format correctly. I have tried it several
different ways but it won't answer any rings with it set. Do I need to
turn on getty arguments?

____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi

____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Michael Stowe]

Post by Todd Patton
I can't seem to get minicom to report anything other than OK - perhaps I
don't have it set right. I cranked up the server logging but I am seeing
a cadance of 0,0,0,0,0,0

My high-level advice is to stop leaping to hylafax to either diagnose or
fix your basic modem issues.

If "ring" doesn't show up in minicom when you dial the modem, hylafax
won't see anything, either. Note that in your modem setup, hylafax
usually has a modem initialization string -- issue that manually in
minicom so you see the same thing.

Post by Todd Patton
I wasn't certain on the config file parameters DRON= and DROFF= , along
with the DistinctiveRing V-20,F-8-4-8

It's so that you can tell hylafax exactly what your modem produces when
dialed -- which, as above, you're in the dark on -- and it may not produce
anything useful until you tweak its initialization string.

So, in minicom, when you dial your phone, you should see something like this:
RING
DROF=40
DRON=8
DROF=4
DRON=8
RING

The config parameters DRON= and DROFF= are to tell hylafax exactly what
your modem produces. You can see this in minicom (or, if not, go back to
step 1)

Post by Todd Patton
When the fax number rings a get 2 short rings instead of 1 long ring.

Yes, what you actually need is what your modem reports.

Post by Todd Patton
What is the proper way to have the modem communications displayed in
minicom? I turned on "Echo" but I don't see anything unless it actually
picks up the line.

Use the same initialization string you issue to hylafax. If this doesn't
work, consult your modem manual for a better initialization string.



____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*

[Todd Patton]

Post by Lee Howard

Post by Todd Patton
I just bought a new modem to use with hylafax - an external Trendnet
TFM-560x. Trendnet claims this works with Linux. I installed the modem
but using command probemodem ttyS0, I can't seem to communicate with the
modem.

I almost always first test the modem with minicom before running
faxaddmodem. Have you tried to use the modem with minicom?
Lee.

Good suggestion. Please Excuse the top-posting mess.

When using probemodem -s 19200 ttyS0 I get

/bin/stty: standard input: Input/output error

/usr/sbin/probemodem: line 226: kill: 14150 - no such process

/usr/sbin/probemodem: line 230 /tmp/.probemodem.F14133/probemodem14131:
no such file or directory.

/usr/sbin/probemodem: line 290 /tmp/.probemodem.F14133/probemodem14131:
no such file or directory.

installed minicom but cannot dial - It reports that I am already online
and I can't seem to hangup.
Secondly, I got a crap load of messages to faxmaster
subject modem on ttyS0 seems to be wedged
- repeated attempts to initialize the modem have failed
Makes sense since the communication lights seem to be stuck on.

____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-***@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail ***@ifax.com.*