On a test fax:
-- Executing [s at incoming-fax:1] Set("DAHDI/4-1",
"FAXFILE=/var/spool/asterisk/fax/20110415_1825") in new stack
-- Executing [s at incoming-fax:2] Answer("DAHDI/4-1",
"") in new stack
-- Executing [s at incoming-fax:3] ReceiveFAX("DAHDI/4-1",
"/var/spool/asterisk/fax/20110415_1825.tif") in new stack
-- Channel 'DAHDI/4-1' receiving FAX
'/var/spool/asterisk/fax/20110415_1825.tif'
-- Channel 4 detected a CED tone towards the network.
[Apr 15 18:25:52] WARNING[5600]: res_fax_spandsp.c:367 spandsp_log:
WARNING T.30 ECM carrier not found
[Apr 15 18:25:52] WARNING[5600]: res_fax_spandsp.c:367 spandsp_log:
WARNING T.30 ECM carrier not found
== Spawn extension (incoming-fax, s, 3) exited non-zero on
'DAHDI/4-1'
/var/spool/asterisk/fax exists, but no file 20110415_1825.tif is created.
Using spandsp-0.0.6-pre18, the Jan 22 release.
Do the log notes of the CED tone or the T.30 ECM warning have anything
to do with this?
chan_dahdi.conf:
[pstn]
context=incoming-pstn-line ; Incoming calls go to [incoming-pstn-line]
in extensions.conf
faxdetect=incoming
faxbuffers=>6,full ; who knows what this does
busydetect=yes
dahdichan => 4
Any idea on how to debug this?
sean