ENUM anyone?

Fully featured open source IP telephony system.

Moderator: ljtom

ENUM anyone?

Postby cogi » 10 Nov 2009, 16:40

ENUM RFC 3761 is a service that uses the Internet DNS system to translate E.164 (i.e. ordinary) telephone number into IP address or Uniform Resource Identifier (URI) that can be used for communication. ENUM stands for E.164 NUmber Mapping.

Public ENUM service is using globally allocated DNS zone e164.arpa. Each country can register a domain corresponding to an international prefix. So, for example for Poland (+48) it is 8.4.e164.arpa.

But the real question is? Is it possible to have our "Private ENUM" service? Of course it is 8-) Why would we need it? As an example: we can simplify our dialplan (Private ENUM) or build a peering point with other VoIP service providers (Carrier/Infrastructure ENUM).

To make a use from our private ENUM service we will need DNS server which supports NAPTR records. I will use BIND.

At first we need to create our "ENUM" zone. In this example I'm creating e164.atr.
Code: Select all
/etc/named.conf

zone "e164.atr" {
        type master;
        notify no;
        file "pz/e164.atr";
};


Code: Select all
/var/named/pz/e164.atr
@       IN      SOA     ns.e164.atr. hostmaster.e164.atr. (
                        200911101       ; serial, todays date + todays serial #
                        8H              ; refresh, seconds
                        2H              ; retry, seconds
                        4W              ; expire, seconds
                        1D )            ; minimum, seconds
;
                NS      ns              ; Inet Address of name server
;
localhost       A       127.0.0.1
ns              A       192.168.1.20

6.6.7.7.6.6.6.4.4.8.4.e164.atr. NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:48446667766@pbx1.branch.org!".


Let's check if it is working:
Code: Select all
[root@atrcc pz]# dig 6.6.7.7.6.6.6.4.4.8.4.e164.atr naptr

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> 6.6.7.7.6.6.6.4.4.8.4.e164.atr naptr
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25653
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;6.6.7.7.6.6.6.4.4.8.4.e164.atr.        IN      NAPTR

;; ANSWER SECTION:
6.6.7.7.6.6.6.4.4.8.4.e164.atr. 86400 IN NAPTR  10 100 "u" "E2U+sip" "!^.*$!sip:48446667766@pbx1.branch.org!" .

;; AUTHORITY SECTION:
e164.atr.               86400   IN      NS      ns.e164.atr.

;; ADDITIONAL SECTION:
ns.e164.atr.            86400   IN      A       192.168.1.20

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Nov 10 18:23:30 2009
;; MSG SIZE  rcvd: 147

It is. If IP PBX will lookup for E.164 number 48446667766 (6.6.7.7.6.6.6.4.4.8.4.e164.atr) it will be redirected to 48446667766@pbx1.branch.org via SIP protocol. Thanks to this we can bypass traditional telephony network and connect directly via SIP, perfect!

Cheers,
Cogi
User avatar
cogi
Site Admin
 
Posts: 14
Joined: 01 Nov 2009, 12:05

Return to Asterisk

Who is online

Users browsing this forum: No registered users and 1 guest

cron