| Summary: | ASTERISK-28640: app_voicemail with ODBC - error logging is useless | ||
| Reporter: | Jaco Kroon (jkroon) | Labels: | |
| Date Opened: | 2019-12-01 09:02:19.000-0600 | Date Closed: | |
| Priority: | Minor | Regression? | No |
| Status: | Open/New | Components: | Applications/app_voicemail/ODBC |
| Versions: | 13.29.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | At best you'll find a log entry that states that an error occurred. Ideally when there is an SQL error, the actual error should be logged. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2019-12-01 09:02:21.029-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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Joshua C. Colp (jcolp) 2019-12-02 07:28:21.940-0600 Do you plan on contributing any changes to improve this? By: Jaco Kroon (jkroon) 2019-12-03 02:15:34.321-0600 That's the plan. Started looking at the ODBC implementation in asterisk and realized there are duplication of effort in at least some of the consumers. So perhaps this needs to be a larger clean-up. Our issue was sorted out by enabling mysql error logging and picking up the errors from there. I'll take a more in-depth look when I can. I did action a patch to try and resolve the immediate stuff but that was unsuccessful and I seem to have dropped the patch from my local codebase. By: Sean Bright (seanbright) 2019-12-05 08:24:58.910-0600 You could use {{ast_odbc_print_errors()}} which is already part of the API exposed by {{res_odbc}}. | ||