Kannel IS your sending gateway. it translates HTTP to SMSC protocols.
If you use an aggregator doing HTTP, then you can talk directly HTTP
to him. No need of Kannel in this case as your application already
speaks HTTP.
Kannel has a HTTP driver to talk to other Kannel or similar HTTP
servers but if your aggregator speaks another variant of HTTP, then
the aggregator should implement a kannel driver.
On 04.09.2006, at 07:52, Niels Przybilla wrote:
Hi,
But sms-service is only for receiving, or also sending sms ?
Best regards
Niels
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 4. September 2006 06:36
An: Stipe Tolj
Cc: Niels Przybilla; devel@kannel.org
Betreff: Re: own http gateway
Stipe Tolj wrote:
Niels Przybilla wrote:
Hi,
in http i can define wether it is for "brunet" or "wapme". I think
this is related to the http request you need for the different sms
providers.
my concrete question is, where i can define the string for
the http
requests and the parameters for my sms provider
Kannel deals with proprietary HTTP APIs of SMS aggregators
as follows:
you need to implement an own "type" (like burnet, wapme) in the
gw/smsc/smsc_http.c module to make the HTTP SMSC type act
against your
SMS provuider's API.
I have a beast here called "generic HTTP SMSC patch", that
is able to
use teh URLTrans escape codes for the get-url varlues and
regex'es the
HTTP response to determine if submission was considered
successfully,
temp. failture or final failure.
The patch works and is in production state at a customer's site.
Adding the patch for post-1.4.1 release.
I think perhaps Niels means SMS services.
Niels, see get-url and post-url in the Userguide
http://www.kannel.org/download/1.4.0/userguide-1.4.0/userguide
.html#AEN3087
Arne
