Re: Hylafax job failed
Michael Hierweck <michael@hierweck.de> writes:
Hallo!
> Ich habe, wie empfohlen, hylafax 4.1.5 kompiliert.
> Your facsimile job to 02319698472 failed because: Stop and wait failure
> (modem on hook); Giving up after 3 attempts to send same page
Dieser Stop and wait failure deutet afaik auf die schon beschriebene
Problematik hin.
> Sicherheitshalber sende ich meine config.ttyI0 mit:
> Class1TCFResponseDelay: 75 # 75ms delay between recv TCF & response
> Class1SendPPMDelay: 75 # 75ms delay before sending PPM
> Class1SendTCFDelay: 75 # 75ms delay between sending DCS & TCF
> 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 # #
> #Class1SendEOPWaitCmd: <delay:90> #Class1SendTCFWaitCmd: <delay:70>
> #Class1SendPPMWaitCmd: <delay:70>
Hm, ist das eine mit Hylafax 4.1.5 neu erstellte config? Wenn nein,
dann solltest Du das machen.
Meine sieht nämlich teilweise etwas anders aus.
Class1Cmd: AT+FCLASS=1 # command to enter class 1
Class1TCFResponseDelay: 75 # 75ms delay between recv TCF & response
Class1SendMsgDelay: 75 # 75ms delay after training
Class1SwitchingDelay: 75 # 150ms delay in switching transmission dire
ction
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
#Class1MsgRecvHackCmd: "" # command to avoid +FCERROR before image
Class1PPMWaitCmd: "<delay\0727>" # \072 == : to avoid awk problem
Class1TCFWaitCmd: "<delay\0727>"
Class1EOPWaitCmd: "<delay\0729>"
Class1SwitchingCmd: "<delay\0727>" # assumption: +FRS not supported
> Muss ich doch den Kernelpatch einsetzen?
Nein, bei mir sind die Probleme mit Version 4.1.5 ohne den Patch gelöst.
Viele Grüße
Markus
--
http://www.nospam.please
Scorefile adjusted
mv *.spam > /dev/null
GPG Key available, send mail with subject:getpgp
Reply to: