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

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Aug 13 16:48:25 CDT 2007


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:48 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.


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

---------------------------------------------------------------------- 
 johann8384 - 08-13-07 16:48  
---------------------------------------------------------------------- 
I do not think that is the case. I have experienced this exact problem and
I know I was using the full e.164 format (+1NXXNXXXXXX for a NA number) and
it was not returning properly. 

I won't be able to do it until later this week but if it is useful I can
setup a machine to test against our ENUM databases to see if it is still
broken. Last time I tested OpenSER worked just fine but Asterisk failed on
the exact same lookups in the exact same DNS server. 

At the time I was using Asterisk 1.4.4 if I remember correctly and it was
broken in trunk at that time as well. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-13-07 16:48  johann8384     Note Added: 0068801                          
======================================================================




More information about the asterisk-bugs mailing list