SMS – Simulator


The Simulator creates a virtual environment for the Content Providers (CPs) to test the created applications before connecting with the real-world system. The applications can be tested with actual validations using the simulator.


Following are the software requirements need to install the TAP Simulator.

  • Java – version 1.6.0 or upper
    1. Install Java in Windows:

    1. Install Java in Linux:

Other required libraries are bundled in the package.

Start-Up the Simulator

Step 1: Extract the file

Step 2: Go to the bin folder of the extracted file

Step 3: Start the TAP using sdp-simulator.bat file placed in the bin folder.

Linux – sh sdp-simulator console

Windows – sdp-simulator.bat console


TAP can be accessed from URL http://localhost:10001/

Stop the Simulator

Press Ctrl + C to stop the simulator

Using the Simulator

SDP clients can send requests to the SDP Simulator. Created applications can be used to send requests to the simulator.


Figure 3.1

“Customers Phone” displays the messages received to the customer’s phone.

When a message is received to the customer’s phone, the phone screen displays the message as shown in the figure above.

Similarly, the “Messages sent to Customer” section shows the messages with the details (message sent time, destination phone number and message content) as shown in the figure below.

Figure 3.2

User can still test the MT part alone (without MO) with any application provided that it can send MT messages.

For that, send the MT message to the following URL (which accepts SMS MT) and the MT message will be displayed in the simulator.


To send a message to the application, the CP can use the provided interface in the simulator. Refer the figure below.

Figure 3.3

Above interface is to simulate message sending to the application.

If Delivery Report is required, the option under “Additional Requests” should be selected.Then the “Delivery Report URL” has to be specified, as in the figure below.

Figure 3.4

Enter the details as follows.

URLThe URL where the application ishttp://localhost:5555/mo-receiver
Application IDUnique ID of the ApplicationAPP_00001
PasswordPassword of the application. The application password will be autogenerated when the application is created.password
Customer NumberThe phone number from which the message is sent94232323232
To NumberThe phone number which receives the message77000
EncodingMessage encoding typeText, Binary
(If the encoding type is set to “Binary” the Binary header should be specified. This is applicable only for SMS service. Refer figure 3.5)
applicationIdMessage contentTest Message
Delivery Report RequiredSelect the check box to generate Delivery Report request from the application side
Delivery Report URLURL which sends delivery reports to the application.http://localhost:5555/deliveryReportsms
Status/Error CodeSelect the response status/error code to generate, when MT (Mobile Termination) message received from application.S1000:Success

Following figure shows sample Status/Error codes.

Figure 3.5

If the “Encoding” type selected as “Binary”, a Binary Header has to be specified. Refer the figure below.

Figure 3.6

Once the values are entered correctly, click on the “Send” button.


The messages sent to the application will be displayed with its sent time, phone number, message content and status under “Message sent to Application” section.

Figure 3.7

Response Error Codes

This can respond to a message sent by the client application. A response code will be sent to the destination phone number and the corresponding response shall be identified accordingly.

This will send following error codes to the preconfigured phone numbers as given in the list.

For any other number this will send success response.

Phone NumberStatus CodeDescription
9900000P1001Partial Success
9900001E1301App Not Available Error
9900003E1302SP Not Available Error
9900004E1303Invalid Host IP Error
9900005E1304App Not Found Error
9900006E1305Invalid App ID Error
9900007E1306Invalid Routing key Error
9900008E1307SP Not Found Error
9900009E1310MO Not Allowed Error
9900012E1311MT Not Allowed Error
9900013E1312Invalid Request Error
9900014E1313Authentication Failed Error
9900015E1314NCS Not Available Error
9900016E1315App Connection Refused Error
9900017E1316MSISDN Not Allowed Error
9900018E1317TPS Exceeded Error
9900019E1318TPD Exceeded Error
9900020E1319AT Message Failed Error
9900021E1320SBL Fail Error
9900022E1321Sender Not Allowed Error
9900023E1322Recipient Not Allowed Error
9900024E1323HTTP Request Not Allowed Error
9900025E1324Invalid MSISDN Error
9900026E1325Insufficient Fund Error
9900027E1326Charging Not Allowed Error
9900028E1327Charging Operation Not Allowed Error
9900029E1328Charging Amount Too High Error
9900030E1329Charging Amount Too Low Error
9900031E1330Invalid Sender Address Error
9900051E1350Subscription Reg Blocked Error
9900052E1351Subscription Reg Already Registered
9900053E1352Subscription Reg SLA Error
9900054E1353Subscription Reg Charging Error
9900031E1330Invalid Sender Address Error
9900055E1354Subscription Unreg SLA Error
9900056E1355Subscription Unreg Blocked Error
9900057E1356Subscription Unreg Not Registered
9900061E1360Internal Error
9900062E1361System Error
Restricted Content / Members Only

You cannot view this content because It is available to members only. Please or Register to view this area.