Summary:	ASTERISK-10260: SQL 2005 Escape Character
Reporter:	slakware (slakware)	Labels:
Date Opened:	2007-09-08 23:01:12	Date Closed:	2011-06-07 14:08:23
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Resources/res_odbc
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) func_odbc.conf
Description:	Much like the bug posted here: http://bugs.digium.com/view.php?id=10075 However this occurs when the sp_execute sp is executed as follows. exec sp_execute 534,'\_%','outgoing','1' The call is not placed. I'm not sure exactly where the problem lies. If anyone can help shed some light it would be greatly appreciated.
Comments:	By: Tilghman Lesher (tilghman) 2007-09-08 23:30:43 Please upload the contents of your func_odbc.conf file, so I can replicate the issue. By: slakware (slakware) 2007-09-09 10:23:26 I'm using ARA. If I switch the database to MySQL everything works great... By: Tilghman Lesher (tilghman) 2007-09-09 13:56:25 Asterisk doesn't directly call any stored procedures.  If there is an error in a stored procedure, then the issue is there, not in Asterisk. By: slakware (slakware) 2007-09-09 14:38:57 What about passing parameters between the drivers? Perhaps the escape code is sent to freetds and freetds constructs the execution of the sp with the passed values. The freetds driver which communicates with MSSQL gets the parameters from Asterisk, hence the context indicated within the execution of the sp as well as the escape sequence. By: Tilghman Lesher (tilghman) 2007-09-09 14:43:25 In that case, the issue would be with FreeTDS not passing forward a parameter, not with Asterisk.  There is nothing we can do to fix this issue for you, and I suspect the issue is on your database server, not even in FreeTDS.