[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-07-2008 02:58 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-07-08 02:58  
---------------------------------------------------------------------- 
OK.  It's not quite "ditch everything after the *" - the ITAD portion
actually gets used in the DNS lookup.  I think you can see from the example
how it's supposed to work, but I just wanted to be clear. 

Also: how many digits are supported in these lookups, for both "normal"
ENUM style queries, as well as Freenum/ISN queries?  The Freenum/ISN stuff
may get pretty long - 20 digits on the left side of the * is not
unforseeable, and on the right side of the * there will hopefully be six or
seven digits (though the limit is a 32 bit number.)  Are there buffer
overflow checks on these sequences?  (Sorry, I'm not a coder or I'd look
myself - I just break things and test them.) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-07-08 02:58  jtodd          Note Added: 0086517                          
======================================================================