|Summary:||ASTERISK-16905: Asterisk crashes on an incoming call from an automatic created SIP peer (autocreatepeer=yes)|
|Reporter:||Loic Didelot (voipgate)||Labels:|
|Date Opened:||2010-11-03 03:30:18||Date Closed:||2012-01-28 11:54:11.000-0600|
|Environment:||Attachments:||( 0) 5363-backtrace.txt|
|Description:||I have autocreatepeer=yes in my sip.conf with a context that that does not allow outbound calls. While testing I provided accidentally wrong credentials to my SIP phone (Linksys SPA 941).|
In the gap where the SIP phone did not register calls were rejected by asterisk.
[2010-11-03 09:21:56] NOTICE: chan_sip.c:21187 handle_request_invite: Failed to authenticate device "SIP phone" <sip:firstname.lastname@example.org>;tag=cb5438a4837a1267o0
Once the phone registered, the peer has been created in asterisk and I can see the peer by using "sip show peers". If I now launch a call asterisk crashes.
****** ADDITIONAL INFORMATION ******
Here is my sip.conf
bindport = 5060
bindaddr = 0.0.0.0
context = INCOMING
; codec settings
|Comments:||By: Paul Belanger (pabelanger) 2010-11-03 08:02:24|
Thank you for your bug report. In order to move your issue forward, we require a backtrace from the core file produced after the crash. Please see the doc/backtrace.txt file in your Asterisk source directory.
Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:
after enabling, reproduce the crash, and then execute the instructions in doc/backtrace.txt.
When complete, attach that file to this issue report. Thanks!
By: Loic Didelot (voipgate) 2010-11-10 16:26:43.000-0600
I noticed that the crash does not happen with every SIP client. For example with Twinkle asterisk did not crash with BRIA or a Linksys SPA asterisk did crash.
By: David Vossel (dvossel) 2010-12-23 15:53:28.000-0600
Is this resolved by 18504?
By: Paul Belanger (pabelanger) 2012-01-28 11:54:05.501-0600
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