SMSC Simulator

SMPP SMSC simulator to test SMS messaging applications.


Melrose Labs operates SMSC simulators (aka SMPP server simulators) and Dedicated SMSC Simulators for use in the development and testing of SMS text messaging capabilities within applications. They simulate SMSCs (short message service centres) and SMPP SMS gateways, and simulate SMS message delivery. SMPP v3.3, SMPP v3.4 and SMPP v5 using TLS and non-TLS connections are supported.

Applications send SMS messages to mobiles by submitting messages to the SMSC Simulator service using SMPP. The SMSC simulators simulate the delivery of the messages, including the generation of delivery receipts back to the application. SMS messages from mobile numbers can also be submitted and delivered to the SMS application (see Simulate Inbound SMS to your Application).

The SMSC simulators enable you to send SMS messages from your application without messages being delivered to real mobile phones and therefore without any SMS delivery costs. Stress testing of your application can also be performed to show how your application behaves under load and various other scenarios tested before live operation and without affecting production SMSCs. The SMSC simulators can handle high rates of SMS and a large number of simultaneous connections from your application.

Using the SMSC Simulator service

The SMSC Simulator service is publicly available and connection details can be found below. Melrose Labs also provides a Dedicated SMSC Simulator service for those with testing needs beyond the public service. SMSC Simulator is part of Melrose Labs SMPP Testing services.

SMPP over TLS support is available for SMS applications to connect securely (SMPP TLS port: 8775).

SMSC Simulator SMPP Account Details

The system ID and password are dynamically updated on this webpage. Click on "Generate" to retrieve your password.

Server:smscsim.melroselabs.com
Port:2775 (non-TLS), 8775 (TLS)
System ID:545938
Password: (valid 10-days)
Sign Up | Login for 90-day password
System type:null

Use the above SMPP bind parameters with the SMSC simulators. If you need any help, or have any suggestions for improving the simulators, then send us a support request.

Dedicated SMSC Simulator
Test inbound and outbound SMS loads. High TPS. Customisations.

Pricing

SMPP SMS Gateway
Your SMS gateway platform

Get platform

Inbound MO SMS Tool

Use this tool to send MO SMS to your application from the SMSC Simulator to simulate inbound SMS from a mobile. SMPP system ID and password must be the same as used by your application, and destination address must contain system ID.

Please provide an address (min. 8 characters).
Please provide an address (min. 8 characters).
Related services 
 Tyr SMS Gateway
 SMS Test
 Rich Messaging
 SMPP SMS Gateway
 SMPP Load Balancer
 Dynamic SMS Pricing
 SMPP Testing
 Message Exchange
 RCS Messaging
 SS7 SMSC
 SMS Firewall
 REST-SMPP Intelligent Bridge
Tutorials:  Send SMS with SMPP (Python, Java, Go, Perl, C++, C#, Node.js, Ruby, PHP)

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.

Example: If your system ID was "123456" then to send an inbound SMS to your application you would use a separate SMPP transmitter (TX) bind, or the Inbound MO SMS Tool, to submit a message (submit_sm) to the destination_address "99123456" (digits in bold are your system ID). This would cause the SMSC Simulator service to send a deliver_sm to your application with the source_addr that you set in the submit_sm and destination_addr of "99123456".

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

SMSC simulators last updated 9 July 2020

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)

Melrose Labs SMSC Simulator Abbreviated SMPP PICS

SMSC Simulator Abbreviated SMPP Protocol Implementation Conformance Statement (SMPP PICS)

Operations Supported

ItemFunctional Unit/DescriptionSupported
PDU-OUTBINDIs the outbind PDU supported?NO
PDU-BIND-TRANSMITTERIs the bind transmitter PDU supported?YES
PDU-BIND-RECEIVERIs the bind receiver PDU supported?YES
PDU-BIND-TRANSCEIVERIs the bind transceiver PDU supported?YES
PDU-UNBINDIs the unbind PDU supported?YES
PDU-ESME-GENERIC-NACKIs the generic_nack PDU initiated by the EMSE supported?YES
PDU-SMSC-GENERIC-NACKIs the generic_nack PDU initiated by the SMSC supported?YES
PDU-SUBMIT-SMIs the submit_sm PDU supported?

  • schedule_delivery_time - absolute and relative supported
  • validity_period - ignored
  • registered_delivery - SMSC delivery receipt supported
  • message_payload TLV (0x0424) supported Added 9 Jul 2020
YES
PDU-SUBMIT-MULTIIs the submit_multi PDU supported?NO
PDU-DELIVER-SMIs the deliver_sm PDU supported?

  • MO SMS for ESME-initiated submit_sm only
  • delivery receipts for ESME-initiated submit_sm only
  • message_payload TLV (0x0424) supported Added 9 Jul 2020
  • data_coding from submit_sm used in deliver_sm (MO) Added 1 May 2021
YES
PDU-ESME-DATAIs the data_sm PDU initiated by the EMSE supported?

  • registered_delivery - SMSC delivery receipt supported
  • message_payload TLV (0x0424) supported Added 9 Jul 2020
YES
PDU-SMSC-DATAIs the data_sm PDU initiated by the SMSC supported?

  • MO SMS for ESME-initiated data_sm only
  • delivery receipts for ESME-initiated data_sm only
  • message_payload TLV (0x0424) supported Added 9 Jul 2020
YES
PDU-QUERY Is the query_sm PDU supported?

  • message_id - only parameter used to identify message
  • RX or TRX bind must be present to drive delivery of MT SMS
YES
PDU-CANCEL Is the cancel_sm PDU supported?

  • message_id - only parameter used to identify message
  • RX or TRX bind must be present to drive delivery of MT SMS
YES
PDU-REPLACEIs the replace_sm PDU supported?NO
PDU-ESME-ENQUIRE-LINKIs the enquire_link PDU initiated by the EMSE supported?YES
PDU-SMSC-ENQUIRE-LINKIs the enquire_link PDU initiated by the SMSC supported?YES
PDU-ALERTIs the alert_notification PDU supported?NO

Notes on using the SMSC Simulator service

  1. SMPP (Short Message Peer-to-Peer) protocol must be used to connect to the simulator.
  2. Use SMPP v3.3, v3.4 or v5 and specify the version in the bind request.
  3. Bind using one or more transmitter (TX), receiver (RX) or transceiver (TRX) binds.
  4. Use transceiver (TRX) or receiver (RX) binds to receive delivery receipts.
  5. If a delivery receipt has been requested for a message, a receipt will be returned to your application in <1 second after the submit_sm_resp. If there is no existing TRX or RX bind, then the receipt may be discarded.
  6. Mobile numbers (MSISDNs) should be in international format.
  7. TLS 1.1 and up are supported for SMPP sessions. SSL and TLS 1.0 are not supported for connections.

Source code for the original version of our SMSC simulator can be found in the Melrose Labs GitHub repository at smpp-smsc-simulator.

For production SMSCs and SMS gateways we suggest you take a look at the following:

Pricing

The SMSC Simulator service is provided free-of-charge for the public service.

Dedicated SMSC Simulator instances

We also offer dedicated SMSC Simulator instances with support for 8000 SMS/sec, up to 50 SMPP binds, SMPP v5 flow control and congestion avoidance, and configurable DLRs (status, latency, format). Please contact us if you are interested in dedicated SMSC Simulator instances.

Service snapshot

  • Test SMS applications and infrastructure without SMS cost
  • SMPP v3.3, v3.4 and v5
  • MT and MO SMS testing (A2P and P2A)
  • SMPP over TCP and SMPP over TLS 1.1+ supported
  • SMPP test tool

Related

Find out more...

Please provide your name.
Please provide a valid company name.
Please type your message.
Please provide a valid email address.