[asterisk-bugs] [JIRA] (ASTERISK-19296) Attended transfer and hangup events

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Fri Nov 8 11:30:03 CST 2013


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

Richard Mudgett commented on ASTERISK-19296:
--------------------------------------------

Your issue is in queue, please be patient, and we will get to it as time permits and developer resources become available.


                
> Attended transfer and hangup events
> -----------------------------------
>
>                 Key: ASTERISK-19296
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19296
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Features
>    Affects Versions: 1.8.9.0
>            Reporter: Thomas Sevestre
>            Assignee: Thomas Sevestre
>
> Say we have 3 users with extensions 100, 101 and 102
> 100 call 101
> 101 answers and use the attended transfer features to call 102
> 101 hangup before 102 answers
> => The hangup event (AMI) is not fired immediately (it is fired when 102 answers)
> Edit:
> With atxferdropcall=yes and the same scenario as above, the bridge between 100 and 101 lingers after 101 hangs up until either 102 answers or atxfernoanswertimeout expires.  There is no need for the 100 to 101 bridge to remain once 101 hangs up in this case.  The call to 102 should immediately transfer to 100 in this case.

--
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