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

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-26101:
--------------------------------------------

Please attach a log of the situation.  Off-hand I think this may be a misunderstanding of the hold message.  When B initiates the atxfer, B puts A on hold.  Since A hangs up and thus goes away before the transfer completes there is no need to unhold A.

> [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: Unassigned
>            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)