Summary:ASTERISK-08470: 302 Redirect not working?
Reporter:deti (deti)Labels:
Date Opened:2007-01-03 10:57:36.000-0600Date Closed:2007-03-14 08:41:30
Versions:Frequency of
Environment:Attachments:( 0) y.log
( 1) z.log
( 2) zz.log
Description:Currently a 302 answer to a call lets asterisk crash. See attached file for complete log. It is reproducible for me - can anyone please confirm that?
Comments:By: Serge Vecher (serge-v) 2007-01-03 11:21:16.000-0600

format_mp3 or mpg123 in use?

By: deti (deti) 2007-01-03 11:26:31.000-0600

The extension redirected to calls the Mp3Player application. The problem is _not_ releated to this. The crash even occurs with any other redirection target.

By: Serge Vecher (serge-v) 2007-01-03 11:34:01.000-0600

ok, the backtrace is useless, because asterisk was compiled with optimizations. Please check the "DONT OPTIMIZE" flag under compiler options in menuselect, recompile and reproduce the crash. Also, please make sure that verbosity is at least 4 and include the log starting with a complete INVITE packet, not a middle of the transaction. Thanks!

By: deti (deti) 2007-01-03 17:50:49.000-0600

Asterisk compiled with DONT OPTIMIZE. When the crash happens the stack seems to be messed up. After some more crash tests I managed to get a more plausible backtrace finally. (see file z.log)

By: deti (deti) 2007-01-03 17:54:00.000-0600

seems that we have something:

*** glibc detected *** double free or corruption (!prev): 0x081e12b8 ***

ASTERISK-1  0x08079b1c in ast_channel_free (chan=0x820b7d8) at channel.c:1094

By: Olle Johansson (oej) 2007-02-15 12:19:10.000-0600

I don't this is a SIP issue any longer, from reading the back trace.

By: Serge Vecher (serge-v) 2007-02-19 08:52:13.000-0600

deti, is this still an issue with absolute latest 1.4 svn (rev > 54600)? If so, please produce a new bt...

By: Mark Spencer (markster) 2007-02-21 10:36:39.000-0600

Can you show me the dialplan entries that correspond to this?


By: Serge Vecher (serge-v) 2007-03-14 08:41:29

If you are able to reproduce this problem with 1.4.1, please reopen the issue with dialplan excerpts attached.