Halo,
Thanks for the direction... I overlooked that variable...
So, I just need to put like 65(30+20+15) on throughput paramater on
Kannel-Main, and 30 on Kannel-A, etc?
Somewhere in the list, said that 1.5.0 better in handling throughput
than 1.4.3 svn (svn-4871 is 1.4.3 series right?) is it true so that I
better used 1.5.0 instead?
Thanks for the help
On 11/24/2010 2:24 AM, Nikos Balkanas wrote:
Hi,
On a low-end system, kannel can easily handle ~650 MTs with DLRs, using
internal dlr storage, or ~350 MTs using DB dlr storage. To limit submit
rate, read UG about throughput parmeter.
BR,
Nikos
----- Original Message ----- From: "I Gede Wijaya S" <[email protected]>
To: <[email protected]>
Sent: Tuesday, November 23, 2010 7:31 PM
Subject: Max send messages and queue (SMPP)
Halo again list,
How much max messages can kannel send per seconds?
My vendor give limitation on sending sms/seconds based on some
category. Example:
- category A: 30/secs
- category B: 20/secs
- category C: 15/secs
on "push" sms system, not "MO-MT" system. On MO-MT, there are no limit
we can send the MT/reply.
We can combined category at once on sending (A+B+C) but still, each
category must follow "the rule'. In our old system based on http, we
will launch the sending messages based on rule above. So, there will
be 30 program send each 1 sms on A category, 20 program send each 1
sms on B category, and 15 program send each 1 sms on C category. When
vendor got the problem(can not accept the incoming messages), there
will be no additional program to launch on each category/sms, because
"the old" program is still try to send/resend the earlier smses.
So, I think, only one kannel is not enough. So I have a plan to build
like these:
SMSBOX-A <---> Kannel-A <--> OpenSMMPBox <-----> Kannel-Main
SMSBOX-B <---> Kannel-B <--> OpenSMMPBox <-----> Kannel-Main
SMSBOX-C <---> Kannel-C <--> OpenSMMPBox <-----> Kannel-Main
SMSBOX-MO-MT <---> Kannel Main
For now, only OpenSMPPBoxis on my mind. Maybe there are other type of
proxy? HTTP Proxy?
I build the above based on my understanding on UG. So, could you give
some advice for the build because I'm still not clear on kannel
arsitecture/flow?:
example:
group = core (on Kannel-A)
sms-outgoing-queue-limit = 30 #(and 20 on Kannel B, and 15 on Kannel C)
but I don't understand on "Set maximum size of outgoing message queue.
After number of messages has hit this value, Kannel began to discard
them. The default value, 1 million, works for most installations.".
So, if Kannel-A reach 30 outgoing sms, will be denied.is it right? sms
push codes will give "4xx"? how do Kannel-A should stop on "30"? On my
understanding, all incoming messages on Kannel-A will be delivered and
queued on Kannel-Main. Or I will make "sms-outgoing-queue-limit" as 75
(A+B+C+10 spare on MO-MT) on Kannel-Main?. So when vendor got troubled
and can't accept our sms, the queue will be 75, and what next? Does
sms will discarded(I don't know the meaning discarded here) by
Kannel-Main? Or Kannel-Main will "inform" on Kannel A,B,C that the
limit is queued, and Kannel A and B and C will queued too based on
each rule? So if, for example, Kannel-A reach 30, how could our
program know? Is it with "4xx" on sms push reply codes on each smsbox
(example, 30 on SMSBOX A)?
Thanks in advanced...
