I've got an update on this issue which is still somehow unsolved: I sent out a message to around 60 recipients and I did set the deferred time to some minutes in the future. This worked out quite good: No strange timestamps or leftovers in the dlr table.
Is it possible for kannel to get 'confused' while submitting messages to the SMSC, waiting for ACK's and already dealing with delivery status updates on previously (some seconds before) submitted messages at the same time? We use the EMI2 protocol with the parameters throughput=2 and flow-control=1. Does anyone else have experience with bulk-sms'ing? How do other user handle this case? Thanks for any input. Dave > Hello, > > I sent out a message last Friday about strange DLR (MySQL) entries. There > are still a few questions open. > > When sending SMSes to multiple recipients the DLR table gets populated > with lots of entries having a timestamp in the form of: > IP-Address:Port-MsgNum (123.123.123.123:5000-56) Has anyone else seen > this? > > All of these entries have a status 8 (SMSC submit) although all (or most) > of them have been successfully delivered as verified with our SMSC > provider... > > It seems to me that kannel is not picking up every DLR from the SMSC > (correctly). Please help me on this! Any hint is appreciated! > > Dave > > > >
