[asterisk-bugs] [Asterisk 0014331]: [patch] reg->username is parsed for each registration refresh rather than once on sip reload

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14331 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   14331
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1-beta4 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-26 06:19 CST
Last Modified:              2009-07-20 10:44 CDT
====================================================================== 
Summary:                    [patch] reg->username is parsed for each
registration refresh rather than once on sip reload
Description: 
The registration string can contain an expanded user portion of the form
user at domain (and possibly user at domain:domainport). This expanded user
portion is currently stored in reg->username and parsed each time there is
a registration refresh. It would be better if the configuration was parsed
only once and the sip_registry structure contained the atomic fields
separately through the addition of, for example, reg->regdomain and
reg->regdomainport elements
====================================================================== 

---------------------------------------------------------------------- 
 (0107959) dvossel (administrator) - 2009-07-20 10:44
 https://issues.asterisk.org/view.php?id=14331#c107959 
---------------------------------------------------------------------- 
If the tweak was going in all the branches we could probably justify just
throwing in the bug fix, but since the tweak is only going into trunk, and
the bug fix needs to go into every branch, a separate report should be
created.  So yes, go ahead and resubmit the patch with the existing addr
field logic and submit a separate bug report for the other issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-20 10:44 dvossel        Note Added: 0107959                          
======================================================================