|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Transmission problems: info and questions
Ross Boylan wrote:
On Mon, May 29, 2006 at 01:20:53PM -0700, Lee Howard wrote:
Be careful not to confuse the faxalter -t meaning of "tries" with the
sendfax -t meaning of "tries".
Oh, my! The terminology and option names seem to invite confusion.
Yes they do, seemingly. It would seem that many of the various client
utilities and such that come with HylaFAX were not developed in
parallel, but rather in a method somewhat distinct from each other. I'm
not sure that bringing everything into agreement with each other is
warranted yet, however.
In faxalter -t "tries" refers to the
number of calls that will be placed. In sendfax -t "tries" refers to
the number of attempts that will be made to send the entire fax job
after a connection is made to the remote receiver. In sendfax -T
"maxdials" refers to faxalter -t "tries". So you're running into the
max number of protocol attempts (meaning as sendfax gives -t) as set
forth by the client program and not the max number of dials (meaning as
set by faxalter -t).
Is the rule that whenever either limit is exceeded the job is done?
Yes, both sendfax -t and -T are maximums. Thus when either is reached
the job is done.
Is there a way to reset the parameter set by sendfax -t after
submission?
It's possible to do, yes, but faxalter does not come with this
capability. (I could add the feature to hylafax+, but then you still
wouldn't get it, hrmm... dilemma.)
I think I understand what 1) is, and that faxalter -t or sendfax -T
determines this.
Yes, these control the maximum number of calls that will be placed.
But as for what you call "protocol attempts" and the man page refers
to as "attempts to send a particular page", I'm uncertain.
In order to prevent a T.30 incompatibility from racking up 12 phone
calls there is this "tries" maximum that involves how many times a call
connected with a remote fax device and properly initiated fax protocol,
but then broke down on a certain page. (This should almost never
happen, by the way, and the fact that it is occcuring is indicative of
there being more serious underlying issues.)
Class1SwitchingCmd: "<delay\0727>"
I put the previous line in config.ttyS0. Now I get
May 29 14:02:20.80: [26205]: MODEM TIMEOUT: reading line from modem
May 29 14:17:59.06: [28747]: --> [9:ERATH0ROR]
May 29 14:20:05.49: [28797]: -->
+[265:?^Yht???1?Y?b??^]&?r^VN;^]?0^W???^A^F??T0w^V????????,^^?3?5s^V???2oP^^???Y8r_?(?9>?c^A?G|Z???(:??c?<|,??+???,?v??y;?^B????b^V?p:^P^P^Rsg
+?P^V? {9?me??[4?^Tn? Y
+z??????X?h?a/CY?k?,f?,v????^Rl??%?*$??v?^E}??^O!(??}?^K^R?^N??pA????m]K?Y^X?2^Z^Dc??h?6?S^[^R??v???-?n??Q?^WT^P^P???m??t??^K??jA????^D??^]^V?
+'?]
May 29 14:20:05.97: [28797]: --> [9:ERROATH0R]
Argh!
Well, the config change didn't cause this. I'm not certain, either what
would cause "ERROATH0R" ... is there another process (another faxgetty,
maybe) toying with the same modem?
Do I need to restart
or bounce faxgetty as well (it's running from inittab)?
Technically no, not for sending. But you've got some weird stuff going
on there.
Did the characters get mangled in transmission (e.g., did \0727 start
out as something else on your end)?
No \0727 is correct. You can also write it:
Class1SwitchingCmd: "<delay:7>"
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*
