[asterisk-bugs] [Asterisk 0010690]: sip peer with missing close bracket causes all subsequent sip peers not to load

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=10690 
====================================================================== 
Reported By:                dtyoo
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   10690
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2007-09-10 17:34 CDT
Last Modified:              2008-09-12 18:20 CDT
====================================================================== 
Summary:                    sip peer with missing close bracket causes all
subsequent sip peers not to load
Description: 
We have found that if you leave the trailing square bracket off a given sip
peer name in sip.conf, then you reload chan_sip.so, all peers that would be
loaded after the broken peer do not load.  It looks like the config parser
understands what is wrong as I see the following in the messages file:

config.c: parse error: no closing ']', line 25 of xxxx.sip.conf

But then all the rest of your sip peers disappear.  Obviously the error is
the lack of a closing brace.  But I would think that the impact of this
config error could be minimized if just this sip peer were tossed, and the
next sip peer were loaded normally.  With frequent manual editing of a
large sip.conf this is bound to happen sometime.  This has happened to us a
couple times, each time causing a fairly substantial outage for us as
several thousand sip peers disappear.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-12 18:20 svnbot         Status                   ready for testing =>
resolved
2008-09-12 18:20 svnbot         Resolution               reopened => fixed   
======================================================================