[asterisk-bugs] [JIRA] (ASTERISK-22393) CEL: During BRIDGE_ENTER/BRIDGE_EXIT events, the Peer field is never populated, even if a channel is in the bridge

Matt Jordan (JIRA) noreply at issues.asterisk.org
Fri Sep 27 08:49:03 CDT 2013


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

Matt Jordan updated ASTERISK-22393:
-----------------------------------

    Target Release Version/s: 12.0.0-beta1
    
> CEL: During BRIDGE_ENTER/BRIDGE_EXIT events, the Peer field is never populated, even if a channel is in the bridge
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22393
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22393
>             Project: Asterisk
>          Issue Type: Bug
>          Components: CEL/General
>    Affects Versions: 12
>            Reporter: Matt Jordan
>            Assignee: Kinsey Moore
>      Target Release: 12.0.0-beta1
>
>
> Say we have Alice and Bob.
> Alice enters into a bridge. A BRIDGE_ENTER event is created with no Peer field. This makes sense, as no one else is in the bridge.
> Bob enters into the same bridge. A BRIDGE_ENTER event is also created; however, the Peer field is empty.
> Ideally, CEL events would inform you of the channels that are in the bridge when you enter a Bridge. At the very least, in a two-party bridge, your peer should be displayed.
> Multi-party bridges have two options.
> # Display nothing
> # Display a comma delineated list of the channels in the bridge with you when you enter/exit.
> Note that the PeerAccount field should also be populated.

--
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