SMSC Simulator

SMS Text Simulator: Simulate Inbound SMS to your Application

To simulate MO SMS (i.e. inbound SMS or person-to-application SMS) from a mobile to your application, you can either (a) use an SMPP TX bind to submit the MO message to the simulator or (b) use the above Inbound MO SMS Tool.

In either case, you would submit a message using the above SMPP account details to a destination_address that contains the digits of your system ID. By including the digits of your system ID in the destination_address, the message will be routed by the simulator to your application. The destination_address field must be at least 8 digits in length so ensure that you prepend or append at least two digits to your system ID, otherwise the simulator will reject the submission.

The simulator also supports the use of schedule_delivery_time in the submit_sm and this can be used to schedule delivery of MT and MO SMS.

SMPP operations supported by the simulators

We are working to ensure that our simulators allow you to test most, if not all, aspects of SMPP applications such as applications with SMS support and SMS infrastructure. Operations currently supported by the simulators are shown below. Further operations will be provided in future and frequent updates.

• Session Management:
  • bind_receiver/resp - Used for receiving delivery receipts.
  • bind_transmitter/resp - Used for submitting messages.
  • bind_transceiver/resp - Supported for v3.4 and v5, and used for submitting messages and receiving delivery receipts.
  • unbind/resp - ESME unbinding from SMSC and SMSC issues unbind_resp. SMSC unbinding from ESME when ESME unresponsive.
  • enquire_link/resp - Will respond to enquire_link from ESME and will issue enquire_link to ESME every 45s of inactivity.
• Message Submission:
  • submit_sm/resp - Will issue positive response with message_id of 8 characters in length for v3.3 and 64 characters for v3.4 and v5. Will issue error response (ESME_INVDSTADR/0x0000000B) if destination_address less than 8 characters in length.
• Message Delivery:
  • deliver_sm/resp - Delivery receipts sent to ESME on receiver binds (SMPP v3.3, 3.4 and v5) and transceiver binds (SMPP v3.4 and v5 only). deliver_sm short_message field with textual receipt plus TLVs containing message ID (i.e. receipted_message_id), status of message (i.e. message_state with value of 2 for DELIVERED) and error (i.e. network_error_code with value of zero indicating no error)

Public SMSC Simulator service

The SMSC Simulator public (shared) service supports up to 100 SMS/sec and is charged at:

• USD 100 for 5 SMPP credentials
• USD 25 for 1 SMPP credential

Credentials are valid for 90-days from issue.

Dedicated SMSC Simulator instances

We also offer Dedicated SMSC Simulator instances with support for 8000 SMS/sec, up to 50 SMPP binds, unlimited number of SMPP credentials, SMPP v5 flow control and congestion avoidance, and configurable DLRs (status, latency, format).

Instances are available at our London, Frankfurt, Stockholm, Cape Town, Hong Kong, Singapore, Sydney, North Virginia, Ohio and São Paulo locations.

Available in one month blocks at GBP 250 per month.

Please contact us if you require a Dedicated SMSC Simulator instance.