Connecting to BITE SMS center via SMPP protocol

BITE SMPP service draft Version: 0.3 Author: TDBA

Information for Value Added Service Providers This document describes basic usage information of BITĖ SMPP service for Value Added Service Providers (VASP). BITĖ SMPP service is used to proxy short messages between SMS center and VASP and visa-versa.

Server information

IP address
Port 2325
Protocol SMPP v3.4

Connection information including SMPP system ID and password is provided per contract basis. Please note that access to BITĖ SMPP service is restricted to single or range of IP addresses provided by VASP.


VASP will receive those MO messages destined to the short (e.g. 1599) or long (e.g. 37069900000) number assigned to the VASP, if any. Additionally, assigned numbers might be limited by one or several keywords in the short message.


For each successful MT message sending attempt by VASP there is a corresponding transaction logged. Price per single MT message depends on the destination number provided. Usually there are different tariffs applied for messages destined to the BITE network, networks within the VASP country of origin (Lithuania or Latvia) or to the foreign networks.

Protocol information

SMS multipexor implements a set of Protocol Data Units (PDUs) as per SMPP v.3.4 Issue 1.2.

Default character set

In case submit_sm or deliver_sm PDU contains coding field value set to 0 (default alphabet), BITE SMPP service will treat short_message data as string coded in GSM alphabet.

Delivery reports

BITE SMPP service provides delivery reports if requested by VASP with registered delivery flag in submit_sm PDU. Information in deliver_sm PDU relating to delivery report is stored in the following TLV fields: receipted_message_id (0x001E) and message_state (0×0427). receipted_message_id holds message id previously returned by submit_sm_resp and message_state contains message delivery status as indicated in section 5.2.28 of SMPP v.3.4. Additionally, for delivery report BITE SMPP service will set short_message mandatory field with the value similar to the following: id:12345678 stat:DELIVRD. This should help non SMPP v.3.4 compliant clients to extract delivery report information.

Number of outstanding SMPP operations

BITE SMPP service has a limit of 10 outstanding (unacknowledged) operations for each VASP. It means that if VASP hasn’t sent an answer to 10 subsequent PDUs, BITE SMPP service won’t delivery any messages until it receives answer from VASP to some of previously sent messages. We recommend that similar strategy for number of outstanding operations should be followed at VASP level as well.

Source address

By default, source address of submit_sm PDU is limited to any of the number assigned to VASP as described in the Routing section. Additionally, VASP might request for allowance of any (e.g. alphanumeric) sender address which must follow SMPP specification.

Tariff information encapsulation

Currently charging is only based on rules described in the Charging section of this document. Therefore any information provided in submit_sm PDU about the tariff class is not taken into account.

Receiving messages from other mobile networks

Generally, only those MO SMS messages sent by BITE customers are delivered as SMPP deliver_sm PDUs to a particular SMPP connection. The reason for this is the fact that SMSC of other mobile network does message delivery directly to BITE customer and in this scenario BITE SMSC does not participate in message delivery at all.

It is now possible to receive SMS messages sent from other mobile networks (including Lithuanian and foreign ones) over SMPP connection. As a requirement, receiving number must be in MSISDN format (e.g. 37069900000), belong to BITE and having a valid IMSI. Prior to be able to receive messages from other networks, special configuration is needed (please contact your manager from BITE).

In order to be able to differentiate at SMPP level what is the network (BITE or not) of the message sender (source_addr), Numeric Plan Indicator of the source address (source_addr_npi) has to be analyzed. In case MO SMS message was sent by BITE customer, source_addr_npi value is always set to 1 (ISDN (E163/E164)). Otherwise, when message originated from other Lithuanian or foreign network, source_addr_npi value is set to 0 (Unknown).

Type of Number of the source address (source_addr_ton) is left unchanged (as set by other mobile network). Usually it will have a value of 1 (International), but please be aware that other values (e.g. 5 - Alphanumeric) might be possible as well, since message might have been originated not from a mobile phone but a system connected to other network's SMSC (e.g. via SMPP).


In case of failure detected in BITE SMPP service or any other technical questions or issues should be redirect to Services Support by emailing

Known issues

  • Currently non implemented PDUs are as follows: submit_sm_multi and data_sm.
  • Special considerations should be taken when data contains @ (commercial “at”) character, coded as 0×00 in GSM alphabet. Currently this character might not be transmitted over submit_sm.

Frequently Asked Questions

  • Does the price of SMS sending through SMPP is the same as sending it through SOAP?

Usually yes, but this is contract dependant. Please keep in mind that in most cases there are three different prices according to the destination – BITE network, foreign networks within same country (LT or LV) and destinations abroad.

  • Will we get any delivery report sending SMS through SMPP?

Yes, if you set a registered delivery flag in submit_sm PDU as described above. Please be aware that delivery report receipt is subject to charging conditions.

  • How we will know that account really received SMS?

You might use delivery reports to check about short message delivery status.

  • Do we need for SMS sending through SMPP use account MSISDN or AccountID?

Currently destination always has to be set to the recipient’s MSISDN (as per E.164). Please always use international number format (e.g. 37069900000) and set TON to “International” (1).

  • What happens when SMS is sent for account, who doesn‘t have money in his bill account?

Message recipient is never charged when short message is sent over SMPP. As long as recipient is active in BITE network, message will be delivered.

  • Can I send SMS through SMPP in Russian?

Yes, you need to set data_coding to 8 in SMPP submit_sm PDU and encode message data in UCS2 (UTF-16BE) character set. Please be aware that maximum Unicode message length is 70 bytes (2 bytes per single character).

smpp_tech.txt · Last modified: 2009/05/26 11:06 by dziugas