[asterisk-bugs] [JIRA] (ASTERISK-29469) Transfer target remains on hold after remote attended transfer

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue Jun 8 09:54:08 CDT 2021


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

Asterisk Team commented on ASTERISK-29469:
------------------------------------------

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/].

> Transfer target remains on hold after remote attended transfer
> --------------------------------------------------------------
>
>                 Key: ASTERISK-29469
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29469
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 15.7.2, 18.4.0
>            Reporter: Ben Smithurst
>              Labels: patch
>         Attachments: transfer-fix.diff
>
>
> We had a problem where a remote attended transfer would leave the transfer destination on hold, with that person only hearing hold music, but the original caller hearing the transfer target.
> We run an Asterisk cluster and customers do not necessarily always receive and place calls via the same server.
> So for example:
> * A calls B (via Asterisk server X)
> * B puts A on hold, and places a new call to the transfer target C (via Asterisk server Y)
> * B speaks to C and then initiates transfer
> * B's phone puts C on hold via server Y and then immediately sends a REFER to Asterisk server X which then handles it via an 'external_replaces' hook, and routes an INVITE-with-Replaces to Asterisk server Y
> * Asterisk server Y completes the transfer BUT doesn't take C off hold.
> The attached patch fixes this problem.  It looks like Asterisk already takes calls off hold when there isn't a remote transfer (i.e. external_replaces hook) involved, so I'm hoping this is correct behaviour.  We've had it in production for around 48 hours now and multiple customers have confirmed it fixes their problem and we've had no new problems reported.
> Please note we've confirmed the fix on 15.7.2 only - we reproduced the problem on 18.4.0 but have not reproduced the problem there as we have reverted our production systems to 15.7.2 for the time being for other reasons.



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



More information about the asterisk-bugs mailing list