Summary:ASTERISK-15926: ENUMQUERY fails for seemingly valid e164.org record
Reporter:Tony Vroon (chainsaw)Labels:
Date Opened:2010-04-08 11:23:01Date Closed:2011-06-07 14:04:53
Versions:Frequency of
Description:The following e164.org record, which seems valid:
gold ~ # dig +short any
100 10 "u" "E2U+SIP" "!^\\+441733207745$!sip:745@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
 == ast_get_enum() profiling: FAIL,, 495 ms

An ENUM lookup website seems to agree that the record is valid:
Comments:By: John Todd (jtodd) 2010-04-27 12:56:00

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?

By: Paul Belanger (pabelanger) 2010-05-13 09:13:45

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines