[asterisk-bugs] [Asterisk 0010305]: SIP peer re-register using Realtime causes to loop and segfault.

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Jul 26 12:06:45 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10305 
====================================================================== 
Reported By:                punkgode
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10305
Category:                   Addons/res_config_mysql
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:            1.2.22  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-25-2007 15:08 CDT
Last Modified:              07-26-2007 12:06 CDT
====================================================================== 
Summary:                    SIP peer re-register using Realtime causes to loop
and segfault.
Description: 
When a SIP peer re-register on Asterisk, it starts looping with SIP OPTIONS
requests and SQL Requests, causing it to hang after a short period of
time.

Using 
- SIP client Twinkle v0.9 (also with Linksys PAP2)
- Asterisk 1.2.22 (app_queue modified, nothing to do here)
- SIP realtime setup with res_mysql_config.
====================================================================== 

---------------------------------------------------------------------- 
 punkgode - 07-26-07 12:06  
---------------------------------------------------------------------- 
It presents the same problem using ODBC with a MySQL, it loops and
segfaults.

Update:
The problem doesn't show up using rtcachefriends=yes
The problem is that if I use that option, changes to the database won't
have an impact on Asterisk until I manually do a sip reload. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-26-07 12:06  punkgode       Note Added: 0067933                          
======================================================================




More information about the asterisk-bugs mailing list