[asterisk-bugs] [Asterisk 0015111]: [patch] parsing of sip register lines is broken

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Jan 5 09:31:56 CST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15111 
====================================================================== 
Reported By:                ffs
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   15111
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Target Version:             1.6.2.0
Asterisk Version:           1.6.2.0-beta1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-14 11:03 CDT
Last Modified:              2010-01-05 09:31 CST
====================================================================== 
Summary:                    [patch] parsing of sip register lines is broken
Description: 
A register line within sip.conf has the following format:

[transport://]user[:secret[:authuser]]@domain[:port][/extension][~expiry]

To extract the extension the parser is searching for '/' in the whole line
(from right to left).
As [/extension] is optional this causes trouble if there is no extension
defined and [transport://] is set.

Suggested solution: parse extension and expiry after the last '@'
character.

A backport to affected older versions would be appreciated.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014668 register: '/' in username not supported
has duplicate       0015342 parsing of sip register lines is still ...
====================================================================== 

---------------------------------------------------------------------- 
 (0116050) tzafrir (manager) - 2010-01-05 09:31
 https://issues.asterisk.org/view.php?id=15111#c116050 
---------------------------------------------------------------------- 
Just to make this explicit, and hopefully avoid future duplicates (I was
about to reopen this one before figuring out) - if you need a slash in the
username, the transport has to be specified explicitly.

register => foo/bar:password at domain ; fails. Will probably be identified
as some strange transport 'fo'
register => foo\/bar:password at doman ; you get an explicit '\/' in the
username
register => udp://foo/bar:password@domain ; works 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-05 09:31 tzafrir        Note Added: 0116050                          
======================================================================




More information about the asterisk-bugs mailing list