I'm running into errors when using Enum lately. I can't figure out what
the problem might be as I've had Enum up and running in the past. I'm
running the latest CVS-Head compiled version. I've also tried using the
new Enum function with the same results. When doing a lookup on a number
that exists in the enum server I get the following results:
-- Executing EnumLookup("SIP/MarcSnom-e69d",
"18886532145") in new stack
Oct 13 22:55:51 WARNING[2208]: app_enumlookup.c:89 enumlookup_exec: The
application EnumLookup is deprecated. Please use the ENUMLOOKUP()
function instead.
Oct 13 22:55:52 WARNING[2208]: enum.c:235 parse_naptr: NAPTR Regex match
failed.
Oct 13 22:55:52 WARNING[2208]: enum.c:354 enum_callback: Failed to parse
naptr :(
Oct 13 22:55:52 WARNING[2208]: dns.c:162 dns_parse_answer: Failed to
parse result
Oct 13 22:55:52 WARNING[2208]: dns.c:208 ast_search_dns: DNS Parse error
for 5.4.1.2.3.5.6.8.8.8.1.e164.org
-- Executing Dial("SIP/MarcSnom-e69d", "") in new stack
Oct 13 22:55:52 WARNING[2208]: app_dial.c:734 dial_exec_full: Dial
argument takes format
(technology1/number1&technology2/number2...|optional timeout)
Any help would be greatly appreciated.
Marc.
Apparently ENUM now REQUIRES a + at the beginning of the number to query. EnumLookup(+18886532145) No I didn/t see it documented anywhere.. It seems to require it even if there is no + at the beginning of the ENUM record in DNS. We use ENUM to look up extensions and so should not prefix the number with a +.> > I'm running into errors when using Enum lately. I can't figure out > what the problem might be as I've had Enum up and running in the past. > I'm running the latest CVS-Head compiled version. I've also tried > using the new Enum function with the same results. When doing a lookup > on a number that exists in the enum server I get the following results: > > -- Executing EnumLookup("SIP/MarcSnom-e69d", "18886532145") in new > stack > Oct 13 22:55:51 WARNING[2208]: app_enumlookup.c:89 enumlookup_exec: > The application EnumLookup is deprecated. Please use the ENUMLOOKUP() > function instead. > Oct 13 22:55:52 WARNING[2208]: enum.c:235 parse_naptr: NAPTR Regex > match failed. > Oct 13 22:55:52 WARNING[2208]: enum.c:354 enum_callback: Failed to > parse naptr :( > Oct 13 22:55:52 WARNING[2208]: dns.c:162 dns_parse_answer: Failed to > parse result > Oct 13 22:55:52 WARNING[2208]: dns.c:208 ast_search_dns: DNS Parse > error for 5.4.1.2.3.5.6.8.8.8.1.e164.org > -- Executing Dial("SIP/MarcSnom-e69d", "") in new stack > Oct 13 22:55:52 WARNING[2208]: app_dial.c:734 dial_exec_full: Dial > argument takes format > (technology1/number1&technology2/number2...|optional timeout)
Yes adding the "+" before ${EXTEN} to my extensions.conf did the trick
exten => _1800NXXXXXX,1,EnumLookup(+${EXTEN})
Thanks.
> Apparently ENUM now REQUIRES a + at the beginning of the number to query.
>
> EnumLookup(+18886532145)
>
> No I didn/t see it documented anywhere.. It seems to require it even if
> there is no + at the beginning of the ENUM record in DNS. We use ENUM
> to look up extensions and so should not prefix the number with a +.
>>
>> I'm running into errors when using Enum lately. I can't figure
out
>> what the problem might be as I've had Enum up and running in the
past.
>> I'm running the latest CVS-Head compiled version. I've also
tried
>> using the new Enum function with the same results. When doing a lookup
>> on a number that exists in the enum server I get the following results:
>>
>> -- Executing EnumLookup("SIP/MarcSnom-e69d",
"18886532145") in new
>> stack
>> Oct 13 22:55:51 WARNING[2208]: app_enumlookup.c:89 enumlookup_exec:
>> The application EnumLookup is deprecated. Please use the ENUMLOOKUP()
>> function instead.
>> Oct 13 22:55:52 WARNING[2208]: enum.c:235 parse_naptr: NAPTR Regex
>> match failed.
>> Oct 13 22:55:52 WARNING[2208]: enum.c:354 enum_callback: Failed to
>> parse naptr :(
>> Oct 13 22:55:52 WARNING[2208]: dns.c:162 dns_parse_answer: Failed to
>> parse result
>> Oct 13 22:55:52 WARNING[2208]: dns.c:208 ast_search_dns: DNS Parse
>> error for 5.4.1.2.3.5.6.8.8.8.1.e164.org
>> -- Executing Dial("SIP/MarcSnom-e69d", "") in
new stack
>> Oct 13 22:55:52 WARNING[2208]: app_dial.c:734 dial_exec_full: Dial
>> argument takes format
>> (technology1/number1&technology2/number2...|optional timeout)
>
>
------------------------------