TMS2 Migration

Migrating existing TMS2 applications to TMS3

TMS3 includes full "legacy mode" support for existing TMS2 USSD- and SMS-based third-party applications.

However, the TMS2 platform's interconnect protocols have certain irregularities and issues that are all addressed in the updated TMS3 interconnect protocols. For a list of these differences, please view the "Differences between TMS2 and TMS3 protocols" section.

TMS3 extends the capabilities of its predecessor by offering a single unified web API for initiating communication-related tasks such as sending SMS messages, performing OBS billing or tracking the status of sent messages. This API can be used in conjunction with the normal "callback"-method of USSD and SMS application programming to create rich end-user experiences. For documentation on the new TMS3 web API, please see the TMS3 web API documentation.

The normal "callback URL"-method for implementing USSD and SMS applications has also been improved in TMS3; for example, users are now allowed to specify custom URL parameters directly in the callback URL when configuring an application via the TMS3 administrative web interface.

Steps to port an existing TMS2 application to TMS3

If you simply need to port an existing TMS2 USSD or SMS application to TMS3, please do the following:

  1. The HTTP GET/POST parameters sent by TMS to a third-party application when a message is received have changed slightly to enforce a standard naming scheme. Ensure that your web-based application is modified accordingly; see "Differences between TMS2 and TMS3 protocols" section for a direct comparison of the differences.
  2. Log into the TMS administrative web interface with your TMS username and password and go to either the "USSD" or "SMS" page to access your application configuration. Now, click on the application you wish to change, and set "Connection type" to "HTTP GET" or "HTTP POST"; in other words, make sure that "TMS2 legacy support" is not selected. Click "save changes" to update your application's configuration.
  3. (Optional) You can use the TMS3 web API to send SMS messages, initiating OBS billing, etc. If you are currently sending SMS messages via one of the legacy TMS2 mechanisms, then you are not forced to change this, although it is recommended that you rather adopt the web API as any further enhancements to the platform will be exposed via this API.