Daniel, There are many issues in the ESME <-> SMSC dynamic to account.
In first place, SMSC's usually pose a restriction in the max throughput they can accept. If you send more than the accepted maximum the SMSC will deny the messages, resulting in a resending and obviously in a preformance penalty. Check the logs and adjust the max_throughput parameter if neccesary. Furthermore, Kannel could be configured to keep open a finite number of threads. It defaults to 10, you can rise (or lower) that number to try to increase throughput. Check "max_pending_submits". If all that's not enough, you can try establishing more than on SMSC connection, maybe use some exclusively for MT queueing. We did that in the past to overcome a limitation on the SMSC side (max msg/sec on the SMSC). You'll need the SMSC to create extra connections of course. I'd recommend you to check with the SMSC operator about the optimal parameters to maximize performance. Hope it helps, Alejandro On 8/4/07, Daniel Eriksson <[EMAIL PROTECTED]> wrote: > Hello, > > How do I speed up the transmission of MT:s to an SMSC? > > As part of a stress test, that an operator imposes on us, we need to send > MT responses to 10000 MO:s that the SMSC sends us, and we need to send on > avarage 50 MT:s per second to pass the test. > > Using Kannel, I am only able to respond at a rate of 14 MT:s per second. > It seems that Kannel queues most of the MTs and sends them after the SMSC > has finished sending us MO:s. > > I suspect that Kannel is slowed down due to the way the SMSC receiver is > set up. The receiver is "synchronous", which I think means that the SMSC > blocks after sending each MO deliver_sm request until Kannel has sent a > deliver_sm_resp response (or until an uspecified timeout is reached). > > I describe my setup in detail below. > > Regards, > > Daniel > > > I have set up one core group like this: > > ----------- > group = core > admin-port = 13000 > smsbox-port = 13001 > admin-password = **** > admin-allow-ip = "127.0.0.1" > log-file = "/var/log/kannel/kannel-bearerbox.log" > log-level = 2 > box-deny-ip = "*.*.*.*" > box-allow-ip = "127.0.0.1" > access-log = "/var/log/kannel/kannel-bearerbox-access.log" > ------------ > > One SMSC connection like this: > > ------------ > group = smsc > smsc = smpp > smsc-id = anoperator > host = ***.***.***.*** > port = 8190 > receive-port = 8190 > smsc-username = "username" > smsc-password = ******* > system-type = "APPSRV" > source-addr-ton = 7 > source-addr-npi = 62 > dest-addr-ton = 1 > dest-addr-npi = 1 > enquire-link-interval = 40 > log-level = 2 > ------------ > > An SMS box like this: > > ------------ > group = smsbox > bearerbox-host = 127.0.0.1 > sendsms-port = 13013 > log-file = "/var/log/kannel/kannel-smsbox.log" > log-level = 2 > access-log = "/var/log/kannel/kannel-smsbox-access.log" > -------------- > > And one SMS service like this: > > ------------ > group = sms-service > keyword = default > text = "Thanks!" > ------------ > > Kannel version information: > > Kannel bearerbox version `1.4.1'. > Build `Aug 2 2007 15:14:07', compiler `4.1.1 20070105 (Red Hat 4.1.1-51)'. > System Linux, release 2.6.20-1.2944.fc6, version #1 SMP Tue Apr 10 > 17:27:49 EDT 2007, machine i686. > Hostname *****, IP 127.0.0.1. > Libxml version 2.6.29. > Using OpenSSL 0.9.8b 04 May 2006. > Using native malloc. > > > > -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
