C isn't my specialty but I think I understand what dlr.* does: creates and
updates DLR records for msgs to individual MSISDNs. This makes sense and
seems reasonable.
What I still don't quite get is is how "dlrurl" is supposed to work: if it
is part of the gateway it would seem unnecessary to have it as a parameter
as if it's external URL/URI but on the other hand as an external URL I
would expect to be able to pass it user-definable parameters, ie. allow
external users to track their own messages even without access to the DLR
store.
the DLR storage is completely internal to Kannel and is not supposed from the outside.
it is used to track internally messages kannel has sent to SMSC's. The DLR url is a callback mechanism to tell your application the status of the message. You can not ask kannel for the status of a message, you will get informed when the status changes and thats by the DLR URL mechanism.
ie.
if I have a call like this:
http://mysmsgateway.com:13013/cgi-bin/sendsms?username=****&to=004917878262267&mclass=2&text=hm&password=******
validity=1440&dlrmask=2&dlrurl=http://anotherserver.com/cgi-bin/dlr_process.cgi?to=004917878262267&test=hm&msg_id=4
you have to URL encode the URL you put into &dlrurl.
I only seem to get the first paramater "to=004917878262267" back.
right because &test=.. is not part of the parameter &dlrurl anymore.
Andreas Fink
Global Networks Switzerland AG
------------------------------------------------------------------
Tel: +41-61-6666333 Fax: +41-61-6666334 Mobile: +41-79-2457333
Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland
Web: http://www.global-networks.ch/� [EMAIL PROTECTED]
------------------------------------------------------------------
Send SMS to +979 979 UNICEF (+979979864233) to donate a
small amount to the children of Iraq. http://www.gni.ch/unicef
