[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 09:54 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
====================================================================== 

---------------------------------------------------------------------- 
 otmar - 05-07-08 09:54  
---------------------------------------------------------------------- 
>Otmar: I tried an Infrastructure test. Seems to work. I'm afraid I'm too
behind on my mailing lists to say if I know if the "i" zone delineator
appears in places other than directly after the country code, nor do I know
if this code is "hard-coded" for two digits or what. 

It's supposed to be a the country code. See Section 5 in
http://www.ietf.org/internet-drafts/draft-ietf-enum-combined-08.txt

>Are there other examples that might exist "in the wild" that have the "i"
in different places for testing purposes?

Not that I know. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-07-08 09:54  otmar          Note Added: 0086535                          
======================================================================