[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:                     assigned
Asterisk Version:           1.6.1-beta4 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
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:              2010-01-26 10:48 CST
====================================================================== 
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
====================================================================== 

---------------------------------------------------------------------- 
 (0117196) dvossel (administrator) - 2010-01-26 10:48
 https://issues.asterisk.org/view.php?id=14331#c117196 
---------------------------------------------------------------------- 
I believe it had something to do with how the regdomain was set.  I
remember looking at these two patches and knowing that I would have to
modify this one in order to regain the expected behavior.

Here is an example of the config in our lab that broke.

-------------------------------
register => user at peer_1

[peer_1]
fromdomain=10.10.10.10
-------------------------------

the expected behavior for that register line is that peer_1 will be found,
and the fromdomain will take its place as the address. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-26 10:48 dvossel        Note Added: 0117196                          
======================================================================