[asterisk-bugs] [Asterisk 0009692]: Regular expression parsing for ENUM entries on ENUMLOOKUP fails

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9692 
====================================================================== 
Reported By:                jtodd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   9692
Category:                   Functions/func_enum
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 62039 
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             05-08-2007 19:00 CDT
Last Modified:              08-13-2007 16:35 CDT
====================================================================== 
Summary:                    Regular expression parsing for ENUM entries on
ENUMLOOKUP fails
Description: 
ENUMLOOKUP returns errors when it should return a URL.  The data in the DNS
is valid, but Asterisk chokes on the re-write.  Verified on TRUNK from a
few days ago, and I haven't seen any ENUM-related fixes so it's a safe bet
it's still broken.


====================================================================== 

---------------------------------------------------------------------- 
 jamesgolovich - 08-13-07 16:35  
---------------------------------------------------------------------- 
Just trying to hit up some older bugs and looking at this it seems as if
its already been addressed by doc/enum.txt:

  a) The use of "+" in lookups is confusing, and warrants further
  explanation.  All E.164 numbers ("global phone numbers") by
  definition need a leading "+" during ENUM lookup.  If you neglect to
  add a leading "+", you may discover that numbers that seem to exist
  in the DNS aren't getting matched by the system or are returned with
  a null string result.  This is due to the NAPTR reply requiring a
  "+" in the regular expression matching sequence.  Older versions of
  Asterisk add a "+" from within the code, which may confuse
  administrators converting to the new function.  Please ensure that
  all ENUM (e164.arpa) lookups contain a leading "+" before lookup, so
  ensure your lookup includes the leading plus sign.  Other DNS trees
  may or may not require a leading "+" - check before using those
  trees, as it is possible the parsed NAPTRs will not provide correct
  results unless you have the correct dialed string.  If you get
  console messages like "WARNING[24907]: enum.c:222 parse_naptr: NAPTR
  Regex match failed." then it is very possible that the returned
  NAPTR expects a leading "+" in the search string (or the returned
  NAPTR is mis-formed.) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-13-07 16:35  jamesgolovich  Note Added: 0068799                          
======================================================================