ℹ️ The Auron SMS Server is now Auron Omni. Learn more here.

How can we help?

SMPP server channel (SMS)

Use the SMPP Server channel to set up 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 over an internet connection. The number of simultaneous SMPP Server channels depends on the license tier of your Auron Omni subscription.

Edit SMPP Server channel
Edit SMPP Server channel

The SMPP Server is highly flexible and customizable, making it suitable for almost any use case. This flexibility is achieved through triggers for SMPP authentication, acknowledgements, and message forwarding.

Handling bind request (logins)

When Always accept bind request is set to false, the SMPP Server channel creates an incoming SmppServerBind message for each incoming bind request.

To manually handle bind requests, configure a trigger that processes incoming SmppServerBind messages.

To accept a bind request, set the StatusCode property to 0. Any other value rejects the bind request.

After setting the StatusCode, set the StatusID property of the SmppServerBind message to SCHEDULED. The SMPP Server channel will then process the message and send the corresponding bind response to the connecting SMPP client.

You will find a number of trigger templates that can help you complete your SMPP Server configuration.

Note: A SystemID can be up to 15 characters, a Password can be up to 8 characters.

Settings

PropertyDescription
PortThe TCP port to listen on.
IP VersionThe IP version to use. This can be IPv4 (0), IPv6 (1), or both (2).
IP Address v4The IPv4 address to listen on. Use this option if the server should only be available on a specific IPv4 network. Leave empty to listen to all IP’s.
IP Address v6The IPv6 address to listen on. Use this option if the server should only be available on a specific IPv6 network. Leave empty to listen to all IP’s.
CertificateTo secure the connection with TLS, you must use a server certificate.

Specify the certificate name and the certificate store. The available certificate stores are:
  • Local Machine. Access requires the service to run as LocalSystem or with administrator rights.
  • Current User. This is the certificate store of the user running the Auron Omni service
Default charsetThis is the SMSC default character encoding used for non Unicode messages.

Adjust this setting if you experience issues with characters such as ‘[‘, ‘]’, or ‘@’.

Options include:
  • Incoming and outgoing SMS use GSM charset in 8bit (-6)
  • Incoming and outgoing SMS use GSM charset in 7bit (-3)
  • Incoming SMS uses GSM charset in 7bit, outgoing uses ASCII (-1)
  • Outgoing SMS uses GSM charset in 7bit, incoming uses ASCII (-2)
  • Incoming SMS uses GSM charset in 8bit, outgoing uses ASCII (-4)
  • Outgoing SMS uses GSM charset in 8bit, incoming uses ASCII (-5)
Always accept bind requestAlways accepts any bind (login) request from clients. Disable this option and use an “SMPPServerBind” trigger to control authentication using a lookup table.
Always accept incoming SMS messagesAlways accepts incoming SMS messages sent to the server. Disable this option and use an “SMPPServerAcknowledge” trigger to implement custom logic such as credit checks.
Store SHA1 of PasswordStores an SHA1 hash of the password instead of the plain text password.

When ‘Always accept bind request’ is disabled every incoming bind becomes a new ‘SMPPServerBind’ type message. If this option is checked the channel doesn’t store the password in the SMPPServerBind but stores an SHA1 hash instead.
Create log for each clientSpecifies a directory where Auron Omni creates a detailed log file for each client that connects to the server.