To prevent messages from being sent twice (e.g. if the subscriber has their hand set off), use (see documentation):
Validity number (minutes) Optional. If given, Kannel will inform SMS Center that it should only try to send the message for this many minutes. If the destination mobile is off other situation that it cannot receive the sms, the smsc discards the message. Note: you must have your Kannel box time synchronized with the SMS Center. == Rene Kluwen -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nikos Balkanas Sent: woensdag 2 juni 2010 6:44 To: Barry Murphy; Alan McNatty Cc: Users Subject: Re: DLR not being emptied for numbers it can't send to Hi, Then you should wait more. Failure can be either immediate (unknown subscriber) or can take up to 2 days (expired). In the latter case you should wait at least that long before cleaning DB, else kannel will report "Error: Cannot find dlr for message..." when it receives final failure. "Bufferred" is not a final dlr and kannel is waiting for the final DLR before deleting from DB. BR, Nikos ----- Original Message ----- From: "Barry Murphy" <[email protected]> To: "Alan McNatty" <[email protected]> Cc: "Users" <[email protected]> Sent: Wednesday, June 02, 2010 6:37 AM Subject: Re: DLR not being emptied for numbers it can't send to > Hi, > > Thanks for your input. Yes they seem to be dropped, if I login to either > of my current SMSC providers, they report as "Buffering" or something > along > those lines. I am using DLR DB so a manual clean out is easy enough for > me, > however I'd like to re-send the message via another carrier if not > delivered within X minutes to which I'm currently seeking a carrier that > can deliver to 2Degrees (NZ) with MNP > > P.s. Good to see another kiwi on the list :) > > Thanks > Barry > > > On Wed, 02 Jun 2010 15:10:41 +1200, Alan McNatty <[email protected]> > wrote: >> Hi Barry, >> >> Yeah - my understanding is the messages are silently dropped if off-net >> (without any notification). Your best option might be treat them as >> expired (possibly with a manual clean-up) after a standard network TTL >> if no DLR received (messages don't typically live on the network more >> than 5 days if undelivered). Obviously this would be best achieved using >> a DB for DLR storage. >> >> HTH's >> >> Cheers, >> Alan >> >> On 02/06/10 14:59, Barry Murphy wrote: >>> Yes I do use dlr-mask=31 and get nothing back in reurn from either > SMSC. >>> amdtelecom are a company I am looking at possibly using as a SMSC if > they >>> can route correctly to this network I'm having issues to. >>> >>> Thanks >>> Barry >>> >>> >>> >>> On Wed, 2 Jun 2010 05:46:25 +0300, "Nikos Balkanas" > <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> Nope. For that you would need portability support in bearerbox. I have > >>>> developed such a feature for a commercial version used by amdtelecom. >>>> >>>> Nevertheless your carriers should return a failed DLR if they fail to >>>> deliver. Are you using dlr-mask=31? >>>> >>>> BR, >>>> Nikos >>>> ----- Original Message ----- >>>> From: "Barry Murphy" <[email protected]> >>>> To: "Users" <[email protected]> >>>> Sent: Wednesday, June 02, 2010 5:33 AM >>>> Subject: DLR not being emptied for numbers it can't send to >>>> >>>> >>>> >>>>> Hi, >>>>> >>>>> I have a problem where if a number cannot be delivered to, it stays > in >>>>> DLR >>>>> table until manually removed. I have this problem with both SMSc >>>>> providers >>>>> I use and it's only when trying to deliver to a single carrier that > is >>>>> having issues with MNP. I wish to know if it's possible to have > kannel >>>>> attempt to redeliver a message that is stuck in DLR table using > another >>>>> SMSc that I have as a backup. >>>>> >>>>> Look forward to your response >>>>> Thanks >>>>> Barry >>>>> >>>>> >>>>> >>> >
