[Home]

Summary:ASTERISK-24681: Asterisk restarts during attended transfer if on-hold peer is disconnected before the ringing tones are heard
Reporter:Max Man (maxman)Labels:
Date Opened:2015-01-13 15:57:03.000-0600Date Closed:2015-02-20 19:19:05.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:13.0.1 Frequency of
Occurrence
Constant
Related
Issues:
is related toASTERISK-25003 Asterisk crashes on attended transfer (using feature)
Environment:FREEPBX Distro 6.12.65-22. faxdetect=no context=from-sip-external callerid=Unknown notifyringing=yes notifyhold=yes tos_sip=cs3 tos_audio=ef tos_video=af41 alwaysauthreject=yes useragent=FPBX-12.0.13(13.0.1) disallow=all allow=ulaw allow=alaw allow=gsm allow=g726 allow=g722 progressinband=no callevents=no language=ru rtpend=20000 rtpstart=10000 bindport=5060 jbenable=no minexpiry=60 defaultexpiry=120 registerattempts=0 maxexpiry=3600 notifyhold=yes notifyringing=yes srvlookup=no allowguest=no g726nonstandard=no videosupport=no maxcallbitrate=384 canreinvite=no rtptimeout=30 rtpholdtimeout=300 rtpkeepalive=0 checkmwi=10 registertimeout=20 nat=yes Attachments:
Description:Making internal call from (1) ext to (2) another, answering the call on (2), pushing ** (which is feature code for attended transfer), dialing the ext number (f.e. 222) on (2) and at the same time (before the ringing tones are heard) hanging down the (1) phone, after that getting the following in the console:

ERROR[2969]: astobj2.c:116 INTERNAL_OBJ: user_data is NULL
Disconnected from Asterisk server
Asterisk cleanly ending (0).
Executing last minute cleanups

Asterisk process is restarted... seems like this bug can cause all active calls to disconnect.
Comments:By: Matt Jordan (mjordan) 2015-01-13 19:47:55.735-0600

Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:

make install

After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace



By: Rusty Newton (rnewton) 2015-01-29 18:43:38.990-0600

Max, we will need to close this issue out if you can't provide a backtrace. We don't have your exact configuration and therefore cannot reproduce this issue.

Without a backtrace we have nothing to go on...