tyntec’s Global Number Verification minimizes message loss and unsuccessful call attempts with real-time phone number verification, providing key information on your users’ phone numbers, such as subscriber status and roaming data.
Global Number Verification is available with the Synchronous SOAP (Simple Object Access Protocol) API.
SOAP is a protocol used for exchanging messages over a computer network. The messages that are sent do not rely on the underlying transport protocol, which is HTTP Post in most cases (and in the specific case of the tyntec infrastructure).
The messages are structured as XML documents and are defined in two parts: the SOAP standard and the tyntec WSDL file.
- The SOAP standard describes elements necessary for communication, such as the “SOAP Envelope,” which encloses the actual content to be sent. This content is application-specific and is in this case defined by the WSDL file that tyntec provides. A simple XML parser can be used for extracting the data from the SOAP response.
- The WSDL file can be accessed at one of the following URLs, depending if HTTP or HTTPS is used:
To implement and use Global Number Verification Synchronous, you should implement the call of a Web Service as defined by the SOAP specification (http://www.w3.org/TR/soap12-part1/) with the help of the provided WSDL file.
Furthermore, the customer needs a computer system with a fixed IP address from where the SOAP call is initiated. This computer system must be reachable from the tyntec IP. For the fastest implementation and expert support from tyntec, we strongly recommend that the Global Number Verification is implemented using:
- Java Axis2 1.3 Web Services framework:
- Tomcat 5.5 or higher for hosting the axis framework:
The following documents are useful in implementing the Global Number Verification service with the above components:
This is the overview of the workflow for querying phone number information:
In addition, the following information is relevant if you’re using the Synchronous SOAP protocol:
As metioned previously, tyntec’s SOAP implementation uses HTTP as its transport layer. The initial request consists of the number to be queried, in international format. The result will contain:
Number range holder network information (MCC/MNC)
- Number range holder country
- Number range holder time zone
Subscription network information
- IMSI network info (MCC/MNC)
- IMSI country
- IMSI time zone
- HLR network info (MCC/MNC)
- HLR country
- HLR time zone
Servicing network information
- MSC network information (MCC/MNC)
- MSC country
- MSC time zone
- Presence information of the handset (true/ false)
- Roaming information (true/ false)
- Porting information (true/ false)
- SS7 network error code