Hi Stuart, there is issue on SMSC you connected to. Kannel in suspended mode sends SMPP_ESME_RX_T_APPN (temporarely NACK) to SMSC and it should retry later. Here could be two possibilities why it doesn't work: 1) bug in SMSC because it doesn't retry 2) all your MOs marked as single shot. So the SMSC just try once and doesn't retry.
You should contact your SMSC operator and ask what's going on. If it's not possible to change SMSC's behaviour you must switch to asyncron message processing as already suggested on this list. Cyrus Patel wrote: > > Hi Stuart, > > Thanks for this. I'm reading the kannel source code now and don't > understand why it is still receiving messages when it in the suspended > state. > > We need to throttle like this because our application takes a variable > amount of time to handle SMSs (depending on the message type in the SMS). > So we require a sophisticated method of "pushing back" on messages. > > For example, some types of incoming SMSs only take 100ms to process - > others might take up to 1sec. So we cannot use a flat throttling rate like > 5 SMSs/sec. > > Cheers, > Cyrus > > -----Original Message----- > From: Stuart Beck [mailto:[EMAIL PROTECTED] > Sent: 27 March 2007 15:20 > To: Cyrus Patel > Cc: users@kannel.org > Subject: Re: Kannel "suspended" mode behaviour > > Hi Cyrus, > > Our kannel will still be exhibiting this behaviour, we had not verified if > this was still occurring when we upgraded to this version as we > already had a policy of a full restart rather than an individual smsc > restart (due to this problem) > > What is the reason why you want to use this method to perform throttling? > -- Thanks, Alex
