asterisk users - Oct 2015 - pjsip database error when using MS SQL via ODBC

I have a project that is requiring the use of MS SQL from asterisk. I get 
an error when the pjsip contact tries to update the contact table.
  
 [Oct 15 21:34:55] WARNING[3033]: res_odbc.c:649 
ast_odbc_prepare_and_execute: SQL Execute returned an error -1: 22018: 
[FreeTDS][SQL Server]Conversion failed when converting the varchar value 
'3.000000' to data type int. (101)
  
 The datatype in MySQL is integer and in MS SQL is integer. What could be 
the cause of this? Is it likely some kind of FeeTDS conversion issue?  If I 
change the MS SQL type to double the error goes away, but I am unsure of 
the long term issues associated with this.
  
 Thanks

Bryant Zimmerman (ZK Tech Inc.)
616-855-1030 Ext. 2003

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20151016/f93f79fe/attachment.html>

On Fri, Oct 16, 2015 at 12:45 PM, Bryant Zimmerman <BryantZ at zktech.com>
wrote:
>  I have a project that is requiring the use of MS SQL from asterisk. I get
> an error when the pjsip contact tries to update the contact table.
>
> [Oct 15 21:34:55] WARNING[3033]: res_odbc.c:649
> ast_odbc_prepare_and_execute: SQL Execute returned an error -1: 22018:
> [FreeTDS][SQL Server]Conversion failed when converting the varchar value
> '3.000000' to data type int. (101)
>
> The datatype in MySQL is integer and in MS SQL is integer. What could be
the
> cause of this? Is it likely some kind of FeeTDS conversion issue?  If I
> change the MS SQL type to double the error goes away, but I am unsure of
the
> long term issues associated with this.
>
Bryant:

There are two columns in the ps_contacts table that currently are
defined with an Integer type - 'qualify_timeout' and
'qualify_frequency'. Which one is currently giving the conversion
error?

Matt

Matthew Jordan
Digium, Inc. | Director of Technology
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org

On Fri, Oct 16, 2015 at 12:45 PM, Bryant Zimmerman <BryantZ at zktech.com>
wrote:
>>  I have a project that is requiring the use of MS SQL from asterisk. I 
>> get an error when the pjsip contact tries to update the contact table.
>>
>> [Oct 15 21:34:55] WARNING[3033]: res_odbc.c:649
>> ast_odbc_prepare_and_execute: SQL Execute returned an error -1: 22018:
>> [FreeTDS][SQL Server]Conversion failed when converting the varchar 
>> value '3.000000' to data type int. (101)
>>
>> The datatype in MySQL is integer and in MS SQL is integer. What could 
>> be the cause of this? Is it likely some kind of FeeTDS conversion 
>> issue?  If I change the MS SQL type to double the error goes away, but 
>> I am unsure of the long term issues associated with this.
>>
>Bryant:
>
>There are two columns in the ps_contacts table that currently are defined
with an Integer type - 'qualify_timeout' and
'qualify_frequency'. Which one is currently giving the conversion error?
>
>Matt
------

Hi guys,

Sorry to resurrect an old post but I just ran into this same issue with
Postgresql via ODBC. For me it was the 'qualify_timeout' value causing
the issue.

Thanks,
Nic.