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

[Thomas Sevestre (JIRA)]

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

Thomas Sevestre commented on ASTERISK-19296:
--------------------------------------------

I've tested with the latest 13 version, the behavior is still the same.

The new AttendedTransfer event is fired at the right moment.
It easy to emulate the hangup event.

> 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 was sent by Atlassian JIRA
(v6.2#6252)