[asterisk-bugs] [JIRA] (ASTERISK-28971) app_userevent: Does not handle UTF characters

[Joshua C. Colp (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251306#comment-251306 ] 

Joshua C. Colp commented on ASTERISK-28971:
-------------------------------------------

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.

> app_userevent: Does not handle UTF characters
> ---------------------------------------------
>
>                 Key: ASTERISK-28971
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28971
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_userevent
>    Affects Versions: 13.32.0
>         Environment: CentOS virtual machine running on VMware ESXi
>            Reporter: Volodya Ivanets
>            Severity: Minor
>
> 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.
> ```[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```
> If CallerID name contains the "á" character call will be dropped. "300 á" in the example below:
> ```    -- Executing [s at macro-test:1] NoOp("SIP/300-0000000a", "300 ▒ 300") in new stack
>     -- Executing [s at 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'```



--
This message was sent by Atlassian JIRA
(v6.2#6252)