[asterisk-bugs] [JIRA] (ASTERISK-23280) Failed bridge when running ParkAndAnnounce from macro

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-23280:
----------------------------------------

The key here is that the macro execution is occurring as a result of an execution from an {{applicationmap}} in {{features.conf}} - that is, when the channel is in the Macro (or GoSub), it is actually already in an existing bridge.

ParkAndAnnounce is calling {{ast_bridge_join}} to join the holding bridge. However, since that is occurring while a channel is in the bridge, {{bridge_channel_internal_join}} detects that the channel is in a bridge and bails.

Basically, any application that wants to join a bridge should also check to see if the channel is already in a bridge. If we are in a bridge, we should simply get moved from our existing bridge to the new one.
                
> Failed bridge when running ParkAndAnnounce from macro
> -----------------------------------------------------
>
>                 Key: ASTERISK-23280
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23280
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_parkandannounce, Core/Bridging, Features/Parking
>    Affects Versions: 12.0.0
>            Reporter: Anders Larsson
>            Severity: Minor
>
> In Asterisk 11.6 you can park a call from a macro by calling the ParkAndAnnounce application.
> In 12.0.0 it's not longer possible.
> When trying to do so, you get this error and the ParkAndAnnounce application ends.
> {noformat}
> DEBUG[7118][C-00000000]: bridge_channel.c:1994 bridge_channel_internal_join: Bridge 9f437397-4864-4351-bf29-b37e6ccacf12: 0x16e3768(SIP/vpn-sbc-00000001) failed to join Bridge
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira