Get Started with Number Lookup – ENUM

You can use the Number Lookup ENUM interface to retrieve mobile subscription information given one or more mobile subscriber numbers (MSISDN). This page walks you through account sign up, what a request looks like, and authentication.

Sign up for a Mitto Account

To get started with Mitto, do the following:

1. Sign up for a Mitto account at https://www.mitto.ch/contact/ or write to info@mitto.ch.
2. Submit the IPs you want to use for requests. They must be whitelisted on Mitto’s system.
3. Mitto will respond with your API key. We will confirm configuration of your IP addresses and callback URL.

Request Requirements for the Number Lookup ENUM API

For the ENUM API, you access everything with a uniform resource identifier (URI) consisting of the base zone and the phone number. See the ENUM API Authentication section for more details.

Response Format and Content for the ENUM API

For the ENUM API, responses are returned in a table.

The response will have the following format:
;;ANSWER SECTION:
491XXXXXXXXX.1 IN NAPTR 0 0 “u” “E2U+SIP”
“!^.*$!sip:+491XXXXXXXXX@ims.mnc02.mcc262.3gppnetwork.org\;cost=0.002200000
\ ;ported=0\;user=phone!” .
;; ANSWER SECTION:
491XXXXXXXXX.1 IN NAPTR 0 0 “u” “E2U+SIP”
“!^.*$!sip:+491XXXXXXXXX@ims.mnc02.mcc262.3gppnetwork.org\;cost=0.002200000
\ ;ported=0\;user=phone!” .


The main parameters returned by the lookup request are the Mobile Country Code (MCC), the Mobile Network Code (MNC) and the cost associated to the service:

Number = +491XXXXXXXXX
MCC = 262 (Germany)
MNC = 02 (Vodafone)
cost = 0.002200000
ported = NOT PORTED

The Number Lookup service can be retrieved for multiple MSISDN by using the same DIG request with multiple contents:
dig @185.124.68.123 –p 5353 IN NAPTR 4.3.2.1.5.5.5.2.7.1.9.4.e164.arpa 4.3.2.1.6.5.5.2.7.1.9.4.e164.arpa

In this case the answer to the lookup request will have the following format:
;; ANSWER SECTION:
491725551234. 1 IN NAPTR 0 0 “u” “E2U+SIP”
“!^.*$!sip:+491XXXXXXXXX@ims.mnc02.mcc262.3gppnetwork. org\;cost=0.002200000\;ported=0\;user=phone!” .

;; ANSWER SECTION:
491725561234. 1 IN NAPTR 0 0 “u”“E2U+SIP”
“!^.*$!sip:+491XXXXXXXXX@ims.mnc03.mcc262.3gppnetwork. org\;cost=0.002200000000\;ported=1\;omnc=02\;user=phone!” .

The main information returned by the request is similar to the previous example:

Number = +491XXXXXXXXX
MCC = 262
MNC = 02
cost = 0.002200000
ported = NOT PORTED

Number = +491XXXXXXXXX
MCC = 262
MNC = 03 (E-plus)
cost = 0.002200000
ported = PORTED OMNC = 02 (the number was ported from Vodafone to E-plus)

Authentication

This section describes authentication for the ENUM interface and the HTTP REST API.

ENUM API Authentication

For the ENUM API, you access it through a uniform resource identifier (URI) consisting of a base zone and a phone number. The base zone is e164.arpa.

You can reach the API using the following interfaces:

The ENUM API uses IP whitelists for authentication, so you must register the IP address of your client to ensure access to the ENUM Lookup API. Contact your account manager or the support desk for assistance.

You access the ENUM API through the following base zone: e164.arpa

The complete lookup ENUM URI is built as follows:
[Reverse MSISDN number separated by dots].e164.arpa

For example, to look up the number +491XXXXXXXXX using the ENUM API, use the following URI:
4.3.2.1.5.5.5.2.7.1.9.4.e164.arpa

Using the DIG command, it is easy to access Mitto’s ENUM Lookup API:
dig @185.124.68.123 -p 5353 IN NAPTR 4.3.2.1.5.5.5.2.7.1.9.4.e164.arpa