Summary:	ASTERISK-26110: bridge: Crash when performing attended transfer
Reporter:	Denis S.Davydov (denis.davydov)	Labels:
Date Opened:	2016-06-11 12:14:18	Date Closed:	2016-06-24 11:51:33
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Core/Bridging/bridge_basic
Versions:	13.9.1	Frequency of Occurrence
Related Issues:
Environment:	Virtual Machine on ESXi6 (VM Version 8, 4vCPU, 8Gb RAM), OS: CentOS release 6.7 (Final) i386	Attachments:	( 0) backtrace.txt
Description:	I have core dump. Asterisk-PBX 13.9.1 on CentOS release 6.7 (Final).
Comments:	By: Asterisk Team (asteriskteam) 2016-06-11 12:14:19.082-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Denis S.Davydov (denis.davydov) 2016-06-11 12:15:34.289-0500 See backtrace.txt attached. By: Joshua C. Colp (jcolp) 2016-06-13 10:13:32.093-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information Specifically for this case more information about what was going on at the time and the Asterisk log. By: Denis S.Davydov (denis.davydov) 2016-06-14 05:45:52.941-0500 Joshua, my Asterisk-PBX working on a heavy load. Almost all calls are coming from the call-center and the automatic alerting system which working thru AMI. I cannot reproduce this issue, because my log files are not in debug mode and I have a lot of calls at this time with bridging. Also I didn't see such type of crash from the beginning of using Asterisk 13. I will setup log files to debug mode and let you know if Asterisk-PBX will crash again. Thank you for your attention. By: Denis S.Davydov (denis.davydov) 2016-06-15 10:06:48.386-0500 Today I've got similar crash. My full logfile has been attached within lastest backtrace (I have already recompiled my Asterisk with DONT_OPTIMZE flag and BETTER_BACKTRACE). Please, take a look at attached files. Crashing after that snippet: {code} [Jun 15 12:34:25] DEBUG[4182][C-00002665] bridge_native_rtp.c: Bridge '33770058-eebb-4c05-bab4-9fcefb23361d' can not use native RTP bridge as channel 'SIP/3133-00007080' has features which prevent it [Jun 15 12:34:26] DEBUG[4182][C-00002665] bridge.c: Bridge technology native_rtp is not compatible with properties of existing bridge. [Jun 15 12:34:26] DEBUG[4182][C-00002665] bridge.c: Chose bridge technology simple_bridge [Jun 15 12:34:26] DEBUG[4182][C-00002665] bridge.c: Bridge 33770058-eebb-4c05-bab4-9fcefb23361d is already using the new technology. [Jun 15 12:34:26] DEBUG[4182][C-00002665] bridge.c: Bridge 33770058-eebb-4c05-bab4-9fcefb23361d: 0x63f791fc(SIP/3133-00007080) is joining simple_bridge technology [Jun 15 12:34:26] DEBUG[3287][C-0000261e] audiohook.c: Read factory 0x1dd4e404 and write factory 0x1dd4ee24 both fail to provide 160 samples [Jun 15 12:34:26] DEBUG[4185][C-00002664] res_rtp_asterisk.c: Unknown RTCP packet (pt=207) received from 212.248.28.10:47271 [Jun 15 12:34:26] DEBUG[4207][C-00002666] audiohook.c: Failed to get 160 samples from read factory 0xbff702cc {code} By: Joshua C. Colp (jcolp) 2016-06-16 12:05:26.216-0500 I've removed the other attachments as they are the issue being tracked at ASTERISK-26116. Have you seen a reoccurance of the issue reported here and gotten a full console log from it? By: Denis S.Davydov (denis.davydov) 2016-06-24 03:50:01.054-0500 I think all previous crashes were caused by CentOS 6.8 i386 with PAE that worked on 8Gb RAM. We reinstall the same version of Asterisk on CentOS 6.8 x86_64. Thrid day all is norminal. By: Joshua C. Colp (jcolp) 2016-06-24 11:51:33.492-0500 Since you've mentioned this appears to be isolated to the PAE environment and seems to be outside of Asterisk, I'm closing this out. If you exhibit the same problem under non-PAE feel free to comment and this issue will reopen. Just ensure you attach updated logs and information.