I'm not sure. When I look at the http smsc in user guide / code, I always think MO traffic, because its listening to a specific port on the bearerbox.
How can I configure the sendsms http interface, to use an http smsc to push through send-url? Because I only want 1 connection from my push server, and to use smsc or some other param to distinguish between provider/protocol. (rather than listening on different ports for each protocol/provider) / Brian ________________________________ From: Rene Kluwen <[email protected]> To: 'Brian McCavour' <[email protected]>; 'Andreas Fink' <[email protected]> Cc: "'[email protected]'" <[email protected]> Sent: Wednesday, December 12, 2012 1:14:01 PM Subject: RE: Making a http to http MT kannel You can set up two different http smsc’s for that, right? Like smscA and smscB. And when you call the sendsms, do something like: http://smsbox.host.name:port/cgi-bin/sendsms?username=foo&password=bar&smsc=smsA&to=0123456&text=Hello+world or http://smsbox.host.name:port/cgi-bin/sendsms?username=foo&password=bar&smsc=smsB&to=0123456&text=Hello+world or am I missing your point? =+= Rene From:[email protected] [mailto:[email protected]] On Behalf Of Brian McCavour Sent: woensdag 12 december 2012 19:02 To: Andreas Fink Cc: [email protected] Subject: Re: Making a http to http MT kannel Right, sorry I was not clear. What I mean by protocol was just the body content format.I want the http IN to be able to take the same message data, and send it to 2 differnet http OUT with different format, based on a parameter in the request from the server. Basically, my goal is to be able to send a request from my server like http://smsbox.host.name:port/cgi-bin/sendsms?username=foo&password=bar&SOMEID=id1&to=0123456&text=Hello+world then have Kannel inernaly do: if (SOMEID == id1) { POST <smscA> ... <foo>text</foo> } else if (SOMEID == id2) { POST <smscB> ... <bar>text</bar> } So foo, and bar are the 2 protocols I was speaking of earlier. I just realized also that I can survive with no body in the request from my server, (as above) just not in sending to the smsc. So actually I guess I do need the smsbox afterall. I think my first solution was not good. I should configure a sendSms for my server, as in the example above and then configure a sms-service with a post-url to post this data to smsc (smsA, smsB in exmaple)I just might need to do some special implementations for formatting the posted data. ________________________________ From:Andreas Fink <[email protected]> To: Brian McCavour <[email protected]> Cc: "[email protected]" <[email protected]> Sent: Wednesday, December 12, 2012 11:28:36 AM Subject: Re: Making a http to http MT kannel protocol ID's can be of different kind. There is a PID field in the SMS PDU which you can set by &pid=... if I'm not mistaken. But there are also port numbers of WAP which can be considered Port ID's. They are in a UDH header. Both are not part of the content by itself and the SMSC you submit it to have to support it. UDH headers are widely supported. Setting the PID might not.. On 12.12.2012, at 17:13, Brian McCavour <[email protected]> wrote: Hi, I just want to list what I believe is supported and what I believe I need to add support for, and see what you “experts” think. I have 2 http interfaces to 2 different SMSC, using 2 separate (content) protocols, and an HTTP interface from my server. I intend only to push content. (MT) So I need to setup kannel to do: http in with some protocolID >>> format data based on ID >>> http out data to correct interface I read the userguide and I’m poking around the code right now, but I’m a bit confused. (I have j2me background, so I’m learning C as I go) Problem: http in, listening for my server Solution: It seems like what I need is the http SMSC configured to use “sendsms”. If I do this I guess I basically ignore the smsbox, and so I’m just running the bearerbox process only. So I would configure the bearerbox for a http / generic smsc. This would be listening for my server. Problem: Routing to correct SMSC Solution: I could reuse one of the request cgi param, maybe generic-param-service to modify the “send-url” internaly. (or maybe theres an escape code I could use directly from the configuration file) Problem: The incoming request from server needs to support body data, and the the outbound SMSC request/post needs to support body data Solution: Have not really made progress here. I guess I would just have to implements this, as I don’t see any body support. Am I on the right track? Sorry if I seem so lost, im in slightly over my head, but hopefully not for too long. Any tips/hints/corrections etc.. are encouraged. Thanks, Brian
