[asterisk-dev] Asterisk Realtime Updates - LDAP - Enable Option

Andrew Latham lathama at gmail.com
Sun Jan 20 20:36:12 CST 2013

On Sun, Jan 20, 2013 at 9:27 PM, Matthew Jordan <mjordan at digium.com> wrote:
> On 01/20/2013 07:47 PM, Andrew Latham wrote:
>> On Sun, Jan 20, 2013 at 8:34 PM, Matthew Jordan <mjordan at digium.com> wrote:
>> On this issue.  I did some digging and on a simple "svn co, configure,
>> make, make install, make samples, asterisk -c" many of the realtime
>> and other "modules" attempt to connect to localhost servers (ldap,
>> odbc, pgsql, etc).  The logs show that because the configs are
>> commented or empty they use the defaults to attempt to connect.  In
>> some cases multiple times during load by calling reload. This was not
>> confined to realtime. I noticed that "motif" does this too.
>> If there is a reason that this should be happening by default then hit
>> me with the clue bat.
> I think the problem here is the assumption that 'make samples' produces
> a set of configuration files that are suitable for some definition of a
> basic installation. That isn't the case.
> Currently, the sample configuration files serve primarily as
> documentation of existing configuration options and examples of those
> configuration options. While those examples illustrate how things *can*
> be set up, that doesn't mean those examples translate perfectly to real
> world systems.
> A number of people have proposed either re-purposing the existing sample
> configuration files to act as a recommended configuration or, barring
> that, creating additional make targets/sets of files that act as a basic
> configuration for certain Asterisk deployments. To date, no one has
> created those.
> As a first step to re-purposing the existing sample configuration files,
> the documentation of configuration information would have to be moved
> out of the configuration files to some other source. A patch that could
> help that was written by Terry Wilson. He wrote an improvement for the
> Configuration Framework and the XML documentation APIs that allow them
> to support documenting configuration information in Asterisk source.
> That patch is currently being worked onto get it ready for another round
> of code review for Asterisk 12.
> --
> Matthew Jordan
> Digium, Inc. | Engineering Manager
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> Check us out at: http://digium.com & http://asterisk.org

Regardless of the sample configs a file with only [general] will spark
this issue.  I am assuming that the modules should not be attempting
to connect.  I also assume it just an issue of man-power.  It is also
possible that the hardcoded usernames and passwords that the modules
use to connect with should be removed.

~ Andrew "lathama" Latham lathama at gmail.com http://lathama.net ~

More information about the asterisk-dev mailing list