[asterisk-bugs] [Asterisk 0014331]: reg->username is parsed for each registration refresh rather than once on sip reload
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jan 26 06:19:54 CST 2009
The following issue has been SUBMITTED.
======================================================================
http://bugs.digium.com/view.php?id=14331
======================================================================
Reported By: Nick_Lewis
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14331
Category: Channels/chan_sip/Registration
Reproducibility: always
Severity: tweak
Priority: normal
Status: new
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-01-26 06:19 CST
======================================================================
Summary: 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
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-01-26 06:19 Nick_Lewis New Issue
2009-01-26 06:19 Nick_Lewis Asterisk Version => 1.6.1-beta4
2009-01-26 06:19 Nick_Lewis Regression => No
2009-01-26 06:19 Nick_Lewis SVN Branch (only for SVN checkouts, not tarball
releases) => N/A
======================================================================
More information about the asterisk-bugs
mailing list