TelecomSpace Telecom Tutorials, Forum, Latest Trends, News

SMSC will have SMPP server which talks to ESME (smpp client ) using SMPP protocol over TCP/IP.
During the service agreement between ESME and service provider(SMSC side) one unique short code will be allocated to ESME. At the SMSC end smpp server will have list of all ESME address and active connection. When you send any message to short code, messages first comes to SMSC, SMSC decodes it according to GSM 3.4 spec, then one of module in SMSC checks the destination address if it is short code then that module routes messages to SMPP server part of the SMSC. Now SMPP server will have all active connection , according to destination address it selects the ESME - SMPP server connection object , that object will be responsible to encode message according to SMPP protocol and forward to ESME.
Let me know if you need more clarification.
Thanks,

luckystrings wrote:
1) The part where you said that a module in SMSC will route the SMS to SMPP Server Part. Is there any HTTP interface used here to
fwd the SMS ? 
The interface between SMSC and SMPP is proprietary, each vendor can have his own communication, there is no standard, as both reside in the same system(product).
Basically it is just Interprocess comm(IPC), one could use DB or files or queues or socket communication between those two processes.

Quote:
2) and also active connections from SMPP server to ESME -  I have an SMPP account provided with some port number. How does the SMPP server push the SMS to ESME.. is it thru HTTP ?  ... pls forgive if this may sound a lill stupid..

Communication between SMSC and ESME can be on either SMPP ot HTTP.
If you have SMPP account, you could connect to the SMPP IP+Port on TCPIP and the SMPP will push MOs to ESME on SMPP connection. and ESME will push MTs on the same connection in reverse.
If you have HTTP account with the operators SMSC, then the SMSC will post the MO onto an URL given by you and to push MTs SMSC will give you on URL.

Hope it helps you!

luckystrings wrote:
I have an SMPP account with the operator thru which my server is receiving and sending SMS. I have requested operator personel to route all MO SMS sent to a new shortcode (say 55555) to my server thru SMPP. Now the issue is that the operator guy is asking me for an HTTP interface URL to configure the SMS routing of tht new shortcode to my server.

Short codes can be configured to deliver the MOs on either SMPP or HTTP. What  I understand is, you have a short code from the operator. The operator can either route on SMPP or HTTP, but for some reason he wants to deliver you the MOs on http.
So, now what you could do is, configure an URL on a public IP and give it to him. Then operator will post the MO on the URL.

URL should look like: http://YourPublicIP/sendmo.asp?from=xxxxxxxx&dest=55555&message=xxxxxxxxxx
or http://YourPublicIP/sendmo.php?from=xxxxxxxx&dest=55555&message=xxxxxxxxxx

It is fairly simple to setup.
You could also download and  use Kannel SMS Gateway (http://www.kannel.org) to send and receive messages.

luckystrings wrote:
Now I need to figure out how to handle SMS coming on HTTP interface (my server's Public IP:). I just have a smpp binary from logica running on my server.

SMPP and HTTP are both completely different things. You can not use both together in for the same transaction. ( However you could use http to receive MO and use SMPP to send MT or vice versa)
Here, you need to use PHP or ASP to receive the HTTP post and parse the parameters, you will get sender, destination, message etc, and the
rest is your application logic.

luckystrings wrote:
Currently I dont have any Application running on my server to accept HTTP requests (no application developed yet to support this) and forward it to other modules in my server.
A simple PHP(Apache)/ASP(IIS) page would be enough. It can accept the MO and may be dump in DB from where the other modules can pick up and do the rest of processing. This development wouldn't take more than couple of hours for who know little bit of php.
Btw, whats your OS?

luckystrings wrote:
we use RHEL 3
Then use Apache+PHP and a simple PHP page to get MO and store it somewhere, your job is done.

Check these links: http://docs.upsidewireless.com/index.php?title=MO_HTTP

@luckystrings

If you really need to understand the engineering of SMSC hardware and software you have to understand the underlying modules that are used within smsc. Their interconnection is via TCP/IP, you can read the details here
http://blog.ektel.com.np/2011/12/short-message-service-center-smsc/