[asterisk-bugs] [JIRA] (ASTERISK-26101) [patch] Bridge: Channel is not unheld in attended transfer

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26101:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> [patch] Bridge: Channel is not unheld in attended transfer
> ----------------------------------------------------------
>
>                 Key: ASTERISK-26101
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26101
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging/bridge_basic
>    Affects Versions: 13.9.0
>         Environment: Debian 7.10
>            Reporter: Niclas Larsson
>            Assignee: Niclas Larsson
>            Severity: Minor
>         Attachments: atxfer2.patch, atxfer.patch
>
>
> 1. A calls B
> 2. B starts a atxfer to C
> 3. A => moh, B => hold
> 4. C answers
> 5. A hung up
> 6. B and C is still talking (and the atxfer is aborted) but B is still on hold
> Shouldn't B be unholded as soon as the channel starts dialing or at least when C answers?
> The following patch solves the problem (when C answers) but I'm not quite sure if it's the right place/thing to do.
> Inline patch removed.



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