SMSC Simulator

SMPP SMSC simulator to test SMS messaging applications.


Melrose Labs provides access to SMSC simulators (aka SMPP server 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 are supported using TLS and non-TLS connections.

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 (i.e. MO SMS) can also be submitted and delivered to the SMS application.

Accessing the SMSC Simulator service

The SMSC Simulator service is publicly available and connection details can be purchased below. Dedicated SMSC Simulator instances are also available 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

Server:smscsim.melroselabs.com
Port:2775 (non-TLS), 8775 (TLS)
System ID:
Password:
Sign Up | Login to purchase 90-day SMPP credentials
System type:null

Use the above SMPP account details in your application or our SMPP clients to connect to the SMSC simulators. SMPP credentials must be purchased to use the SMSC Simulator service.

More / Pricing

Inbound MO SMS Tool

Use the Inbound MO SMS Tool to send MO SMS to your application from the SMSC Simulator to simulate inbound SMS from a mobile.

SMPP clients

SMPP Client SMPP Sender SMPP Multi-Sender SMPP Chat

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

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)
SMSC Simulator technical details

For production SMSCs and SMS gateways we suggest the following platforms and services:

Pricing

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

Credentials are valid for 90-days.

Sign Up | Login to purchase 90-day SMPP credentials

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.

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.