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?
--
Stuart Beck
Cyrus Patel wrote:
Hi Stuart,
I've upgraded to Kannel 1.4.1 and unfortunately it appears to be the same
behaviour.
I've put the log level to debug and when in suspended mode I can see the
deliver_sm PDUs containing my messages but they just seem to silently
disappear and don't show up in the access.log.
Am I correct in understanding that your kannel doesn't do this i.e. it
properly stores the SMSs on the SMSC?
This is my new Kannel version information - I wonder if I'm missing
something?
Kannel bearerbox version `1.4.1'.
Build `Mar 27 2007 14:18:25', compiler `3.4.4 20050721 (Red Hat 3.4.4-2)'.
System Linux, release 2.6.9-22.EL, version #1 Mon Sep 19 18:20:28 EDT 2005,
machine i686.
Hostname bentley.Seeker.local, IP 192.168.100.4.
Libxml version 2.6.16.
Using OpenSSL 0.9.7a Feb 19 2003.
Using native malloc.
Thanks,
Cyrus
-----Original Message-----
From: Cyrus Patel [mailto:[EMAIL PROTECTED]
Sent: 27 March 2007 14:15
To: 'Stuart Beck'
Cc: [email protected]
Subject: RE: Kannel "suspended" mode behaviour
Hi Stuart,
Thanks - that's good news. I'm using Kannel 1.4.0 - I'll upgrade to 1.4.1
and give it a go.
Cheers,
Cyrus
-----Original Message-----
From: Stuart Beck [mailto:[EMAIL PROTECTED]
Sent: 27 March 2007 13:39
Cc: [email protected]
Subject: Re: Kannel "suspended" mode behaviour
Hi Cyrus,
We found this same bahaviour in earlier versions, I am not sure if it is
intended or not, however it is internal kannel behaviour and not
the SMSC throwing your messages away.
It would be worth knowing the version of kannel that you are using as it
would help to determine if there have already been updates for this
issue, we are using kannel from cvs-20060727 patched up to 1.4.1 - we have
not checked to see if this issue still exists in 1.4.1.
