[asterisk-bugs] [JIRA] (ASTERISK-25641) bridge: GOTO_ON_BLINDXFR doesn't work on transfer initiated channel

[Dmitry Melekhov (JIRA)]

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

Dmitry Melekhov commented on ASTERISK-25641:
--------------------------------------------

Richard, then you did a mistake, just because I never said it works as expected.

I commented that I got attended transfer working , which I tried by Joshua suggestion, but this is just another way to get n-way conference.

Original problem- GOTO_ON_BLINDXFR doesn't work on transfer initiated channel - still exists.
Please, fix it, or , if this behavior change it transition from asterisk 11 to 13 is by design, confirm this change.
Thank you!


> bridge: GOTO_ON_BLINDXFR doesn't work on transfer initiated channel
> -------------------------------------------------------------------
>
>                 Key: ASTERISK-25641
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25641
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging/bridge_basic
>    Affects Versions: 13.6.0
>         Environment: Centos 7 x86-64
>            Reporter: Dmitry Melekhov
>            Assignee: Unassigned
>         Attachments: blind-ast11, blind-ast13
>
>
> Hello!
> I'm trying to get n-way call on asterisk according to instructions here
> http://habrahabr.ru/sandbox/52259/
> although it is in russian, dialplan is quite obvious, and it works in asterisk 11,
> but doesn't work in asterisk 13 because GOTO_ON_BLINDXFR macro is executed only for one channel, namely another side of transfer, but no for channel initiated transfer.
> As I know, this change is not documented, so I assume this is bug.
> I'll attach console output for asterisk 11 and asterisk 13.
> Thank you!



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