[asterisk-bugs] [JIRA] (ASTERISK-20679) Not redirected call when atxfer. Subscriber who transfers a call, can not connect to the third party.

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-20679:
------------------------------------

    Attachment: CLI log.txt

attaching "CLI log.txt" so some can view in browser.
                
> Not redirected call when atxfer. Subscriber who transfers a call, can not connect to the third party.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20679
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20679
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.10.1, 1.8.16.0, 1.8.18.0
>         Environment: Linux 2.6.31, ARMv5TE(Marvell 88F6281 SoC)
>            Reporter: alexandr kurkin
>            Severity: Critical
>         Attachments: CLI log, CLI log.txt, wireshark
>
>
> We call from one client to another. On the second  press "*2". Hear "transfer". Then dial the number of the third party. The third subscriber rings. We pick up on it. But the connection between second and third is not established. In the console I don`t see a message of third subscriber`s answer. Then I hang up second subscriber. But the first and the third is not connected. Then I hang up the first and the third subscribes. 
>  And then in the console I see periodically message:
> "[Nov 13 11:54:45] WARNING[2397]: chan_sip.c:3918 __sip_autodestruct: Autodestruct on dialog '3a617f3264cc2f6104a3dc5f7...]
> I recorded all of the packages that are currently being send to each other subscribers, but did not see anything incorrect.
> I am attaching wireshark`s dump and CLI log.
> Our asterisk is compiled without LOW_MEMORY flag.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira