Andreas Fink wrote:
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.
yep, but users may still *want* to act Kannel as SMS transport layer, mainly for
abstraction purposes and hence the ability to switch routes to other SMSCs.
So, the gw/smsc/smsc_http.c module has a design to *add* own HTTP API protocol.
Either you can add them and run in your own setup, or provide a patch for us to
include.
I have a patchset here called 'smsc-http-generic' that does a "generic HTTP API"
GET call, by utilizing the escape codes known from get-url of sms-service. So
the GET parameters are not hard-coded in the module, but can be added in the
config. Result interpretation via regex.
This is scheduled to enter CVS post-1.4.1 release.
Stipe
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------
