Topic: ENUM e164.org e164.arpa

[PWDasterisk]

Asterisk 1.4.21.1
SAIL: 2.2.1-688

Has anyone addressed the issue of how to implement an ENUM lookup within the SARC/SAIL environment for an outbound call.

The enum.conf file exists but I can't see any structure in the SAIL interface that utilizes it. Intercepting and modifying the dial plan through the Custom Apps then passing the ENUM results back to the standard AGI selintra OutCos, OutCluster and OutRoute functions without breaking the normal programming flows doesn't seem like a trivial task. Most of extensions.conf appears to be hardcoded to the SME/SAIL manager interface.

Although logical I don't know if would be possible to setup ENUM as a special carrier instance similar to the PTT_DiD_Group that would allow Routes to assign the ENUM "trunk" as a first choice in the route with a fallback to standard trunks if the ENUM lookup fails or returns a null result.

Any ideas or implementations that worked for anyone else???

[SARK devs]

Try this if you wish to experiment...

Create a custom app with a span of internal and give it an extension expression to catch E-164 numbers... (or, alternatively use a prefix, like 9 or something)...

exten=>_(1-9)XXXXXXXXXX.,1,do-your-arpa-lookup
exten=>_(1-9)XXXXXXXXXX.,n,do-your-enum-sip-dial
exten=>_(1-9)XXXXXXXXXX.,n,Hangup

exten=>_(1-9)XXXXXXXXXX.,102,do-a-regular-dial (non E164!) - use dial (local/...) to send the call back into the standard SAIL routing stack
exten=>_(1-9)XXXXXXXXXX.,n,Hangup 

Something like this.  Now you can dial E164 format numbers and have your code do the enumlookup.   You'll need to do the dial and post-dial-cleanup yourself but that's OK.  Ordinary dials and failed lookups will proceed through the SAIL routing stack in the normal way.

We haven't done any of this but our best guess is that it should work OK.

Best

S