[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:                
====================================================================== 
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-04-04 08: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.
====================================================================== 

---------------------------------------------------------------------- 
 (0120130) hugolivude (reporter) - 2010-04-04 08:21
 https://issues.asterisk.org/view.php?id=17010#c120130 
---------------------------------------------------------------------- 
Yes I always thought that to be a bit strange, however this is how the VoIP
provider for that number instructs its users to set up sip.conf.  I cut and
pasted sip.conf from a web page they provide.  I re-confirmed that the DiD
6132885759-sw2 does not appear in any form (including 6132885759-sw2) in
the sip settings they recommend.  

I spent several days troubleshooting this w/ them, so If you still feel
their set ups are incorrect or they are not generating the appropriate SIP
signaling for the set up they are recommending, please let me know and I'll
re-open the trouble ticket I created w/ them.

Please note however that the setup I provided worked fine in 1.4.  It's
also working in 1.6, but I had to remove context=incoming-bogus-calls from
the [general] section.  It's the backward compatibility that prompted me to
open this case. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-04 08:21 hugolivude     Note Added: 0120130                          
======================================================================