[asterisk-bugs] [JIRA] (ASTERISK-27349) Failed to join Bridge when calling ConfBridge from applicationmap

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-27349:
--------------------------------------------

The DTMF features (features.conf) supports ad-hock multi-party bridging as an option for attended transfers.  See the features.conf.sample file.  Or you could initially redirect the two parties to a confbridge and then originate other parties into the confbridge conference.

> Failed to join Bridge when calling ConfBridge from applicationmap
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-27349
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27349
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge, Core/Bridging
>    Affects Versions: 13.17.2
>            Reporter: Vasilis Agg
>            Assignee: Unassigned
>         Attachments: debug_log_2, extensions.conf, features_applicationmap.conf
>
>
> In Asterisk 11 it was possible to use a macro to  join a conference by calling the ConfBridge application. In Asterisk 13, it is no longer possible.
> When ConfBridge app is executed i get the following error
> {noformat}
> [Oct 16 10:16:05] DEBUG[26114][C-00000003] bridge_channel.c: Bridge 66a5a549-5e4b-469a-8b18-54845fc65c98: 0xaa474d80(SIP/100-00000006) failed to join Bridge
> {noformat}
> I have find out that bridge_channel_internal_join detects that the channel is in a bridge and returns without joining the bridge. 
> To reproduce the problem first start a call and then the caller has to press *0 to start the macro.The caller fails to join the conference.
> The above error can be found in the debug log.



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