[BUG] EMI2 DLR (Was: emi2 DLR question)

"Oded Arbel" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Sorry - my mistake : it does dlr_add again after getting the ACK. I missed that.
 
But this is another problem altogether, twice a problem actually :
1. when doing dlr_add the first time, it doesn't mask out the FAIL/BUFFERED/SUCESS bits on the dlr_mask, with the effect that a later dlr_find will find those bits enabled and will not remove the DLR from the database. since that DLR will never be used again (final delivery reports are generated from the second dlr_add() call),it will remain for all eternity - or actually, since the "ts" field is filled with the "transaction id" of EMI, which are reusable - the next time that transaction id is used to send an MT, a "duplicate entry" error will be generated when using persistant DLRs.
2. since the current DLR code (w/o the patch that I submitted) have a certain logic, even if the first dlr_add() call will mask the "final DLR" bits on the dlr_mask, when the 51 response's dlr_find is called, the DLR record will still not be deleted from the database (The DLR patch I submitted changes the logic to remove DLRs from the database if an SMSC_* type DLR is received and no "final" DLRs are set in the mask).
 
We have a patch to fix all that, but it won't be tested till tuesday so I won't submit it for now.
 
--
Oded Arbel
m-Wise mobile solutions
[email protected]
 
+972-9-9581711 (116)
+972-67-340014
 
::..
Ask me about microwaving cats for fun and profit.
 -- Bumper Sticker

 



-----Original Message-----
From: Oded Arbel 
Sent: Sunday, September 15, 2002 12:13 PM
To: Kannel-devel (E-mail)
Subject: emi2 DLR question.


Hi list.
 
Does anyone receives delivery notfication (delivered, failed or buffered) using EMI2 ? because the current implemenation looks very broken to me - when doing dlr_add() the driver uses the transaction id of the message as the "time stamp" (ts), and also matches that when receiving SMSC_FAIL/SMSC_SUCCESS. but when receiving delivery notification, the transaction ID is not available anymore, and instead it tries to match using the SCTS field from the EMI message - this looks to me like it will always fail.
 
Comments ?
 
--
Oded Arbel
m-Wise mobile solutions
[email protected]
 
+972-9-9581711 (116)
+972-67-340014
 
::..
A short cut is the longest distance between two points.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.