[asterisk-bugs] [JIRA] (ASTERISK-24764) AMI event notification of linkedid propagation

John Bigelow (JIRA) noreply at issues.asterisk.org
Fri Feb 6 08:53:35 CST 2015


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

John Bigelow updated ASTERISK-24764:
------------------------------------

    Attachment: full.txt

> AMI event notification of linkedid propagation
> ----------------------------------------------
>
>                 Key: ASTERISK-24764
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24764
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: SVN, 13.1.1
>         Environment: Asterisk branches 13
>            Reporter: John Bigelow
>         Attachments: full.txt
>
>
> There is a situation where the linkedid of the BRIDGE_ENTER CEL event isn't what is expected due to how and when linkedid propagation occurs. It's expected that at least one of the two BRIDGER_ENTER CEL events would have a linkedid containing the channel ID of the other channel it has been bridged with. There is not any further CEL AMI events that indicate the change when the propagation occurs. The situation is as follows and the attached log demonstrates it:
> * 'alice' enters Stasis(App_A).
> * 'bob' enters Stasis(App_B).
> * AMI {{Bridge}} action is executed with alice as channel1 and bob as channel2.
> * bob enters the bridge *first* (usually alice enters first). The {{linkedid}} of the BRIDGER_ENTER CEL event for bob is *bob*.
> * alice enters the bridge *second*. The {{linkedid}} of the BRIDGER_ENTER CEL event for alice is *alice*.



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



More information about the asterisk-bugs mailing list