Goal (short description)
Goal is to set ENUM (RFC3761,Wikipedia) records to provide E.164 telephone number to URI translation.
Applicability
It is applicable for institution or even person using E.164 telephone number and willing to provide such translation.
Prerequisites (OS, dependencies on other software)
- DNS server with NAPTR support (i.e. current BIND9).
- Enum domain which is constructed as reversed telephone number +123456 -> 6.5.4.3.2.1.suffix.
Suffixes
e164.arpa - Public User Enum tree
If you want to use Public User Enum you need to be eligible user of number(s) and register your number or prefix by registrator in country where the number belongs. Your eligibility is validated by special process that depends on your registrator (validation SMS, TSP Invoice, ...).
Current status of golden tree (e164.arpa) delegations could be fount at enumdata.org
nrenum.net - Private NREN tree
nrenum.net is an effort of National Research and Education Networks (NREN) and provides nrenum.net provides countries, where the Golden ENUM Tree (e164.arpa) is not (yet) available, with the possibility to publish ENUM data. The nrenum.net tree is queried by the participating partners in case no ENUM data is found in the Golden Tree.
See nrenum.net for more infromation.
sample.edu - Institutional private tree
You can have you own private tree within you domain. It is usable for internal routing i.e. in case that you have several locations or so and you need to provide different share translation different from golden tree or nrenum.
There are also lots of managed private tree like enum.org enum.info and so on.
Configuration (OS agnostic)
Number prefix is 123456 (with 3 digit branch) and suffix is e164.arpa.
- Create zone 6.5.4.3.2.1.e164.arpa
- Prepare records
These recorda provides translation for numbers starting with +123456 (+123456789 but also +1234567899999).
Following records use wildcards, which can fasten the setup but can be sometimes problematic. Be carefull especially when using more records (for dfferent numbers or prefixes) order pref flags service regexp replacement *.6.5.4.3.2.1.e164.arpa. IN NAPTR 100 10 "u" "E2U+sip" "!^(.*)$!sip:\\1@sample.edu!" . *.6.5.4.3.2.1.e164.arpa. IN NAPTR 100 10 "u" "E2U+h323" "!^\\+12(3456.*)$!h323:\\1@sample.edu!" .
First one is for SIP service. Translation of +123456789 leads to URI sip:123456789@sample.edu.
Second one is for H.323 service. Translation of +123456789 leads to URI h323:3456789@sample.edu.
You can also set up records for full numbers