Error Receiving A Fax … But With A Fax That Was Received Without Problems

Home » Asterisk Users » Error Receiving A Fax … But With A Fax That Was Received Without Problems
Asterisk Users 4 Comments

Dear all,

When receiving a fax, the extension is “spawned”, despite nothing but positive messages (see below)

The sending fax considers it a success & the verbose output of asterisk gives a “FAX_SUCCESS” and a “NO_ERROR” error in the ReceiveFax command.

The problem is that all the next steps (conversion of the fax to pdf &
sending it to a mailbox) are never executed. When I do this manually, there seems nothing wrong with the received file ….

Any hints ?

Asterisk output:

* — *Executing [502@LocalSets:5] *ReceiveFAX*(“*DAHDI/4-1*”, ”
*/tmp/201409211416.tif*”) in new stack

* — *Channel ‘DAHDI/4-1’ receiving FAX ‘/tmp/201409211416.tif’

* — *Channel ‘DAHDI/4-1’ FAX session ‘0’ started

* — *FAX handle 0: [ 037.139057 ], entering CLOSING state

* — *FAX handle 0: [ 037.139097 ], entering CLOSING state

* — *Channel ‘DAHDI/4-1’ FAX session ‘0’ is complete, result: ‘SUCCESS’
(FAX_SUCCESS), error: ‘NO_ERROR’, pages: 1, resolution: ‘204×196’, transfer rate: ‘14400’, remoteSID: ‘059323634’

* == *Spawn extension (LocalSets, 502, 5) exited non-zero on ‘DAHDI/4-1’

Extensions-snippet

exten => 502,1,Verbose(3,Incoming Fax)

same => n,Set(FAXDEST=/tmp)

same => n,Set(tempfax=${STRFTIME(,,%C%y%m%d%H%M)})

same => n,Verbose(3,- destination: ${FAXDEST}/${tempfax}.tif)

same => n,ReceiveFax(${FAXDEST}/${tempfax}.tif)

same => n,Verbose(3,- Fax receipt completed with status:
${FAXSTATUS})

same => n,Verbose(3,converting fax)

same => n,System(/usr/bin/tiff2pdf ${FAXDEST}/${tempfax}.tif -o
${FAXDEST}/${tempfax}.pdf)

same => n,Verbose(3,fax converted … sending fax)

same => n,System(echo “[TC] new fax” | mutt -s “TC:fax from
${CALLERID}” myname@mymail.com -F /root/.muttrc -a ${FAXDEST}/${tempfax}
.pdf)

same => n,Hangup()

4 thoughts on - Error Receiving A Fax … But With A Fax That Was Received Without Problems

  • Bart Remmerie wrote:

    Kia ora,

    After the fax is completed the call is hung up so subsequent dialplan logic does not execute. You need to place the rest in the ‘h’ extension which is executed upon hangup.

    Cheers,

  • Dear Joshua,

    I don’t think this is it:
    first, this has been working in the past second, why would I get a message like the one below “exited non-zero” if everything is normal.

    In the past, all following lines were executed just fine (converting the tif to a pdf and sending it a gmail mailbox)
    I’m not convinced that everything is dropped after the ReceiveFax line, especially since the “Spawn extension” message applies to the ReceiveFax line itself (as if something goes wrong there) => any hints on where/how I
    can get a more detailed logging of this ?

    * == *Spawn extension (LocalSets, 502, 5) exited non-zero on ‘DAHDI/4-1’

  • Bart Remmerie wrote:

    If the either side didn’t hang up (or it took awhile for the hangup to be recognized) then the dialplan would continue.

    Because the message is there to inform you of what happened. It’s not indicative of a problem in all cases.

    This means that whatever was executing either encountered an error or the channel was hung up, which is when dialplan execution stops. This is normal as I previously mentioned.