SSH to your Dedicated SMSC Simulator (DSS) instance to generate SMPP credentials and start, stop or check the DSS.

== Generate SMPP credentials ==

To generate SMPP credentials for applications to connect to the SMSC Simulator using SMPP, use the following command: ./ec2MLSMSCSimulator gencredentials

The will produce output similar to the following: ./ec2MLSMSCSimulator Melrose Labs - Build timestamp: Mar 2 2021 17:49:23

Generated SMPP Credentials (valid 90 days)

System ID Password

980632 30fc81
443358 32abd5

The credentials will be valid for 90 days. When the credentials expire, the DSS will reject SMPP bind attempts using those credentials with an SMPP "command status" 13 returned to your application. You can generate new credentials using the above steps.

The SMPP system type is always null (empty).

If required, a system ID may be used simultaneously by multiple applications.

== Starting the SMSC Simulator ==

The DSS will automatically start (systems service) when an AWS EC2 instance is launched or reboots.

To start DSS:

sudo systemctl start smscsimulator

To get the status of the DSS process:

sudo systemctl status smscsimulator

== Connecting your application via SMPP to the DSS ==

Use SMPP credentials (system ID and password) created above with your application.

Your application should connect to port 2775 at the hostname of your DSS AWS EC2 instance.

When your application is connected and has established its SMPP sessions with the DSS, your application can then submit messages to the DSS.

CDR files can be found in the cdrs directory at /home/ec2-user/cdrs. These files contain a row for each message submitted to the simulator.

See the SMPP specification at https://smpp.org  for further details using the Short Message Peer-to-Peer (SMPP) protocol.

== Stopping the SMSC Simulator ==

To stop DSS:

sudo systemctl stop smscsimulator

== Further documentation ==

https://melroselabs.scrollhelp.site/dss/dedicated-smsc-simulator