| Summary: | ASTERISK-29112: Invalid UTF-8 string (problem with umlauts in callerid) | ||||
| Reporter: | 1357 (1357) | Labels: | |||
| Date Opened: | 2020-10-07 08:14:53 | Date Closed: | 2020-10-07 08:20:00 | ||
| Priority: | Minor | Regression? | |||
| Status: | Closed/Complete | Components: | General | ||
| Versions: | 16.5.0 | Frequency of Occurrence | Occasional | ||
| Related Issues: |
| ||||
| Environment: | CentOS 7 | Attachments: | |||
| Description: | I already asked for help in the forum but nobody could solve this problem:
we are currently experience some problems with our asterisk installation. Every time there are umlauts (we are located in a german speaking country) in the CallerID we receive the following error messages: ERROR[19407][C-0000006c] json.c: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string. ERROR[19407][C-0000006c] : Got 12 backtrace records # 0: /usr/sbin/asterisk(ast_json_pack+0x94) [0x4f7ca4] # 1: /usr/sbin/asterisk(ast_channel_publish_varset+0x2b) [0x57e2eb] # 2: /usr/sbin/asterisk(pbx_builtin_setvar_helper+0x123) [0x5343c3] # 3: /usr/lib64/asterisk/modules/app_mysql.so(+0x2e9f) [0x7f77aff5de9f] # 4: /usr/lib64/asterisk/modules/app_mysql.so(+0x378b) [0x7f77aff5e78b] # 5: /usr/sbin/asterisk(pbx_exec+0xb9) [0x52b1b9] # 6: /usr/sbin/asterisk() [0x51eb85] # 7: /usr/sbin/asterisk() [0x520bf4] # 8: /usr/sbin/asterisk() [0x52217b] # 9: /usr/sbin/asterisk() [0x59e7a9] #10: /lib64/libpthread.so.0(+0x7dd5) [0x7f781b3d2dd5] #11: /lib64/libc.so.6(clone+0x6d) [0x7f781a77502d] asterisk version -> 16.5.0 jansson.x86_64 -> 2.10-1.el7 jansson-devel.x86_64 -> 2.10-1.el7 We set the CallerID of incoming calls according to a database (where we check if the caller is in our customer database) (app_mysql). I am not quite sure why this problem occurs. We used an older asterisk version before and never had any problems with umlauts on that installation. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2020-10-07 08:14:53.975-0500 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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. | ||||