Hi, I'm working on SMS Gateway using Kannel 1.4.3 between our application servers and an SMSC. We have developed a application that sends HTTP GET requests to our internal Kannel proxy.
*"http://127.0.0.1:13013/cgi-bin/sendsms?username=tester&password=tester&to=99999123456&text=hello&to=12345 <http://127.0.0.1:13013/cgi-bin/sendsms?username=tester&password=tester&to=99999123456&text=hello&to=12345>"* ======================================================================================================================================== *The kannel status shown below:* Kannel bearerbox version `1.4.3'. Build `Jun 21 2014 20:01:15', compiler `4.8.3'. System CYGWIN_NT-6.1, release 1.7.30(0.272/5/3), version 2014-05-23 10:36, machine i686. Hostname Patidar.it.bulk24sms.net, IP 192.168.1.2. Libxml version 2.9.1. Using OpenSSL 1.0.1h 5 Jun 2014. Using native malloc. Status: running, uptime 0d 0h 24m 18s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 20000 (0 queued), store size -1 SMS: inbound (0.00,0.00,0.00) msg/sec, outbound (70.45,28.14,13.72) msg/sec DLR: 0 queued, using internal storage Box connections: wapbox, IP 127.0.0.1 (on-line 0d 0h 24m 13s) smsbox:mysmsbox, IP 127.0.0.1 (0 queued), (on-line 0d 0h 24m 7s) SMSC connections: *mysmsc* SMPP:127.0.0.1:1111/1111:test:vma (online 1458s, rcvd 0, sent 20000, failed 0, queued 0 msgs) ======================================================================================================================================== The problem is that how to measure actual push rate of kannel for sending sms to particular SMSC. Are there any limitations on the HTTP side of the gateway? Shouldn't Kannel accept requests at max speed, queue them and then deliver to the SMSC according to the accept rate of the SMSC itself? I've read through the documentation multiple times but I couldn't find any solutions yet. Thanks a lot for your support! *Thanks & Regards,* *Fakirchand Patidar*
