[hylafax-users] problems sending a fa with hylafax 4.2.1 and CAPI

[berndq <berndq@xxxxxxx>]

Hi everybody,

I am setting up two hylafax servers on similar machines (same SW, 
slightly different HW) and the both show the same problem.

configuration is
- hylafax 4.2.1
- debian 2.6.8 kernel
- debian capi4hylafax 01.02.03-7
- AVM Fritz card DSL and Fritz card DSL V2

CAPI itself is working fine (there are tools supplied by AVM to test 
CAPI functionality)

Hylafax is configured to send faxes with

  SendFaxCmd:             /usr/bin/c2faxsend

and this can be seen in the logs:


Apr  8 15:43:47 localhost FaxQueuer[6723]: JOB 20 (active dest 58 pri 
127 tts 0:00 killtime 2:59:00): CMD START /usr/bin /c2faxsend -m faxCAPI 
sendq/q20 (PID 6874)
Apr  8 15:43:48 localhost kernel: capilib_new_ncci: kcapi: appl 4 ncci 
0x20201 up
Apr  8 15:44:03 localhost kernel: kcapi: appl 4 ncci 0x20201 down
Apr  8 15:44:04 localhost FaxQueuer[6723]: JOB 20 (active dest 58 pri 
127 tts 0:00 killtime 2:58:43): CMD DONE: exit status 0
Apr  8 15:44:04 localhost FaxQueuer[6723]: JOB 20 (sleeping dest 58 pri 
126 tts 0:00 killtime 2:58:43): SEND INCOMPLETE: requeue for 5:27;
Apr  8 15:44:04 localhost FaxQueuer[6723]: JOB 20 (sleeping dest 58 pri 
126 tts 0:00 killtime 2:58:43): SLEEP FOR 5:27


So the job exit status is 0 but the send is classified as problematic, 
the fax is queued again, no reason given

I assume that a status of 0 means "all ok" so I wonder why it is re-queueed.

The corresponding document exists in docq.

The receiving machine (tested with a fax device and another Fritz
cards installaion) only shows the fax header (including e.g. the station
id but no content)

no erros can be seen in the logs from c2faxsend.

Looking at the sources faxd/faxQueueApp.c++ in method
sendJobDone (the only occurence of "SEND INCOMPLETE: requeue":

 if (!job.suspendPending) {
     job.remove();                       // remove from active list
     if (req->tts > now) {
         traceQueue(job, "SEND INCOMPLETE: requeue for "
             | strTime(req->tts - now)
             | "; " | req->notice);
          setSleep(job, req->tts);
          Trigger::post(Trigger::SEND_REQUEUE, job);
          if (req->isNotify(FaxRequest::when_requeued))
              notifySender(job, Job::requeued);

according to faxstat -s the job does not have a TTS immediately after it 
is queued:

  HylaFAX scheduler on localhost.localdomain: Running
  Modem faxCAPI (xxx): Running and idle

  JID  Pri S  Owner Number       Pages Dials     TTS Status
  23   127 R   root 58            0:1   1:12         Sending job

So what can be the reason why "SEND INCOMPLETE: requeue ..." is logged 
and the job re-queued?

Bernd



____________________ 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*