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

[Jonathan Rose (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221238#comment-221238 ] 

Jonathan Rose commented on ASTERISK-24027:
------------------------------------------

I've got a fairly simple patch that fixes the channel from being kicked from the bridge afterward, but I don't know if its realistically going to be feasible to get the dynamic feature to keep running when the mixmonitor sets the soft hangup flag the way it is currently doing so. The dynamic features themselves are running through one of pbx_exec, macros, or gosub and from that point whatever application is running is going to see the soft hangup flag first and act on it. I'm not sure what to do about this at the moment.

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