Supplier Connection fields

General Explanation
   
Name  Name of the connection that you will see on the platform
Symbolic Name Symbolic connection name used in the back of the system, usually by NOC to track the connection status
Status: Defines activity status of the connection. Active, Inactive, Blocked, Stopped, Maintenance, Test
Number of Instances Number of binds possible to connect in parallel, offered from the supplier for this connection 
Connection Type [SMPP] Defines protocol type for the connection, SMPP only.  
   
SMPP  
   
Remote host  IP address or symbolic host server of the supplier.
Remote port  Port number of the supplier. 
Remote RX port  Defines connection port if Receiver(TX)/Transmitter (RX) is needed this is the port for Transmitter (RX) to connect to. 
Local host  Needed host information for VPN setting. (requires the previous mapping by our Engineer team)
Local port  Needed port information for VPN setting. (requires the previous mapping by our Engineer team)
Session type: Defines if session type is: TRX = Transceiver (one bind works with both receiving and sending), TX=Transmitter (used for sending messages), RX=Receiver (used for receiving DLR report, also can use one individual RX port), TX/RX=one TX and one RX.
Protocol version: Protocol version (3.4 used currently)
System type  Is an optional login parameter that should be set only if required by the SMPP server. This field, together with "Bind Address TON", "Bind Address NPI" and "Address range" exist besides "System ID" and "Password" in bind_transmitter, bind_receiver and bind_transceiver PDU. Sometimes connection data from the supplier specifies some exact values for these fields, but in most of the cases not. If specified by the supplier, they must be entered. Otherwise, leave the default (blank).
Please check SMPP 3.4 Issue 1.2 specification, section 4.1
System ID  Username for connecting to the supplier connection.
Password  Password for connecting to the supplier connection.
Bind Address TON  Your link supplier might tell you to specify particular Bind TON, Bind NPI, Source TON, Source NPI, Destination TON or Destination NPI values. (TON = Type Of Number, NPI = Numbering Plan Indicator). Default values: If the sender address is alphanumeric (contains both letters and numbers) or non-numeric, TON is set to 5 and NPI to 0. If the sender address is a short code, TON is set to 3, and NPI is set to 0. (By default, a number is considered to be a short code if the length of the number is 5 digits or less). If the sender starts with a “+”, TON is set to 1, and NPI is set to 1.
If none of the above conditions is met, TON is set to 0 and NPI is set to 1 (unless the sender is blank, in which case both are set to 0). If the recipient starts with a “+”, TON is set to 1, and NPI is set to 1. Otherwise, TON is set to 0 and NPI is set to 1.

TON is "Type of number" and has the following values:
0: Unknown
1: International
2: National
3: Network Specific
4: Subscriber Number
5: Alphanumeric
6: Abbreviated

NPI is "Numbering plan indicator and has following values:
Unknown = 0
ISDN/telephone numbering plan (E163/E164) = 1
Data numbering plan (X.121) = 3
Telex numbering plan (F.69) = 4
Land Mobile (E.212) =6
National numbering plan = 8
Private numbering plan = 9
ERMES numbering plan (ETSI DE/PS 3 01-3) = 10
Internet (IP) = 13
WAP Client Id (to be defined by WAP Forum) = 18

Currently, Source and Destination TON and NPI are defined in the engine and you may ignore these fields. Next major version of the platform will clarify meaning of these fields.

For Bind TON/NPI please additionally read the comment for "System Type"
Bind Address NPI 
Source Address TON 
Source Address NPI 
Destination Address TON 
Destination Address NPI 
Address range  Is a parameter used primarily when receiving messages. It is sent to the SMSC after login, and is useful if several telephone numbers are used on a single SMPP link. See explanation for "System Type".
Charset: The charset used for encoding of the message text, GSM 03.38 or Latin1. 
ID Matching: In SMPP connections, the message ID in submit_sm_resp and in deliver_sm are not always sent in the same format. These are options: exact - the same, dec/dec - decimal in both, hex/dec - hexadecimal in submit_sm_resp and decimal in deliver_sm...
ID Location: SMPP allows that message ID in DLR is sent in DLR text or in TLV.

For text, please check:
SMPP 3.4 Issue 1.2 specification, Appendix B

For TLV please check:
SMPP 3.4 Issue 1.2 specification, 5.3.2.12
Err Location: Defines whether the DLR error code is in DLR text or TLV.

For text, please check:
SMPP 3.4 Issue 1.2 specification, Appendix B

For TLV please check:
SMPP 3.4 Issue 1.2 specification, 5.3.2.31
Err Format  Enter values here if different from standard SMPP error codes and the default err:NNN template. If unsure best leave empty. Default is err:([0-9]+)

Please check:
SMPP 3.4 Issue 1.2 specification, Appendix B
Error Mapping  Matching error code list with supplier's error code list.
Throughput SMS  How much SMS could be sent per second through one bind.
Throughput PDU  How much SMS could be sent per second through whole connection. 
Window Size  Number of outstanding transactions before requiring a response to at least one of the outstanding transactions.

For text, please check:
SMPP 3.4 Issue 1.2 specification, Sections 2.5-2.9
DLR Generate Ratio  If "Generate DLR" is checked, here you define the percentage of DELIVERED DLR reports from 1% to 100%
Validity Period  Period of time defined by supplier, for which SMS will wait to be sent due to inactivity of mobile number. 
Enquire Link Interval  Time of (default 30sec) when the system is sending a request to the connection for information if the connection is still online or offline. 
Reconnect Delay  Time of (default 60sec) when the system is trying to reconnect connection back online. 
Timeout  Period of (default 60sec) when the system is giving the time to the connection to connect back online
Data Coding In short it means - when converting to data coding set in “Charset” - which data_coding value to set in SMPP submit_sm PDU to TELL supplier that that is chosen data coding.
So normally it works - if GSM, DCS=0. If the supplier is using Latin1, DCS is also 0 (value 0 means default for Supplier).
Sometimes can happen a special case where the supplier's default encoding is GSM but the platform owner wants to use Latin1. So in this case we can set Charset to Latin1, and Data coding to 3.
Please check SMPP 3.4 Issue 1.2 specification, Section 5.2.19
DLR is Sent by supplier If this option is checked, then you are asking/expecting from your supplier to give you DLR report
Generate DLR = Delivered Check "DLR Generate Ratio" explanation
SSL SSL/TLS connections requires previous mapping by our Engineer team

Other Articles