Well, theres really not much to choose between HTTP and SMPP. I am aware of high throughput providers through HTTP interface too. So in the end, it all boils down to easy maintenance and of course more importantly, the connection protocol supported by your service provider.

Most of the major aggregators available today support EMI-UCP, SMPP and HTTP. But you may get CIMD2, SMTP (email), FTP interfaces too. So when you are faced with such a scenario where you have to connect to multiple providers/aggregators, Kannel is a preferred choice to use as client. All you need to do is develop an HTTP/web client towards Kannel and use a single Kannel instance to connect to all the different providers. Kannel currently allows you to connect on SMPP/EMI-UCP/CIMD2/SEMA/HTTP (albeit a predefined one but you can easily integrate your own HTTP client) interfaces.


HTH,
Jeetendra


Baden de Bari wrote:

Makes more sense now - something like

1) Web/HTTP --- Kannel (formats request to SMPP) --- SMSC --- SMS End User

2) Web/HTTP Post ---- SMSC ---- SMS End User

Peter Beckman indicated that "I need an SMPP connection to a major aggregator" - this is when you would want to use Kannel - for higher traffic?

What are the benefits of using SMPP over HTTP Post, and when should we consider using an SMPP client, like Kannel?

 


----- Original Message -----
From: Navjot Singh
Date: Fri, 09 Jul 2004 11:51:04 +0530
To: [EMAIL PROTECTED]
Subject: Re: HTTP POST vs. SMPP

> hi,
>
> You dont need kannel if you can/want to talk directly to SMSC. Either
> you write HTTP client(which is so simple) or SMPP client(which is not
> much difficult).
>
> 1.
> HTTP to your SMS server might return some status. succ/fail - use that
> to handle billing.
>
> 2.
> In SMPP, your SMSC will return submit_sm_resp for submit_sm ad later
> deliver_sm (if requested). use that for billing. This can be some
> difficult task.
>
> You want to use kannel if you want to connect your SMSC using SMPP but
> dont know/want to write SMPP client. kannel will act as middle man, will
> handle your simple HTTP request, convery it to SMPP request, send it to
> SMSC and update you with delivery status, whcih will help you in manage
> billing)
>
> hope it clears
> navjot singh
>
> Baden de Bari wrote:
>
> > We want to have per-user credits billing on our web application, which
> > must be seamless. Does it matter if we use HTTP POST or SMPP?
> >
> > To use SMPP, we need to have a server like Kannel, or is there an
> > installable component (MS) we can use for this?
> >
> > We're still trying to figure out how this all works, so your help is
> > appreciated.
> >
> >
> >
> > Thank you.
> >
> > --
> > Wise men talk because they have something to say; fools, because they have to say something.
> > web: http://www.geocities.com/badenx
> > email: [EMAIL PROTECTED]
> >
> >
> > --
> >
> > ___________________________________________________________
> > Sign-up for Ads Free at Mail.com
> > http://www.mail.com/?sr=signup
> >
> >
> > .
>
> --
> regards
> Navjot Singh
>
> When you jump for joy, beware that no-one moves the ground from beneath
> your feet. -- Stanislaw Lem, "Unkempt Thoughts"
>





--

Wise men talk because they have something to say; fools, because they have to say something.

web:  http://www.geocities.com/badenx

email: [EMAIL PROTECTED]


--

___________________________________________________________
Sign-up for Ads Free at Mail.com
http://www.mail.com/?sr=signup

Reply via email to