[asterisk-bugs] [Asterisk 0014331]: [patch] reg->username is parsed for each registration refresh rather than once on sip reload
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jul 15 02:34:48 CDT 2009
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-15 02:34 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
======================================================================
----------------------------------------------------------------------
(0107763) Nick_Lewis (reporter) - 2009-07-15 02:34
https://issues.asterisk.org/view.php?id=14331#c107763
----------------------------------------------------------------------
dvossel
Yes this was a minor tweak that slightly improved performance but not
behavior.
I am not familiar with the way branches and merging operate. The patch was
against head at the time that it was submitted. I am not sure whether it
will apply cleanly now.
Issue History
Date Modified Username Field Change
======================================================================
2009-07-15 02:34 Nick_Lewis Note Added: 0107763
======================================================================
More information about the asterisk-bugs
mailing list