Re: Claro http communication
Thanks for your input! I hope we can submit a patch soon. - Hervé Le lundi 25 mai 2009 à 23:20 +0200, Alejandro Guerrieri a écrit : > Well, this implementations are nowadays confined to gw/smsc_http.c, so > it's quite simple to add a new one without bloating the rest of the > code. > > Until someone comes with some a-la-apxs pluggable architecture (any > volunteers? ;) ), that's the way to do it. Not as clean as it could > be, but fair enough imho. > > Regards, > -- > Alejandro Guerrieri > aguerri...@kannel.org > > > > On 25/05/2009, at 23:09, Milan P. Stanic wrote: > > > On Mon, 2009-05-25 at 17:28, Juan Nin wrote: > >> There are already several HTTP SMSC specific implementations on > >> Kannel, the ones that Hervé mentioned are some of them. > > > > Kannel supports SMPP, EMI, UCP, AT, several HTTP and the others > > protocols. I hope that the kannel will not become to bloated if we > > tried to push every variant of HTTP specific implementation into it. > > > >> Of course you can do it directly without Kannel, but it's a good > >> approach to do it via Kannel, so that you always use it as your > >> gateway and not one method for some carriers and another one for > >> others, It's also nice to do it via Kannel cause it already > >> implements > >> stuff like it's internal queue, etc > > > > -- > > Kind regards, Milan > > > >
Re: Claro http communication
To receive MO's, Kannel listens on an HTTP port for requests, like a regular web server. Each http-smsc implements a slightly different interface (some accept http params, other xml documents, etc), but the underlying principle remains the same and is implemented on the smsc here>_receive_sms function in smsc_http.c. Regards, -- Alejandro Guerrieri aguerri...@kannel.org On 25/05/2009, at 23:14, Nikos Balkanas wrote: Hi, Besides, only MTs are pushed through kannel's HTTP interface. MO's are not. Hervi clearly talks about MOs. kannel also offers all these nifty sms-services, which would have to be built from scratch. An interesting question is how do you receive SMS over HTTP. Do you poll the SMSc HTTP every 5" to see if there are any new SMS or DLRs? BR, Nikos - Original Message - From: "Juan Nin" To: Sent: Monday, May 25, 2009 11:28 PM Subject: Re: Claro http communication Milan, There are already several HTTP SMSC specific implementations on Kannel, the ones that Hervι mentioned are some of them. Of course you can do it directly without Kannel, but it's a good approach to do it via Kannel, so that you always use it as your gateway and not one method for some carriers and another one for others, It's also nice to do it via Kannel cause it already implements stuff like it's internal queue, etc Regards, -- Juan Nin 3Cinteractive / Mobilizing Great Brands http://www.3cinteractive.com On Mon, May 25, 2009 at 5:22 PM, Milan P. Stanic wrote: On Mon, 2009-05-25 at 18:14, Hervι Nicol wrote: We have to send / receive SMS and DLRs over Claro (brazilian telco). We will communicate with them by HTTP. ^ If we write a patch for kannel for operator-specific HTML communication (just like for Clickatell, Brunet, 3united.com...), is there any chance that it may be included in Kannel CVS? You have to communicate with kannel over HTTP. Kannel have to communicate with provider over HTTP. Why you could not communicate with provider over HTTP without kannel. What should be role of the kannel in your case? I don't like to say that you do not have good reason for that. I'm just curious. Do you have some special hints / advices on how to proceed? It won't be too hard for us to write this code considering the existing operator-specific code, but it costs nothing to ask for some advice before starting to work on it ;) -- Kind regards, Milan
Re: Claro http communication
Well, this implementations are nowadays confined to gw/smsc_http.c, so it's quite simple to add a new one without bloating the rest of the code. Until someone comes with some a-la-apxs pluggable architecture (any volunteers? ;) ), that's the way to do it. Not as clean as it could be, but fair enough imho. Regards, -- Alejandro Guerrieri aguerri...@kannel.org On 25/05/2009, at 23:09, Milan P. Stanic wrote: On Mon, 2009-05-25 at 17:28, Juan Nin wrote: There are already several HTTP SMSC specific implementations on Kannel, the ones that Hervé mentioned are some of them. Kannel supports SMPP, EMI, UCP, AT, several HTTP and the others protocols. I hope that the kannel will not become to bloated if we tried to push every variant of HTTP specific implementation into it. Of course you can do it directly without Kannel, but it's a good approach to do it via Kannel, so that you always use it as your gateway and not one method for some carriers and another one for others, It's also nice to do it via Kannel cause it already implements stuff like it's internal queue, etc -- Kind regards, Milan
Re: Claro http communication
Hi, Besides, only MTs are pushed through kannel's HTTP interface. MO's are not. Hervi clearly talks about MOs. kannel also offers all these nifty sms-services, which would have to be built from scratch. An interesting question is how do you receive SMS over HTTP. Do you poll the SMSc HTTP every 5" to see if there are any new SMS or DLRs? BR, Nikos - Original Message - From: "Juan Nin" To: Sent: Monday, May 25, 2009 11:28 PM Subject: Re: Claro http communication Milan, There are already several HTTP SMSC specific implementations on Kannel, the ones that Hervι mentioned are some of them. Of course you can do it directly without Kannel, but it's a good approach to do it via Kannel, so that you always use it as your gateway and not one method for some carriers and another one for others, It's also nice to do it via Kannel cause it already implements stuff like it's internal queue, etc Regards, -- Juan Nin 3Cinteractive / Mobilizing Great Brands http://www.3cinteractive.com On Mon, May 25, 2009 at 5:22 PM, Milan P. Stanic wrote: On Mon, 2009-05-25 at 18:14, Hervι Nicol wrote: We have to send / receive SMS and DLRs over Claro (brazilian telco). We will communicate with them by HTTP. ^ If we write a patch for kannel for operator-specific HTML communication (just like for Clickatell, Brunet, 3united.com...), is there any chance that it may be included in Kannel CVS? You have to communicate with kannel over HTTP. Kannel have to communicate with provider over HTTP. Why you could not communicate with provider over HTTP without kannel. What should be role of the kannel in your case? I don't like to say that you do not have good reason for that. I'm just curious. Do you have some special hints / advices on how to proceed? It won't be too hard for us to write this code considering the existing operator-specific code, but it costs nothing to ask for some advice before starting to work on it ;) -- Kind regards, Milan
Re: Claro http communication
On Mon, 2009-05-25 at 17:28, Juan Nin wrote: > There are already several HTTP SMSC specific implementations on > Kannel, the ones that Hervé mentioned are some of them. Kannel supports SMPP, EMI, UCP, AT, several HTTP and the others protocols. I hope that the kannel will not become to bloated if we tried to push every variant of HTTP specific implementation into it. > Of course you can do it directly without Kannel, but it's a good > approach to do it via Kannel, so that you always use it as your > gateway and not one method for some carriers and another one for > others, It's also nice to do it via Kannel cause it already implements > stuff like it's internal queue, etc -- Kind regards, Milan
Re: Claro http communication
Milan, There are already several HTTP SMSC specific implementations on Kannel, the ones that Hervé mentioned are some of them. Of course you can do it directly without Kannel, but it's a good approach to do it via Kannel, so that you always use it as your gateway and not one method for some carriers and another one for others, It's also nice to do it via Kannel cause it already implements stuff like it's internal queue, etc Regards, -- Juan Nin 3Cinteractive / Mobilizing Great Brands http://www.3cinteractive.com On Mon, May 25, 2009 at 5:22 PM, Milan P. Stanic wrote: > On Mon, 2009-05-25 at 18:14, Hervé Nicol wrote: >> We have to send / receive SMS and DLRs over Claro (brazilian telco). We >> will communicate with them by HTTP. > ^ >> If we write a patch for kannel for operator-specific HTML communication >> (just like for Clickatell, Brunet, 3united.com...), is there any chance >> that it may be included in Kannel CVS? > > You have to communicate with kannel over HTTP. Kannel have to > communicate with provider over HTTP. Why you could not communicate with > provider over HTTP without kannel. > What should be role of the kannel in your case? > > I don't like to say that you do not have good reason for that. I'm just > curious. > >> Do you have some special hints / advices on how to proceed? >> It won't be too hard for us to write this code considering the existing >> operator-specific code, but it costs nothing to ask for some advice >> before starting to work on it ;) > > -- > Kind regards, Milan > >
Re: Claro http communication
On Mon, 2009-05-25 at 18:14, Hervé Nicol wrote: > We have to send / receive SMS and DLRs over Claro (brazilian telco). We > will communicate with them by HTTP. ^ > If we write a patch for kannel for operator-specific HTML communication > (just like for Clickatell, Brunet, 3united.com...), is there any chance > that it may be included in Kannel CVS? You have to communicate with kannel over HTTP. Kannel have to communicate with provider over HTTP. Why you could not communicate with provider over HTTP without kannel. What should be role of the kannel in your case? I don't like to say that you do not have good reason for that. I'm just curious. > Do you have some special hints / advices on how to proceed? > It won't be too hard for us to write this code considering the existing > operator-specific code, but it costs nothing to ask for some advice > before starting to work on it ;) -- Kind regards, Milan
