RE: outgoing queue limit in bearbox

Thanks Amin for your suggestion...
Can we run multiple kannel instances on the same box?Amin Mukhaimer <[email protected]> wrote:I had a somewhat similar problem is that it tends to get slow when sending high amounts of SMSs to specific SMSC, and SMSs sent to other SMSCs are delayed for a while, so I decided to run multiple Kannels, one for each operator, hopping that would increase overall performance.
 
I don’t know if that helps, but good luck.
 
From: [email protected] [mailto:[email protected]] On Behalf Of Nick Mahilani
Sent: Wednesday, November 21, 2012 1:16 AM
To: [email protected]
Subject: outgoing queue limit in bearbox
 
Hi,
I have an application which is using Kannel to send outgoing sms via multiple SMSC's. However, there is an insane volume of messages that needs to go through one of the SMSC which is impacting the other binds due to the global outgoing queue limit check in the code.
 
 if (max_outgoing_sms_qlength > 0 && !resend &&
01091          queue_length > gwlist_len(smsc_list) * max_outgoing_sms_qlength) {
01092         gw_rwlock_unlock(&smsc_list_lock);
01093         debug("bb.sms", 0, "sum(#queues) limit");
01094         return SMSCCONN_FAILED_QFULL;
01095     }
I am very new to the kannel codebase so wanted to get some input on how complicated is the fix to isolate the queue limits to each bind/SMSC. I would like the other binds to not get affected by high volume of traffic on one of the binds. So if one smsc queue is backed up, it does not impact the messages sent to other SMSC's.
Also, what is recommended outgoing queue limit value in terms of messages per second being sent through Kannel?
 
thanks,
Nick