Change SMPP Connection page field descriptions

Last Updated : Oct 29, 2021 |
Prolog information
Use this page to change the configuration of an SMPP connection.
General Settings group
Field or Button
Description
Zone
Select the name of the zone from the drop-down box.
Note:
The Zone drop-down box appears only when you create new zones. If you do not create any new zones, you do not see the drop-down box.
Changing Zone from the default zone to any other zone is not allowed. However, you may change the zone for connections for which the existing zone is not the default zone.
Name
The name of the SMPP connection.
Enable
The options are:
  • Yes
  • No
Transport Protocol
Select the transport protocol that is used to send a request to SMSC.
The options are:
  • TCP
  • TLS
Host Address
Enter the host address of the service provider or the Short Message Service Center (SMSC).
Shared
Select the relevant Shared option to enable or disable the SMS Processor field.
The options are:
  • Yes
  • No
If you select Yes, the SMS Processor drop-down box is disabled and all the available SMS processors are shared for that particular zone. If you select No, the SMS Processor drop-down box is enabled and you must select one of the available processors from the drop-down box.
The default is No.
SMS Processor
Select the SMS processor from the drop-down box.
Note:
The system displays the drop-down box if you select the shared option No.
Port
Enter the port number of the service provider or the SMSC.
Bind Mode
Select the Bind Mode from the drop-down list box. The options are:
  • Transceiver: The user can send SMS and get the delivery receipt.
  • Transmitter: The user can only send SMS. The user does not get any delivery receipts.
  • Receiver: The user can only receive an SMS.
User Name
Enter the user name.
Password
Enter the password.
Address Range
Enter the address range.
Set From field to
The options are:
  • Short Code
  • Blank
Short Code/Long Number
Organization
In this box, enter either the short code or the long number provided by the SMSC.
Select the relevant organization from the multi-select drop-down list. The options are:
  • <All> : The short code can be used by all the organizations and none organizations. If the administrator selects multiple options in the drop-down list, only <All> is saved.
  • <None>: None of the organizations can use this short code. The administrator can select organizations in addition to <None>.
  • The other organizations that are enabled in the system.
Additional Entry
Use the Additional Entry link to specify additional short codes or long numbers.
Advanced Parameters group
These parameters are optional.
Field or Button
Description
Service Type
Helps to identify the type of sender to bind as transmitter with the SMSC. The system_type parameter is used to categorize the type of External Short Message Entities. For example, Voice Mail System (VMS) and Overthe-air Activation System (OTA).
By default the value is NULL.
Refer to the SMPP 3.4 specifications for additional details.
Address Type of Number
Use to define the type of number to be used in the Short Message Entities (SMEs) address parameters. The defined values are:
  • 00000000: Unknown
  • 00000001: International
  • 00000010: National
  • 00000011: Network Specific
  • 00000100: Subscriber Number
  • 00000101: Alphanumeric
  • 00000110: Abbreviated
Refer to the SMPP 3.4 specifications for additional details.
Address Numeric Plan Indicator (NPI)
Use to define the Numeric Plan Indicator (NPI) to be used in the SME address parameters. The defined values are:
    • 00000000: Unknown
    • 00000001: ISDN (E163/E164)
    • 00000011: Data (X.121)
    • 00000100: Telex (F.69)
    • 00000110: Land Mobile (E.212)
    • 00001000: National
    • 00001001: Private
    • 00001010: ERMES
    • 00001110: Internet (IP)
    • 00010010: WAP Client Id (to be defined by WAP Forum)
