Configuration in Ozeki NG SMS Gateway
In the next step, you need to install and configure SMPP (Short Message
Peer-to-Peer) connection. There are three ways to start the installation:
-
Click "Add" button in the top right-hand corner of the Service Providers
panel on the left of the Management Console interface, or
-
Click "Add service provider" textlink in the bottom left-hand corner of
the Service Providers panel on the left of the Management Console interface, or
-
Click "Service providers" menu item on the top bar, then select
"Add service provider" item.
After you have completed one of these actions, the Add service provider
panel will appear on the right side of the GUI. This panel contains a list
of protocols you can install and use for communication with an SMS service
provider.
Look for "SMPP Connection", then click on the "Install" textlink to
select the SMPP protocol (Figure 8).
Figure 8 - Adding a new SMPP connection
Now the SMPP Configuration panel appears on the right side of the interface.
The first tab is the SMPP settings, where you can specify the SMPP
server settings.
You need to specify the following parameters: host name,
port number, username and password.
Check out these data in your Ozeki Android SMPP SMS Gateway (on the top
left-hand) and enter the appropriate information (Figure 9).
Figure 9 - Specifying the SMPP server settings
In the fields below, enter the telephone number used to this connection and the
service provider name. Select a clearly distinguishable and well-defined
connection name and give different names for different connections.
Specify the information in the edit boxes. When you enter the
phone number you should use international format, so start with "+". It is a
required information. Do not leave this field empty, otherwise SMS sending
will fail.
You can tick the "overridable" checkbox on the right side of the Telephone
number edit box. This grants that you can replace the phone number specified
in the Telephone number edit box with a different one to be displayed as the
sender of an outgoing message. You can also replace the number with text
(it can contain up to 11 characters). As a result, before you send your
message, you can enter any different phone number or a name as the sender ID
of the message.
In order to configure logging, click the next tab. It is called "Logging".
This tab consists of 2 parts: "Logging" and "Log file settings" sections.
Here, you can select the program to make log about
sent and received messages in human readable format and/or log low level
communication.
If you choose the second option the program will make log files including
binary codes representing the communication data.
Tip: Select at least the "Log sent and received messages in human
readable format" option, because logfiles can help to solve
communication problems (Figure 10).
Figure 10 - Settings on the Logging tab
The second part of the tab is Log file settings, where you can
setup the size and the number of available logfiles.
Log rotation saves disk space, since it grants that older (and probably
no longer needed) logfiles will be deleted automatically from the log
directory. You can enter the Log directory manually, or you can use
the default, which has the following access path:
C:Program FilesOzekiOzekiNG - SMS GatewayLogs.
You can enter the maximum size of a logfile below.
If the logfile reach this size, a new file will be created. The default maximum
logfile size is 8000 kB. You can type an individual value by entering
a positive whole number.
The next edit box is Number of rotated files. It contains the maximum
number of rotated logfiles that are saved. You should enter a positive whole
number. By default, it's vaule is 8 (as you can see Figure 10 above).
If you use the default specifications, do not change this text boxes.
In the Configuration panel the next tab is Connection. Here you can
enter protocol-specific options and specify NPI and TON settings
(in the left section). On the right side you can make
communication link management settings.
You can select a protocol version by ticking either of v3.3
or v3.4.
Below you can enter the System type. It is for assigning
the protocol standard of the other side (SMSC). This information is specified by
the service provider.
The Bind mode describes the way of communication between
Ozeki NG SMS Gateway and the SMSC of a Service Provider. In this section you can
choose Transmitter, Receiver or Transceiver.
If you use this connection only for sending SMS messages, choose Transmitter.
If you use this connection only for receiving messages, choose Receiver.
If you use this connection for sending and receiving messages as well,
choose Transceiver.
Under Bind mode settings you can also find edit boxes for TON and NPI
settings. TON refers to Type Of Number, while NPI is the acronym for Network
Protocol Identification. In this fields, you should enter numbers.
This information is provided by the GSM service provider (Figure 11).
Figure 11 - Connection tab
In the right side of the Communication tab you can
control communication links. The first setting is "Windows size", where
you can increase the window size, if windowing is supported by your SMPP
service provider.
If you tick the Send keepalive packets checkbox in this Communication link
management section, you can make the program send keepalive packets
to maintain connection. Proxy servers will drop a connection after a short
period of time if there is no activity on it. Keepalive packets are sent
during idle periods to keep the connection open.
In this checkbox you can enter the maximum length of idle connection between
the Ozeki NG SMS Gateway and the SMS Center of the Service Provider.
You should specify any positive whole number. If the default specification
(30 seconds) is appropriate for you, do not change this edit box.
Finally, in this tab you can also check the Slow down communication to
checkbox if your service provider cannot accept messages at a high speed.
The next tab in the Configuration settings is Message submission,
which consists of two parts: Delivery reports and
Submit timeout handling. In "Delivery
reports" section you can activate Request delivery reports option.
Delivery reports are messages about the delivery status of the sent messages.
They are returned by the service provider when your message arrives to the
recipient mobile device. In the next edit box (Delivery date format)
you can enter the date format used by your service provider in delivery reports.
The right side of the panel is Submit timeout handling, where you can specify
the preferred way to manage submit timeout. In the Submit timeout
edit box you can enter the maximum waiting time for an SMSC response
confirming that your message has been successfully submitted. A submission is
successful if the SMSC has accepted the message for delivery.
In this field you should use numerical characters representing any positive
whole number. If the default specification (60 seconds) is appropriate for you,
do not change this setting.
In addition, if there is no response from the SMSC after the defined length of
time, you can choose the message status.
Select one of the following radio buttons:
If there is no response from the SMSC, select "Sent" to consider a message
sent even.
If there is no response from the SMSC, select "Not sent" to consider a
message not sent (Figure 12).
Figure 12 - Message submission tab
As you can see in Figure 11, the next tab is Message data.
It also contains two main sections: "Character encoding of text messages" and
"Message data transport". First, you can enter the preferred character set
(Default, ISO_8859_1, UCS2, GSM7bit) and the character encoding policy
(Best match, Transform, Enforce).
Best match: Converts to preferred character set if lossless conversion is
possible. (Character substitutions are not allowed.)
Transform: Converts to preferred character set if possible. (Character
substitutions are allowed.)
Enforce: Always uses the preferred charset. (Character substitutions
and character losses are allowed.)
Then you can setup one of the following options if it is required:
Use GSM 7 bit packed encoding, Encode @ sign as iso 8859-1
character, Convert incoming GSM 7 to iso 8859-1.
In the right side of the panel you can find "Message data transport" section.
You can check segmentation and reassembly (SAR) in order to automatically split
outgoing messages and reassemble incoming messages if needed as long messages
should be sent via the mobile network in several parts.
Since some service providers might ask you to use TLV fields instead of the
standard SM field, in the last section you can select from the following options:
Put UDH into TLV for binary SMS
Put UDH into TLV for text SMS
Put msg data into TLV instead of SM field
Figure 13 - Message data tab
The next tab is Encoding.
Here you can find the following sections: ESM Class field, Number
format encoding, DCS field, Service type.
In ESM Class section you can choose from these options:
Put Delivery Report Req. into ESM class
Put UDHI into ESM class for text SMS
Put UDHI into ESM class for binary SMS
In case your service provider asks you to set ESM class field to 00 for
all messages, leave these fields unchecked.
In the right side of the panel, in Number format encoding section
you can specify TON and NPI numbers. At the bottom of the panel you
can specify DCS that determines the charset, the message class and
binary message encoding, and service type parameter of SUBMIT SM PDU (Figure 12).
Figure 14 - Encoding tab
The last tab on the Configuration panel is Advanced tab (Figure 13). In this section
you can specify the Service type parameter of DELIVER_SM PDU. Its default
value is 0. If it is appropriate for you, do not change this setting.
The other section is SMPP Error Handling, where you can specify that when
the transfer for this connection should stop. It should stop when Throttling
Error or Message Queue Full Error is received. You have to enter any positive
whole number.
Figure 15 - Advanced tab
After configuration click on "OK" button.
If the Advanced tab Connect automatically on startup checkbox was checked
in the bottom left-hand corner of the panel, Ozeki NG SMS Gateway will
automatically initiate a connection with the SMSC.
If this checkbox is not checked, you need to initiate connection
manually.
To initiate the connection manually, click the Connect
link in the left side of the screen (in the panel of the service provider
connection) (Figure 16).
Figure 16 - Links to operations
If you click on the name of a service provider connection in the Management
Console, you can open the panel of the service provider connection.
This panel consists of three sections.
On the top of the panel you can find the name of the service provider
connection (with the name of its protocol in brackets).
You can see an icon, which shows the status of the service provider
connection. If it is not connected, the icon is marked with an "X".
To the right of this icon you can find textlinks to perform
different operations.
Configure: this hyperlink leads back to the configuration panel, which allows you
to configure or modify the configuration
of an installed service provider connection.
Events: click on this link to bring up the Events panel.
You can use this option to view the logging of the latest server events
related to the service provider connection.
Connect: click on it to connect the service provider
connection with the SMS Center.
Disconnect: click on it to disconnect the service provider connection
from the SMS Center.
Uninstall: this option allows you to uninstall the service provider
connection.
In the middle part of the panel you can see some of the most important
configuration information.
The options that have been (re)activated
during the configuration are checked with a tick.
The options, which have not been activated or those that have been
deactivated during the configuration are marked with an "X".
At the bottom of this panel you can find some protocol information.
