[asterisk-bugs] [Asterisk 0016768]: SIP Message parameters and URI parameters not parsed correctly

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16768 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16768
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-04 03:22 CST
Last Modified:              2010-02-04 03:50 CST
====================================================================== 
Summary:                    SIP Message parameters and URI parameters not parsed
correctly
Description: 
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).

====================================================================== 

---------------------------------------------------------------------- 
 (0117699) Nick_Lewis (reporter) - 2010-02-04 03:50
 https://issues.asterisk.org/view.php?id=16768#c117699 
---------------------------------------------------------------------- 
At the moment parse_uri only supports the uri-param ";transport=" . It
could do with supporting ";user=", ";method=", ";ttl=", ";maddr=" and ";lr"
as well. It should not strip arbitrary uri-params unless there are headers

The parse_uri function could be simplified to parse from left to right

The parse_uri function could unconditionally decode user and password (no
decode required for domainlabel). The headers aggregate should remain
encoded 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-04 03:50 Nick_Lewis     Note Added: 0117699                          
======================================================================