Re: AW: own http gateway
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
---
Re: AW: own http gateway
Niels Przybilla wrote: > Hi, > > But sms-service is only for receiving, or also sending sms ? For sending you use the HTTP interface, as it says in the userguide... http://www.kannel.org/download/1.4.0/userguide-1.4.0/userguide.html#AEN4064 Arne -- T: 69 51 15 52 | M: 92 88 44 66 When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute-- and it's longer than any hour. That's relativity. -- Albert Einstein
Re: AW: own http gateway
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
AW: own http gateway
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 >
