Iain, There are a couple of reasons you might not want to use internal storage. The first is that its wiped out when Kannel restarts, so if there is a problem, or you want to add a new SMSC into the configuration any outstanding DLRs are lost.
>>This is actually NOT necessarily true.... >>If your .store is not located in /tmp/ (as suggested by the user guide) >>Your store WILL be persistent! The second would be if you had 2 Kannel boxes running and there was the possibility of a DLR coming back into the other Kannel box from the one that sent it. You would need to have a single database that both boxes shared. >>This also is NOT necessarily true... >>If you configure ALL your smsboxes WITHOUT an smsbox-id, then YES...Ben is right. >>How ever, if you need the DLR to be handled by the box that issued it...you can name your >>smsboxes and bearerbox will send all DLRs to THAT box. >>But...Why bother? Who cares WHICH box notifies the sendsms user? Its quite possible that people have phones switched off in meetings, on flights, go on an underground train etc. So whilst most messages are delivered quickly its possible with a large volume of messages to see outstanding DLRs for quite some time. >>This also is NOT necessarily true... >>As I said in an earlier mail, SOME SMSC tell you if the message is buffered at either the phone or the SMSC >>In that case you will receive intermediate DLRs (if you requested them with a proper dlr-mask) >>In general any message you submit to your supplier should get a FINAL DLR within 5 minutes >>We allow a latency margin of 1% (meaning that 1% of all traffic is allowed to have it's DLR delivered AFTER 5 minutes) >>IF this is the case, then a route is considered OK. Because a small margin of the handsets you a trying >>to reach is indeed switched of or something >>So in short, Ben is not wrong, but his information needed some additions... Regards Ben On 13 Mar 2007, at 11:54, Iain Dooley wrote: >> Thats correct. Kannel will always call the URL you provide to send >> you a DLR. The storage method is irrelevant in that respect. > > okay, so i'm sorry if this sounds really bleeding obvious, and if > it does it's because i've never dealt with astronomical volumes of > messages but: > > in a machine with (say) 1gb of RAM, and a dlr-url, and the fact > that most smsc's don't tell you anything except the 'final' state > of a message (and the fact that your messages generally get > delivered pretty quickly as long as your smsc isn't complete > shite).... > > why does anyone use mysql or postgresql dlr-storage? i mean, does > anyone, at any time, have more than, say, 100mb of dlr-storage? > mysql/postres, they can handle TERABYTES of data, but, couldn't you > handle a dlr-queue for a _telco_ with a peasant's budget worth of ram? > > cheers > > iain > -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.10/720 - Release Date: 3/12/2007 7:19 PM
