Hi Cyrus,
I would suggest instead something like what we do here if this can be applied
to your situation....
Our kannel is configured to send through to an http application that simply
replies with an empty message back to kannel
It also has the 'omit-empty = true' flag set to not send empty messages
So the message is processed by kannel and not waiting for a reply to send back.
Once the application has completed processing the request it 'pushes' the
desired responce back to kannel via http.
--
Stuart Beck
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: [email protected]
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?
