GSM Protocol Providers

The following table describes the settings for GSM Protocol Providers.

GSM 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.
  • UDH: split messages using UDH concatenation. Note that this only works with PDU mode; see "GSM UDH Split Size".
Important Deployment Considerations

While xMatters supports these protocols, it has no control over how carriers and aggregators handle the requests. Generally, UDH concatenation does not work for Devices that reside in CDMA network. 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.

Prepend + to Dest

Indicates whether to add a plus symbol (+) to the beginning of each phone number sent to the GSM engine.

This feature is available only on deployments where all text phone Devices were created after 4.1 patch 006 or later. If you have text phone Devices that were added prior to applying the required patch, you must either delete the Devices (which will automatically enable this feature) or work with xMatters Support to reconfigure your existing Devices.

GSM UDH Split Size

The UDH split mechanism for GSM requires that the actual message size be smaller than the pre-configured size (i.e., the size specified in the Split Size field). The purpose of this size difference is to leave room for adding the UDH header. For example, if you configure the Split Size setting to 160, the actual split size will be smaller than 160.

The precise size difference is determined by the type of characters within the message. There are two different character types: 7 bits for ASCII and GSM, and 16 bits for the rest of the world. The size specified in the Split Size field is for 7-bit characters.

For example, if the Split Size field is set to 160: