[chan-capi-users] Cannot capicommand(sendfax) because of reason 0x3400
Niki Hammler
mailinglists at nobaq.net
Mon Aug 21 20:01:22 UTC 2006
Armin Schindler schrieb:
> Hi,
Hi Armin,
Thanks for your reply!
> I cannot see anything wrong in your log. It's just that the driver
> (I assume AVM) is dropping the call without a specific error code.
Hmm, but this does not seem correct to me:
capi sendfax: fax send failed reason=0x3400 reasonB3=0x0000
The funny thing is that the fax has been received on the other side.
But the FAXSTATUS is definitiveley wrong according to the README.txt...
> Maybe a more verbose log does provide more info, try
> set verbose 9
> capi debug
I don't know If I'm allowed to post so much log output here, so I've put
it here:
http://www.nobaq.net/~niki/sendfax.txt
Everything seems normal to me until the
capi sendfax: fax send failed reason=0x3400 reasonB3=0x0000
> You also could try to send this fax to your destination with the tool
> 'capifax' which is part of the isdn4k-utils. It's a simple program which
> does the same as chan-capi when sending a fax.
I did it:
# capifax -v -v -i Hammler -h 'Testfax mit capifax' -c 0316391985
031690850090 /home/daten/testfax.sff
Disconnected.
Reason : 3400 No additional information
Reason-B3 : 0000 No additional information
Remote Station ID : SC&C GmbH & Co KEG
Transfer-Rate : 14400 bps
Resolution : low
Number of Pages : 1
seems to be the same error...
> If this doesn't work either, the problem is the destination or your AVM
> driver/setup.
Oke, seems to be the case.
However, can I be sure that all Faxes with these errorcodes are received
successfully by the remote station and ignore the error? (I hate
ignoring errors ;-)
Thank you,
Niki
> Armin
>
> On Wed, 16 Aug 2006, Niki Hammler wrote:
>> Hi,
>>
>> TxFAX did not work because of "Unable to find a codec translation path
>> from alaw to unknown".
>>
>> So I decided to use the capicommand(sendfax) because receivefax already
>> works and does great job!
>>
>> I use the Hylafax-Emulator "afaxd" to send faxes through a callfile to
>> asterisk.
>>
>> When I send a fax, afaxd created a callfile which dials a number and
>> then jumps to context "faxout", extension "s" and priority "1".
>>
>> My extensions.conf looks like this:
>>
>> [faxout]
>> exten => s,1,SetCallerID(194576)
>> exten => s,2,capicommand(sendfax|${FILE})
>> exten => s,3,GotoIf($[${FAXSTATUS} = 1] ? 4 : 6)
>> exten => s,4,Set(STATUS=0)
>> exten => s,5,Goto(7)
>> exten => s,6,Set(STATUS=1)
>> exten => s,7,System(${EXECUTE} -r ${JOBID} ${STATUS})
>> exten => s,8,Hangup()
>>
>> It whould work. The number is called, the destination fax answers the
>> call and (seems) to begin receiving data.
>> But after some time executing capicommand(sendfax) I suddenly get the
>> strange errorcode 0x3400. Google resolves this message to the very cool
>> "No additional information"-Message.
>> So I've absolutely no idea where I could begin finding the error.
>>
>>
>> Here is what happens during sending out the fax:
>>
>> -- Attempting call on CAPI/contr1/073490630410 for s at faxout:1 (Retry 1)
>> Aug 16 19:18:58 WARNING[17940]: channel.c:1602 ast_waitfor_nandfds:
>> Thread 311310 Blocking 'CAPI/ISDN1/073490630410-5', already blocked by
>> thread 0 in procedure (null)
>> > Channel CAPI/ISDN1/073490630410-5 was answered.
>> -- Executing SetCallerID("CAPI/ISDN1/073490630410-5", "194576") in
>> new stack
>> -- Executing capiCommand("CAPI/ISDN1/073490630410-5",
>> "sendfax|/tmp/1155748738.tif") in new stack
>> capi sendfax: fax send failed reason=0x3400 reasonB3=0x0000
>> -- Executing GotoIf("CAPI/ISDN1/073490630410-5", "1 ? 4 : 6") in new
>> stack
>> -- Goto (faxout,s,4)
>> -- Executing Set("CAPI/ISDN1/073490630410-5", "STATUS=0") in new stack
>> -- Executing Goto("CAPI/ISDN1/073490630410-5", "7") in new stack
>> -- Goto (faxout,s,7)
>> -- Executing System("CAPI/ISDN1/073490630410-5",
>> "/usr/local/sbin/afaxd -r 1155748738 0") in new stack
>> -- Executing Hangup("CAPI/ISDN1/073490630410-5", "") in new stack
>> == Spawn extension (faxout, s, 8) exited non-zero on
>> 'CAPI/ISDN1/073490630410-5'
>> == ISDN1#02: CAPI Hangingup for PLCI=0x101 in state 4
>> Aug 16 19:19:25 NOTICE[17940]: pbx_spool.c:279 attempt_thread: Call
>> completed to CAPI/contr1/073490630410
>>
>>
>> Comment: The file is called xxx.tif but it IS an SFF file! I modified
>> afaxd to execute gs to output a sff-file instead of a tif file using
>> this command:
>>
>> gs -dNOPAUSE -dBATCH -r$resolution -sDEVICE=cfax -sOutputFile=$tiffFile
>> $psFile
>>
>> So the file is only called *.tif but the content should be SFF. The
>> first four bytes of the file are "Sfff"
>>
>>
>>
>> Thank you a lot in advance!
>>
>> Niki
>>
>> _______________________________________________
>> Chan-capi-users mailing list
>> Chan-capi-users at lists.melware.net
>> http://lists.melware.net/mailman/listinfo/chan-capi-users
>>
>
More information about the Chan-capi-users
mailing list