[asterisk-bugs] [JIRA] (ASTERISK-22804) Redirecting two bridged lines via AMI causes race condition, preventing the second redirect from working properly.

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-22804:
------------------------------------

    Status: Waiting for Feedback  (was: Triage)
    
> Redirecting two bridged lines via AMI causes race condition, preventing the second redirect from working properly.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22804
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22804
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.5.1, 11.6.0
>         Environment: CentOS    AMI
>            Reporter: Jeff Hoppe
>            Assignee: Jeff Hoppe
>         Attachments: ConferenceCallIssue.pdf, fullGBBGB, issuesample, nonissuesample
>
>
>  The scenario is agent is connected to a customer in a queue.  Agent redirects customer to ConfBridge via AMI command in application.  Agent calls third party and connects., the two channels are bridged.   We execute two AMI redirects to put the agent and 3rd party into  the ConfBridge that the customer is sitting in.  This will happen successfully at times but other times we will have the following  issue.    The first redirect call will put the 3rd party in the ConfBridge, and the second redirect will hang up the Agent and proceed to dial the 3rd party phone number again.   When this happens we have to hang up on this extra DIAL attempt and put ourselves back in the ConfBridge to get things back to where we should be.	
> 	We are upgrading from Asterisk 10 to Asterisk 11.   This issue happens on 11.5.1 but does not happen in 10.11.  
> 	
> 	I attached a PDF file that will explain what I have found. 
> 	
> 	All the information is gathered from testing on version 11.5.1, before I created this bug tracker entry, I did verify that it is an issue on 11.6.0 as well.
> 	
> 	
> 	Attached files:
> 	
> 		Issuesample  -->  This shows the DEBUG for a call that has this issue.
> 		nonIssuesample  -->  This shows the DEBUG for a call that does not have this issue.
> 		fullGBBGB --> This shows 5 calls in a row where the first and fourth scenarios are good and the rest are bad.

--
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