similar to: faster timeout in ENUMLOOKUP() function

Does anyone have a better ENUM lookup handler than the built-in ENUMLOOKUP() function? The built-in function does not properly handle multiple return values such as: 8.9.9.3.2.8.8.6.6.8.1.e164.org has NAPTR record 200 10 "u" "E2U+SIP" "!^\\+1866(.*)$!sip:1866\\1 at tollfree.sip-happens.com!" . 8.9.9.3.2.8.8.6.6.8.1.e164.org has NAPTR record 200 10 "u"

Hi all, Does ENUMLOOKUP can query multiple DNS servers without having to replicate the same code in which the only thing replaced is the server? If I use ENUMLOOKUP(${exten}), Asterisk will parse enum.conf file to find the list of DNS servers in order of preference to be queried, but, I pretend to use something like this: ${ENUMLOOKUP(+${ARG1:2:},sip,c) which does not seam to care about

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

Since e164.org added DNC and ADDRESS records my enum configuration has failed. Using both the old EnumLookup app and the new ENUMLOOKUP function, the lookups have consistantly failed since e164.org added E2U+ADDRESS and E2U+DNC records. Mar 6 17:39:44 WARNING[14222]: enum.c:235 parse_naptr: NAPTR Regex match failed. Mar 6 17:39:44 WARNING[14222]: enum.c:354 enum_callback: Failed to parse naptr

I'm setting up a private enum zone to simplify/centralize dialplans for a number of Asterisk servers. In several dialed number situations, there are a handful of possible destinations for the call, and I'd like to have * try ENUMENTRY1, ENUMENTRY2, .., ENUMENTRYN just in case the first result is temporarily unable to handle the call. In at least some cases, I'd also like the order in

The freenum.org project wants to use your trunks! The freenum.org project is an ENUM parallel tree, which has as an eventual goal the distribution of ENUM numbering in nations or areas which due to political or other issues are not able to get secure, inexpensive, or functional ENUM capabilities. As a preliminary round, we're putting toll-free gateways into the system for various nations.

Hello all you Gurus out there! Please could you explain something to me: Currently I try to get ENUMLOOKUP() working. Naturally I do all the testing with my own number. I registered my number at e164.org I paid for registration of my number at a registration agent for e164.arpa (I know, I don't need both. I just did the .arpa registration first and later discoverd the free .org service....)

Ok, so you've read the Wiki and gotten call routing using ENUM to work (http://www.voip-info.org/tiki-index.php?page=Asterisk%20E164%20Call%20Routing) with your own ENUM-alike domain, e164.example.com. But how do you populate it with data? You can do it manually, but that gets very tedious very quickly. Or you can use the nifty DDNS updating program that comes with bind9. The first thing is

Hello, After upgrading to 1.4 my ENUMLOOKUP returns nothing. Even with new format. I've tried commands: SET(foo=${ENUMLOOKUP(+13015611020,,,,loligo.com)}); ${ENUMLOOKUP(+13015611020,ALL,c,,e164.org)}; Could I turn debug of ENUMLOOKUP on? Thanks. Michael -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I use Asterisk 1.2.17 in my site, and now I'm trying to configure ENUM lookup in my server. When someone calls a number that has multiple ENUM entries, randomly Asterisk seems to fail to return a correct answer, and dial by ENUM fails. I've goggled a bit on this, but didn't get any good conclusion. There is some RFC Compliant ENUM Macro that can be used that is announced

Hi all, I have a problem with 1.6.1.7-rc1 and ENUM (with an own PowerDNS server and NAPTR record). Maybe somebody has more experience with this or can give me some input. The dialplan: exten => 292,1,Set(DIAL_NUMBER=43660123456) exten => 292,2,Set(sip= ${ENUMLOOKUP(+${DIAL_NUMBER},sip,,1,ns3.e164.xxx.com)}) ;x'ed out the domain name starting from here exten => 292,3,NoOp(${sip})

This has been giving me a headache for a little while, so I thought I would throw the question out to the list. Imagine there is a database lookup function that takes place that, given a number, returns call routing information. It might be a postgresql lookup, it might be an enum lookup. If I have something like: exten => _.,1,LookUp(${EXTEN}) exten => _.,2,Dial(${RESULT}) Then the

The freenum.org beta continues to roll forward. If you have an Asterisk or SER SIP gateway/proxy, please see if you can make some sense of the examples below and install them in your system. Your users will hopefully be able to dial toll free numbers in various nations just like they dial regular numbers in those same country codes. I'd like to get some additional people trying to make

I would like to implement enum lookup in my dial plan but searching for solution / implementation I'm getting confused what is current standard. On some pages I read that the ENUMLOOKUP is not in development anymore and suggesting on using Enumlookup.agi scrip , some are saying that Asterisk 1.2.0 comes with a new powerful ENUMLOOKUP. So there is probably no need to use this script anymore;

Hi All, For a 1.4 version asterisk, whats the recommended mechanism for dialling with ENUM lookup? At the moment I user SIPbroker, but am getting tired of it hanging on certain numbers, so I was thinking about implementing it myself. I've seen various vo-ip.info pages (http://www.voip-info.org/wiki/view/Asterisk+cmd+EnumLookup) talking about the func ENUMLOOKUP instead of EnumLookup

I use ENUM lookup in my dialplan before sending calls through my PSTN trunk. One problem arises... When ENUMLOOKUP finds an SIP contact for that e164 number, Asterisk dials that contact, but when the remote server that should answer the call is down, or the IP link is down for some reason, the dial to PSTN trunk (which has the next priority) only takes place after the ring time of Dial

I've been tinkering with ENUM and found that the lack of a debug message in enum.c that says it has actually succeeded in resolving an address is a bit of a nuisance. It makes it difficult to see if failures with ENUM are due to problems with parsing NAPTR records (in enum.c) or mistakes in extensions.conf An extra line of debug information would be much appreciated! Iain

I'm still learning some of the basics. Can someone explain in layman's terms what's the difficulty for Asterisk to support SIP/TCP (and even RTP/TCP)?

List, Im a Cisco certified Network guy with little telecom experience (BRI/PRI at the time) so please forgive my terminology. I am showing interest after the Network World SHSU October 4 article. We have 3 offices (Hub-Spoke T1 Frame relay to the remote offices(Data & voice on separate T)). Each office currently does their own thing for telecom. Our Main(HUB) office currently has 14 channels

Hello, I'm in trouble here with what appears to be a total meltdown of my DNS on my Domain Controllers. I only have two DCs right now and I cannot resolve anything on either of them. I am on Ubuntu 16.04 with a compiled version of Samba 4.10.4. I also have a compiled version of BIND 9.10.3-P4-Ubuntu <id:ebd72b3> # service bind9 status ? bind9.service - BIND Domain Name Server ?