[asterisk-bugs] [JIRA] (ASTERISK-28897) app_confbridge: AMI Event "ConfbridgeTalking off" not fired when user leaves ConfBridge while talking

Joshua C. Colp (JIRA) noreply at issues.asterisk.org
Mon May 18 04:28:25 CDT 2020


     [ https://issues.asterisk.org/jira/browse/ASTERISK-28897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-28897:
--------------------------------------

    Assignee: Ben Reinsen
      Status: Waiting for Feedback  (was: Triage)

I think the reason that this was not really done is because you receive notification that the channel in question is leaving the conference bridge - so that should reset and clear any state you may have. Can you explain why this is not enough for your situation?

> app_confbridge: AMI Event "ConfbridgeTalking off" not fired when user leaves ConfBridge while talking
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28897
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28897
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 16.9.0
>            Reporter: Ben Reinsen
>            Assignee: Ben Reinsen
>            Severity: Trivial
>         Attachments: ami.log
>
>
> Confbridge fires Events to AMI when users start and stop talking in a conference. 
> https://wiki.asterisk.org/wiki/display/AST/ConfBridge+AMI+Events#ConfBridgeAMIEvents-ConfbridgeTalking
> When a user leaves a conference or disconnects because of networking problems while talking no final "ConfbridgeTalking off" event is fired for that user, which leaves external apps that query AMI for ConfbridgeTalking events in a wrong state. 
> As the user actually stopped talking, when he has left the conference, I would kindly suggest to fire a final "ConfbridgeTalking off" event when a currently talking users leaves a conference



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list