You'll get in a lot of trouble regarding performance if you do that: Your DLR table will grow and grow and unless you provide means of rotating/backup the data to another table, you'll be doing searches on an eternally growing data set, resulting in performance degradation.
There's no problem if you handle a couple hundred messages a day, but if you'r dealing with a couple _hundred thousand_ a day, things start to slow down very fast! :) Anyway, I recommend you to make some indexes for the fields Kannel will use for searching when doing the updates. That should get you going faster, keep in mind that each message you deliver will generate at least 2 or 3 hits to the database, so keep it small and simple. Regards, On Apr 8, 2005 4:00 PM, David Abbott <[EMAIL PROTECTED]> wrote: > We changed the source code to NOT delete the row, just update it. Hopefully > there isn't any problem with this approach, but just seemed easier at the > time. > Maybe there should be (yet another?!?) config option defining persistence of > the DLR row. > > >Just a quick note: Don't expect Kannel to _persistently_ store the > >DLR's on the MySQL database. It just uses MySQL as a temporary means > >of storing DLR's while they wait to be sent back from the SMSC. When > >the "final" DLR arrives (sent, not sent, etc), Kannel DELETES the row > >from the database and make a final request to the script you > >instructed whith the parameters you passed (look at the docs for info > >regarding how to do that). > > > >That script should care for the persistent storage of your DLR data > >(maybe changing a flag on your message log table or something like > >that). > > > >Hope it helps, > > > > > >On Apr 8, 2005 5:59 AM, Catalin Trifu <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > DLR = delivery report. > > > A SMS can have various statuses: queued by the SMSC, delivered to > >phone, undeliverable, etc. > > > Kannel can ask the SMSC about the status of the sent SMS and can report > >back to your application. > > > Take a look at dlr-url and dlr-mask in the docu' > > > Using the above you can instruct kannel to forward statuses from SMSC > >to your application. If you > > > use MySQL for Kannel's own DLR storage it will also store the status in > >the MySQL database. > > > > > > > > > Catalin > > > > > > > > > Alejandro J. Ramírez wrote: > > > > Hmmm thanks Rodrigo... > > > > > > > > I'm still not clear on this DLR thing... is this some kind of CDR that > > > > can be used for billing? Or only record of outgoing SMSs? > > > > > > > > So if I want to save my DLR, I must use MySQL or any of the other > > > > options? > > > > If I user the URL for store-status I see nothing there... what does > >this > > > > mean? I am CERTAIN that im able to deliver SMS... but im a little bit > > > > confused (as you all might see..) > > > > > > > > Thanks again!! > > > > > > > > Alejandro Ramírez > > > > > > > > > > > > > > > > -----Mensaje original----- > > > > De: Rodrigo Cremaschi [mailto:[EMAIL PROTECTED] > > > > Enviado el: Jueves, 07 de Abril de 2005 01:36 p.m. > > > > Para: Alejandro J. Ramírez; users@kannel.org > > > > Asunto: Re: DLR report? > > > > > > > > INTERNAL means RAM. > > > > > > > > ----- Original Message ----- > > > > From: Alejandro J. Ramírez > > > > To: users@kannel.org > > > > Sent: Thursday, April 07, 2005 5:30 PM > > > > Subject: DLR report? > > > > > > > > > > > > > > > > > > > > > > > > Hi All! > > > > > > > > I'm living using Kannel a lot but as a newbie. i have lots > > > > of > > > > questions. One is. Where are the DLR reports stored? I have it set up > >as > > > > > > > > INTERNAL, but where is this stored?? Is it an specific file?? > > > > > > > > Thank you so much!! > > > > > > > > > > > > Alejandro Ramírez > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >-- > >Alejandro Guerrieri > >Magicom > >http://www.magicom-bcn.net/ > > > > _________________________________________________________________ > It's fast, it's easy and it's free. Get MSN Messenger today! > http://www.msn.co.uk/messenger > > -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/
