[asterisk-bugs] [Asterisk 0017677]: [regression][patch] Core dump when loading sip peers

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17677 
====================================================================== 
Reported By:                outcast
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17677
Category:                   Channels/chan_sip/General
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 278131 
Request Review:              
====================================================================== 
Date Submitted:             2010-07-20 14:20 CDT
Last Modified:              2010-07-24 08:04 CDT
====================================================================== 
Summary:                    [regression][patch] Core dump when loading sip peers
Description: 
When I load the following peer asterisk core dumps

[sip.broadvoice.com]
type=peer
user=phone
host=sip.broadvoice.com
fromdomain=sip.broadvoice.com
fromuser=4137711403
secret=xxxxxx
username=4137711403
insecure=port,invite
context=from-broadvoice
authname=4137711403
fromsipuri=sip:4137711403 at sip.broadvoice.com
dtmfmode=inband
dtmf=inband
;Disable canreinvite if you are behind a NAT
canreinvite=no
nat=no

====================================================================== 

---------------------------------------------------------------------- 
 (0124942) elguero (reporter) - 2010-07-24 08:04
 https://issues.asterisk.org/view.php?id=17677#c124942 
---------------------------------------------------------------------- 
Sure, no problem:

[peer1]
context=peer1context
type=peer
host=192.168.1.2
callbackextension=9991
directmedia=no
insecure=port,invite
dtmfmode=rfc2833
qualify=yes
disallow=all
allow=ulaw
nat=no

[peer2]
context=peer2context
type=peer
host=192.168.1.2
callbackextension=9992
directmedia=no
insecure=port,invite
dtmfmode=rfc2833
qualify=yes
disallow=all
allow=ulaw
nat=no 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-24 08:04 elguero        Note Added: 0124942                          
======================================================================