[asterisk-bugs] [JIRA] (ASTERISK-21689) AMI bridge continues to try and bridge even after reporting "Channel2" does not exist; and fails resulting in hangup of Channel1

[Asterisk Team (JIRA)]

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

Asterisk Team closed ASTERISK-21689.
------------------------------------

    Resolution: Suspended

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> AMI bridge continues to try and bridge even after reporting "Channel2" does not exist; and fails resulting in hangup of Channel1
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21689
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21689
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging, Core/ManagerInterface, Features
>    Affects Versions: 11.3.0
>         Environment: CentOS 6
>            Reporter: William luke
>            Assignee: Joshua Colp
>         Attachments: ami.txt, cli.txt
>
>
> Sometimes when executing an AMI Bridge on two channels one of the channels will have hungup and disappeared. Although the timing must be precise for this to occur (the hangup event and the bridge event "passing in transit" so to speak) we're seeing it a few hundred times a day on a busy system.
> The AMI Bridge correctly response that Channel2 does not exist. It then continues to try and do the bridge anyway (!). This results in Channel1 being hungup.
> It's worth noting that if Channel1 doesn't exist it gives the same error, but *does not* try and continue, which to me is the correct behavior.
> This seems to happen regardless of the dialplan, however for our testing we had Channel1 sitting in a Wait loop, like so:
> exten => _X.,1,Answer()
>         same => n,Set(DiallingHub=${EXTEN})
>         same => n,UserEvent(GLDiallingHubJoin,DiallingHub: ${DiallingHub},Channel: ${CHANNEL})
>         same => n(agentinhub),NoOp(AGENT ${EXTEN} waiting in Dialling Hub)
>         same => n,Wait(600)
>         same => n,Goto(agentinhub)
> I've included the AMI output and CLI outputs when this occurs.
> If you need any further details please let me know.



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