[asterisk-bugs] [Asterisk 0008089]: [patch] The record# parameter in ENUMLOOKUP is ignored
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon May 5 16:10:39 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=8089
======================================================================
Reported By: otmar
Assigned To: bbryant
======================================================================
Project: Asterisk
Issue ID: 8089
Category: Functions/NewFeature
Reproducibility: always
Severity: feature
Priority: normal
Status: feedback
Asterisk Version: 1.6.0-beta5
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 50028
Disclaimer on File?: Yes
Request Review:
======================================================================
Date Submitted: 10-04-2006 10:19 CDT
Last Modified: 05-05-2008 16:10 CDT
======================================================================
Summary: [patch] The record# parameter in ENUMLOOKUP is
ignored
Description:
In function_enum, the args.record parameter is never evaluated.
That's also a bug in ast_get_enum, which does not offer a seperate
parameter for this.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0005526 [patch] Carrier ENUM support + some rew...
related to 0005666 [patch][post 1.4] Add NAPTR string pars...
related to 0011560 ENUM LOOKUP IS NOT WORKING AGAIN
======================================================================
----------------------------------------------------------------------
jtodd - 05-05-08 16:10
----------------------------------------------------------------------
A few notes on the testing of this:
1) The "default" technology really should be SIP in any of these queries,
since that is the most typical technology to be used for DNS-based pointer
lookups at this time. This may be what causes some of the backwards
compatibility issues that bbryant notes.
2) +437203001721 does not (any longer) have valid data in the DNS in
e164.arpa, so will always fail. It is useful only as a test to confirm
failure modes.
3) enum.yoyodynelabs.com does not have valid NAPTR data in the DNS for
1234567890, so will always fail. It is useful only as a test to confirm
failure modes.
4) Snuffy: Please include your testing dialplan as a file attachment so I
can duplicate experiments. There's too much cruft to sift through in the
last debug comment.
5) Freenum/ISN/ITAD parsing is broken with this patch. The query goes to
the DNS correctly for a NAPTR record and the DNS supplies a reply, but no
valid NAPTRs are returned to the function call.
Other notes: as of today's TRUNK, this applies cleanly.
Issue History
Date Modified Username Field Change
======================================================================
05-05-08 16:10 jtodd Note Added: 0086429
======================================================================
More information about the asterisk-bugs
mailing list