[asterisk-bugs] [JIRA] (ASTERISK-22270) Attended transfer to a Queue stops music on hold on caller

Matt Jordan (JIRA) noreply at issues.asterisk.org
Thu Aug 8 20:29:04 CDT 2013


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

Matt Jordan commented on ASTERISK-22270:
----------------------------------------

This is also a duplicate of ASTERISK-17833. ASTERISK-21317 has someone's private configuration information attached to it, so it is only viewable by bug marshals.

As this is a duplicate of an existing issue, I'm closing it out to that issue.
                
> Attended transfer to a Queue stops music on hold on caller
> ----------------------------------------------------------
>
>                 Key: ASTERISK-22270
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22270
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.4.0
>            Reporter: Etienne Allovon
>         Attachments: issue22270-asterisk-axfer.log
>
>
> When you make an attended transfer to a queue, it stops the music on hold for the caller when attended transfer is completed.
> Here's how to reproduce :
> - Given A calls B (SIP peers),
> => B answers and they both speak to each other,
> - B starts an attended transfer (with phone xfer button) to queue Q1,
> => A is put on hold and hears the music on hold
> - B waits to hear the music of queue Q1 and completes the transfer
> => Though A is queued in Q1, he doesn't hear the music on hold anymore
> In fact, as soon as the _transferrer enters_ the Queue, when he completes the transfer, the transferred has no music on hold anymore.
> For example if you make the following dialplan to reach the Queue :
> {code}
>   exten = 1000,1,Wait(2)
>   same = n,Queue(q1)
> {code}
> If B completes the transfer before being queued in the queue Q1, A will hear the music on hold.
> Notes :
> - This is the same issue as ASTERISK-20230 which was open for 1.6 branch but closed due to end of maintenance,
> - It is also probably the same as a private issue ASTERISK-21317 for 1.8 branch but I can't see it

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list