Pieslēgšanās BITE SMS centram izmantojot SMPP protokolu

:!: Tehniskā informācija pieejama angļu valodā

BITE SMPP service draft Version: 0.2 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 213.226.130.226
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.

Routing

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.

Charging

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.

Support

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

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.
 
lv/smpp_tech.txt · Labota: 2008/01/22 10:34 , veicis martins