[asterisk-bugs] [JIRA] (ASTERISK-21140) Asterisk 11 Seg Faults on READ after ConfBridge KICK
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Tue Feb 19 15:15:19 CST 2013
Rusty Newton created ASTERISK-21140:
---------------------------------------
Summary: Asterisk 11 Seg Faults on READ after ConfBridge KICK
Key: ASTERISK-21140
URL: https://issues.asterisk.org/jira/browse/ASTERISK-21140
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: Applications/app_confbridge
Affects Versions: 11.2.1
Environment: (61)[root at 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
Reporter: Michel R. Vaillancourt
Severity: Critical
Given the following testing dialplan:
[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})
... with:
[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
... 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list