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

[Richard Mudgett (JIRA)]

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

Richard Mudgett updated ASTERISK-25641:
---------------------------------------

    Attachment: jira_asterisk_25641_v13.patch

[^jira_asterisk_25641_v13.patch] - This should fix the GOTO_ON_BLINDXFR issue.  We were calling a function with invalid parameters which the function checked and just simply returned.  If assertions were enabled you would have had an assertion triggered.

Please test the patch.  Thanks.

[~mjordan] The delimiter could be either '^' or ',' since the first thing the function does is convert the '^' delimiters to commas.

> 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, jira_asterisk_25641_v13.patch
>
>
> 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)