Re: matching delivery reports to their corresponding outgoing message
Patrick Okui wrote:
Hi all,
I'd like to be able to figure out which message a particular
delivery report belongs to. The dates on the report are helpful,
but I'd like to be able to match based on the ts since that's
more definite.
Currently I'm thinking of modifying gw/bb_alog.c to store the id
that the SMSC gives after submit_sm (and the script in my
dlr-url can strip it from the delivery report).
Any cleaner ways to do this?
(PS: running version 1.4.0 on FreeBSD)
whenever you thing of changing or adding things, please go with the CVS HEAD
branch, and never with release source trees. 1.4.0 is way too old.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
RE: matching delivery reports to their corresponding outgoing message
The usual way of solving this problem is giving every message that you sent out a unique ID (e.g. the autoincrement field of the table that you store your messages in will do nicely). You can pass this ID as a parameter of your dlr-url. This is a clean, proven method that is independant of the underlying sms bearer. Rene Kluwen Chimit -Original Message- From: Patrick Okui [mailto:[EMAIL PROTECTED] Sent: vrijdag 21 juli 2006 16:20 To: users@kannel.org Subject: matching delivery reports to their corresponding outgoing message Hi all, I'd like to be able to figure out which message a particular delivery report belongs to. The dates on the report are helpful, but I'd like to be able to match based on the ts since that's more definite. Currently I'm thinking of modifying gw/bb_alog.c to store the id that the SMSC gives after submit_sm (and the script in my dlr-url can strip it from the delivery report). Any cleaner ways to do this? (PS: running version 1.4.0 on FreeBSD) -- patrick
