Scribd
Upload
533 views3 pages

GoIP With SMPP Support

DBL Technology has released a beta firmware update that provides SMPP support for their GoIP devices to allow external applications to send and receive SMS messages through the GoIP. The update can be downloaded from the provided links. SMPP is an open protocol that allows non-mobile entities to interface with SMS centers. It defines operations and data exchange between an external short message entity and SMS center via TCP. GoIPs can act as an SMS center by receiving messages from external sources and forwarding them to local mobile networks or vice versa, providing an alternative to connecting directly to a wireless network's SMS center. The GoIP configuration page allows enabling SMPP and setting the required ID, password, and port for communications.

Uploaded by

Jonathan Edson Lara
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
533 views3 pages

GoIP With SMPP Support

DBL Technology has released a beta firmware update that provides SMPP support for their GoIP devices to allow external applications to send and receive SMS messages through the GoIP. The update can be downloaded from the provided links. SMPP is an open protocol that allows non-mobile entities to interface with SMS centers. It defines operations and data exchange between an external short message entity and SMS center via TCP. GoIPs can act as an SMS center by receiving messages from external sources and forwarding them to local mobile networks or vice versa, providing an alternative to connecting directly to a wireless network's SMS center. The GoIP configuration page allows enabling SMPP and setting the required ID, password, and port for communications.

Uploaded by

Jonathan Edson Lara
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

GoIP with SMPP Support

Date: Monday, December 07, 2012

DBL Technology has just released a beta firmware for SMPP support and can be upgraded from the following links
for the corresponding models.

For GoIP-4 and GoIP-8: dbltek.com/update/GS-4.01-44-SMPP.pkg

For GoIP-16: dbltek.com/update/GST-1.01-9-4.pkg

Please note that these versions for testing purpose. You are welcome your comments and test results to
[email protected].

SMPP
The Short Message Peer to Peer (SMPP) protocol is an open message-transfer protocol that enables short message
entities (SMEs) outside the mobile network to interface with an Short Message Service Center (SMSC). Non-mobile
entities that submit messages to, or receive messages from an SMSC are known as External Short Message Entities
(ESMEs).

The SMPP protocol defines:


• a set of operations for the exchange of short messages between an ESME and an SMSC
• the data that an ESME application must exchange with an SMSC during SMPP operations
The protocol is based on pairs of request/response PDUs (protocol data units, or packets) exchanged over OSI layer
4 (TCP session or X.25 SVC3) connections. PDUs are binary encoded for efficiency. GoIP is only using the TCP
connection.
The most commonly used versions of SMPP are v3.3, the most widely supported standard, and v3.4, which
adds transceiver support (single connections that can send and receive messages). For more information on the
protocol, please download the SMPP 3.3 and SMPP 3.4 from the links below.

SMPP 3.4 Protocol


Specification .pdf
SMPP_v3_4_Issue1_2.pdf(1182.6 k)
http://www.nowsms.com/discus/messages/1/SMPP_v3_4_Issue1_2-24857.pdf

SMPP 3.3 Protocol


Specification.pdf
SMPP-IF-SPEC.v3.3.pdf (88.3 k)
http://www.nowsms.com/discus/messages/1/SMPP-IF-SPEC_v3_3-24858.pdf

The latest SMPP version is v5.0 which is currently not widely adapted. GoIPs currently only support SMPP v.3.3
and v.3.4.
Role of GoIPs in SMPP

An SMS center (SMSC) is responsible for handling the SMS operations of a wireless network.

1. When an SMS message is sent from a mobile phone, it will reach an SMS center first.
2. The SMS center then forwards the SMS message towards the destination.
3. The main duty of an SMSC is to route SMS messages and regulate the process. If the recipient is
unavailable (for example, when the mobile phone is switched off), the SMSC will store the SMS message.
4. It will forward the SMS message when the recipient is available.

When an EMSE sends messages to an SMSC, it must first subscribe a connection from to a GSM Service Provider.
This usually incurs setup cost and charges for sending messages. Instead of sending messages to a GSM network
SMSC, the alternative is to send messages to GoIP. When GoIP is using SMPP to communicate with ESME, its role
is in fact an SMSC. In this case, GoIP is not a full function SMSC. Its main roles are

1. to receive messages from ESME and then send them the GSM network SMSC.
2. to receive messages from the GSM network SMSC and the send them to ESME.

The diagram below shows the SMSC role of GoIPs when using SMPP to communicate with ESME.

ESME SMSC

GoIP

Local
GSM Networks
Internet GoIP-4

GoIP-8

GoIP-16
GoIP Configuration
After the device has been upgraded successfully and rebooted, you can now access the Preference page to enable
the SMPP support as shown below.

The three parameters used for SMPP communications with the SMSC (Short Message Service Center) are ID,
Password, and Port.

a) ID is the name assigned to the SMSC (GoIP) and is used as an authentication ID with ESME. In this case,
all GSM channels/lines in the SMSC are considered as one group. When ESME sends messages to this
ID, messages are distributed to each GSM channel for sending based on the Round-Robin scheme

If it is necessary to send messages to a specific SMSC channel (a GSM channel in GoIP) directly, the 2-
digit channel number (01 to xx, where xx is the maximum number of channel in the device). ESME
should then send message to ID + "xx". For example, if ID is GoIP1 and the designated channel for the
message is 02, the ESME must send message to ID = GOIP102.

b) Password is the authentication password for receiving SMS via SMPP. If the password is incorrect, the
message is discarded.

c) Port is the communication port used for SMPP communications with the SMSC. The default port number
is 7777. If the SMS originator is using a different, this port must be changed accordingly.

Remarks:
1. ESME is a SMPP client. A SMSC must be added as a Service Provider connection in an ESME. The ID,
Password, and Port must match those assigned in the designated GoIP.

2. ESME must be configured to Transceiver mode for sending and receiving messages.

3. UCS2 and ASCII encoding methods are supported. When UCS2 format is used, a maximum of 70 charachers
per message can be sent. When ASCII format is used, it will then be converted to GSM 7-bit format;
therefore, a maximum of 160 characters per message can be sent.

4. TLV parameters are not supported.

You might also like