[asterisk-bugs] [JIRA] (ASTERISK-30102) Hangup_handler not invoked

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-30102:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Hangup_handler not invoked
> --------------------------
>
>                 Key: ASTERISK-30102
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30102
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_simple
>    Affects Versions: 18.0.1
>         Environment: Hosted in Azure
>            Reporter: Morten Sølvberg
>            Severity: Major
>
> I am recording calls with MixMonitor, and I am using "hangup_handler_push" on all calls I crate/receive, to make sure that the calls are always sent to the same location in the dialplan where I move the recording to a mounted drive.
> This usually works fine, but I see that when I use the Bridge command, then the hangup_handler is removed for the *Briged* party. 
> I assume that this happens due to the masquerade functionality in Asterisk, and that the hangup_hanlder isn't copied to the new channel. 
> I can see the hangup_handler being invoked on Surrogate channel, but not on the actual channel.
> Lukily I can use the F option in the Bridge command, so the *Bridged* party is sent to another place in the dialplan when the *Bridger* hangs up.
> This also works fine.
> However if the *Bridged* party hangs up, then the channel is not sent to the defined localion in the dialplan.
> I have an h extension in all the the contexts that the channel has been in, but it does not hid any of these either.
> Is this a known issue and/or can you think of a workaround?



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