[asterisk-bugs] [JIRA] (ASTERISK-24027) MixMonitor AMI action called during AGI execution from bridge feature causes channel to leave AGI has hung up

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-24027:
-----------------------------------

    Target Release Version/s: 13.0.0-beta2

> MixMonitor AMI action called during AGI execution from bridge feature causes channel to leave AGI has hung up
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24027
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24027
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_mixmonitor, Resources/res_agi
>    Affects Versions: 12.4.0
>            Reporter: Matt Jordan
>            Assignee: Jonathan Rose
>      Target Release: 12.6.0, 13.0.0-beta2
>
>
> MixMonitor has a check in it that, when applied to a channel, determines if the channel is in a bridge and, if it is, sets the UNBRIDGE soft hangup flag. This is the bridging framework's sign that it needs to check the state of the world.
> Unfortunately, res_agi decides this means that the channel has hung up, kills the AGI, and terminates the whole thing.
> {code}
> [1404943348] DEBUG[10460]: autochan.c:58 ast_autochan_setup: Created autochan 0xb4b96c30 to hold channel PJSIP/201-00000042 (0xb4bf6a04)
> [1404943348] DEBUG[10460]: channel.c:2597 ast_softhangup_nolock: Soft-Hanging (0x40) up channel 'PJSIP/201-00000042'
> [1404943348] DEBUG[31077][C-00000018]: res_agi.c:3809 run_agi: PJSIP/201-00000042 hungup
> <PJSIP/201-00000042>AGI Tx >> HANGUP
> {code}
> You should be able to run the MixMonitor AMI action on a channel that is in an AGI called from a bridge feature and not have it hang up.



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