[asterisk-bugs] [Asterisk 0017150]: ENUMQUERY fails for seemingly valid e164.org record

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17150 
====================================================================== 
Reported By:                Chainsaw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17150
Category:                   Functions/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.6 
JIRA:                       SWP-1276 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-08 11:23 CDT
Last Modified:              2010-04-27 12:56 CDT
====================================================================== 
Summary:                    ENUMQUERY fails for seemingly valid e164.org record
Description: 
The following e164.org record, which seems valid:
gold ~ # dig +short 5.4.7.7.0.2.3.3.7.1.4.4.e164.org any
100 10 "u" "E2U+SIP" "!^\\+441733207745$!sip:745 at linx.net!" .

Provokes a set of 4 warnings in Asterisk:
== ast_get_enum(num='+441733207745)', tech='ALL', suffix='e164.org',
options='', record=1
  == ENUM options(): pos=1, options='0'
[2010-04-08 16:48:28] WARNING[1958]: enum.c:518 parse_naptr: NAPTR Regex
match failed. Reason: No match
[2010-04-08 16:48:28] WARNING[1958]: enum.c:604 enum_callback: Failed to
parse naptr
[2010-04-08 16:48:28] WARNING[1958]: dns.c:235 dns_parse_answer: Failed to
parse result
[2010-04-08 16:48:28] WARNING[1958]: dns.c:276 ast_search_dns: DNS Parse
error for 5.4.7.7.0.2.3.3.7.1.4.4.e164.org
  == ast_get_enum() profiling: FAIL, 5.4.7.7.0.2.3.3.7.1.4.4.e164.org, 495
ms

An ENUM lookup website seems to agree that the record is valid:
http://enumquery.com/lookup?e164=%2B441733207745&source=form&query=%C2%BB
====================================================================== 

---------------------------------------------------------------------- 
 (0121008) jtodd (administrator) - 2010-04-27 12:56
 https://issues.asterisk.org/view.php?id=17150#c121008 
---------------------------------------------------------------------- 
Asterisk is doing exactly what it's supposed to do, given what you show in
the DNS.  It looks like at that particular time, there was bogus data in
the DNS for that NAPTR.  

I see valid data in the DNS now - does Asterisk work as expected with that
particular lookup now? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-27 12:56 jtodd          Note Added: 0121008                          
======================================================================