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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17010 
====================================================================== 
Reported By:                hugolivude
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   17010
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Target Version:             1.6.2.9
Asterisk Version:           SVN 
JIRA:                       SWP-1299 
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-05-11 07:31 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0121695) eeman (reporter) - 2010-05-11 07:31
 https://issues.asterisk.org/view.php?id=17010#c121695 
---------------------------------------------------------------------- 
hugolivude:

1. if you are using insecure=port,invite to match on IP, then type=peer
not friend
2. if you are trying to thwart unauthorized access to your box, consider
allowguest=no in your [general] section
3. your asterisk box is running from an RFC1918 address, you should be
declaring an externip and localnets in [general]

[general]
externip = 200.201.202.203
localnet=192.168.2.0/255.255.255.0 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-11 07:31 eeman          Note Added: 0121695                          
======================================================================