[asterisk-bugs] [JIRA] (ASTERISK-28295) Non-breaking space handling

Philip Mott (JIRA) noreply at issues.asterisk.org
Tue Feb 19 11:02:47 CST 2019


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

Philip Mott edited comment on ASTERISK-28295 at 2/19/19 11:01 AM:
------------------------------------------------------------------

Hi Chris,

We're using chan_sip, and the call originated from outside our network, so I can't say how it was generated - I wish I knew!  I've tried replicating the issue by using various other strange unicode characters and making internal calls using the Dial command, but it's handled those fine, which again seems to imply it's this specific character that's causing problems for some reason.

Thanks,

Philip


was (Author: nexbridge):
Hi Chris,

We're using chan_sip, and the call originated from outside our network, so I can't say how it was generated - I wish I knew!

Thanks,

Philip

> Non-breaking space handling
> ---------------------------
>
>                 Key: ASTERISK-28295
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28295
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 13.23.1
>         Environment: Debian 9.6
>            Reporter: Philip Mott
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: pjsip
>
> We recently received a SIP invite header of the following form:
> bq. INVITE sip:01234567890%A0 at 1.2.3.4
> Which led to the following Asterisk errors:
> bq. json.c: Error building JSON from '\{s: s, s: s\}': Invalid UTF-8 string.
> bq. stasis_channels.c: Error creating message
> I believe "%A0" is a URL-encoded non-breaking space, so it seems like that's not being handled correctly.
> Three questions:
> # Is this something that can be fixed, in the sense of not generating error messages?
> # Is there a simple way for me to recreate the error?  Only I'm finding it difficult to put a non-breaking space into the Dial command, and obviously if I can replicate the issue then I can look into ways of protecting against it if need be.
> # How would you specify special characters like that in the Asterisk REGEX function?
> P.S. Sorry I couldn't find a component relating to json.c when filling out this form so went with 'General' - please correct if wrong!



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



More information about the asterisk-bugs mailing list