[asterisk-bugs] [Asterisk 0017174]: Connection Problem with UnixODBC 2.1.14

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17174 
====================================================================== 
Reported By:                davidsharon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17174
Category:                   Addons/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.18 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-13 03:16 CDT
Last Modified:              2010-04-14 02:50 CDT
====================================================================== 
Summary:                    Connection Problem with UnixODBC 2.1.14
Description: 

I upgraded UnixODBC version to 2.2.14. 

After installation and configuration, I tried iSql (the new release) for
Oracle 11g. It works without any problem: it can connect and execute SQL
commands.

On Asterisk side, in func_odbc.conf, 

[BLACKLIST]
dsn=oracle
; oracle is defined in odbc.ini as dsn. it works with isql. 
readsql = SELECT count(*) as Say FROM Blacklist where CallerId =
'${SQL_ESC(${ARG1})}'; 

In extensions.conf, we have a voicemenu scenario:

...
[voicemenu-custom-7661]
include = default
exten = s,1,NoOp(IVR_BlackList)
exten = s,2,Answer()
exten = s,3,Set(ARG1=${CALLERID(name)})
exten = s,4,Set(Result=${ODBC_BLACKLIST(${ARG1})})
exten = s,5,GotoIf(${Result}=1?0:)
exten = s,6,Playback(dir-welcome)
exten = s,7,Goto(queues,6500,1)   
...

When this context is executed, res_odbc raises an exception and Asterisk
is stopped.

After checking out the log files and the source code, I realized that we
might have a library-related problem.

Could you please check this case and advise us how to fix it?

Thank you in advance,

David

P.S. Upgrading our Asterisk to 1.6.18 didn't solve this issue.
====================================================================== 

---------------------------------------------------------------------- 
 (0120374) davidsharon (reporter) - 2010-04-14 02:50
 https://issues.asterisk.org/view.php?id=17174#c120374 
---------------------------------------------------------------------- 
The previous version is 1.6.1.12.

Before upgrade, it was NOT working. Assuming that this was a
library-related problem, we thought that upgrading the Asterisk would solve
this situation. But it persists.

odbc.ini and odbcinst.ini are configured correctly and referencing to
right modules. When I use iSql, there is no problem: I can connect and
execute SQL commands over iSQL.

Sure, I will share our config files and logs. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-14 02:50 davidsharon    Note Added: 0120374                          
======================================================================