Summary:	ASTERISK-28971: app_userevent: Does not handle non-ASCII characters
Reporter:	Volodya Ivanets (Volodya)	Labels:
Date Opened:	2020-06-30 06:47:09	Date Closed:	2023-01-25 11:30:51.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Applications/app_userevent
Versions:	13.32.0 16.15.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	CentOS virtual machine running on VMware ESXi	Attachments:
Description:	Every time when a string with a "special" character is passed to dialplan application UserEvent, Asterisk stops dialplan execution and rejects the call with a 603 Declined response. Below is a simple context that I used for testing. {noformat} [macro-test] exten => s,1,Noop(${CALLERID(name)}) exten => s,n,UserEvent(test,callerid_name: ${CALLERID(name)}) exten => s,n,Answer exten => s,n,Wait(5) exten => s,n,Hangup {noformat} If CallerID name contains the "á" character call will be dropped. "300 á" in the example below: {noformat}    -- Executing [s@macro-test:1] NoOp("SIP/300-0000000a", "300 ▒ 300") in new stack    -- Executing [s@macro-test:2] UserEvent("SIP/300-0000000a", "test,callerid_name: 300 ▒") in new stack  == Spawn extension (macro-test, s, 2) exited non-zero on 'SIP/300-0000000a' in macro 'test' {noformat}
Comments:	By: Asterisk Team (asteriskteam) 2020-06-30 06:47:11.258-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. 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) 2020-06-30 06:55:17.173-0500 The Asterisk dialplan is not very UTF aware, which can result in these kind of problems. You may try using the FILTER dialplan function to filter them out to allow things to proceed, this was mentioned in ASTERISK-28830 for issues there. By: Volodya Ivanets (Volodya) 2020-07-01 03:00:36.828-0500 Thank you for the suggestion! By: Sean Bright (seanbright) 2020-07-16 13:57:49.037-0500 FWIW, ▒ is a "medium shade" character and it has a completely different representation in UTF-8 than á does.