On Wed, Apr 13, 2022 at 12:36 PM marek <cervaj...@gmail.com> wrote: > hi, > > working on problem with asterisk+odbc through problematic firewall > (asterisk and DB are on separated machines) > > there is some problem with SQL_ATTR_CONNECTION_DEAD . its not detecting > problematic connection. can be replicated with iptables -I INPUT .. -j DROP > > will you accept patch for forcing sanitysql param ? (force sending > SELECT 1 test) > > if i understand this part of code > > > https://github.com/asterisk/asterisk/blob/b87c5f51248fddd443ad5487e2857d9c754575fa/res/res_odbc.c#L872 > > it will not use sanitysql if SQL_ATTR_CONNECTION_DEAD exist in unixODBC >
That depends on what the patch does. If it adds an option to change how the connection is determined to be dead, yes. -- Joshua C. Colp Asterisk Technical Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
