asterisk users - Jan 2008 - rxfax does not work (anymore)

Below is my extensions.conf for the fax part


[incoming_28345474]
;
;********************************************************************
;       BEGIN - Inbound call handlers
;********************************************************************
;
exten => 8862100,1,NoOp(${CALLERID(num)})
exten => 8862100,2,Background(if-u-know-ext-dial)
exten => 8862100,3,Set(CALLERID(num)=${CALLERID(num)})
exten => h,1,hangup()
include => fax2emailstart
include => local

[fax2emailstart]
exten => 3000,1,SetVar(CALLEDFAX=${EXTEN})      ; tm.ronald at gmail.com
exten => 3000,2,Answer
exten => 3000,3,Macro(fax2emailservice)

exten => h,1,System(/var/lib/asterisk/scripts/fax2emailservice
"${CALLERIDNUM}" "${CALLEDFAX}" "${EXTNAME}"
"${EXTEMAIL}" "${FAXFILE}"
"${EXTCOMPANY}")

[macro-fax2emailservice]
 exten =>
s,1,SetVar(FAXFILE=/var/spool/asterisk-fax/${CALLEDFAX}/${UNIQUEID})
 exten => s,2,Set(EXTEMAIL=${DB(${MACRO_EXTEN}/xEmail)})
 exten => s,3,NoOP()
 exten => s,4,Set(EXTNAME=${DB(${MACRO_EXTEN}/xName)})
 exten => s,5,NoOP()
 exten => s,6,Set(EXTCOMPANY=${DB(${MACRO_EXTEN}/xCompany)})
 exten => s,7,rxfax(${FAXFILE}.tif)
 exten => s,103,SetVar(EXTMAIL=ronald at elmit.com)
 exten => s,104,Goto(7)
 exten => s,105,SetVar(EXTNAME=Ronald)
 exten => s,106,Goto(7)
 exten => s,107,SetVar(EXTCOMPANY=Elmit)
 exten => s,108,Goto(7)


When I call this PSTN number and dial the extension number 3000, then I
see that:

*CLI>
[Jan 27 16:03:21]     -- Zap/3-1 answered SIP/601-006a2970
[Jan 27 16:03:24]     -- Executing NoOp("SIP/88621001-00728610",
"88621001") in new stack
[Jan 27 16:03:24]     -- Executing BackGround("SIP/88621001-00728610",
"if-u-know-ext-dial") in new stack
[Jan 27 16:03:24]     -- Playing 'if-u-know-ext-dial' (language
'en')
[Jan 27 16:03:28]     -- Executing Set("SIP/88621001-00728610",
"CALLERID(num)=88621001") in new stack
[Jan 27 16:03:32]   == CDR updated on SIP/88621001-00728610
[Jan 27 16:03:32]     -- Executing SetVar("SIP/88621001-00728610",
"CALLEDFAX=3000") in new stack
[Jan 27 16:03:32]     -- Executing Answer("SIP/88621001-00728610",
"")
in new stack
[Jan 27 16:03:32]     -- Executing Macro("SIP/88621001-00728610",
"fax2emailservice") in new stack
[Jan 27 16:03:32]     -- Executing SetVar("SIP/88621001-00728610",
"FAXFILE=/var/spool/asterisk-fax/3000/1201421004.8") in new stack
[Jan 27 16:03:32]     -- Executing Set("SIP/88621001-00728610",
"EXTEMAIL=fax.ronald at gmail.com") in new stack
[Jan 27 16:03:32]     -- Executing NoOp("SIP/88621001-00728610",
"") in
new stack
[Jan 27 16:03:32]     -- Executing Set("SIP/88621001-00728610",
"EXTNAME=Ronald Wiplinger") in new stack
[Jan 27 16:03:32]     -- Executing NoOp("SIP/88621001-00728610",
"") in
new stack
[Jan 27 16:03:32]     -- Executing Set("SIP/88621001-00728610",
"EXTCOMPANY=Elmit.com") in new stack
[Jan 27 16:03:32]     -- Executing RxFAX("SIP/88621001-00728610",
"/var/spool/asterisk-fax/3000/1201421004.8.tif") in new stack
vpbx*CLI>
Disconnected from Asterisk server


I have no idea why it disconnects and hope somebody can help me to get
to work.

bye

Ronald

Ronald Wiplinger wrote:
> [Jan 27 16:03:32]     -- Executing RxFAX("SIP/88621001-00728610",
> "/var/spool/asterisk-fax/3000/1201421004.8.tif") in new stack
> vpbx*CLI>
> Disconnected from Asterisk server
> 
> 
> I have no idea why it disconnects and hope somebody can help me to get
> to work.
> 
> bye
> 
> Ronald
> 
You subject says it doesn't work anymore.  Did you change something? 
Upgrade Asterisk and not SpanDSP?

This is the same message you would see if the asterisk service wrecked. 
  Have you tried turning on full debugging?  If not, edit the 
/etc/asterisk/logger.conf and make sure there is a line in there like:

full => notice,warning,error,debug,verbose

Then, go through your fax process and check the file 
/var/log/asterisk/full.  It will have tons of information about what 
went on.

When you are done with this, be sure to disable the full logging because 
it will eat a lot of drive space.

--
Mark Johnson
http://www.astroshapes.com/information-technology/blog/