Summary: | ASTERISK-26833: CLONE - app_confbridge: kick not working just after channel entered the conference | ||||
Reporter: | Marco Nicoloso (mnicolos) | Labels: | |||
Date Opened: | 2017-03-02 10:59:40.000-0600 | Date Closed: | 2017-03-02 11:01:38.000-0600 | ||
Priority: | Major | Regression? | |||
Status: | Closed/Complete | Components: | Applications/app_confbridge | ||
Versions: | 11.23.1 11.24.1 | Frequency of Occurrence | |||
Related Issues: |
| ||||
Environment: | centos 5,6,7 64bit | Attachments: | |||
Description: | Original ISSUE:
------------------------------------------------------------------------------------------------------- When conference have one channel, kick for that channel not works. EaglePhoneUK*CLI> confbridge list conf_731_1 Channel User Profile Bridge Profile Menu CallerID Muted ============================== ================ ================ ================ ================ ===== SIP/4274581-00000000 a2b_owner a2b_conf a2b_menu 1380975115111 No CLI> confbridge kick conf_731_1 SIP/4274581-00000000 No participant named 'SIP/4274581-00000000' found! -------------------------------------------------------------------------------------------------------- My comments on this: it is reproduceable also on 11.23.1 and not only on the last channel that enters the conference. This bug happens when the channels just entered the conference and they undergo a kick (e.g. from AMI). The kick in AMI finishes OK, but the channels still remain in the conference and subsequent kicks will produce the error No participant named 'SIP/4274581-00000000' found! The only way to kick them from the conference is an hangup request. | ||||
Comments: | By: Asterisk Team (asteriskteam) 2017-03-02 10:59:41.172-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2017-03-02 11:01:27.307-0600 Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions |