Yes of course, just make different config files for each and run an instance 
for each, like

 

bearerbox  operator1_config

smsbox        operator1_config

 

bearerbox operator2_config

smsbox      operator2_config

 

make sure they have different ports/spool directory/database tables/ log files… 
and good luck

 

Amin

 

From: Nick Mahilani [mailto:[email protected]] 
Sent: Wednesday, November 21, 2012 7:00 PM
To: [email protected]
Cc: [email protected]
Subject: 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 ( <http://doxygen.kannel.org/d5/d27/bb__smscconn_8c.html#a8> 
max_outgoing_sms_qlength > 0 && ! 
<http://doxygen.kannel.org/d6/d9f/wtp__init_8h.html#a33a30> resend &&
01091          queue_length >  
<http://doxygen.kannel.org/da/d23/list_8h.html#a6> gwlist_len(smsc_list) * 
max_outgoing_sms_qlength) {
01092          <http://doxygen.kannel.org/d2/dbd/gw-rwlock_8h.html#a4> 
gw_rwlock_unlock(&smsc_list_lock);
01093          <http://doxygen.kannel.org/d7/d7f/log_8h.html#a14> 
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

Reply via email to