[asterisk-bugs] [Asterisk 0017011]: Context statement removed from [general] section of sip.conf, but remained active even after a reload

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17011 
====================================================================== 
Reported By:                hugolivude
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17011
Category:                   Core/Configuration
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.1.17 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-03-11 21:00 CST
Last Modified:              2010-03-15 10:22 CDT
====================================================================== 
Summary:                    Context statement  removed from [general] section of
sip.conf, but remained active even after a reload
Description: 
Cent OS 5.0

When a context in the [general] section of sip.conf is removed, it
persists even after a reload. I discovered this while troubleshooting issue
https://issues.asterisk.org/view.php?id=17010.  

I have sip.conf this way:

[general]
context=incoming-bogus-calls
.
.
.
[voip-provider]
context=ValidIncoming
.
.
.

I found that asterisk was sending calls from my voip-provider to
“incoming-bogus-calls” instead of “ValidIncoming”.  I removed
context=incoming-bogus-calls
from the [general] section and did a reload but Asterisk continued to try
and send the calls to “incoming-bogus-calls” as indicated in the sip
debug messages.

I rebooted and this behaviour ceased - the calls began to be directed to
“ValidIncoming” as expected.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-15 10:22 lmadsen        Status                   new => closed       
2010-03-15 10:22 lmadsen        Resolution               open => no change
required
======================================================================