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

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-27349:
-----------------------------------

    Assignee: Vasilis Agg  (was: Unassigned)
      Status: Waiting for Feedback  (was: Triage)

This specific behavior has always been undefined at best. Calling something like ConfBridge inside of a DTMF feature like that is not the best thing to do.

Instead of trying to be in a bridge while in a bridge can the ChannelRedirect[1] dialplan application be used to redirect the channel out of the current bridge and into the dialplan where it can then enter the ConfBridge?

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Application_ChannelRedirect


> 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: Vasilis Agg
>         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)