[asterisk-bugs] [Asterisk 0017010]: When a context is defined in [general] section of sip.conf, other contexts are ignored

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17010 
====================================================================== 
Reported By:                hugolivude
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17010
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
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:              
====================================================================== 
Date Submitted:             2010-03-11 20:47 CST
Last Modified:              2010-03-15 10:21 CDT
====================================================================== 
Summary:                    When a context is defined in [general] section of
sip.conf, other contexts are ignored
Description: 
Cent OS 5.0

When a context is defined in the general section of sip.conf, contexts
defined in other sections are ignored.

Set up sip.conf this way:

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


Calls from my voip-provider should go to “ValidIncoming”, but Asterisk
attempts to send them to “incoming-bogus-calls”

I’ve had sip.conf set up this way for a long time. The idea was
recommended to thwart DOS attacks. It worked in Version 1.4 (and previous
versions) but when I upgraded to 1.6, all calls were sent to
incoming-bogus-calls regardless of source.  I suppose allowguest can be
used now to achieve the desired effect, but the current behaviour is not
backwards compatible.
====================================================================== 

---------------------------------------------------------------------- 
 (0119357) lmadsen (administrator) - 2010-03-15 10:21
 https://issues.asterisk.org/view.php?id=17010#c119357 
---------------------------------------------------------------------- 
Additional information is required. Perhaps there is something else causing
the incoming calls to not match on your peer, and it's not actually the
issue you're seeing that is the problem.

For example, I have the exact same setup that you do (in terms of using
context=default in my [general] section) but that has not stopped me from
using context=incoming_calls in my peer definitions.

Please provide the following:

* Full sip.conf configuration file with passwords removed or obfuscated.
* a SIP trace from the Asterisk console showing the problem you are
having

I'm thinking there is likely a configuration issue here since it sounds
like you upgraded from 1.4 to 1.6.1.x
 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-15 10:21 lmadsen        Note Added: 0119357                          
2010-03-15 10:21 lmadsen        Status                   new => feedback     
======================================================================