[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
Tue Jan 26 10:58:23 CST 2010
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:58 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
======================================================================
----------------------------------------------------------------------
(0117199) Nick_Lewis (reporter) - 2010-01-26 10:58
https://issues.asterisk.org/view.php?id=14331#c117199
----------------------------------------------------------------------
Wow - I was unaware that the register string could (or should) suck
fromdomain from the peer def like this. It may explain my previous question
in this issue:
>>The sip_pvt's fromdomain field used to be set before this
>When before this point in the registration process was p->fromdomain set?
Issue History
Date Modified Username Field Change
======================================================================
2010-01-26 10:58 Nick_Lewis Note Added: 0117199
======================================================================
More information about the asterisk-bugs
mailing list