[asterisk-bugs] [Asterisk 0008089]: [patch] The record# parameter in ENUMLOOKUP is ignored

[noreply at bugs.digium.com]

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 23:17 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 23:17  
---------------------------------------------------------------------- 
There appear to be many, many problems with this patch as it stands now.  

 - no default tech/method
 - wrong counts on methods
 - wrong results on specific priority queries
 - inconsistent results over multiple queries (eventually all lookups
fail)
 - no valid replies at all for most query methods and types
 - lots of problems with regexp issues (or at least, complaints in debug)

I've included a short not-quite-a-regression-test dialplan as an
attachment (enum-extensions-test.conf) which anyone can feel free to extend
to their heart's content.  I'm still using my own entries in the DNS as a
source of test material in the DNS, since I have some artificial entries
that are complex enough to exercise the various options of the lookup
routines.

Otmar - do you have any sources of valid infrastructure ENUM test queries
or objects in the public DNS that could be used in an extension of these
tests?  I wasn't able to test with that. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-05-08 23:17  jtodd          Note Added: 0086446                          
======================================================================