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

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-26101:
-----------------------------------

    Summary: [patch] Bridge: Channel is not unheld in attended transfer  (was: [PATCH] Atxfer - missing ami unhold event)

> [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
>            Severity: Minor
>
> 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.
> {code}
> diff --git a/main/bridge_basic.c b/main/bridge_basic.c
> index c4cf2a0..2a20898 100644
> --- a/main/bridge_basic.c
> +++ b/main/bridge_basic.c
> @@ -2193,6 +2193,8 @@ static int threeway_enter(struct attended_transfer_properties *props)
>  static int consulting_enter(struct attended_transfer_properties *props)
>  {
> +       unhold(props->transferer);
> +
>         return 0;
>  }
> {code}



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