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
