[asterisk-bugs] [JIRA] (ASTERISK-21362) Segfault during bridge channel proxy inspection in a masquerade caused by an AMI Redirect of two channels
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Fri Mar 29 12:33:02 CDT 2013
Rusty Newton created ASTERISK-21362:
---------------------------------------
Summary: Segfault during bridge channel proxy inspection in a masquerade caused by an AMI Redirect of two channels
Key: ASTERISK-21362
URL: https://issues.asterisk.org/jira/browse/ASTERISK-21362
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: General
Affects Versions: 11.3.0
Environment: CentOS 6.4
Reporter: William luke
Severity: Critical
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
More information about the asterisk-bugs
mailing list