[asterisk-bugs] [JIRA] (ASTERISK-29356) Bridge operation (AMI) is rejected if either party is already a member of a bridge

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29356:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Bridge operation (AMI) is rejected if either party is already a member of a bridge
> ----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29356
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29356
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging
>    Affects Versions: 17.5.0, 18.2.0
>         Environment: EL6 and EL8
>            Reporter: Tom Thompson
>            Severity: Major
>
> We have a program that provides a GUI, automated operation and reporting for a telephony agent. It is implemented via  AMI - though the issue is more generic to a bridge operation
> The application can be regarded as 3rd party call control i.e. any client operations are controlling a device residing on the server
> The agent opens a voice path to a dialplan extn running a conference. From there the agent can make calls, take calls, hold calls, transfer calls etc. 
> The agent is also able to transfer together 2 parties connected to the conference. This was successfully done using the bridge command in AMI. The worked well in Asterisk 11.x
> We recently jumped through a few versions of asterisk to Asterisk 17. We notice now that the bridge operation is rejected. This happens even if just one party of the bridge pair already resides on the agent conference. 
> In investigating the issue we got no direction from the debug logs (or at least none that was clear.
> Some experimentation with the code indicated that the rejection occurred at the following lines in 
> file main/bridge.c
> proc bridge_move_locked
> lines 2444
> if (ast_test_flag(&dst_bridge->feature_flags, AST_BRIDGE_FLAG_MASQUERADE_ONLY)
> 		|| ast_test_flag(&src_bridge->feature_flags, AST_BRIDGE_FLAG_MASQUERADE_ONLY)) {
> 		ast_debug(1, "Can't move channel %s from bridge %s into bridge %s, masquerade only.\n",
> 			ast_channel_name(chan), src_bridge->uniqueid, dst_bridge->uniqueid);
> 		return -1;
> 	}
> We feel that this issue relates to functionality worked previously and is a reasonable operation to be performing. For this reason we regard this a a bug.
> I was likely introduced prior to asterisk 17 and the blocking code is in ast* 18.2.0 bridge.c line 2455
> Regards Tom Thompson



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