Pretty much, except for ts. If that were true for ts, you should get your DLR sometime in 4000 AD :-)
If I ma not mistaken, ts is actully the DLR meesage-id. It is related to your original message-id, (hence kannel can find it) but is not the same. BR, Nikos ----- Original Message ----- From: hafez ahmad To: Nikos Balkanas Cc: [email protected] Sent: Monday, January 12, 2009 12:09 PM Subject: Re: How DLR matched with in the Database Dear Nikos, Thanks for reply, but can you please explain more, I have the following in my config file: and my log: field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc 2009-01-12 11:49:09 [29596] [36] DEBUG: DLR[mysql]: Looking for DLR smsc=MYCONN, ts=643779203, dst=9xxxxxxxxxxx, type=1 is that mean that kannel look for the recorde with timestamp = 643779203 and destination = 9xxxxxxxxxxx and smsc = MYCONN. and thanks again. Regards, Hafez On Sun, Jan 11, 2009 at 5:10 PM, Nikos Balkanas <[email protected]> wrote: No. It matches your configuration file, where you describe the exact matching between variables and columns in your table. BR, Nikos ----- Original Message ----- From: hafez ahmad To: [email protected] Sent: Sunday, January 11, 2009 3:57 PM Subject: How DLR matched with in the Database Dears, when DLR back to kannel from the SMSC, how it match with the mysql DLR table ?, is it using the Message id ? Regards, Hafez -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com
