search for: e2u

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 :( Mar 6 17:39:44 WARNING[14222]: dns.c:163 dns_parse_answer: Failed to parse result Mar 6 17:39:44 WARNI...

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" "E2U+SIP" "!^\\+1866(.*)$!sip:1641641866\\1 at sip.tollfreegateway.com!" . And thus does not handle roll-over should one be unava...

...=> _.,1,LookUp(${EXTEN}) exten => _.,2,Dial(${RESULT}) Then the LookUp function has to deal with making sure the number is properly filled in before returning ${RESULT}. For example, if I have a wildcard DNS record that looks like this: *.3.9.3.0.0 IN NAPTR 100 100 "u" "SIP+E2U" "!^+*00393(.*)!sip:\1@pulver!" . *.0.0.7.1 IN NAPTR 100 100 "u" "IAX2+E2U" "!^+*(.*)!iax2:iaxtel/\1!" . They won't work since the pattern matching and replacement code is unimplemented. (not to mention the fact that bind barfs on the \1) One way a...

...r if you let it. All resolve to one of the same three gateways: tf.voipmich.com sip.tollfreegateway.com tollfree.sip-happens.com ;; QUESTION SECTION: ;3.5.3.6.4.1.3.7.7.8.1.e164.org. IN ANY ;; ANSWER SECTION: 3.5.3.6.4.1.3.7.7.8.1.e164.org. 60 IN NAPTR 200 10 "u" "E2U+SIP" "!^\\+1877(.*)$!sip:1877\\1 at tf.voipmich.com!" . 3.5.3.6.4.1.3.7.7.8.1.e164.org. 60 IN NAPTR 200 10 "u" "E2U+SIP" "!^\\+1877(.*)$!sip:1641641877\\1 at sip.tollfreegateway.com!" . 3.5.3.6.4.1.3.7.7.8.1.e164.org. 60 IN NAPTR 200 10 "u...

...n 'SIP/273-98117048' -- Executing [h at sip:1] Hangup("SIP/273-98117048", "") in new stack == Spawn extension (sip, h, 1) exited non-zero on 'SIP/273-98117048' srv21*CLI> The NAPTR record: 6.5.4.3.2.1.0.6.6.3.4.e164.xxx.com 100 10 "u" "E2U+sip" "!^.*$! sip:273 at 10.0.43.105!" . The output of a dig command using the ns3.e164.xxx.com (so DNS seems to be fine): dig @ns3.e164.xxx.com 6.5.4.3.2.1.0.6.6.3.4.e164.xxx.com ANY ; <<>> DiG 9.5.1-P3 <<>> @ns3.e164.xxx.com 6.5.4.3.2.1.0.6.6.3.4.e164.xxx....

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

...600 SERVER=nameserver.example.com SERVER=sparx ZONE=e164.example.com KEYFILE=Kclient.example.com.+157+13404.key nsupdate -v -k ${KEYFILE} << EOF server ${SERVER} zone ${ZONE} update delete *.6.6.6.e164.example.com. update add *.6.6.6.e164.example.com. ${TTL} NAPTR 100 100 "u" "E2U+IAX2" "!\\\\+(.*)!iax2:foofone/\\\\1!" . update add *.6.6.6.e164.example.com. ${TTL} TXT "greate $0.00/minute rate from FooFone!" show send EOF the first update line deletes any existing records for +666, the second adds the NAPTR record for ENUM call routing, and the thir...

...into "080012345" as it's sent to the remote gateway residing at gateway.mycompany.com (which could actually have SRV records associated with it, as well - that is up to the owner of the DNS for mycompany.com.) $ORIGIN 0.0.8.2.3.freenum.org. * 3600 IN NAPTR 100 10 "u" "E2U+sip" "!^\\+32800(.*)$!sip:0800\\1@gateway.mycompany.com!" . 3600 IN NAPTR 100 10 "u" "E2U+voice:sip" "!^\\+32800(.*)$!sip:0800\\1@gateway.mycompany.com!" . WHAT ARE THE DISCLAIMERS ON THIS? THIS SERVICE IS PROVIDED BY THE PROVIDER ``AS IS''...

Anyone succeeded in using regexp replacements in ENUM, like "!\\+421257296(.*)$!sip:2\\1@stuba.sk!" I can't get it to work in ASterisk. I've added '\\1' and Debug echos "1" I've added '\\\\1' and debug echoes "\1", but regexp fails to work. The example above is from the nic.at presentation, I can't get it to work. /Olle

...y to start testing with it. However, I have a question. As I understand things the following ENUM entry would return info for all telephone numbers of any length beginning with 00393. The Asterisk pattern would be _00393. (notice the dot) *.3.9.3.0.0 IN NAPTR 100 100 "u" "SIP+E2U" "!^+*00393(.*)!sip:\1@pulver!" . I would like to know if it's possible to have an ENUM entry that would be the equiv of the Asterisk pattern _21XX (notice no dot). -- Eric Wieling * BTEL Consulting * 504-210-3699 x2120