<br><font size=2 face="sans-serif">you're right - app_rxfax.so kills Asterisk-version
1.2.13 - Where seems to be a bug when freeing the a struct ast_frfree -
at line 327 of app_rxfax.c causing to crash asterisk. - Commenting this
line prevents asterisk from crashing for testcases but cannot be a solution
for production-systems.</font>
<br><font size=2 face="sans-serif">With asterisk-1.2.9 it worked so where
seems to be some changes since this version causing this crashes.</font>
<br>
<br>
<br><tt><font size=2>asterisk-users-bounces@lists.digium.com wrote on 17.11.2006
02:35:34 PM:<br>
<br>
> A little progress on this problem<br>
> <br>
> Examining the logs i found a weird looking 'soft hangup' which <br>
> reminded me on an earlier issue we had. (and the reason why we were
<br>
> still on the 'i' release of bristuff). It looked as if the channel
<br>
> hung up just before rxfax actually could begin to work.<br>
> <br>
> Normally we would let the faxdetection be automatic and let ast jump
<br>
> to the 'fax' extension, which in turn calls the faxreceive macro as
<br>
> described in my original post.<br>
> <br>
> Bypassing all that and directly tie-ing an extension to the <br>
> faxreceive macro (not even answering the channel), gives a successful
<br>
> fax reception. RxFax has a check whether the channel is answered,
and <br>
> it will answer it, if not already.<br>
> <br>
> I think this was a lucky shot in the dark though. The problem seems
<br>
> to be a mismatch between the state of the channel (answered) and what
<br>
> it actually is. Getting data from the channel wont work then i guess.<br>
> <br>
> This is a suitable workaround for our little setup for now. The only
<br>
> thing we miss at this point is that we wont be able to receive faxes
<br>
> at every extension anymore, just the one.<br>
> <br>
> I do not have enough knowledge of the sources to suggest a fix for
<br>
> this. It looks like either the specific stuff for our card (quadbri)
<br>
> or asterisk itself would be the area to look into, but again, i am
<br>
> not (yet) capable of doing so myself.<br>
> <br>
> Hope this helps anyone fixing the real problem.<br>
> <br>
> marcel<br>
> <br>
> On 16 nov 2006, at 11:27, Marcel van der Boom wrote:<br>
> <br>
> > Hi,<br>
> ><br>
> > I'm using spandsp-0.0.3<br>
> > [http://www.soft-switch.org/downloads/snapshots/spandsp/ <br>
> > spandsp-20061116.tar.gz]<br>
> ><br>
> > on a bristuffed asterisk (1.2.13)<br>
> > [http://212.91.251.199/~junghanns.net/downloads/bristuff-0.3.0-
<br>
> > PRE-1v.tar.gz]<br>
> ><br>
> > libtiff is at version 3.6.0<br>
> ><br>
> > Running on: Linux router2 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10
<br>
> > UTC 2006 i686 GNU/Linux<br>
> > Debian testing distro.<br>
> ><br>
> > I've tried many combinations of bristuffed ast and spandsp <br>
> > versions, but all fail at the same point. The last combination
i <br>
> > got to work was bristuffed 0.3.0-PRE-1i with spandsp-0.0.2-pre25
<br>
> > (on an earlier kernel)<br>
> ><br>
> > The app_rxfax.c in use is from:<br>
> > [http://www.soft-switch.org/downloads/snapshots/spandsp/test-apps-
<br>
> > asterisk-1.2/app_rxfax.c]<br>
> ><br>
> > On reception of a fax through RxFax, i get the exception. The
<br>
> > relevant part of the dialplan is<br>
> ><br>
> > [macro-faxreceive]<br>
> > ; Receive a fax<br>
> > exten => s,1,Set(FAXFILE=${FAXSPOOL}/${UNIQUEID}.tif)
; Save the <br>
> > fax in a tif file<br>
> > exten => s,2,RxFAX(${FAXFILE})
; Receive
it<br>
> > exten => s,3,NoOp("Fax reception complete")
;<br>
> > exten => s,4,Hangup<br>
> ><br>
> > Running asterisk (with the above versions) through gdb and doing
a <br>
> > backtrace gives me:<br>
> ><br>
> > #0 0xa7d45947 in raise () from /lib/tls/libc.so.6<br>
> > #1 0xa7d470c9 in abort () from /lib/tls/libc.so.6<br>
> > #2 0xa7d7afda in __fsetlocking () from /lib/tls/libc.so.6<br>
> > #3 0xa7d8289f in mallopt () from /lib/tls/libc.so
.6<br>
> > #4 0xa7d82942 in free () from /lib/tls/libc.so.6<br>
> > #5 0xa75efd68 in rxfax_exec (chan=0x818c5f8, data=0xa74a4798)
at <br>
> > app_rxfax.c:327<br>
> > #6 0x08090088 in pbx_extension_helper (c=0x818c5f8, con=<value
<br>
> > optimized out>, context=<value optimized out>, exten=0x818c83c
"s", <br>
> > priority=2,<br>
> > label=0x0, callerid=0x0, action=1) at pbx.c:554<br>
> > #7 0xa762cb05 in macro_exec (chan=0x818c5f8, data=0xa74aafe8)
at <br>
> > app_macro.c:221<br>
> > #8 0x08090088 in pbx_extension_helper (c=0x818c5f8, con=<value
<br>
> > optimized out>, context=<value optimized out>, exten=0x818c83c
"s", <br>
> > priority=1,<br>
> > label=0x0, callerid=0x0, action=1) at pbx.c:554<br>
> > #9 0x08091dee in __ast_pbx_run (c=0x818c5f8) at pbx.c:2231<br>
> > #10 0x08092a1c in pbx_thread (data=0x818c5f8) at pbx.c:2518<br>
> > #11 0xa7f0d0bd in start_thread () from /lib/tls/libpthread.so.0<br>
> > #12 0xa7de892e in clone () from /lib/tls/libc.so.6<br>
> ><br>
> > This seems to indicate that the ast_frfree(inf); at line 327
of <br>
> > app_rxfax.c causes the problem chain?<br>
> ><br>
> > I'm a bit lost on how to debug this further. Is this actually
a <br>
> > spandsp problem or is another package the cause?<br>
> > Any tips?<br>
> ><br>
> > marcel<br>
> ><br>
> ><br>
> > -- <br>
> > Marcel van der Boom<br>
> > HS-Development BV
-- http://www.hsdev.com<br>
> > So! webapplicatie framework -- http://make-it-so.info<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > --Bandwidth and Colocation provided by Easynews.com --<br>
> ><br>
> > asterisk-users mailing list<br>
> > To UNSUBSCRIBE or update options visit:<br>
> > http://lists.digium.com/mailman/listinfo/asterisk-users<br>
> <br>
> -- <br>
> Marcel van der Boom<br>
> HS-Development BV
-- http://www.hsdev.com<br>
> So! webapplicatie framework -- http://make-it-so.info<br>
> <br>
> <br>
> _______________________________________________<br>
> --Bandwidth and Colocation provided by Easynews.com --<br>
> <br>
> asterisk-users mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> http://lists.digium.com/mailman/listinfo/asterisk-users<br>
</font></tt><font size=3 face="sans-serif"><br>
Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich
geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese E-Mail und ihren Inhalt. Das unerlaubte
Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.<br>
<br>
This e-mail and any attached files may contain confidential and/or privileged
information. If you are not the intended recipient (or have received this
e-mail by mistake) please notify the sender immediately and delete this
e-mail. Any unauthorised duplication, disclosure or distribution of this
e-mail and content is strictly forbidden. </font>