> -----Original Message-----
> From: Mauricio Ramos [mailto:[EMAIL PROTECTED]]
>
> > That is how it is done. AFAIK, modules only try to resend if
> > the sending failed because of connection problems. when you
> > receive an SMSC_FAILED message - the module has given up on
> > trying to ever send that message.
>
> But that's not true at least for stable 1.2 because ever SIGHUP Kannel
> resends the limbo (failed and dlr-notified messages)
You are refering to SMPP - as I've said, this is a bug which is already fixed in the
CVS.
> 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.
--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]
+972-9-9581711 (116)
+972-67-340014
::..
43. If I knew it wasn't going to work, I would have tested it sooner.
--Top 100 things you don't want the sysadmin to say
