[asterisk-bugs] [JIRA] (ASTERISK-21356) Segfault during bridge channel proxy inspection in a masquerade caused by an AMI Redirect of two channels

[William luke (JIRA)]

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

William luke commented on ASTERISK-21356:
-----------------------------------------

Thanks for the patch. The not locking while changing pointers fits in exactly with what it looked like was happening, I just had no idea how to find out where.

I've applied this to our system where we were seeing the issues last night, and will let you know how it runs for the next few days.

Again, many thanks for the swift turnaround on this!
                
> Segfault during bridge channel proxy inspection in a masquerade caused by an AMI Redirect of two channels 
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21356
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21356
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 11.3.0
>         Environment: CentOS 6.4
>            Reporter: William luke
>            Assignee: William luke
>            Severity: Critical
>         Attachments: backtrace.txt, debuglog.tar.gz, jira_asterisk_21356_v11.patch
>
>
> Asterisk segfaulted during normal operation.
> After speaking to mjordan on #asterisk he advised that it looks like the a redirect thread (Thread 1) is trying to access a bridged channel using a NULL pointer.
> The scenario is that two channels are in a bridge, and then we execute a dual Redirect (via AMI) to put them both into a ConfBridge, so that we can bring a 3rd party into the call.
> This happens successfully hundreds of times a day on this system, so must be some sort of edge case when it goes wrong.
> I also *should* have a full debug log available, but it's quite a busy system and would be rather a large file (Circa 50Gb/day). I'm sure I could make it available if it would help.
> [gl-agentconf]
> exten => _X.,1,Set(ConfBridgeNumber=99${EXTEN})
>         same => n,NoOp(Putting AGENT into ConfBridge ${ConfBridgeNumber})
> ;       same => n,Set(JITTERBUFFER(fixed)=default);Adaptive with defaults.
>         same => n,Answer()
>         same => n,ConfBridge(${ConfBridgeNumber})
>         same => n,NoOp(Putting AGENT back into their Dialling Hub. Exten: ${EXTEN})
>         same => n,Goto(gl-diallinghub,${EXTEN},agentinhub)
> [gl-customerconf]
> exten => _X.,1,Set(ConfBridgeNumber=99${EXTEN})
> ;       same => n,Set(JITTERBUFFER(fixed)=default);Adaptive with defaults.
>         same => n,NoOp(Putting CUSTOMER into ConfBridge ${ConfBridgeNumber})
>         same => n,Answer()
>         same => n,ConfBridge(${ConfBridgeNumber})

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