[Home]

Summary:ASTERISK-21139: Asterisk 11 Seg Faults on READ after ConfBridge KICK
Reporter:Michel R. Vaillancourt (jkl5group)Labels:
Date Opened:2013-02-19 09:42:29.000-0600Date Closed:2017-08-29 09:12:59
Priority:CriticalRegression?
Status:Closed/CompleteComponents:Applications/app_confbridge
Versions:11.2.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:(61)[root@cloudpbx2 src]$ uname -a Linux cloudpbx2.jkl5group.com 2.6.18-348.el5 #1 SMP Tue Jan 8 17:57:28 EST 2013 i686 i686 i386 GNU/Linux cloudpbx2*CLI> core show version Asterisk SVN-branch-11-r381702 built by root @ cloudpbx2.jkl5group.com on a i686 running Linux on 2013-02-19 15:21:56 UTC Attachments:( 0) backtrace.txt
Description:Given the following testing dialplan:

{noformat}
[test_bunker]
 exten => s,1, NoOp(... crash test dummy ...)
 same => n, Answer(1)
 same => n, Set(_access_code=5555097)
 same => n, Set(_bridge_profile=ccb_bridge)
 same => n, Set(_menu_profile=ccb_guest_menu)
 same => n, Set(_user_profile=ccb_guest_user)

 same => n, Read(digits,"hold-or-dial-0",1,i,1,9)
 same => n, GotoIf($[${digits}==9]?makeadmin:startconf)

 same => n(makeadmin), Set(_user_profile=ccb_admin_user)
 same => n(startconf), Set(admin_count=${CONFBRIDGE_INFO(admins,${access_code})})
 same => n, ConfBridge(${access_code},${bridge_profile},${user_profile},${menu_profile})
{noformat}

... with:

{noformat}
[ccb_admin_user]
 type=user
 admin = yes
 marked = yes
 music_on_hold_when_empty = yes
 music_on_hold_class = default
 jitterbuffer = yes
 announce_join_leave = no
 announce_user_count = yes
{noformat}

... run a 2+ participant conference.  Have "Leader" (marked) user drop call.  All guests kicked, as expected/specified.  Now dial back into the conf context.  Asterisk seg faults on READ command.

Same behavior if run as an AGI.

Tested on 3 different servers, reproducible in all cases.
Comments:By: Matt Jordan (mjordan) 2013-02-19 10:33:17.880-0600

Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:

make install

After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Michel R. Vaillancourt (jkl5group) 2013-02-19 11:38:39.900-0600

Backtrace as requested.  Let me know if you need anything else.
By: Sean Bright (seanbright) 2017-08-29 09:13:00.176-0500

I am not able to reproduce on Asterisk 13 (currently the oldest supported version of Asterisk) with the configuration you supplied. If you are able to reproduce on Asterisk 13 or higher, please re-open.