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

[Chris Savinovich (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Savinovich updated ASTERISK-28295:
----------------------------------------

    Assignee: Philip Mott
      Status: Waiting for Feedback  (was: Triage)

Hello Philip, please provide us with more information.  What channel technology are you using? (chan_sip or chan_pjsip).   Some more background into how the call originated would help (is it another phone in the same network? and if so what phone brand is it. Is is a local channel call?)

Thanks
C. Savinovich


> 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: Philip Mott
>            Severity: Minor
>
> 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)