Data Coding Scheme
Indicates the data coding scheme of the short message. This value depends on the language and the settings required by the service provider. To send normal English messages the default value is 0. To send SMS in other languages like Italian, Russian, Chinese modify this value to 8 ( equivalent of "0 0 0 0 1 0 0 0 UCS2 (ISO/IEC-10646) as per the SMPP specifications for a particular service provider. Modify this value based on your testing results with the service provider. Modifying the value from 0 to something different reduces the number of characters being sent per SMS as more number of bits are required to represent each character in different languages.
Refer to the SMPP 3.4 specifications for additional details.
SMS Character Encoding
Indicates one of the following values (ASCII, Cp1252, ISO8859_1,UnicodeBig, UnicodeBigUnmarked, UnicodeLittle, UnicodeLittleUnmarked, UTF8, UTF-16). This value is used in conjunction with SMS Data Encoding value.
Source Type of Number
Use to define the type of number to be used in the SME address parameter. The defined values are :
  • 00000000: Unknown
  • 00000001: International
  • 00000010: National
  • 00000011: Network Specific
  • 00000100: Subscriber Number
  • 00000101: Alphanumeric
  • 00000110: Abbreviated
Refer to the SMPP 3.4 specifications for additional details.
Source Numeric Plan Indicator
Use to define the Numeric Plan Indicator (NPI) to be used in the SME address parameters. The defined values are:
  • 00000000: Unknown
  • 00000001: ISDN (E163/E164)
  • 00000011: Data (X.121)
  • 00000100: Telex (F.69)
  • 00000110: Land Mobile (E.212)
  • 00001000: National
  • 00001001: Private
  • 00001010: ERMES
  • 00001110: Internet (IP)
  • 00010010: WAP Client Id (to be defined by WAP Forum)
Refer to the SMPP 3.4 specifications for additional details.
Destination Type of Number
Use to define the type of number to be used in the SME address parameter. The defined values are:
  • 00000000: Unknown
  • 00000001: International
  • 00000010: National
  • 00000011: Network Specific
  • 00000100: Subscriber Number
  • 00000101: Alphanumeric
  • 00000110: Abbreviated
Destination Numeric Plan Indicator
Use to define the Numeric Plan Indicator (NPI) to be used in the SME address parameters. The defined values are:
  • 00000000: Unknown
  • 00000001: ISDN (E163/E164)
  • 00000011: Data (X.121)
  • 00000100: Telex (F.69)
  • 00000110: Land Mobile (E.212)
  • 00001000: National
  • 00001001: Private
  • 00001010: ERMES
  • 00001110: Internet (IP)
  • 00010010: WAP Client Id (to be defined by WAP Forum)
Refer to the SMPP 3.4 specifications for additional details.
Priority Flag
Allows the originating SME to assign a priority level to the short message.
Four priority levels are supported:
  • 0: Level 0 (lowest) priority
  • 1: Level 1 priority
  • 2: Level 2 priority
  • 3: Level 3 (highest) priority
Refer to the SMPP 3.4 specifications for additional details.
Registered Delivery
Use to request an SMSC delivery receipt and/or SME originated acknowledgements. The options are:
  • None
  • Always
  • Failures Only
Refer to the SMPP 3.4 specifications for additional details.
Validity Period
Can be defined in minutes; ranging from 0 to 4320. This is a relative value for SMSC.
Refer to the SMPP 3.4 specifications for additional details.
Long SMS Sending Process
You can send a long SMS using one of the following options:
  • MESSAGE_SEGMENTATION: Breaks the SMS into multiple parts (segmentation).
  • MESSAGE_PAYLOAD: Sends all the data in one SMS.
Note:
When you use MESSAGE_SEGMENTATION, the system by default breaks lengthy outbound SMS messages into segments no larger than:
  • 160 characters: If the SMS Character Encoding is set to a 7 or 8 bit character encoding.
  • 70 characters: If the SMS Character Encoding is set to one of the 16 bit encodings.
This default setting can be changed by adding the following properties in $MMSSERVER_HOME/lib/config/smsserver.properties and then running the service mmsserver restart command:
  • smpp.max.segment.size=160
  • smpp.max.segment.size.16bit=70
When outbound SMS messages are sent, they are broken into segments of the specified size. The maximum segment size should be obtained from the SMSC.