Hi!

When Kannel fails delivering an MT to a remote SMSC, if it's a temporary
error it will retry to resend it according to the "sms-resend-freq" and
"sms-resend-retry" settings.
If we then reach "sms-resend-retry" number of attempts kannel will generate
a "NACK/Retries Exceeded" error.

On SMPP the typical case is when the remote SMSC returns a temporary error
on the submit_sm_resp.

The problem with this approach is that the application never gets a DLR
with the error that the remote SMSC returned, so unless you got your logs
in debug mode, there's no way to know why the MT failed.

Can this be changed, so that instead of sending back the "NACK/Retries
Exceeded" error, have it send the real error that the remote SMSC returned?
I guess the ideal would be to have a DLR be sent on each of the failed
attempts (the error could vary on each attempt), but if not, at least have
the real error from the last attempt be sent instead of the "NACK/Retries
Exceeded" one.

I'm not sure how straight forward this would be, since this logic is
probably used by all the different smsc drivers.

Thanks in advance.

Reply via email to