Query Structure
Each ENUM query sent to the API should contain the following structure:
$ dig @lookup.engy-api.io -p 6363 <number>.<optional_product>.e164.arpa IN NAPTR
Where:
lookup.engy-api.io
is the eNgY Solutions ENUM API endpoint.6363
is the port for the ENUM API.<number>
represents the mobile telephone number in reverse order, separated by dots.<optional_product>
represents the product being used. If left empty, the default product will be used.
Successful Query Response Example
$ dig @lookup.engy-api.io -p 6363 5.2.3.2.0.2.1.0.7.7.4.4.e164.arpa IN NAPTR
; <<>> DiG 9.10.6 <<>> @lookup.engy-api.io -p 6363 5.2.3.2.0.2.1.0.7.7.4.4.e164.arpa IN NAPTR ; (1 server found)
;; global options: +cmd
;; Got answer: ;; ->>HEADER<<- opcode: QUERY status: NOERROR id: 46510 ;; flags: qr rd ra; QUERY: 1 ANSWER: 1 AUTHORITY: 0 ADDITIONAL: 1
;; QUESTION SECTION: ;5.2.3.2.0.2.1.0.7.7.4.4.e164.arpa. IN NAPTR
;; ANSWER SECTION: 5.2.3.2.0.2.1.0.7.7.4.4.e164.arpa. 3600 IN NAPTR 0 0 "u" "E2U+SIP" "!^.*$!sip:[email protected];gsm_error_code=0;imsi=234308193242210;msc=44795291012;omnc=15;ported=1!" .
;; ADDITIONAL SECTION: RequestId. 6000 IN TXT "36274d20-0a6e-492b-8f73-c12f26ffb999"
;; Query time: 432 msec ;; SERVER: lookup.engy-api.io#6363(lookup.engy-api.io)
Unsuccessful Query Response Example
$ dig @lookup.engy-api.io -p 6363 1.2.3.2.0.2.1.0.7.7.4.4.e164.arpa IN NAPTR
; <<>> DiG 9.10.6 <<>> @lookup.engy-api.io -p 6363 1.2.3.2.0.2.1.0.7.7.4.4.e164.arpa IN NAPTR ; (1 server found)
;; global options: +cmd
;; Got answer: ;; ->>HEADER<<- opcode: QUERY status: REFUSED id: 21869 ;; flags: qr rd ra; QUERY: 1 ANSWER: 1 AUTHORITY: 0 ADDITIONAL: 1
;; QUESTION SECTION: ;1.2.3.2.0.2.1.0.7.7.4.4.e164.arpa. IN NAPTR
;; ANSWER SECTION: 1.2.3.2.0.2.1.0.7.7.4.4.e164.arpa. 3600 IN NAPTR 0 0 "u" "E2U+SIP" "!^.*$!sip:[email protected];err=1!" .
For executing the same query against specific products (if configured in the future), the following format can be used:
$ dig @lookup.engy-api.io -p 6363 <number>.<optional_product>.e164.arpa IN NAPTR
Where <optional_product>
can be customized based on future configurations or requirements.