No subject


Tue Apr 12 01:01:39 CDT 2011


negative_connection_cache is the number of seconds to cache the
information if there is a problem. Is that correct? Is there anything
that should be considered before changing this figure?

Again, thanks guys for your help.

Kind Regards
Stuart Elvish

On 27 June 2011 21:40, Tilghman Lesher <tilghman at meg.abyt.es> wrote:
> On Monday 27 June 2011 04:26:50 Stuart Elvish wrote:
>> This was originally posted on the asterisk-users list but I didn't
>> receive any responses. Here's hoping that someone on the dev list can
>> point me in the right direction.
>>
>> I currently have 3 servers setup to provide a small MySQL cluster. I
>> can easily run custom database queries via func_odbc and res_odbc with
>> failover DSN's (up to five) but I can't seem to add any failover DSN's
>> into the realtime configuration file (extconfig.conf). Has anyone been
>> able to configure either the standard ODBC driver or Asterisk to use a
>> failover DSN for realtime system configuration?
>>
>> Currently my extconfig.conf has a setup something similar to this:
>> sippeers =3D> odbc,mysql-asterisk,sipendpoints but being
>
> sippeers =3D> odbc,mysql1,sipendpoints,1
> sippeers =3D> odbc,mysql2,sipendpoints,2
> sippeers =3D> odbc,mysql3,sipendpoints,3
>
> and in res_odbc.conf:
>
> [mysql1]
> ...
> negative_connection_cache =3D> 300
>
> [mysql2]
> ...
> negative_connection_cache =3D> 300
>
> --
> Tilghman
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> =A0 http://lists.digium.com/mailman/listinfo/asterisk-dev
>



More information about the asterisk-dev mailing list