search for: naptrs

Displaying 20 results from an estimated 48 matches for "naptrs".

Did you mean: naptr
2018 Nov 14
0
AST-2018-010: Remote crash vulnerability DNS SRV and NAPTR lookups
Asterisk Project Security Advisory - AST-2018-010 Product Asterisk Summary Remote crash vulnerability DNS SRV and NAPTR lookups Nature of Advisory Denial Of Service Susceptibility Remote Unauthenticated Sessions Severity Moderate
2008 May 07
3
better enumlookup handler
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"
2004 Jun 20
4
call waiting from PSTN
I'm trying to switch from one call to another incoming call from PSTN. When I'm getting a "beep" I press flash but instead of swithing to the second call, I'm getting a dial tone. even if I press *0, I cannot connect to the second call. Anybody had this problem? Tx, Bogdan
2005 Oct 13
2
Enum parse errors
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
2006 Mar 06
1
ENUM lookup issues with e164.org
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
2003 Nov 20
2
SIP URIs and ENUM or other types of lookup
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
2009 Jul 24
1
EVERY toll free number appears to be in e164.org??
ENUM lookups at e164.org return a IP route for ALL toll-free numbers. I was surprised to observe that ALL toll-free numbers get a hit at e164.org. It appears that ALL toll-free prefixes have been delegated, thereby publishing an IP route for YOUR TOLL-FREE NUMBERS, my toll-free numbers, and even toll-free numbers that have not been allocated. :-) See below Should I care? Even though this
2004 Jul 21
2
ENUM lookup help
Hello everyone, I playing around with ENUM and have configured * to query a few sources for testing purposes (fierymoon, e164.arpa, e164.org). I'd like to know if there is a way to query these servers manually (ie outside of asterisk via nslookup or equivalent) to find out if particular exchanges are listed with wildcards, so as to terminate calls to those prefixes (I'm not trying to
2003 Nov 30
1
LCR with ENUM and DDNS: half the story
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
2005 Mar 10
1
multiple enum results
...to handle the call. In at least some cases, I'd also like the order in which the servers in the enum results are tried to be random. The wiki pointed me at enumlookup.agi for enum support of multiple NAPTR results per lookup. By default, enumlookup.agi will either return equal order/priority NAPTRs as a single &'d result, or individual ones in order according to NAPTR defined order and priority. What I'd prefer is for equal order/priority results to be returned separately in the order the DNS server gave them, while still sorting by order/priority if they differ among results. B...
2009 Nov 16
0
ENUM and Asterisk 1.6
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})
2006 Feb 19
3
Cisco 7905 can't register
My Cisco 7905 can't register with Asterisk (1.0.7-BRIstuffed-0.2.0-RC7k on Debian stable). It could, however, register with another installation of Asterisk and the settings on the phone (apart from the SIP proxy address) haven't changed since then. On the new Asterisk box my sip.conf contains this: [jeremy] type=friend regexten=801 allow=g729 host=dynamic secret=PASSWORD nat=yes
2015 Mar 03
0
TLS, SRTP, Asterisk11 and Snom870s
Am 03.03.2015 um 18:16 schrieb James B. Byrne: > CentOS-6.5 (FreePBX-2.6) > Asterisk-11.14.2 (FreePBX) > snom870-SIP 8.7.3.25.5 > > I am having a very difficult time attempting to get TLS and SRTP > working with Asterisk and anything else. At the moment I am trying to > get TLS functioning with our Snom870 desk-sets. And I am not having > much luck. > > Since this
2015 Mar 03
6
TLS, SRTP, Asterisk11 and Snom870s
CentOS-6.5 (FreePBX-2.6) Asterisk-11.14.2 (FreePBX) snom870-SIP 8.7.3.25.5 I am having a very difficult time attempting to get TLS and SRTP working with Asterisk and anything else. At the moment I am trying to get TLS functioning with our Snom870 desk-sets. And I am not having much luck. Since this is an extraordinarily (to me) Byzantine environemnt I am going to ask if any of you have gotten
2017 Apr 26
3
pjsip direct_media=yes and "unknown" endpoints
I'm trying to implement direct_media between multiple peers and an uplink provider, all of whom have direct_media=yes configures. For originating calls to the uplink provider direct_media=yes works like expected. SIP flows through asterisk, rtp doesn't SIP: enduser <-> SBC <-> asterisk 13 <-> uplink RTP: enduser <-> SBC <-----------------> uplink SBC
2008 Apr 14
4
Unable to load module chan_zap.so
I am having trouble with chan_zap.so not loading. When I load it from modules.conf, Asterisk bails out without any error message. When I load it from the console, it just says "Unable to load module chan_zap.so" no matter what verbose level I am using. dmesg says: Zaptel Version: 1.4.4 Zaptel Echo Canceller: MG2 Freshmaker version: 73 Freshmaker passed register test Module 0:
2003 Sep 22
1
Undocumented variables in chan_sip.c
Trying to read and understand bits and pieces of chan_sip.c I've found these I would like someone to clarify: * srvlookup=yes|no * pedantic * canreinvite=update|yes --"update" seems new Being curious, especially for "srvlookup" functionality... /O
2003 Nov 28
1
Request for debug message in ENUM code
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
2004 Aug 10
0
Re: [Asterisk-Dev] VoIP SPAM, what's next ?
Soren Rathje wrote: > Next thing will probably be a sbl.e164.org service to block spammers like we do with email... :-) Actually we don't need to do that, using normal NAPTR record can be used instead. We know the IP the call is coming from, we can find out from the NAPTR where calls normally go to based on the phone number, if the 2 don't match filter it. -- Best regards, Duane
2004 Dec 11
1
How to setup private enum server ?
Hi, I'd like to setup little private enum server. Any more info on how to do that ? Regards, Rob.