[Home]

Summary:ASTERISK-08337: Asterisk core when busy in a zap call
Reporter:dmb (dmb)Labels:
Date Opened:2006-12-12 10:20:31.000-0600Date Closed:2007-01-16 14:06:01.000-0600
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hello,
An asterisk core ha s been produced when a zap call with call progress busy. That scenario not produce the core always. I attach the full trace and the gdb core back trace.

Any idea?

****** ADDITIONAL INFORMATION ******

full:
[Dec 12 12:42:21] DEBUG[13033] chan_zap.c: Exception on 39, channel 32
[Dec 12 12:42:21] DEBUG[13033] chan_zap.c: Got event Polarity Reversal(17) on channel 32 (index 0)
[Dec 12 12:42:21] DEBUG[13033] chan_zap.c: Ignore switch to REVERSED Polarity on channel 32, state 6
[Dec 12 12:42:21] DEBUG[13033] chan_zap.c: Ignoring Polarity switch to IDLE on channel 32, state 6
[Dec 12 12:42:21] DEBUG[13033] chan_zap.c: Polarity Reversal event occured - DEBUG 2: channel 32, state 6, pol= 0, aonp= 0, honp= 0, pdelay= 600, tv= 1987603821
[Dec 12 12:42:23] DEBUG[13069] dsp.c: ast_dsp_busydetect detected busy, avgtone: 1495, avgsilence 3085
[Dec 12 12:42:23] DEBUG[13069] dsp.c: Requesting Hangup because the busy tone was detected on channel Zap/7-1
[Dec 12 12:42:23] VERBOSE[13069] logger.c:     -- Zap/7-1 is busy
[Dec 12 12:42:23] DEBUG[13069] chan_zap.c: Set option AUDIO MODE, value: ON(1) on Zap/7-1
[Dec 12 12:42:23] DEBUG[13069] chan_zap.c: Hangup: channel: 7 index = 0, normal = 15, callwait = -1, thirdcall = -1
[Dec 12 12:42:23] DEBUG[13069] chan_zap.c: Not yet hungup...  Calling hangup once with icause, and clearing call
[Dec 12 12:42:23] DEBUG[13069] chan_zap.c: disabled echo cancellation on channel 7
[Dec 12 12:42:23] DEBUG[13069] chan_zap.c: Set option TDD MODE, value: OFF(0) on Zap/7-1
[Dec 12 12:42:23] DEBUG[13069] chan_zap.c: Updated conferencing on 7, with 0 conference users
[Dec 12 12:42:23] DEBUG[13069] chan_zap.c: Set option AUDIO MODE, value: OFF(0) on Zap/7-1
[Dec 12 12:42:23] DEBUG[13069] chan_zap.c: disabled echo cancellation on channel 7
[Dec 12 12:42:23] VERBOSE[13069] logger.c:     -- Hungup 'Zap/7-1'
......ASTERISK CRASH HERE .......
[Dec 12 12:42:27] VERBOSE[13182] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log

gdb core back trace:

Loaded symbols for /usr/lib/asterisk/modules/chan_features.so
#0  0x003092f9 in free () from /lib/tls/libc.so.6
(gdb) backtrace
#0  0x003092f9 in free () from /lib/tls/libc.so.6
#1  0x08097e72 in ast_frame_free (fr=0x3cdff4, cache=1) at frame.c:344
#2  0x00f027f7 in dial_exec_full (chan=0xb793cda8, data=Variable "data" is not available.
) at /usr/src/asterisk-1.4.0-beta3/include/asterisk/frame.h:388
#3  0x00f05d7e in dial_exec (chan=0x3cf824, data=0x0) at app_dial.c:1653
#4  0x080c1f86 in pbx_extension_helper (c=0xb793cda8, con=Variable "con" is not available.
) at pbx.c:505
ASTERISK-1  0x080c254a in ast_spawn_extension (c=0x3cf824, context=0x0, exten=0x0, priority=0, callerid=0x0) at pbx.c:2245
ASTERISK-2  0x0026272c in _macro_exec (chan=0xb793cda8, data=Variable "data" is not available.
) at app_macro.c:232
ASTERISK-3  0x080c1f86 in pbx_extension_helper (c=0xb793cda8, con=Variable "con" is not available.
) at pbx.c:505
ASTERISK-4  0x080c329f in __ast_pbx_run (c=0xb793cda8) at pbx.c:2245
ASTERISK-5  0x080c518e in pbx_thread (data=0xb793cda8) at pbx.c:2556
ASTERISK-6 0x080f02d5 in dummy_start (data=0x0) at utils.c:544
ASTERISK-7 0x0046e371 in start_thread () from /lib/tls/libpthread.so.0
ASTERISK-8 0x0036effe in clone () from /lib/tls/libc.so.6
(gdb)


Comments:By: Joshua C. Colp (jcolp) 2006-12-12 11:10:47.000-0600

1. Can you try the latest 1.4 from the branch?
2. Make sure it's unoptimized. This can be achieved by doing make menuselect, going into compiler flags, and making sure DONT_OPTIMIZE is set on.

Thanks!

By: dmb (dmb) 2006-12-13 03:24:44.000-0600

In one month that problem success once.
Can you provide me any possible bug and correction about it of the latest branch of 1.4?

I don't understand the unoptimized answer. Can you explain it please?

Thank you :)

By: Serge Vecher (serge-v) 2006-12-13 08:41:49.000-0600

dmb: so many changes have gone into 1.4 branch since the release of beta-3, that we absolutely must test with the latest code, to make sure the problem is still there and has not been fixed already.

by "unoptimized", we mean compilation with optimizations turned of. This allows for correlation between line #'s provided in the bt and the sources code, allowing the developer to trace back the cause of the crash. See file's note again on how to turn compiler optimizations off. BTW, this should be safe to run in a production environment.

By: dmb (dmb) 2006-12-14 09:00:49.000-0600

hello
ok. I will post the results if the core repeats again.

Thank you :)

By: Jason Parker (jparker) 2007-01-16 14:06:00.000-0600

I'm going to assume that since you haven't been able to reproduce this in over a month after upgrading, that this problem has been fixed previously.  Closing.

If you can in fact reproduce this issue, please contact a bug marshal on IRC at chat.freenode.net, in the channel #asterisk-bugs