Is there any way to "prove" that an EnumLookup is actually being done?
I've been trying to get ENUM working, and have gotten to the point where
I'm pretty sure the NAPTR records are resolving the way they ought to
be, and "manual" lookups using dig return just what they
"ought" to.
But asterisk jumps to the "failure" priority no matter which numbers I
look up, even those that dig (and the list) purport to be good.
Here's what I'm using:
[enumcheck]
exten => _41NXXNXXXXXX,1,EnumLookup(${EXTEN:1})
exten => _41NXXNXXXXXX,2,Dial(${ENUM})
exten => _41NXXNXXXXXX,3,Hangup
exten => _41NXXNXXXXXX,102,Hangup
And in enum.conf
[general] ;
; The search list for domains may be customized. Domains are searched
; in the order they are listed here.
;
search => enum.fierymoon.com
search => ns.palaver.net
search => ns.peoples-wireless.com
search => freenum.org
search => e164.arpa
Here's the CLI output:
-- Executing EnumLookup("Zap/3-1", "12192538552") in
new stack
-- Executing Hangup("Zap/3-1", "") in new stack
== Spawn extension (home, 412192538552, 102) exited non-zero on
'Zap/3-1'
***************
Just trying to figure out if there's any more debugging that I can do. . .
Thanks.
B.