TMT Analysis is a leading provider of data, intelligence and analytics, helping customers find extra value from the information they hold. Our team of technology and telecommunications specialists has a proven track record empowering companies, brands and agencies around the world to better understand their businesses and their customers. TMT Analysis has a suite of technology and telecommunications data available, for further information, please visit www.tmtanalysis.com or email info@tmtanalysis.com.
format required | string json,csv. |
key required | string The API key (obtained from https://viteza.tmtanalysis.com or from Support during customer on-boarding). |
secret required | string The API secret (obtained from https://viteza.tmtanalysis.com or from Support during customer on-boarding). |
number required | string The number in E.164 format. |
{- "number": 40721275636,
- "original_carrier": {
- "name": "Vodafone Romania",
- "spid": 4018720,
- "mcc": 226,
- "mnc": 1,
- "status": 0,
- "ported": true
}, - "current_carrier": {
- "lrn": null,
- "name": "Telekom Romania Mobile (Cosmote)",
- "spid": "4018760,",
- "mcc": 226,
- "mnc": 3
}, - "type": "mobile",
- "status_message": "Success"
}
X-API-Key required | string The API key (obtained from https://viteza.tmtanalysis.com or from Support during customer on-boarding). |
X-API-Secret required | string The API secret (obtained from https://viteza.tmtanalysis.com or from Support during customer on-boarding). |
format | string json/csv |
number | string The number in E.164 format.(Only for one query numbers). |
numbers | Array of strings The numbers in E.164 format.(Only for multiple query numbers). |
{- "format": "json",
- "number": 40721275636,
- "numbers": [
- [
- 40721275636,
- 40721275637
]
]
}
{- "number": 40721275636,
- "original_carrier": {
- "name": "Vodafone Romania",
- "spid": 4018720,
- "mcc": 226,
- "mnc": 1,
- "status": 0,
- "ported": true
}, - "current_carrier": {
- "lrn": null,
- "name": "Telekom Romania Mobile (Cosmote)",
- "spid": "4018760,",
- "mcc": 226,
- "mnc": 3
}, - "type": "mobile",
- "status_message": "Success"
}
ENUM resolution operates much like reverse DNS lookup. To perform the lookup, the E.164 number needs to be transformed as follows:
After transforming the number, perform a DNS lookup looking for NAPTR records:
$ dig -t naptr @TMTIP 0.6.0.0.1.6.6.6.7.0.4.e164enum.tmtvelocity.com
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40696
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;0.6.0.0.1.6.6.6.7.0.4.e164enum.tmtvelocity.com. IN NAPTR
;; ANSWER SECTION:
0.6.0.0.1.6.6.6.7.0.4.e164enum.tmtvelocity.com. 3600 IN NAPTR 10 100 "u" "E2U+pstn:tel"
"!^(.*)$!tel:1\;npdi\;rn=\;cic=4018720\;cc=ro\;cn=VODA\;nt=mobile\;mcc=226\;mnc=01!" .
The parameters returned are based on RFC4694:
Unsuccessful queries will be responded to with status NXDOMAIN and a blank answer section.
Example:
$ dig -t naptr @TMTIP 0.6.0.0.1.6.6.6.1.0.4.e164enum.tmtvelocity.com
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19974
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;0.6.0.0.1.6.6.6.1.0.4.e164enum.tmtvelocity.com. IN NAPTR
TMT Sip Redirect Server
The purpose of the TMT Sip Redirect server is to provide TMT customers with real-time NP data by redirecting SIP messages to the appropriate routing endpoint based on the current network of the called party.
Simplified, the call-flow is:
For each network in the countries to which the Customer can request NP query, the customer will provide:
Example:
For network ‘TIM’, the customer wants to be able to send the calls to 10.1.1.1 and 10.1.1.2 with prefix 998. In this example, 10.1.1.1 is the first route and fails the call to 404 not found.
TMT Sip Redirect server can handle any variables in the message type (3xx message type) and any variables in the Contact field for the 3xx message (multiple routes, q=, expires=, prefix).
For each country provisioned, an operators file is provided during the provisioning process. If any time there are movements in the operators list for a provisioned country, an update is sent by TMT Analysis support to its customers with the new operators file.
The files contain the following fields, separated by “;”:
Example:
filename SK_operators.csv
4219920;SKOTW;O2 Slovakia;231;06
4219910;SKOGE;Orange Slovakia;231;01
4219900;SKTEL;Slovak Telekom;231;02
4219903;SKSWA;Swan 4KA Slovakia;231;03
4219930;SKZSR;ZSR Slovakia;231;99