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 >>> >>> >>> >
