SMPP Protocol Providers

The following table describes the settings for SMPP Protocol Providers.

Note: xMatters supports SMPP version 3.4 only.
SMPP Provider Details

Setting

Description

Name

Name of the service provider.

Description

Description of the provider.

Maximum Retries

Number of times to resend a notification before potentially using an alternate service provider; allowable values are from 0 to 10.

Retry interval

Amount of time in seconds to wait between retries.

Maximum session size

Number of notifications per connection/session.

Split long message

Controls whether notifications that exceed the number of characters specified by the Split size setting are split into multiple smaller messages or sent as a single message.

Split size

Determines the maximum number of characters per message sent to this Protocol Provider. This setting applies only if the Split long message check box is selected.

Maximum message length

If enforced by this provider, the maximum number of characters allowed per notification. For more information, see Setting Maximum Message Length.

Maximum PIN length

If enforced by this provider, the maximum number of characters allowed in a PIN. If the PIN is longer than the maximum PIN length, the leading characters are truncated.

Split Method

Specifies the concatenation mechanism used by the provider when splitting and reassembling long SMS messages. With concatenation, it is possible to send a single long message to a mobile station as a series of several short messages, and to display them as one message on the target Device.

Concatenation is performed at the Device itself, which uses additional information fields within the messages to identify, sort, and join the content into a single message. Up to a maximum of 255 short messages (of less than 160 characters each) can be joined in this way. xMatters provides two methods of concatenating messages: GSM User Data Headers (UDH) and SMPP Segmentation and Reassembly (SAR).

Select one of the following options:

  • None: do not specify a concatenation method.
  • Message Payload: deliver long messages using a separate parameter (message_payload) that supports up to 64K worth of characters. This method does not split and reassemble the message.
  • SAR: split messages using SAR concatenation.
  • UDH: split messages using UDH concatenation.
Important Deployment Considerations

While xMatters supports these protocols, it has no control over how carriers and aggregators handle the requests. You will have to work closely with your carriers to establish the appropriate handling, and then thoroughly test your deployment and message delivery to ensure that you have accounted for the different methods used by your required providers to handle long SMS messages.

Supports New Line

Indicates whether the Protocol Provider supports new line characters (line breaks).

Source Address

Number associated with your SMPP account. This number is used to indicate the sender for outgoing messages. If specified, this value will override the Device Engine setting.

Source Address TON

Your SMPP account’s TON to be used during the server session. If specified, this value will override the Device Engine setting.

Source Address NPI

Client’s NPI required by your service provider for the source address. If specified, this value will override the Device Engine setting.

Default Dest Address TON

TON required by your service provider for the default destination address. If specified, this value will override the Device Engine setting.

Default Dest Address NPI

NPI required by your service provider for the default destination address. If specified, this value will override the Device Engine setting.

Dest Address Subunit

Specifies where to store the message on the target Device (e.g., in a SIM card).

Add New Tag/Value Pair

Allows you to define optional tag/value pairs that can be used to sort messages. For example, “XYZ Marketing”, “XYZ Sales”, “XYZ Data_Center”.

Source Address Overrides By Country

You can set country-specific overrides for the Protocol Provider's Source Address, Source Address TON and Source Address NPI settings. If a country override exists that matches the country specified for a User's text phone Device details, the Protocol Provider will use the source address overrides.

To add a new country override, click Add New Country, and then set the Source Address, Source TON, and Source NPI you want to use. You do not need to enter information into all of the fields; if a field is left blank, xMatters will use the default settings configured for the Protocol Provider.

SMPP Language Encoding

SMPP Protocol Providers can detect the language used in the message, and you can modify the deSmppContext.xml file to specify which language encodings are supported by an SMPP service provider.

To set up the language detection capability:
  1. Stop the xMatters node.
  2. Open the following file:
<xMatters>\node\assets\resources\spring\integration\deSmppContext.xml
 
  1. In the deSmppContext.xml file, locate the smppServiceProviderSupportEncoding bean.
  2. For each encoding not supported by the service provider, change the value to false.
    1. The default value for all encodings is set to true. To indicate that the service provider does not support latin1Encoding, for example, you would modify the latin1Encoding section so it resembles the following:
 <property name="latin1Encoding">
   <value>false</value>
 </property>
 
  1. Save and close the XML file.
  2. Restart the xMatters node.