We've investigated this a little further. It seems that this infinite Generic error loop only occurs with an sms-service where concatenation=true. It appears as if the retry logic is at the overall message level, but when a long message is sent as multiple messages using concatenation, there is no suitable retry logic for the individual pieces.
It seems that a sensible way of handling concatenation might be to break the message into pieces and put each piece of the message into the queue. That way it will 1. Reuse the existing retry logic 2. Ensure that at least most of the message will get delivered even if a piece fails 3. Ensure that the recipient doesn't get multiple versions of the overall message (which we saw a couple times) In the meantime we've fallen back to doing manual concatenation from our application. Sorry, we don't have the time to try and improve this part of the code. But if someone comes forth with a fix, we'd happily try it again. Julian Paas Liketribe.com On 10/11/07 10:30 AM, "Julian Paas" <[EMAIL PROTECTED]> wrote: > I also am having this problem as it seems several others on the users list are > since February. > > I've applied Andrija Petrovic's patch for handling resends on "Generic Error" > when sending an SMS which seems to have worked for that problem, but > unfortunately this is a different issue altogether. > > And it's quite a big problem. At least every day our kannel server ends up in > a tight loop trying to send some messages and I have to restart it. I'm > wondering when my SMSC provider is going to cut me off. > > Does anyone has any suggestions or patches? > > Julian Paas > Liketribe.com
