Hi Stuart,
There is always some form of DLR storage in Kannel. The choice is whether
you use internal or external storage. The only difference here is that,
when you restart the Kannel process, you lose all internal DLR storage
whereas if you use external storage it persists across separate process
executions.
As the developer you would generally not interact with the DLR storage be
it internal or external. I'm surprised you don't request DLR's for all
messages though!
Cheers,
Iain
On Fri, 21 Aug 2009, Stuart Beck wrote:
I'd like to know what is the operational benefit of using DLR storage within
Kannel?
We are currently using an external postgresql store for DLRs and once the
data is stored we are not doing anything with it.
We use a single kannel instance most of the time so there is no requirement
to have DLR's stored for other instances to pick up.
Our application may or may not request DLR's from the carriers as we desire
and processes them internally when they come in so the kannel dlr storage is
from this perspective a wasted effort on our part.
Is there any operational reason internal to kannel that I might want to have
DLR storage enabled?
If I disabled dlr storage / processing, would this impact the DLR messages
getting to our application to be processed?
--
Stuart Beck
-----------
Systems Administrator
m.Net Corporation
No one knows Mobile like m.Net
Tel. No. +61 8 8210 2049
Web: http://www.mnetcorporation.com
Try our new online mobile marketing system
www.campaignmobile.com
ADMA MMA Promotional Campaign of the Year, 2008 Winner .
BRW. FAST 100 Awards, 2008. Number 5.
Deloitte Technology Fast 50 Australia 2008 Winner.
