Hi gordon, you're analysis is correct. the 3 sms will all have the same DLR (smsc and ts). Because of this, Kannel can not guarantee that you will get the same DLR (database) entry upon reception of the DLR from the SMSC. this is quite unfortunate when you are trying to provide acurate logging for individual phone numbers.
this problem and several solutions were discussed on the devel list back in april (see thread: "[PATCH] dlr_mem.c & dlr_sdb.c check for dst"). unfortunately there was no agreement on how to solve this problem. perhaps now that Stipe is back on the list, we may be able to find a solution acceptable to everyone. Stipe? are you familiar with this topic from back in april? Nick On Tue, 2004-08-31 at 22:15, 3steps2web-support wrote: > hi together, > > following problem: > we have setup kannel 1.3.2 with mysql-support ... all is working correct! > > but the DLRs makeing problem, because kannel does confound them. > > kannel create for each sms - i send to him - a timestamp and store that > (with some > other data) in the mysql. > but it could happen that i send more than one sms to kannel at the same > second. > > problem is now, if a dlr is coming ... but i have 3 sms with the same smsc > and > the same ts ... i have tested and kannel deletes the wrong sms :( > > kannel do "SELECT ... FROM dlr WHERE smsc='test' AND ts='280804214231'" > > this causes big problems :( if i have 3 sms with smsc='test' and > ts='280804214231' > he will get 3 sms as result from table dlr ... and deletes one of them ... > ... very often the wrong one :( > ... i think kannel must regard minimum the destination! > > > hope someone is able to help me with that before i get crazy :) > > > regards and thanks! > > gordon > >
