Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.

ID: 22837, SMPP protocol Socket Component for SMSC Connectivity

by Stefan Wloch Email: Anonymous

SMPP Protocol Socket component will allow permanent SMPP connectivity to an SMSC Server (specified as IP Address and Port Number properties)
Download Details
FTP  download also available
CDN Login Required to Download. (You will be redirected to the login page if you click on the Download Link)
To download this, you must have registered:
A free membership

For Delphi, Version 4.0  to 7.0 492 downloads
Copyright: No significant restrictions

Size: 240,891 bytes
Updated on Tue, 30 Nov 2004 07:49:10 GMT
Originally uploaded on Tue, 30 Nov 2004 07:45:18 GMT
SHA1 Hash: 37D4D0DB33978DAE144490928EAF5D37D83A35D5
MD5 Hash: 7AAC2E663EE200F23A6DEF0D4BB8A7F0

    Explore the files in this upload

SMPP Socket Component (TSMPPSocket)

The Short Message Service (SMS) is a facility on the GSM network which enables messages of limited size to be sent to or from a mobile phone. SMS can typically be used in many different ways, e.g. from simple text paging through to sophisticated telemetry, vehicle location tracking and control applications. The ability to be able to connect directly into an SMSC for sending messages to mobiles from land-based messaging applications, and receiving messages back from those mobiles, opens up many more opportunities.

An SMSC provides a number of services, in particular the regulation of the transfer of text messages between mobile phones. When a user sends a text message (SMS message) to a recipient, the phone actually sends the message to the SMSC. The SMSC stores the message and then delivers it to the destination recipient when they are available. The SMSC usually has a configurable time limit for how long it will store the message, and the user can usually specify a shorter time limit if they want. Additionally the message centre will take care of any charging that needs to take place. Generally speaking there is at least one Short Message Service Centre (SMSC) per network. For bulk transmission and reception of SMS messages, SMSC's have conventional, fixed, network interfaces as well as mobile network interfaces. A number of protocols have been defined to support this sort of wire-line access. SMPP is the most commonly used of these protocols.

SMPP stands for Short Message Peer to Peer. It is a communication protocol designed for transfer of short messages between short message centre (SMSC) and SMS application (ESME), external land-based system; typically some sort of computer or ‘host’ running a SMS application. Most telecommunication providers such as BTCellnet offer SMSC services.

The Short Message Peer to Peer (SMPP) protocol is an open industry standard messaging protocol designed to simplify integration of data applications with wireless mobile networks such as GSM, TDMA, CDMA and PDC. The protocol is widely deployed in the mobile telecommunications industry.

The SMPP Socket component will allow permanent SMPP connectivity to an SMSC (specified as IP Address and Port Number properties), thus saving clients time in having to perform ad hoc posts via the internet. Secondly, the SMPP gateway will allow for you to send greater message volumes more efficiently than any of the other protocols on offer. The SMPP connection is typically suitable for customers with large message volumes, and mature SMS applications. These include the likes of network aggregators, large corporates, and IT integrators.

You can download the latest SMPP Protocol Specification from:-

For test purposes, an SMSC Simulator can be downloaded from:-

The Simulator is an application for near-to-live testing of your SMPP applications without need of access to real SMSC. The application behaves as a real SMSC with SMPP interface, your application can bind to it, send messages, unbind etc., however nothing will get delivered anywhere as all the responses are only made-up by the Simulator.

   Latest Comments  View All Add New

Move mouse over comment to see the full text

Could not retrieve comments. Please try again later.

Server Response from: ETNACDC03