[asterisk-bugs] [JIRA] (ASTERISK-27349) Failed to join Bridge when calling ConfBridge from applicationmap
Joseph Hayhoe (JIRA)
noreply at issues.asterisk.org
Mon Nov 12 16:37:47 CST 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-27349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245418#comment-245418 ]
Joseph Hayhoe edited comment on ASTERISK-27349 at 11/12/18 4:35 PM:
--------------------------------------------------------------------
In response to Richard Mudgett above I can confirm this does work in 12+:
I was able to setup basic 3-way calling using in-built features designed for asterisk 12+. I did this simply by adding the following to /etc/asterisk/features.conf:
atxfer = *2
atxferthreeway = *42
atxferabort = #42
You initiate by starting a transfer via *2. The callee is placed on hold and you are presented with a dial tone. Dial the new number to bring into the 3-way call. Then once you are ready to bridge dial *42 (or whatever you defined above for atxferthreeway). To cancel the 3-way call and go back to the original call dial #42 (or whatever you defined above for atxferabort).
was (Author: jhayhoe):
In response to Richard Mudgett above I can confirm this does work in 12+:
I was able to setup basic 3-way calling using in-built features designed for asterisk 12+. I did this simply by adding the following to /etc/asterisk/features_featuremap_custom.conf:
[general]
atxferthreeway = *42
atxferabort = #42
You initiate by starting a transfer via *2. The callee is placed on hold and you are presented with a dial tone. Dial the new number to bring into the 3-way call. Then once you are ready to bridge dial *42 (or whatever you defined above for atxferthreeway). To cancel the 3-way call and go back to the original call dial #42 (or whatever you defined above for atxferabort).
This uses features already defined as part of atxfer via asterisk. You can see other features defined by checking the features.conf.sample via https://github.com/asterisk/asterisk/blob/master/configs/samples/features.conf.sample
> 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)
More information about the asterisk-bugs
mailing list