2015-12-08 11:23 GMT+03:00 Grant Vorenberg <gr...@saicomvoice.co.za>:
> [image: Saicom-now-offers-Cloud-PBX] > <https://branding.synaq.com/api/r/id/22469522/map/0> > Here is my config: > > group = sqlbox > id = sqlbox-db > smsbox-id = sqlbox > #global-sender = "" > bearerbox-host = localhost > bearerbox-port = 13001 > smsbox-port = 13005 > smsbox-port-ssl = false > sql-log-table = sent_sms > sql-insert-table = send_sms > log-file = "/var/log/kannel/kannel-sqlbox.log" > log-level = 0 > #sqlbox optimisation GAV 20151207 > limit-per-cycle = 100 > Try monitoring your database workload. Is send_sms table is big? > > On 07 Dec 2015, at 15:06, spameden <spame...@gmail.com> wrote: > > > > > Grant Vorenberg > > Technical Manager > Office 0861 SAICOM (724 266) Direct 010 140 5012 Support 010 140 5050 > Cell - Fax 010 140 5001 Email gr...@saicomvoice.co.za Visit our website > www.saicomvoice.co.za > > [image: logo image] <http://www.saicomvoice.co.za> > > 2015-12-07 14:03 GMT+03:00 Grant Vorenberg <gr...@saicomvoice.co.za>: > >> <saicom-now-offers-cloud-pbx.gif> >> <https://branding.synaq.com/api/r/id/22451334/map/0> >> >> Hi Guys >> >> I am a new to the list subscription and am looking for a little clarity >> on the SQLBOX. >> >> I have a Debian Wheezy box running: >> Kannel sqlbox version 1.4.4 >> Libxml version 2.7.2 >> MySQL 5.5.43 >> >> The front end is custom and drops message into the send_sms table. These >> messages are terminated via smpp to another system of ours. We process and >> clean out the sent_sms table. >> >> I gather stats on the performance of the system using the status page: >> http://localhost:13000/status >> >> I am trying to understand the following output from the screen: >> Box connections: >> smsbox:sqlbox, IP 127.0.0.1 (2532 queued), (on-line 0d 2h 48m 19s) >> > > This means there is a queue on sqlbox. > > Queue works like this: > > First sqlbox gets messages from DB backend, then it adds messages to own > queue, then it sends message into bearerbox queue and bearerbox splits this > queue over your connected SMSC/upstream operators. > > So if there is a huge queue on sqlbox it means there is a big amount of > MTs in your send_sms table and sqlbox is still submitting those to > bearerbox. > > To optimize sqlbox I'd recommend adding this parameter into sqlbox section > (after group = sqlbox): > limit-per-cycle = 50 this means sqlbox will get 50 bulk messages from DB > per query at once instead of 1. > > > >> >> What I noticed is when our send speeds start dipping on the smpp >> connection (internal/default route), this smsbox:sql queue starts building >> up. >> >> When the smsbox:sqlbox queue starts building up like this: >> 1)What causes this? >> 2) What does this signify? >> >> We generally don’t see this behaviour very often, but its effect is >> detrimental to the performance of the system so I would like to know what >> causes the growth and how to combat it so our send speed is safe-guarded. >> >> >> Here is an excerpt from my config files: >> >> <smsbox conf>: >> group = sqlbox >> id = sqlbox-db >> smsbox-id = sqlbox >> #global-sender = "" >> bearerbox-host = localhost >> bearerbox-port = 13001 >> smsbox-port = 13005 >> smsbox-port-ssl = false >> sql-log-table = sent_sms >> sql-insert-table = send_sms >> >> >> <kannel.conf>: >> group = smsbox >> bearerbox-host = 127.0.0.1 >> sendsms-port = 13013 >> global-sender = 13013 >> smsbox-id=my_smsbox >> >> group=smsbox-route >> smsbox-id=sqlbox >> smsc-id=internal >> >> >> Regards >> >> >> >> >> >> Grant Vorenberg >> >> Technical Manager >> Office 0861 SAICOM (724 266) Direct 010 140 5012 Support 010 140 >> 5050 Cell - Fax 010 140 5001 Email gr...@saicomvoice.co.za Visit >> our website www.saicomvoice.co.za >> >> <logo-image.png> <http://www.saicomvoice.co.za/> >> > >
