Normally the throughput numbers I configure with real SMScs are in the range
20-30 SMS/s. 400 sounds too much.
BR,
Nikos
----- Original Message -----
From: "Sanjay Bhandari" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, August 25, 2010 6:03 AM
Subject: Re: Kannel throughput against a real SMSC
They are telling is the cap is per bind, so that would be per
connection (client).
And yes, we are going to look into network issues. What kind of numbers
have you seen (working against a real SMSC)?
On 8/24/2010 11:00 PM, sangprabv wrote:
400SMS/sec for each connection (client) or for all connections (clients)?
Network issue might be also need to be checked.
sangprabv
[email protected]
http://www.petitiononline.com/froyo/
On Aug 25, 2010, at 9:32 AM, Sanjay Bhandari wrote:
Anyone here have experience working against a real commercial SMSC?
We got decent numbers working against fakesmsc (~1700 SMS/sec
sustained), but get really atrocious throughput against a real SMSC (~30
SMS/sec sustained). The provider is telling us that they cap the rate at
400 SMS/sec per bind. But we are not even close. Next step is for us to
dig into the Kannel-SMSC interface and see what's going on.
I wanted to reach out to folks who have done this before, to ask what
the typical experience was, just so we can focus on the right areas in
trying to debug the issue(s). Thanks for any input.
