CODE YOUR APPS

SMS – SIMULATOR

Overview

TAP 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.

Prerequisites

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

Other required libraries are bundled in the package.

Note: Distribution file will come as a zipped file and extract it to the destination folder.

Start Up the Simulator

Step 1: Extract the sdk-standalone-1.0.0-distribution.zip 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.

Note: An application with the respective NCS enabled, also has to be run with the simulator.

Linux – sh sdp-simulator console

Windows – sdp-simulator.bat console

 

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

Note: An application with the respective NCS enabled, also has to be run with the simulator.

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.

Note: Although the simulator shows the MT message for SMS, user can test MT message alone (without MO), with any application which can send MT messages.

SMS MT

custPhone

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.

http://localhost:7000/sms/send

SMS MO

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.

Field name Description Sample value
URL The URL where the application is http://localhost:5555/mo-receiver
Application ID Unique ID of the Application APP_00001
Password Password of the application. The application password will be autogenerated when the application is created. password
Customer Number The phone number from which the message is sent 94232323232
To Number The phone number which receives the message 77000
Encoding Message encoding type Text, 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)

applicationId Message content Test Message
Delivery Report Required Select the check box to generate Delivery Report request from the application side
Delivery Report URL URL which sends delivery reports to the application. http://localhost:5555/deliveryReportsms
Status/Error Code Select 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

TAP 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.

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

For any other number TAP will send success response.

Phone Number Status Code Description
9900000 P1001 Partial Success
9900001 E1301 App Not Available Error
9900003 E1302 SP Not Available Error
9900004 E1303 Invalid Host IP Error
9900005 E1304 App Not Found Error
9900006 E1305 Invalid App ID Error
9900007 E1306 Invalid Routing key Error
9900008 E1307 SP Not Found Error
9900009 E1310 MO Not Allowed Error
9900012 E1311 MT Not Allowed Error
9900013 E1312 Invalid Request Error
9900014 E1313 Authentication Failed Error
9900015 E1314 NCS Not Available Error
9900016 E1315 App Connection Refused Error
9900017 E1316 MSISDN Not Allowed Error
9900018 E1317 TPS Exceeded Error
9900019 E1318 TPD Exceeded Error
9900020 E1319 AT Message Failed Error
9900021 E1320 SBL Fail Error
9900022 E1321 Sender Not Allowed Error
9900023 E1322 Recipient Not Allowed Error
9900024 E1323 HTTP Request Not Allowed Error
9900025 E1324 Invalid MSISDN Error
9900026 E1325 Insufficient Fund Error
9900027 E1326 Charging Not Allowed Error
9900028 E1327 Charging Operation Not Allowed Error
9900029 E1328 Charging Amount Too High Error
9900030 E1329 Charging Amount Too Low Error
9900031 E1330 Invalid Sender Address Error
9900051 E1350 Subscription Reg Blocked Error
9900052 E1351 Subscription Reg Already Registered
Error
9900053 E1352 Subscription Reg SLA Error
9900054 E1353 Subscription Reg Charging Error
9900031 E1330 Invalid Sender Address Error
9900055 E1354 Subscription Unreg SLA Error
9900056 E1355 Subscription Unreg Blocked Error
9900057 E1356 Subscription Unreg Not Registered
Error
9900061 E1360 Internal Error
9900062 E1361 System Error