asterisk users - Nov 2009 - 1.6.0.18-rc3: SendFAX causes restart

On 1.6.0.18-rc3 using app_fax.so, spandsp-0.0.5, anytime I use SendFAX 
asterisk restarts:

[Nov 15 19:00:36] VERBOSE[17013] logger.c:     -- Executing 
[s at fax-tx-test:1] ESC[1;36;40mNoOpESC[0;37;40m("ESC[1;35;40mSIP/nhi-rive
rside-sip-00000000ESC[0;37;40m", "ESC[1;35;40mContext 
fax-tx-testESC[0;37;40m") in new stack
[Nov 15 19:00:36] VERBOSE[17013] logger.c:     -- Executing 
[s at fax-tx-test:2] ESC[1;36;40mSystemESC[0;37;40m("ESC[1;35;40mSIP/nhi-ri
verside-sip-00000000ESC[0;37;40m", "ESC[1;35;40mrm -f 
/var/spool/asterisk/outgoing/call-testESC[0;37;40m") in new stack
[Nov 15 19:00:37] VERBOSE[17013] logger.c:     -- Executing 
[s at fax-tx-test:3] ESC[1;36;40mSendFAXESC[0;37;40m("ESC[1;35;40mSIP/nhi-r
iverside-sip-00000000ESC[0;37;40m", 
"ESC[1;35;40m/var/spool/asterisk/fax/20091113_1455.tifESC[0;37;40m")
in
new stack
[Nov 15 19:01:01] VERBOSE[17043] logger.c:  Asterisk Event Logger 
Started /var/log/asterisk/event_log
[Nov 15 19:01:01] VERBOSE[17043] logger.c:  Asterisk Dynamic Loader 
Starting:

 From CLI:

     -- Attempting call on SIP/fax at nhi-riverside-sip for s at fax-tx-test:1 
(Retry 1)
   == Using SIP RTP TOS bits 184
   == Using SIP RTP CoS mark 5
   == Using SIP VRTP CoS mark 6
   == Using UDPTL TOS bits 184
   == Using UDPTL CoS mark 5
     -- Executing [s at fax-tx-test:1] 
NoOp("SIP/nhi-riverside-sip-00000000", "Context
fax-tx-test") in new stack
     -- Executing [s at fax-tx-test:2] 
System("SIP/nhi-riverside-sip-00000000", "rm -f 
/var/spool/asterisk/outgoing/call-test") in new stack
     -- Executing [s at fax-tx-test:3] 
SendFAX("SIP/nhi-riverside-sip-00000000", 
"/var/spool/asterisk/fax/20091113_1455.tif") in new stack
pbx*CLI>


Before I file a bug, is there anything I'm missing?

sean

sean darcy wrote:
> On 1.6.0.18-rc3 using app_fax.so, spandsp-0.0.5, anytime I use SendFAX 
> asterisk restarts:
> 
> Before I file a bug, is there anything I'm missing?
Does this happen on earlier versions of the 1.6.0 series prior to this release 
candidate? I'm curious if this is a regression, or if this is an existing
bug.

Leif.