> On Thu, 2 Dec 2010, Gary Kuznitz wrote:
>
>> You get extra points today. I think you found where the problem is. It
>> found /etc/asterisk/sip.conf Warning parse error: No category context
>> for line 1 of /etc/asterisk/sip.conf Unable to load config sip.conf.
>>
>> This is what is in sip.conf.
>> [authentication]
>>
>> [general]
>> context = default
>> allowoverlap = no
>> bindport = 5060
>> bindaddr = 0.0.0.0
>> srvlookup = yes
>> limitonpeers = yes
>> allow = all
>> allowguest=yes
>
> Running out of clues here :)
Another thought...
Asterisk can be started with a command line option that specifies the path
to it's configuration file. The default is /etc/asterisk/asterisk.conf.
Does 'ps -aef | grep asterisk' show the '-C' option being used?
Also, Asterisk's configuration file can specify where ('astetcdir') it
should look for sip.conf.
I use these feature to keep each of my client's configuration files in
separate directories, but all on the same development box.
--
Thanks in advance,
-------------------------------------------------------------------------
Steve Edwards [email protected] Voice: +1-760-468-3867 PST
Newline Fax: +1-760-731-3000
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
