Summary:	ASTERISK-16081: [regression] asterisk sip becomes unresponsive, astobj2.c:115 INTERNAL_OBJ: bad magic number 0x0 for 0x9f0a828
Reporter:	Johann Steinwendtner (steinwej)	Labels:
Date Opened:	2010-05-12 01:15:28	Date Closed:	2010-05-17 13:50:02
Priority:	Major	Regression?	Yes
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) gdb.txt ( 1) sip.trace
Description:	during dialplan configuration I observed a severe problem: normal SIP account: [steinwendtner] type=friend md5secret=efe7d3d521f817dsfghdfghdfh319d53da context=sip_test_context callerid=01229919640 callingpres=allowed host=dynamic mailbox=01229919640@customer dtmfmode=inband canreinvite=no nat=yes progressinband=no language=de qualify=no disallow=all t38pt_udptl=yes,redundancy,maxdatagram=400 allow=alaw simple dialplan: [sip_test_context] exten => 640,1,Hangup sip ATA dials 640, call gets disconnected as expected (603 declined) After this, it becomes unresponsive. SIP ATA cannot register anymore. Sometimes I get tons of: [May 12 07:55:17] ERROR[29092]: astobj2.c:115 INTERNAL_OBJ: bad magic number 0x0 for 0x9f0a828 [May 12 07:55:17] ERROR[29092]: astobj2.c:115 INTERNAL_OBJ: bad magic number 0x0 for 0x9f0a828 sometimes asterisk crashes ****** ADDITIONAL INFORMATION ****** the fix for issue ASTERISK-1654774 seems the cause of it. When I revert this change to the old code, everything seems to work again.
Comments:	By: Leif Madsen (lmadsen) 2010-05-13 09:19:11 If you're getting crashes, please provide the backtrace per doc/backtrace.txt in your Asterisk source. Additionally, if you could provide the SIP trace leading up to these messages, that may also be of use. By: Leif Madsen (lmadsen) 2010-05-13 09:20:21 Also, please verify this is happening on the latest 1.6.2 release as both 1.6.0 and 1.6.1 branches are now security fixes only: --- Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch. More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924 By: Johann Steinwendtner (steinwej) 2010-05-17 07:25:53 Here is the requested information for 1.6.0.27. I could not reproduce the issue on 1.6.2.7 Is the fix for ASTERISK-1654774 really necessary for 1.6.0 ? By: Leif Madsen (lmadsen) 2010-05-17 11:29:06 As this is not an issue in 1.6.2 and the branches of 1.6.0 and 1.6.1 have changed maintenance support I'm suspending this issue. -- Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch. More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924 By: Johann Steinwendtner (steinwej) 2010-05-17 13:35:34 If you are suspending this issue, you are going to suspend the whole 1.6.0.28. No need to make a final version. I' m fine with it, but you need to warn the users. By: Leif Madsen (lmadsen) 2010-05-17 13:50:02 Users have been sufficiently warned about the impending suspension of support for the 1.6.0 and 1.6.1 series for at least 2 month now heavily (and originally announced on http://www.asterisk.org/asterisk-versions in December of 2009). Not all issues could possible be resolved in the 1.6.0 and 1.6.1 branches prior to the end of support, which is why people should switch to 1.6.2 if they require continued maintenance support. For those who directly run into this issue can utilize Asterisk 1.6.2.x. Those who do not have issues with 1.6.0.28 or 1.6.1.20 can continue using those versions for as long as they wish.