SMPP client channel (SMS)
Use the SMPP (client) channel to connect to an SMPP provider.
Find more information about channels in general 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 channels depends on the license tier of your SMS Server installation.
To use the SMPP channel you will need a subscription to an SMPP provider, also called an SMSC or SMS Center. SMPP providers charge a small fee per SMS.
The trial version of the Auron SMS Server has a connection to the Auron demo SMPP gateway pre-configured. This gateway allows for sending up to 10 free SMS messages meant to demonstrate the SMPP functions of the SMS Server. The Auron SMPP Gateway is not available for production or commercial use.
|Connection||The connection is a combination of hostname/port and a ‘secure’ checkbox. Check the ‘secure’ checkbox to enable TLS connections.
Most SMPP providers only accept connections from clients that are white-listed. So when the SMPP Client channel has trouble connecting please verify that our IP address is known with your SMPP provider.
|SystemID / Password||Username and password. SystemID is SMPP lexicon for Username|
|System Type||The type of client connection. This is normally either empty or ‘SMPP’.|
|Version||This is the SMPP version that the client side supports. Normally this should be 3.4. The SMPP Server can identify as 3.3 and 5.0 only for compatibility reasons.|
|Address range||This field is normally empty. But it can contain a range of phone numbers that should be sent to your client. The range in that case should be a regular expression.|
|Connect timeout||The maximum time (S) that the SMPP client will attempt to connect to the server.|
|Bind timeout||The maximum time (S) that the SMPP client will wait for a response on the Bind request. Bind is SMPP lexicon for login.|
|Command timeout||The maximum time (S) that the SMPP client will wait for a response on any account.|
|Large Messages||Indicates how large outgoing messages (i.e. messages longer than 160 characters) should be treated.
There are these options:
|SMSC Default||The is the SMSC default character encoding setting. This is used when sending non-unicode messages.
Try changing this setting if you experience problems sending or receiving characters like ‘[‘, ‘]’ or ‘@’.
This can be one of the following:
|Request delivery report||Check this to always request a delivery report from your provider. A delivery report contains the status of an outgoing message.|
|Reference format||The message reference connects a sent SMS message to a delivery report. Some providers will have the message reference in a different format for the originating SMS and the connecting SMS report.|
|Enquire interval||The interval for the Enquire packet. This is sent to the SMPP Server to let them know the connection is still alive.|
|Assemble multipart SMS||Will try to automatically assemble a multipart message. This means that the SMS Server will only receive a single message instead of all individual parts.|
|Extract application port||Extract the application port of from an SMS message if it was sent to an application port. Some SMS messages can be sent not directly to the inbox but instead to a specific application on the phone.
To do this they use an ‘application port’ that is set in the UDH of the SMS message. With this option enabled the UDH is extracted from the SMS and the application port is integrated in the ‘ToAddress’ of the SMS message.
For example. An SMS message sent to +3112345678 with application port ‘1000’ will have its ‘ToAddress’: ‘+3112345678:1000’ with this setting enabled. With this setting disabled the message will be binary and the UDH will still be part of the message.
|From address||The default from address for SMS messages sent on this channel|
|Service Type||The default service type for SMS messages sent on this channel|
|Message TLV’s||Default TLV’s that should be appending to SMS messages sent on this channel|
|Submit mode||Normally an SMS message is used in a submit_sm package. Set this to data_sm to send the SMS in a data_sm package.|
|Multipart mode||The multipart mode determines how multipart (large) SMS messages are sent by the SMS Server
This can be one of the following:
|Detailed tracing||Log more details to the trace file. This will log all communication with server. Will come at a performance penalty.|
|Reconnect timeout||The number of seconds to wait before re-connecting when a connection is lost.|
|Delivery report timeout||The maximum time (S) to wait for a delivery report.|
|Max pending PDU’s||The maximum number of Protocol Data Units that can be sent and unconfirmed at any time.|
|Max receive queue||The maximum number of SMS messages that can be in the receive queue before they are written to the database|
|Max send queue||The maximum number of SMS messages that can be read from the database and sent out at once.|