It depends on usage case. If all you want is just to update the DLR status in another table, you can use triggers. However if you have more complex actions to take, then dlr-url does its job very well.
Br, Rinor On Mon, Oct 1, 2012 at 2:27 AM, Sebastien Cramatte <scrama...@nixus.es>wrote: > Hi, > > Thank you for your answer. > > Finally after digging mailing list, I've seen that if you use sqlbox > you must specify "boxc_id" to be able to trigger dlr-url > In all case I thing that to avoid overhead it would be better to use > MySQL trigger instead of dlr-url … > > > De: Rinor Hoxha <rinorho...@gmail.com> > Fecha: Mon, 1 Oct 2012 02:24:17 +0200 > Para: - - <scrama...@nixus.es> > CC: "users@kannel.org" <users@kannel.org> > Asunto: Re: Issue with DLR and DLR-URL ... > > what dlr-mask are you using ? > > On Mon, Oct 1, 2012 at 2:21 AM, Rinor Hoxha <rinorho...@gmail.com> wrote: > >> Are you sure apache is listening on 127.0.0.1? >> netstat -ntlp >> >> >> >> On Sun, Sep 30, 2012 at 8:56 PM, Sebastien Cramatte >> <scrama...@nixus.es>wrote: >> >>> Hello, >>> >>> I've setup my Kannel to use DLR >>> >>> As you can see bellow, My provider send DLR information and seems >>> that Kannel handle it … >>> Unfortunately looks that dlr-url is never triggered. My dlr.php script >>> is ok. Moreover in apache log I don't see any http request to dlr.php >>> >>> Any ideas of what occurs here ? I've test with dlr-storage=mysql >>> but I got same issue. >>> Note that SMS are delivered properly to destination. >>> >>> --- bearerbox.log >>> 2012-09-30 20:50:59 [17243] [7] DEBUG: SMPP[amdtelecom] handle_pdu, >>> got DLR >>> 2012-09-30 20:50:59 [17243] [7] DEBUG: DLR[internal]: Looking for DLR >>> smsc=amdtelecom, ts=4c37c964-3b43-4cb1-b8e0-1b930b777b99, dst=34696679787, >>> type=1 >>> 2012-09-30 20:50:59 [17243] [7] DEBUG: DLR[internal]: created DLR >>> message for URL < >>> http://127.0.0.1/dlr.php?dlr=%d&from=%P&to=%p&report=%A&ts=%T&charset=%C&smsc=%i >>> > >>> 2012-09-30 20:5 >>> --- >>> >>> Best regards >>> >> >> >
