Hi,
I see. I thought maybe that was the case with %a & %b only being used
with a SMSC and not the web interface. How easy would this be to add (I
do a little programming but haven't looked at the code yet)? Adding the
DLR-URL into the post is going to be too difficult in the environment for
the box that is doing the original HTTP post to the kannel server.
Or I guess a perl script listening on a socket that can respond to a HTTP
request acting as a middle man (client of the php dlr.php script using
http perl module and the kannel 15015 web sever) would do?
It's not a good idea to put a perl script between kannel and application. It
will be another point of failure in your infrastructure.
The best way to implement this is do that in your application by adding
X-Kannel-DLR-Url header into the HTTP POST request.
And yet another idea:
You could also add a 'fake' HTTP type SMSC, making HTTP GET request to the
real SMSC.
an example based on userguide:
(http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN2297)
group = smsc
smsc = http
smsc-id=fake-smsc-id
system-type = kannel
smsc-username = nork
smsc-password = z0rK
port = 13015
send-url =
http://localhost:13013/cgi-bin/sendsms................smsc=real-smsc-id&dlr-url=http.........
allowed-smsc-id=fake-smsc-id
denied-smsc-id=real-smsc-id
Make sure that dlr-url field is urlencoded. Don't forget to set properly
smsc-id, allowed-smsc-id and denied-smsc-id to avoid looping messages.
I have used this method in one of my previous projects and it worked very
well
Regards
