[hylafax-users] CAPI Error 0x3312 but sending fax successfully

[christian79@xxxxxxxx]

Hello,

I am using Hylafax Server 4.2.5 in combination with Capi4Hylafax and an AVM ISDN Fritz card for sending out faxes. Sometimes it happens that after sending out the fax page successfully (I know this from recipient) an error code 0x3312 is returned, I think from the CAPI interface. See an example Hylafax log here:

Log:
Apr 23 21:02:37.32: [11931]: SESSION BEGIN 000001001 +49.xx.xxxxxx
Apr 23 21:02:37.32: [11931]: SEND FAX: JOB 1001 DEST 0xxxxxx COMMID 000001172
Apr 23 21:02:37.32: [11931]: Try to connect to fax number 0xxxxxx in Hylafax mode on controller 1.
Apr 23 21:02:37.32: [11931]: Dial and starting transfer of TIFF-File docq/doc1003.ps;00 with normal resolution.
Apr 23 21:03:00.96: [11931]: Connection established.
Apr 23 21:03:00.96: [11931]:    StationID = +49 xxx xxxxxx
Apr 23 21:03:00.96: [11931]:    BaudRate  = 9600
Apr 23 21:03:00.96: [11931]:    Flags     = HighRes, MR_compr, No_ECM
Apr 23 21:03:00.99: [11931]: Page 1 was sent. - Last Page!
Apr 23 21:03:00.99: [11931]: Fax file completely transfered to CAPI.
Apr 23 21:03:23.32: [11931]: Connection was dropped with Reason 0x3312 (Connecting not successful (training error)) before Fax was c
ompletely transfered.
Apr 23 21:03:23.43: [11931]: Connection dropped with Reason 0x3400 (No additional information).

Doneq Log (excerpt):
status:REJECT: Too many attempts to transmit: 3, max 3
returned:1


I think this is not really Hylafax related, but maybe someone has an idea what this error code means and why this error happens, as the page was transmitted successfully. 

The error happens for several dial out numbers but not continuously, mostly there are no errors.

My problem here is, that Hylafax tries to resend the fax until the max redial attempts are reached, the recipient receives the fax more than once. Also my notify script is writing the "rejected" error into my database instead of the "successfully done" message which results into monitoring/status problems for me.

If there is no solution for avoiding the 0x3312 message: Is it possible to let Hylafax know that this error code is okay and that there should be no resend attempt and also write down the "successfully done" status into the database?

Thank you,
Christian

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