Hello Community,
I had enabled dlr-storage under kannel to store delivery report in mysql
database and now dlr table is having more then 8 (.8 million) lacs records.
Can any one let me know how should i delete old dlr from database for which
i have not received the delivery report since last 10
Hello Community,
I had enabled dlr-storage under kannel to store delivery report in mysql
database and now dlr table is having more then 8 (.8 million) lacs records.
Can any one let me know how should i delete old dlr from database for which
i have not received the delivery report since last 10
Yes Rene,
I want each clients to be able to have 4 or 5 simultaneous connections using
the same account details.
Is this possible, and how, if yes?
Best Regards,
Michael C. Nwaogu
From: Rene Kluwen rene.klu...@chimit.nl
To: 'Mike Nwaogu'
Dear Alexander,
I have two TLV parameter, the first for carrier routing code 0x1400 and the
second for tariff code 0x1401 so I add two TLV parameter like that
Carrier routing code
group = smpp-tlv
name = TLV-name
tag = 0x1400
type = octetstring
length = 20
smsc-id = x
Tariff code
Dear Michael,
I would suggest, you start read userguide:
http://kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN6204
Thanks,
Alex
Am 02.04.2012 um 13:10 schrieb Michael Farouk:
Dear Alexander,
I have two TLV parameter, the first for “carrier routing code 0x1400” and the
Hello Community,
I had enabled dlr-storage under kannel to store delivery report in mysql
database and now dlr table is having more then 8 (.8 million) lacs records.
Can any one let me know how should i delete old dlr from database for which
i have not received the delivery report since last 10
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
attachment was scrubbed...
URL:
http://www.kannel.org/pipermail/users/attachments/20120402/0b1b8a9e/attachment-0001.html
--
___
users mailing list
users@kannel.org
http://www.kannel.org/mailman/listinfo/users
End
13 matches
Mail list logo
