Alex,
We are not talking about db storage, here. We are talking about internal
storage and spool or file storage used for all MOs. The one seen from HTTP
admin.
BR,
Nikos
----- Original Message -----
From: Alejandro Guerrieri
To: Nikos Balkanas
Cc: Jarratt Ingram ; [email protected]
Sent: Monday, September 13, 2010 1:21 PM
Subject: Re: DLR and Message Type question
"Unmatched DLRs are discarded and erased from storage"
How so? You need to do that _manually_ I'm afraid. If a DLR arrives and it's
not found, it means that it's NOT on the DB, so there's nothing to delete.
If a DLR doesn't arrive, the original entry will remain there forever. You
need to run a manual query to delete them using some criteria (usually
"older than N days").
Kannel only deletes matched "final" DLR's ("final" varying according to your
dlr-mask setting of course).
Regards,
Alex
2010/9/13 Nikos Balkanas <[email protected]>
Hi,
No, do not mess up with msg-id-type or you will loose 100% of your DLRs.
Unmatched DLRs are discarded and erased form storage. You can examine
storage contents from the HTTP admin.
Post your configuration and detailed stsrtup bb logs.
BR,
Nikos
----- Original Message ----- From: "Jarratt Ingram"
<[email protected]>
To: <[email protected]>
Sent: Monday, September 13, 2010 12:37 PM
Subject: DLR and Message Type question
Good Morning All,
I am experiencing some small issues with the DLR mechanism in my current
Kannel configuration,
RPM version of Kannel on Fedora 13 64bit
DLR is currently set to internal storage,
msg-id-type is default as it is not explicitly set.
I have two SMPP connections to a provider both have the same smsc-id and are
both setup with transceiver-mode = 1
The DLR processing works for 90% of the time and every now and again i get
the following in the logs
2010-09-13 11:11:13 [7277] [6] ERROR: SMPP[3]: got DLR but could not find
message or was not interested in it id<27/00/4d599338/1127829048804>
dst<27829048804>, type<2>
This then leaves the message in an ACK/ state and never gets updated to sent
or undelivered, based on the message above does this mean i should rather
set the msg-id-type = 0x02 ? i am assuming that Kannel is able to correctly
determine the DLR's 90% of the time and gets stuck every now and again ?
Also does the Kannel status page EG: DLR: 1247 queued, using internal
storage
directly relate to this i.e id a DLR is not found does the DLR queue get
reduced by 1 ? As i have had over 1k DLR's pending for a few days now
Any help would be appreciated,
Kind regards
Jarratt
