[asterisk-bugs] [JIRA] (ASTERISK-24529) Using AMI Action Bridge to on an already bridged channel causes the incorrect return priority to be used

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-24529:
------------------------------------

    Status: Open  (was: Triage)

> Using AMI Action Bridge to on an already bridged channel causes the incorrect return priority to be used
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24529
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24529
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging
>    Affects Versions: SVN, 12.7.0, 13.0.0
>            Reporter: Corey Farrell
>            Severity: Minor
>
> When using "Action: Bridge" on two channels in dialplan, after one channel hangs up, the other normally goes to the next priority in dialplan.  For example use this method to bridge channel 1 and 2, then bridge channel 1 and 3.  When channel 1 is removed from the first bridge, channel 2 will be sent to the next priority in dialplan.  If channel 3 hangs up before channel 2, channel 2 will by sent to the same priority it originally came from.  Found through testsuite: tests/bridge/bridge_action, channel 3 goes back to Echo() at the end of the test and never hangs up.
> This is related to {{AST_FLAG_IN_AUTOLOOP}}.  When the channel is in a dialplan app and "Action: Bridge" is run, it tells the bridge that the return priority should be current + 1.  The flag is set while the channel is within {{__ast_pbx_run}}, but not when the channel is already in a bridge initiated by AMI.  So when the channel is rebridged it does nothing causes dialplan to advance to the next priority.



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