[asterisk-bugs] [JIRA] (ASTERISK-15575) SIP Message parameters and URI parameters not parsed correctly

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-15575:
----------------------------------------

{{parse_uri_full}} now not only supports the parameters listed in the comment previous, it should also return the residue in the {{residue}} out parameter.

> SIP Message parameters and URI parameters not parsed correctly
> --------------------------------------------------------------
>
>                 Key: ASTERISK-15575
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-15575
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/Interoperability
>            Reporter: nick_lewis
>            Severity: Minor
>
> In some cases abnf message-header params such as to-param, from-param etc and not correctly distinguished from abnf uri-params by chan_sip.c. When message-header params (such as ";tag=") are stripped off, the uri-params (such as ";transport=") are sometimes also stripped off (especially from unbracketed uris).
> ****** ADDITIONAL INFORMATION ******
> In general it is not possible to correctly process message-header params before processing uris due to the nature of the abnf. The message-header params must therefore be left in place and the parse_uri function must return any residue that does not constitute part of the uri so that it can be processed by a message-header specific code.
> also the uri may contain headers after the uri-params so the parse_uri function needs to return these before the residue



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