Hello, i allready about this issue a few days ago. Since i've got no reply i'll try again.
There is a Problem with the DLR Lookup/Update/Delete in DLR-Handling. If we send SMS with Delivery Notification (Mask 31) the DLR is inserted in our Mysql Table with SMSC=xyz, ts=<Time>, destination and other fields. If a new DLR is received from a SMSC to Kannel, Kannel will look in that Table for a matching Entry for the received DLR. Kannel only uses SMSC and TS. TS is Year Month Day Hour Minute Second and Second is the smallest Value. If we send more then 1 SMS per Second through one Connection (which isn't that unusual) Kannel can't find the right entry and SELECT a random one from the MySQL Table. After Kannel found an entry and has processed that entry, Kannel does an UPDATE on the MYSQL tabel. Again only using TS and SMSC and again a random one matching SMSC and TS is updated. Same for DELETE after the entry is solved. A Random one of those Matching is deleted. If you use DLR only for Kannel to first SMSC Delivery (Mask 24) than there is no Problem for UCP and SMPP (haven't tested other Protocols) since for that case SMPP has only one DLR open at any time, and UCP saves in ts=<SMSCID>_<Window> and on every Window there is also only one DLR open at any time. I fixed the Problem by altering SELECT, UPDATE, DELETE to include destination in the WHERE clause. I really hope i don't miss anything. That Bug is in 1.3.1, 1.3.2 and even the new Stable Release 1.4.0. Kind Regards. Mit freundlichen Gr��en YOC AG -------------------------------- Stefan Haubold YOC AG Dircksenstr. 47 10178 Berlin / Germany Tel: +49-30 72 61 62-401 Fax: +49-30 72 61 62-222 mail to: [EMAIL PROTECTED] visit us at: www.yoc.de / www.yoc-ag.de Login mit Alter und Geschlecht per SMS unter 72768 yoc - dein wille geschehe.
