[asterisk-bugs] [Asterisk 0018159]: Segfault related to realtime peers and the astDB

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18159 
====================================================================== 
Reported By:                sysreq
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18159
Category:                   Resources/res_odbc
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.13 
JIRA:                       SWP-2464 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-18 20:59 CDT
Last Modified:              2010-10-29 13:21 CDT
====================================================================== 
Summary:                    Segfault related to realtime peers and the astDB
Description: 
I'm just formulating an hypothesis here (from the backtrace), but the
problem seems to be related to realtime peers cached into astDB, then used
upon restart until the user registers again and a new realtime query is
executed to populate the peer's information.

sip.conf:

rtcachefriends=yes
rtsavesysname=yes
rtupdate=yes
rtautoclear=no
ignoreregexpire=yes

modules.conf:

preload => res_odbc.so
preload => res_config_odbc.so
====================================================================== 

---------------------------------------------------------------------- 
 (0128477) sysreq (reporter) - 2010-10-29 13:21
 https://issues.asterisk.org/view.php?id=18159#c128477 
---------------------------------------------------------------------- 
I'm pretty sure it actually had to do with a peer entry with an empty
'name' field in my Realtime 'sipusers' SQL table.

Oftentimes, Asterisk will look for an entry with an empty 'name' field
(ie. when it receives a UDP packet with no SIP headers and tries to find
out the associated peer).. given that I had such an entry in my 'sipusers'
table, it brought it up and loaded it in memory as a peer entry with no
name, IP address, port, etc.

My guess is that Asterisk then tried to poke the peer ('qualify=yes' by
default in my SQL table) and choked on the fact that it had no name or
other information. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-29 13:21 sysreq         Note Added: 0128477                          
======================================================================