[asterisk-bugs] [Asterisk 0010882]: Settings in sip.conf are not processed

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=10882 
====================================================================== 
Reported By:                BuddyButterfly
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   10882
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 not fixable
Fixed in Version:           
====================================================================== 
Date Submitted:             10-04-2007 00:34 CDT
Last Modified:              10-04-2007 08:19 CDT
====================================================================== 
Summary:                    Settings in sip.conf are not processed
Description: 
OSes:
 1. SuSE 9.3, Kernel 2.6.11
 2. Debian etch 4.0, Kernel 2.6.18

Asterisk version: 1.4.11

When I started with Asterisk I really lost some of my hair due to this
problem. The result was that specific settings in sip.conf did not work and
didn't show up in the debug files. It seemed they were ignored. I used the
standard template
 and left the comments in it as an help. To separate configuration from
comments
 I added all settings at the end of the comment section. The problem was,
that
 the settings like externhost, sipdebug etc. did not work. By chance I
discovered that setting the sipdebug by activating it at the place where it
was
 commented out, it worked. So placing all settings at the beginning of the

comment section just after the [general] context solved the problem. This
can
be easily reproduced by placing the properties directly at the end of the

comment section (for example sipdebug, externhost).

To me this looks like that properties are ignored depending on the
position in
the config file.

====================================================================== 

---------------------------------------------------------------------- 
 file - 10-04-07 08:19  
---------------------------------------------------------------------- 
This is indeed true, but it is documented which options work in what
places. Users and peers have listings detailing what options are applicable
to them. As for reporting options that aren't read in when put in the wrong
place we can't exactly do that, as for type=friend this would cause options
to reported as incorrect when in fact they were. If you have ideas on
clarifying the documentation so others will not face this feel free to
submit a patch. Peace! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-04-07 08:19  file           Status                   new => resolved     
10-04-07 08:19  file           Resolution               open => not fixable 
10-04-07 08:19  file           Assigned To               => file            
10-04-07 08:19  file           Note Added: 0071451                          
======================================================================