Hello,
you should put dlr-mask=31 then you will be able to get all the DLR.
Dlr-url should be accessible, usually on the same machine, and then a script
(php or other) is the solution to make the dlr process.
an example extract from my php script (not perfect but could be a good start)
You can add a timestamp field to your table with default ON_INSERT
CURRENT_TIME_STAMP.
As this is only dlr table, if you delete all, there won't be any
problem other than an error line in your logs for a dlr coming in and
not having a match.
Hope helps
Alvaro
On 4/3/12, spameden
You can add a field to the dlr table of type TIMESTAMP (in mysql).
This will get filled with the current date/time upon insert-time.
After 10 days you can delete all the records that have that field set to
older than 10 days.
== Rene
From: users-boun...@kannel.org
Hello,
Let me confirm that we are getting proper delivery report from SMSC and the
same is getting deleted automatically from dlr table however as we all know
that we generally don't receive 100% delivery report.
So we use to get 80-90% of delivery report and rest 10-20% delivery report
is still
Hello,
Let me confirm that we are getting proper delivery report from SMSC and the
same is getting deleted automatically from dlr table however as we all know
that we generally don't receive 100% delivery report.
So we use to get 80-90% of delivery report and rest 10-20% delivery report
is still
you can use this query:
delete d from dlr d inner join sent_sms s ON s.dlr_url=d.url where
s.momt='MT' and s.time = UNIX_TIMESTAMP('2012-04-02 08:00');
to delete all dlr's from dlr table before 2012-04-02 08:00
the only thing is you need to double check if sent_sms has dlr_url field
the same
Hello,
I am sorry but your provided query will not work for me as i am not using
sqlbox to send messages.
I am using smsbox to send sms via HTTP API call and at bearerbox's end i am
storing dlr under mysql so that in case bearerbox crashes due to any
reason, i have dlr to restore from MySQL.
If you're using HTTP API call, I guess you're also taking advantage of
dlr_url dlr_mask options to get DLRs, right?
Do you store anywhere message statuses and actual dlr_url ?
The problem is you need to delete only old entries, but dlr table itself
doesn't contain a time field there.
There are
parts_num yours shouldn't have, its my modification ;)
2012/4/3 spameden spame...@gmail.com
If you're using HTTP API call, I guess you're also taking advantage of
dlr_url dlr_mask options to get DLRs, right?
Do you store anywhere message statuses and actual dlr_url ?
The problem is you