[asterisk-bugs] [Asterisk 0012693]: sip reload doesn't add new peers

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12693 
====================================================================== 
Reported By:                marsosa
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12693
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0-beta8 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-20-2008 19:08 CDT
Last Modified:              05-20-2008 20:50 CDT
====================================================================== 
Summary:                    sip reload doesn't add new peers
Description: 
I'm testing 1.6.0beta8 and beta9 and in both versions i have the same
problem: when i add new peers to a file included in sip.conf and then do a
sip reload (or full reload) the new peer doesn't appears to be added until
a full restart.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 05-20-08 20:50  
---------------------------------------------------------------------- 
Okay, I believe that I have narrowed the problem down some, and in a way it
is a problem specific to sip.conf.

What happens is that res_phoneprov also parses sip.conf. The problem is
that the included file is only cached in the instance when res_phoneprov
parses sip.conf. As a result, when chan_sip asks to reload sip.conf, we
don't check the status of the cached included file because it was not
properly cached to begin with. This would happen if any configuration file
is parsed by two separate source files.

A workaround for the issue is to unselect res_phoneprov in menuselect and
remove res_phoneprov.so from /usr/lib/asterisk/modules/ but that is not the
long-term solution. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-20-08 20:50  putnopvut      Note Added: 0087092                          
======================================================================