SMPP server channel (SMS)
Use the SMPP Server channel to setup an SMPP Server that other SMPP clients can connect to.
Find more information about channels in general here.
Find a complete guide to setting up a secure SMSC with an SMPP Server channel here.
The SMPP (Short Message Peer to Peer) protocol is designed to send and receive high volumes of SMS messages through an internet connection. The number of simultaneous SMPP Server channels depends on the license tier of your SMS Server installation.
The SMPP Server is extremely flexible and customizable to make it a great fit for almost any use case. A part of this flexibility is achieved by using triggers for SMPP authentication as well as acknowledge or forwarding of SMS messages.
You will find a number of trigger templates that can be configured to finish your SMPP Server configuration.
|The TCP port to listen on
|Which IP version to use. This can be either: IP version 4, IP version 6 or both.
|Which IP address to listen on. This is specified for both IPv4 as well as IPv6. Use this option if the server channel should only be available on a specific network.
|To secure the connection with TLS you will need a server certificate.
Specify the name of the certificate to use and in which store the certificate can be found. These certificate stores are available:
|The is the SMSC default character encoding setting. This is used when you send and receive non-unicode messages.
Try changing this setting if you experience problems sending or receiving characters like ‘[‘, ‘]’ or ‘@’.
This can be one of the following:
|Always accept bind request
|Always accept any bind (login) request from any client. Disable this and create an ‘SMPPServerBind’ trigger to only allow logins according to a lookup table.
|Always accept incoming SMS messages
|Always accept any SMS that was sent to the server. Disable this and create an ‘SMPPServerAcknowledge’ trigger to check against a credits table or to add your own custom logic.
|Store SHA1 of Password
|Does not store the password but an SHA1 hash of the password instead.
|Create log for each client
|Here you can specify a directory where the Auron SMS Server will create a details log file for each client that connects to the server.