[asterisk-bugs] [JIRA] (ASTERISK-21957) Confbridge doesn't tear down an empty conference bridge when all users were kicked via end_marked=yes. Also, side effect crashes.
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Tue Jun 25 16:46:03 CDT 2013
Rusty Newton created ASTERISK-21957:
---------------------------------------
Summary: Confbridge doesn't tear down an empty conference bridge when all users were kicked via end_marked=yes. Also, side effect crashes.
Key: ASTERISK-21957
URL: https://issues.asterisk.org/jira/browse/ASTERISK-21957
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: Applications/app_confbridge
Affects Versions: 11.4.0
Environment: Asterisk 11.4.0 on Raspberry Pi with 2-9-2013-debian-wheezy and 11.3.0 running on an Intel Atom w/ Ubuntu 12.04.
Reporter: Chris Gentle
Assignee: Rusty Newton
Please reference:
http://lists.digium.com/pipermail/asterisk-users/2013-June/279231.html
I've set up a conference where I'm relying on end_marked=yes to kick all participants when the leader exits. This results in an error as shown below:
{noformat}
<< Hangup on console >>
-- <Bridge/0x2364be4-input> Playing 'confbridge-leave.slin' (language 'en')
-- Stopped music on hold on SIP/gent_2880-00000002
-- <SIP/gent_2880-00000002> Playing 'custom/thank-you.ulaw' (language 'en')
-- Executing [1000 at conferences:2] Hangup("SIP/gent_2880-00000002",
"") in new stack
== Spawn extension (conferences, 1000, 2) exited non-zero on
'SIP/gent_2880-00000002'
{noformat}
In this case, the conference leader was the alsa console channel. Once it was hung up, a non-zero exit status caused the confbridge to go into a bad state showing 0 users:
confbridge list
{noformat}
Conference Bridge Name Users Marked Locked?
================================ ====== ====== ========
1000 0 0 unlocked
{noformat}
Asterisk has to be restarted to clear this. In a normal exit, a "confbridge list" would not show conference 1000 because it would have been destroyed.
If no participants are dialed into the conference, everything closes cleanly when the leader exits.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list