[Home]

Summary:ASTERISK-21778: astobj2.c:115 INTERNAL_OBJ: user_data is NULL followed by Segmentation fault on cancelled divert
Reporter:Antony Nikrooz (anikrooz)Labels:
Date Opened:2013-05-10 04:06:44Date Closed:2013-05-30 11:46:05
Priority:CriticalRegression?
Status:Closed/CompleteComponents:
Versions:1.8.17.0 Frequency of
Occurrence
Frequent
Related
Issues:
Environment:Centos 5.8 (kernel 2.6.18) with chan_capi 1.1.4 and Divas4linux 3.0 branchAttachments:( 0) asterisk_crashing.txt
Description:This issue is reproducable in the following way:
Call comes in on ISDN (CAPI) channel, Asterisk connects to SIP (going via MS Lync to Exchange 2010 UM). UM server tries to forward call to another extension on ISDN (Alcatel PABX). Lync sends SIP INVITE to Asterisk, ISDN line starts ringing.
If I then hang up incoming call (ISDN->*sk->Lync), the Lync->*sk->ISDN call doesn't stop ringing. When call is answered, Asterisk crashes:

{noformat}

[2013-05-10 09:24:53] ERROR[5502]: astobj2.c:115 INTERNAL_OBJ: user_data is NULL
lemonade*CLI>
Disconnected from Asterisk server
[root@lemonade asterisk]# /usr/sbin/safe_asterisk: line 145:  5485 Segmentation fault      (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY}
Asterisk ended with exit status 139

{noformat}

Full SIP debug will be attached
Comments:By: Richard Mudgett (rmudgett) 2013-05-10 10:34:00.537-0500

Please attach traces as *.txt files instead of pasting them into comments.  See More-Actions pull down menu and select Attach files.

You may find it helpful to read the Asterisk Issue Guidelines http://www.asterisk.org/developers/bug-guidelines.

By: Rusty Newton (rnewton) 2013-05-10 12:53:12.205-0500

Deleted inline debug post. Please follow the guidelines as Richard recommends above.

Please also read over https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace and follow the instructions found there. You'll want to attach the resulting traces to this issue.

By: Antony Nikrooz (anikrooz) 2013-05-13 02:52:17.821-0500

SIP trace

By: Antony Nikrooz (anikrooz) 2013-05-13 02:52:56.061-0500

SIP Trace attached as .txt file as requested

By: Matt Jordan (mjordan) 2013-05-13 09:56:38.587-0500

Actually, what Rusty requested was a backtrace from the crash. Please follow the instructions at the linked wiki article. Make sure you've compiled Asterisk with DEBUG_THREADS and BETTER_BACKTRACES.

By: Rusty Newton (rnewton) 2013-05-30 11:45:56.772-0500

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines