> > Hang on! :-) The message wasn't mal-formed, was it? I've just
> > intentionally sent a sms with and invalid number whose prefix is not
> > configured to be accepted by Logica's SMSC, so I got the
> > 0x0000000b. The
> > same problem seems to happen when I got errors like
> > 0x00000001, 0x00000014
> > and 0x00000045 ("Message Length is invalid", "Message Queue
> > is full" and
> > "Throttling error", respectively).
>
> 'Message Length is invalid' as well as invalid number prefix
> are caused by malformatted messages which should be rejected
> from bearerbox after delivery is failed and should not be
> retried (as surely the same message would fail time and
> again). 'Message Queue is full' and 'Throttling error'
> messages are temprary failures and should cause the message
> to be requeued for sending immidietly, and not when a SIGHUP
> is received.
> The behavoir described above is in current CVS. genreally
> speaking - the behaviour of SMPP in Kannel 1.2.0 is not correct.
Sorry, I understood what you've said about definitive failures and temporary
failures and how Kannel SHOULD behave regarding SMPP specification, but I
got a little bit confused how Kannel DOES behave CURRENTLY. Please confirm
these statements:
1) Current Kannel CVS ALLWAYS removes message from store when he got ANY
NACK from a SMPP SMSC, either temporary failure (ex. Throttling) or not (ex.
Message Lenght).
2) Current Kannel CVS NEVER resend messages when ANY failure occurs, either
temporary failure or not.
Thank you very much.
