Summary:	ASTERISK-25526: In case of incorrect request in a database, after several attempts, service the asterisk is disconnected
Reporter:	User User (smnv)	Labels:
Date Opened:	2015-11-06 00:40:05.000-0600	Date Closed:
Priority:	Critical	Regression?
Status:	Open/New	Components:	Resources/res_odbc
Versions:	13.5.0	Frequency of Occurrence
Related Issues:
Environment:	Linux 3.13.0-67-generic #110-Ubuntu SMP Fri Oct 23 13:24:41 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Asterisk is set from source codes. Postgresql-9.3 from packages	Attachments:
Description:	In case of incorrect request in a database, after several attempts, service the asterisk is disconnected. The erratic inquiry isn't ignored, operation stops. [Edit by Rusty - debug log removed from *Description* field. Please attach debug logs to the issue as .txt files]
Comments:	By: Asterisk Team (asteriskteam) 2015-11-06 00:40:08.306-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Rusty Newton (rnewton) 2015-11-06 07:38:28.860-0600 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: User User (smnv) 2015-11-10 06:17:53.591-0600 This situation arises if to collect a key shortcut Alt+"184" on program phone 3CXPhone for Windows. When writing in remote DB Postgresql of this call in the table "cel", error state "-1" returned. Then service asterisk crash. The database continued to work. Sorry, but log files are deleted in rotation. We repaired this problem by change of a locale in a database Postgresql with UTF8 on CP1251, and now simply there is a message  "NOTICE[7060][C-00000854]: chan_sip.c:25645 handle_request_invite: Call from '1894' (10.222.0.190:50417) to extension '' rejected because extension not found in context 'internal'", and asterisk not crash. We can't emulate once again such situation, as servers in production operation By: Rusty Newton (rnewton) 2015-11-10 09:55:16.576-0600 Well, without a crash trace, debug logs or configuration for reproduction we can't really move forward on this. I'll go ahead and close this out. Thanks. By: User User (smnv) 2016-04-14 03:19:33.365-0500 It is eliminated by change of parameter in /etc/odbc.ini. ConnSettings        = SET CLIENT_ENCODING to 'Windows-1251' By: Asterisk Team (asteriskteam) 2016-04-14 03:19:33.865-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Reza from Toronto (DIGITALCANADA) 2016-05-23 00:18:18.518-0500 Greetings Folks:   I have **EXACTLY** the same issue.  I executed a successful simulation of 300K+ calls in my asterisk where character set was constant and Asterisk service does not die.  However I've noticed calls originating from SIP clients abruptly kills the Asterisk process.  The error is *almost exactly* as described above, per res_odbc errors, sanity check and "SQL Execute error -1" error message.   In my case, I'm using MySQL versus PostgreSQL.   I too suspect its related to res_odbc and/or unixODBC.  My local & charset was something "latin".  I've changed it to UTF8 and lets see over the course of the next couple of weeks if I encounter the service crash.