--- doc/README.enum-orig 2005-11-09 04:48:13.000000000 +0000 +++ doc/README.enum 2005-11-09 04:48:38.000000000 +0000 @@ -58,6 +58,8 @@ (regardless of order or priority.) If "ALL" is the specified service_type, then a count of all methods will be returned for the DNS record. + s = string. Use the argument as a string, instead of a number + sequence that is processed in an ENUM format. (see below) = The record in priority/order sequence based on the total count of records passed back by the query. If a service_type is specified, all entries of that type will be sorted into an @@ -88,6 +90,7 @@ 0.2.0.1.1.6.5.1.0.3.1.loligo.com. 3600 IN NAPTR 26 100 "u" "E2U+sip" "!^\\+13015611020$!sip:1234@sip-2.fox-den.com!" . 0.2.0.1.1.6.5.1.0.3.1.loligo.com. 3600 IN NAPTR 30 100 "u" "E2U+sip" "!^\\+*([^\\*]*)!sip:\\1@sip-3.fox-den.com!" . 0.2.0.1.1.6.5.1.0.3.1.loligo.com. 3600 IN NAPTR 55 100 "u" "E2U+mailto" "!^\\+13015611020$!mailto:jtodd@fox-den.com!" . +jtodd.phone.loligo.com. 3600 IN NAPTR 10 100 "u" "E2U+sip" "!^\\jtodd$!sip:2203@loligo.com!" . Example 1: Simplest case, using first SIP return (use all defaults except for domain name) @@ -122,7 +125,6 @@ returns: ${foo}="enum-test@sip.nemox.net" [note: this result is subject to change as it is "live" DNS and not under my control] - Example 8: Look up the ISN mapping in freenum.org alpha test zone exten => 100,1,Set(foo=${ENUMLOOKUP(1234*256,,,freenum.org)}) returns: ${foo}="1234@204.91.156.10" [note: this result is subject @@ -133,6 +135,11 @@ exten => 100,1,Set(foo=${ENUMLOOKUP(1234567890,sip,1,enum.yoyodynelabs.com)}) returns: ${foo}="" +Example 10: Look up a NAPTR for a DNS record that is not a numeric. (hostname +examined is "jtodd.phone.loligo.com") +exten => 100,1,Set(foo=${ENUMLOOKUP(jtodd,,s,phone.loligo.com) + returns: ${foo}="2203@loligo.com" + Usage notes and subtle features: @@ -221,6 +228,13 @@ unlikely event you wish to avoid ISN re-writes, put an "n" as the first digit of the search string - the "n" will be ignored for the search. + k) For string searches: You can associate NAPTR records with any + DNS record. While the primary goal of this funciton is to allow ENUM + lookups, any NAPTR records can be obtained by using the "s" option which + treats the argument as a string. This allows (as an example) all email + addresses to be entered into a special DNS zone which then maps those + names to alternate SIP URIs. I suppose this could allow a SIP telephony + device to be associated with a record like "www.domain.com". ==EXAMPLES==