2014-11-05 17:54 GMT+01:00 Alvaro Cornejo <cornejo.alv...@gmail.com>: > Hi > > Those sql commands are for kannel internal queue management only. That is > why there is no UPDATE. > > You have 3 options: > > - do your own dlr handler. It can be as simple as a php script that receives > the call and insert info in a database. You use dlr-url to call it.
For a number of non-technical reasons I cannot do this. > - use sqlbox. What's that? > - hack kannel code to handle dlr as needed. This is what I have done with a three line patch: replace the sql_remove with an sql_update. In my opinion, an SQL table like the one for DLRs should only get INSERTs and SELECTs and never UPDATEs and DELETEs. Also for the sake of scalability. > Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier > celular y Nextel > en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y > GPRS online > Visitenos en www.perusms.com > > On Wed, Nov 5, 2014 at 10:10 AM, Vincenzo Romano > <vincenzo.rom...@notorand.it> wrote: >> >> 2014-11-05 16:01 GMT+01:00 Christopher Burke >> <christopher.bu...@simulity.com>: >> > Yeah, I believe that DLR storage can be achieved using the Kannel SQLBox >> > project. I think GET-URL is possibly less complex. Depends if you’re >> > only >> > storing DLRs or acting on them I guess. >> >> I don't want to write another program when all other bits seems to be >> already there! >> From the source code I can see a set of functions to update the DLR >> storage, one for each different SQL backend. >> But what I see in the reality is that the DLR storage gets only >> INSERTs (upon submission) and DELETEs (upon delivery). >> No UPDATE at all, even if I asked for a dlr-mask=31. >> Isn't there a way to trigger those updates? >> >
