Re: Delivery Report Issues
Hello To All, When I'm sending messages on multiple numbers, then I'm not getting all delivery reports. *This is my kannel monitor log:* Kannel bearerbox version `1.4.4'. Build `Feb 20 2015 13:58:20', compiler `4.4.7 20120313 (Red Hat 4.4.7-11)'. System Linux, release 2.6.32-042stab094.7, version #1 SMP Wed Oct 22 12:43:21 MSK 2014, machine x86_64. Hostname 192-168-1-101, IP 192.168.1.101. Libxml version 2.7.6. Using OpenSSL 1.0.1e-fips 11 Feb 2013. Compiled with MySQL 5.6.22, using MySQL 5.6.23. Using native malloc. Status: running, uptime 2d 0h 57m 5s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 64 (0 queued), store size -1 SMS: inbound (0.00,0.00,0.00) msg/sec, outbound (0.24,0.03,0.00) msg/sec DLR: received 105, sent 0 DLR: inbound (0.33,0.04,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec DLR: 29 queued, using mysql storage Box connections: smsbox:smsbox1, IP 127.0.0.1 (0 queued), (on-line 2d 0h 56m 34s) smsbox:sqlbox1, IP 127.0.0.1 (0 queued), (on-line 2d 0h 55m 56s) SMSC connections: *TR_SMSC1*[TR_SMSC1]SMPP:10.10.10.10:5775/5775::VMA (online 176224s, rcvd: sms 0 (0.00,0.00,0.00) / dlr 87 (0.33,0.04,0.00), sent: sms 58 (0.24,0.03,0.00) / dlr 0 (0.00,0.00,0.00), failed 0, queued 0 msgs) *PR_SMSC1*[PR_SMSC1]SMPP:10.10.10.10:5776/5776::VMA (online 176224s, rcvd: sms 0 (0.00,0.00,0.00) / dlr 11 (0.00,0.00,0.00), sent: sms 5 (0.00,0.00,0.00) / dlr 0 (0.00,0.00,0.00), failed 1, queued 0 msgs) This log shows me *DLR: 29 queued, using mysql storage. *Can you describe me what is the mean of that? I'm not getting any type error in my log and access files. So please suggest me that this problem is from my side or Operator side. Thanks Ammar Ali On Wed, Apr 22, 2015 at 1:34 PM, Ammar Ali ammarali3...@gmail.com wrote: Hello, 4TX and 4RX connections are provided by SMPP provider. Thanks Ammar Ali On Wed, Apr 22, 2015 at 12:51 PM, Tapan Kumar Thapa tapan.thapa2...@gmail.com wrote: Dear Ammar, Configuration seems ok. How many TX and RX or TRX connection is allowed by your smpp provider? Regards Tapan Thapa On Wed, Apr 22, 2015 at 12:46 PM, Ammar Ali ammarali3...@gmail.com wrote: Hello Tapan, This is SMSC configuration for each instances: group = smsc smsc = smpp smsc-id = TR_SMSC1 log-file = /var/log/TR_SMSC1_lOG1.log log-level = 0 host = xxx.xxx.xxx.xxx port = #receive-port= smsc-username = smsc-password = x allowed-smsc-id = TR_SMSC1 preferred-smsc-id = TR_SMSC1 source-addr-ton = 0 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 service-type = CMT system-type = VMA #address-range = ^$ #bind-addr-ton = 0 #bind-addr-npi = 0 enquire-link-interval = 120 reconnect-delay = 0 transceiver-mode = true interface-version = 34 connection-timeout = 0 throughput = 100 reroute-dlr=true Thanks Ammar Ali On Wed, Apr 22, 2015 at 12:39 PM, Ammar Ali ammarali3...@gmail.com wrote: Hello This is my configurations for each instances: *Kannel1* group = core admin-port = 13000 admin-port-ssl=no admin-password = xxx status-password = xxx admin-deny-ip=*.*.*.* admin-allow-ip=*.*.*.* smsbox-interface =127.0.0.1 smsbox-port = 13001 log-file = /var/log/kannel1.log log-level = 0 access-log = /var/log/access1.access dlr-storage = mysql sms-incoming-queue-limit = -1 sms-outgoing-queue-limit = 100 smsbox-max-pending = 100 sms-resend-freq = 60 sms-resend-retry = -1 group = smsbox smsbox-id = smsbox1 bearerbox-host = 127.0.0.1 bearerbox-port = 13001 sendsms-port = 13010 log-file = /var/log/smsbox1.log log-level = 0 access-log=/var/log/smsaccess1.access sendsms-chars = 0123456789+ #max-pending-requests = 512 sendsms-url=/cgi-bin/sendsms #global-sender = 123456 #ms-length = 140 #http-request-retry=5 mo-recode='1' *Kannel2* group = core admin-port = 13100 admin-port-ssl=no admin-password = xxx status-password = xxx admin-deny-ip=*.*.*.* admin-allow-ip=*.*.*.* smsbox-interface =127.0.0.2 smsbox-port = 13101 log-file = /var/log/kannel2.log log-level = 0 access-log = /var/log/access2.access dlr-storage = mysql sms-incoming-queue-limit = -1 sms-outgoing-queue-limit = 100 smsbox-max-pending = 100 sms-resend-freq = 60 sms-resend-retry = -1 group = smsbox smsbox-id = smsbox2 bearerbox-host = 127.0.0.2 bearerbox-port = 13101 sendsms-port = 13110 log-file = /var/log/smsbox2.log log-level = 0 access-log=/var/log/smsaccess2.access sendsms-chars = 0123456789+ #max-pending-requests = 512 sendsms-url=/cgi-bin/sendsms #global-sender = 123456 #ms-length = 140 #http-request-retry=5 mo-recode='1' *Kannel3* group = core admin-port = 13200 admin-port-ssl=no admin-password = xxx status-password = xxx admin-deny-ip=*.*.*.* admin-allow-ip=*.*.*.* smsbox-interface =127.0.0.3 smsbox-port = 13201 log-file = /var/log/kannel3.log log-level = 0 access-log =
Re: Delivery Report Issues
Hi, As far as i know, this line DLR: 29 queued, using mysql storage says, that we have sent 29 messages and waiting for their delivery report. As soon as we get delivery report from upstream smsc, this number will come down. Thanks Regards Tapan Thapa On Fri, Apr 24, 2015 at 3:51 PM, Ammar Ali ammarali3...@gmail.com wrote: Hello To All, When I'm sending messages on multiple numbers, then I'm not getting all delivery reports. *This is my kannel monitor log:* Kannel bearerbox version `1.4.4'. Build `Feb 20 2015 13:58:20', compiler `4.4.7 20120313 (Red Hat 4.4.7-11)'. System Linux, release 2.6.32-042stab094.7, version #1 SMP Wed Oct 22 12:43:21 MSK 2014, machine x86_64. Hostname 192-168-1-101, IP 192.168.1.101. Libxml version 2.7.6. Using OpenSSL 1.0.1e-fips 11 Feb 2013. Compiled with MySQL 5.6.22, using MySQL 5.6.23. Using native malloc. Status: running, uptime 2d 0h 57m 5s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 64 (0 queued), store size -1 SMS: inbound (0.00,0.00,0.00) msg/sec, outbound (0.24,0.03,0.00) msg/sec DLR: received 105, sent 0 DLR: inbound (0.33,0.04,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec DLR: 29 queued, using mysql storage Box connections: smsbox:smsbox1, IP 127.0.0.1 (0 queued), (on-line 2d 0h 56m 34s) smsbox:sqlbox1, IP 127.0.0.1 (0 queued), (on-line 2d 0h 55m 56s) SMSC connections: *TR_SMSC1*[TR_SMSC1]SMPP:10.10.10.10:5775/5775::VMA (online 176224s, rcvd: sms 0 (0.00,0.00,0.00) / dlr 87 (0.33,0.04,0.00), sent: sms 58 (0.24,0.03,0.00) / dlr 0 (0.00,0.00,0.00), failed 0, queued 0 msgs) *PR_SMSC1*[PR_SMSC1]SMPP:10.10.10.10:5776/5776::VMA (online 176224s, rcvd: sms 0 (0.00,0.00,0.00) / dlr 11 (0.00,0.00,0.00), sent: sms 5 (0.00,0.00,0.00) / dlr 0 (0.00,0.00,0.00), failed 1, queued 0 msgs) This log shows me *DLR: 29 queued, using mysql storage. *Can you describe me what is the mean of that? I'm not getting any type error in my log and access files. So please suggest me that this problem is from my side or Operator side. Thanks Ammar Ali On Wed, Apr 22, 2015 at 1:34 PM, Ammar Ali ammarali3...@gmail.com wrote: Hello, 4TX and 4RX connections are provided by SMPP provider. Thanks Ammar Ali On Wed, Apr 22, 2015 at 12:51 PM, Tapan Kumar Thapa tapan.thapa2...@gmail.com wrote: Dear Ammar, Configuration seems ok. How many TX and RX or TRX connection is allowed by your smpp provider? Regards Tapan Thapa On Wed, Apr 22, 2015 at 12:46 PM, Ammar Ali ammarali3...@gmail.com wrote: Hello Tapan, This is SMSC configuration for each instances: group = smsc smsc = smpp smsc-id = TR_SMSC1 log-file = /var/log/TR_SMSC1_lOG1.log log-level = 0 host = xxx.xxx.xxx.xxx port = #receive-port= smsc-username = smsc-password = x allowed-smsc-id = TR_SMSC1 preferred-smsc-id = TR_SMSC1 source-addr-ton = 0 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 service-type = CMT system-type = VMA #address-range = ^$ #bind-addr-ton = 0 #bind-addr-npi = 0 enquire-link-interval = 120 reconnect-delay = 0 transceiver-mode = true interface-version = 34 connection-timeout = 0 throughput = 100 reroute-dlr=true Thanks Ammar Ali On Wed, Apr 22, 2015 at 12:39 PM, Ammar Ali ammarali3...@gmail.com wrote: Hello This is my configurations for each instances: *Kannel1* group = core admin-port = 13000 admin-port-ssl=no admin-password = xxx status-password = xxx admin-deny-ip=*.*.*.* admin-allow-ip=*.*.*.* smsbox-interface =127.0.0.1 smsbox-port = 13001 log-file = /var/log/kannel1.log log-level = 0 access-log = /var/log/access1.access dlr-storage = mysql sms-incoming-queue-limit = -1 sms-outgoing-queue-limit = 100 smsbox-max-pending = 100 sms-resend-freq = 60 sms-resend-retry = -1 group = smsbox smsbox-id = smsbox1 bearerbox-host = 127.0.0.1 bearerbox-port = 13001 sendsms-port = 13010 log-file = /var/log/smsbox1.log log-level = 0 access-log=/var/log/smsaccess1.access sendsms-chars = 0123456789+ #max-pending-requests = 512 sendsms-url=/cgi-bin/sendsms #global-sender = 123456 #ms-length = 140 #http-request-retry=5 mo-recode='1' *Kannel2* group = core admin-port = 13100 admin-port-ssl=no admin-password = xxx status-password = xxx admin-deny-ip=*.*.*.* admin-allow-ip=*.*.*.* smsbox-interface =127.0.0.2 smsbox-port = 13101 log-file = /var/log/kannel2.log log-level = 0 access-log = /var/log/access2.access dlr-storage = mysql sms-incoming-queue-limit = -1 sms-outgoing-queue-limit = 100 smsbox-max-pending = 100 sms-resend-freq = 60 sms-resend-retry = -1 group = smsbox smsbox-id = smsbox2 bearerbox-host = 127.0.0.2 bearerbox-port = 13101 sendsms-port = 13110 log-file = /var/log/smsbox2.log log-level = 0 access-log=/var/log/smsaccess2.access sendsms-chars = 0123456789+ #max-pending-requests = 512 sendsms-url=/cgi-bin/sendsms
Re: Fastest method to insert a million MT messages to Kannel
I have worked with bothBut SQLBox was slower for me.If MySQL, MyISAM uses to crash whe to much operation or a hardware failure.InnoDB is safest but slower . Http post was my solution.But What application is handling the requests and the way it does, matters a lot.As light as possible the application that does the post, that will do a great difference. .NET and Java are to much heavy dutty machines for Bulk. Hope it helps, G. Daniel Camacho ECE # 203135336 Tel. +502 - 56305599 On Friday, April 24, 2015 2:27 PM, ha...@aeon.pk ha...@aeon.pk wrote: SQLBOX is way faster for bulk traffic. On Fri, Apr 24, 2015 at 1:48 AM, Rene Kluwen rene.klu...@chimit.nl wrote: Unless your database is on another server.Sqlbox keeps a tcp connection open to bearerbox.If you use smsbox, you need to connect each time you send an sms.I don’t have hard figures though. It will be interesting to know them. From: users [mailto:users-boun...@kannel.org] On Behalf Of Tapan Kumar Thapa Sent: woensdag 22 april 2015 7:43 To: Alberto Mijares Cc: kannel users@kannel.org Subject: Re: Fastest method to insert a million MT messages to Kannel Also while sqlbox is doing its operations with DB like select from send_sms,submit to bearerbox and than inserting the same to sent_sms table and doing delete from send_sms, it will add some time lag and will put load on server too. On Wed, Apr 22, 2015 at 11:10 AM, Tapan Kumar Thapa tapan.thapa2...@gmail.com wrote:My 2 cents: Adding messages to send_sms table is not an issue. We can add messages to send_sms table very quickly however once sqlbox is submitting those messages to bearerbox, and if beaerebox is unable to submit the same to upstream smsc at desired speed (because upstream smsc is not taking messages at provided speed, (Many factor involves here like hardware capacity, internet bandwidth)) then we will have huge queue at beaerebox level, which actually slow down the overall performance of kannel. On Wed, Apr 22, 2015 at 11:00 AM, Alberto Mijares amijar...@gmail.com wrote:I'd say: with the propper DB and DBI (PostgrSQL + Perl DBI, ie), using PREPARE and COMMIT, SQLBox is your best bet by far. Regards, Alberto Mijares On Wed, Apr 22, 2015 at 12:50 AM, Makhanu Sinja jeysi...@gmail.com wrote: Well last week The same issue was raised on another thread in this mailing list. Let us consider the amount of time sqlbox has to do database CRUD for 1M messages compared to using spool or files. Is there anyone who has worked with both? On 4/21/15, Rene Kluwen rene.klu...@chimit.nl wrote: 1. I think Kannel does support Keep-Alive connections. Not sure about the server side, but I think it does. Just make sure your client also supports it. 2. Yes, probably SQL Box does insert 1,000,000 a lot faster than you can do by http. Question is if your upstream providers handle such a rate. You will end up with a lot of pending messages in the bearerbox queue. == Rene -Original Message- From: users [mailto:users-boun...@kannel.org] On Behalf Of Cliff Court Sent: dinsdag 21 april 2015 10:11 To: users@kannel.org Subject: Fastest method to insert a million MT messages to Kannel Hi All I have set up Kannel with bearerbox and smsbox, which is working and I am writing dlr's to a mysql db. Currently I am submitting messages using a sendsms GET or xml-based POST, as per the Kannel documentation. However, using individual http GET or POSTs for each message is relatively slow when needing to send a large volume of messages. Let's assume I have a 100 msgs/sec connection to an external SMSC using SMPP from bearerbox, which will take ~3 hours to send 1 million MT messages. So my question is what is the fastest method to submit messages to bearerbox to send a million MT messages? I have seen that SQLbox is available and that one can insert messages into the send_sms table for faster submission, but I'm wondering what is the fastest method of submission to bearerbox? Thanks Cliff
Re: I/O error or other error. Re-connecting
Connection to SMSC is fluctuating. Check your VPN logs. On Fri, Mar 27, 2015 at 11:50 AM, Ammar Ali ammarali3...@gmail.com wrote: Hello Everyone, I am getting this error when I'm connecting live SMSC connections with my kannel. *I/O error or other error. Re-connecting.* This is the log: 2015-03-27 11:56:53 [5] [6] DEBUG: Connecting to ***.***.***. 2015-03-27 11:56:53 [5] [6] DEBUG: SMPP[smsc1]: Sending PDU: 2015-03-27 11:56:53 [5] [6] DEBUG: SMPP PDU 0x7fa1ea10 dump: 2015-03-27 11:56:53 [5] [6] DEBUG: type_name: bind_transceiver 2015-03-27 11:56:53 [5] [6] DEBUG: command_id: 9 = 0x0009 2015-03-27 11:56:53 [5] [6] DEBUG: command_status: 0 = 0x 2015-03-27 11:56:53 [5] [6] DEBUG: sequence_number: 1 = 0x0001 2015-03-27 11:56:53 [5] [6] DEBUG: system_id: *** 2015-03-27 11:56:53 [5] [6] DEBUG: password: *** 2015-03-27 11:56:53 [5] [6] DEBUG: system_type: VMA 2015-03-27 11:56:53 [5] [6] DEBUG: interface_version: 52 = 0x0034 2015-03-27 11:56:53 [5] [6] DEBUG: addr_ton: 0 = 0x 2015-03-27 11:56:53 [5] [6] DEBUG: addr_npi: 0 = 0x 2015-03-27 11:56:53 [5] [6] DEBUG: address_range: ^$ 2015-03-27 11:56:53 [5] [6] DEBUG: SMPP PDU dump ends. 2015-03-27 11:56:54 [5] [6] DEBUG: SMPP[smsc1]: Got PDU: 2015-03-27 11:56:54 [5] [6] DEBUG: SMPP PDU 0x7fa1ea10 dump: 2015-03-27 11:56:54 [5] [6] DEBUG: type_name: bind_transceiver_resp 2015-03-27 11:56:54 [5] [6] DEBUG: command_id: 2147483657 = 0x8009 2015-03-27 11:56:54 [5] [6] DEBUG: command_status: 0 = 0x 2015-03-27 11:56:54 [5] [6] DEBUG: sequence_number: 1 = 0x0001 2015-03-27 11:56:54 [5] [6] DEBUG: system_id: BULKTRANS 2015-03-27 11:56:54 [5] [6] DEBUG: SMPP PDU dump ends. 2015-03-27 11:56:54 [5] [6] DEBUG: SMPP[smsc1]: throughput (0.00,1000.00) 2015-03-27 12:02:00 [5] [6] DEBUG: SMPP[smsc1]: throughput (0.00,1000.00) 2015-03-27 12:02:00 [5] [6] ERROR: SMPP[smsc1]: I/O error or other error. Re-connecting. 2015-03-27 12:02:00 [5] [6] ERROR: SMPP[smsc1]: Couldn't connect to SMS center (retrying in 0 seconds). And this is my Kannel configuration: #- # THIS IS A CONFIGURATION FOR KANNEL #- # Single Group CORE #- group = core admin-port = 15000 admin-port-ssl=no admin-password = ** status-password = ** admin-deny-ip=*.*.*.* admin-allow-ip=*.*.*.* smsbox-interface =127.0.0.1 smsbox-port = 15001 #smsbox-port-ssl=no log-file = mykannel.log log-level = 0 access-log = myaccess.access dlr-storage = internal sms-incoming-queue-limit = -1 sms-outgoing-queue-limit = 100 smsbox-max-pending = 100 sms-resend-freq = 60 sms-resend-retry = -1 #- # Single Group smsbox #- group = smsbox smsbox-id = smsbox bearerbox-host = 127.0.0.1 bearerbox-port = 15001 sendsms-port = 15010 log-file = mysmsbox1.log log-level = 0 access-log=smsaccess1.access sendsms-chars = 0123456789+ #max-pending-requests = 512 #sendsms-url=/cgi-bin/sendsms #global-sender = 123456 #ms-length = 140 #http-request-retry=5 mo-recode='1' #- # Multi Group SMSC #- group = smsc smsc = smpp smsc-id = smsc1 log-file = mysmsc1.log log-level = 0 host = ***.***.***.*** port = * #receive-port=2776 smsc-username = *** smsc-password = ** denied-smsc-id = smsc2 allowed-smsc-id = smsc1 preferred-smsc-id = smsc1 source-addr-ton = 0 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 service-type = CMT validityperiod = 600 system-type = VMA alt-charset=us-ascii #alt-charset = ASCII;windows-1252;UTF-8;ISO-8859-1;ISO-8859-7;GSM;UTF-16BE #alt-addr-charset = GSM address-range = ^$ bind-addr-ton = 0 bind-addr-npi = 0 enquire-link-interval = 20 reconnect-delay = 0 transceiver-mode = true interface-version = 34 connection-timeout = 0 throughput = 1000.00 max-pending-submits=10 #reroute=true #reroute-smsc-id=smsc1 reroute-dlr=true #--- group = smsc smsc = smpp smsc-id = smsc2 log-file = mysmsc2.log log-level = 0 host = ***.***.***.*** port = #receive-port=2776 smsc-username = * smsc-password = * denied-smsc-id = smsc1 allowed-smsc-id = smsc2 preferred-smsc-id = smsc2 source-addr-ton = 0 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 service-type = CMT validityperiod = 600 system-type = VMA alt-charset=us-ascii #alt-charset = ASCII;windows-1252;UTF-8;ISO-8859-1;ISO-8859-7;GSM;UTF-16BE #alt-addr-charset = GSM address-range = ^$ bind-addr-ton = 0
Re: Delivery Report Issue
Take tcpdump on front end and analyze SMPP trace. On Mon, Apr 20, 2015 at 12:50 PM, Ammar Ali ammarali3...@gmail.com wrote: Hello, I'm facing a very serious issue when I'm sending message. When I sent a sms from my application to kannel, kannel route this request to particular connected SMPP. Then I'm getting a response (submit_sm_resp) from particular SMPP. *This is my access log file:* 2015-04-20 13:04:20 Sent SMS [SMSC:newtsmsc] [SVC:] [ACT:] [BINF:] [FID:a1d07258-79bd-44d9-adf1-968f596ce1f3] [META:?smpp_resp?] [from:INSIGN] [to:9039238251] [flags:-1:0:-1:-1:63] [msg:12:Hello] [udh:0:] 2015-04-20 13:04:20 Receive DLR [SMSC:newtsmsc] [SVC:] [ACT:] [BINF:] [FID:a1d07258-79bd-44d9-adf1-968f596ce1f3] [META:?smpp_resp?] [from:INSIGN] [to:9039238251] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [udh:0:] But I'm not getting delivery report for this message. *This is my SMPP log:* 2015-04-20 13:04:19 [16851] [9] DEBUG: SMPP[newtsmsc]: throughput (0.00,100.00) 2015-04-20 13:04:19 [16851] [9] DEBUG: SMPP[newtsmsc]: Manually forced source addr ton = 0, source add npi = 1 2015-04-20 13:04:19 [16851] [9] DEBUG: SMPP[newtsmsc]: Manually forced dest addr ton = 1, dest add npi = 1 2015-04-20 13:04:19 [16851] [9] DEBUG: SMPP[newtsmsc]: Sending PDU: 2015-04-20 13:04:19 [16851] [9] DEBUG: SMPP PDU 0x7fae44007b10 dump: 2015-04-20 13:04:19 [16851] [9] DEBUG: type_name: submit_sm 2015-04-20 13:04:19 [16851] [9] DEBUG: command_id: 4 = 0x0004 2015-04-20 13:04:19 [16851] [9] DEBUG: command_status: 0 = 0x 2015-04-20 13:04:19 [16851] [9] DEBUG: sequence_number: 1313 = 0x0521 2015-04-20 13:04:19 [16851] [9] DEBUG: service_type: CMT 2015-04-20 13:04:19 [16851] [9] DEBUG: source_addr_ton: 5 = 0x0005 2015-04-20 13:04:19 [16851] [9] DEBUG: source_addr_npi: 0 = 0x 2015-04-20 13:04:19 [16851] [9] DEBUG: source_addr: INSIGN 2015-04-20 13:04:19 [16851] [9] DEBUG: dest_addr_ton: 1 = 0x0001 2015-04-20 13:04:19 [16851] [9] DEBUG: dest_addr_npi: 1 = 0x0001 2015-04-20 13:04:19 [16851] [9] DEBUG: destination_addr: 9039238251 2015-04-20 13:04:19 [16851] [9] DEBUG: esm_class: 3 = 0x0003 2015-04-20 13:04:19 [16851] [9] DEBUG: protocol_id: 0 = 0x 2015-04-20 13:04:19 [16851] [9] DEBUG: priority_flag: 0 = 0x 2015-04-20 13:04:19 [16851] [9] DEBUG: schedule_delivery_time: NULL 2015-04-20 13:04:19 [16851] [9] DEBUG: validity_period: NULL 2015-04-20 13:04:19 [16851] [9] DEBUG: registered_delivery: 17 = 0x0011 2015-04-20 13:04:19 [16851] [9] DEBUG: replace_if_present_flag: 0 = 0x 2015-04-20 13:04:19 [16851] [9] DEBUG: data_coding: 0 = 0x 2015-04-20 13:04:19 [16851] [9] DEBUG: sm_default_msg_id: 0 = 0x 2015-04-20 13:04:19 [16851] [9] DEBUG: sm_length: 12 = 0x000c 2015-04-20 13:04:19 [16851] [9] DEBUG: short_message: Hello 2015-04-20 13:04:19 [16851] [9] DEBUG: SMPP PDU dump ends. 2015-04-20 13:04:19 [16851] [9] DEBUG: SMPP[newtsmsc]: throughput (1.00,100.00) 2015-04-20 13:04:20 [16851] [9] DEBUG: SMPP[newtsmsc]: throughput (0.00,100.00) 2015-04-20 13:04:20 [16851] [9] DEBUG: SMPP[newtsmsc]: Got PDU: 2015-04-20 13:04:20 [16851] [9] DEBUG: SMPP PDU 0x7fae44007b10 dump: 2015-04-20 13:04:20 [16851] [9] DEBUG: type_name: submit_sm_resp 2015-04-20 13:04:20 [16851] [9] DEBUG: command_id: 2147483652 = 0x8004 2015-04-20 13:04:20 [16851] [9] DEBUG: command_status: 0 = 0x 2015-04-20 13:04:20 [16851] [9] DEBUG: sequence_number: 1313 = 0x0521 2015-04-20 13:04:20 [16851] [9] DEBUG: message_id: 2015-04-20 13:04:20 [16851] [9] DEBUG:Octet string at 0x7fae440025a0: 2015-04-20 13:04:20 [16851] [9] DEBUG: len: 36 2015-04-20 13:04:20 [16851] [9] DEBUG: size: 37 2015-04-20 13:04:20 [16851] [9] DEBUG: immutable: 0 2015-04-20 13:04:20 [16851] [9] DEBUG: data: 61 31 64 30 37 32 35 38 2d 37 39 62 64 2d 34 34 a1d07258-79bd-44 2015-04-20 13:04:20 [16851] [9] DEBUG: data: 64 39 2d 61 64 66 31 2d 39 36 38 66 35 39 36 63 d9-adf1-968f596c 2015-04-20 13:04:20 [16851] [9] DEBUG: data: 65 31 66 33 e1f3 2015-04-20 13:04:20 [16851] [9] DEBUG:Octet string dump ends. 2015-04-20 13:04:20 [16851] [9] DEBUG: SMPP PDU dump ends. 2015-04-20 13:04:20 [16851] [9] DEBUG: DLR[internal]: Adding DLR smsc=newtsmsc, ts=a1d07258-79bd-44d9-adf1-968f596ce1f3, src=INSIGN, dst=9039238251, mask=63, boxc=sqlbox 2015-04-20 13:04:20 [16851] [9] DEBUG: SMSC[newtsmsc]: creating DLR message 2015-04-20 13:04:20 [16851] [9] DEBUG: SMSC[newtsmsc]: DLR = 26 2015-04-20 13:04:20 [16851] [9] DEBUG: SMPP[newtsmsc]: throughput (0.00,100.00) But I'm contacting my SMPP provider then they send some logs that are getting on their SMPP server. 2015-04-20 12:22:30.569 *submit_sm* [EC:00x0:SMPPBOX_DB_CDR_MYSQL] [SVC:blk24trn] [ACT:SMPP] [IP:192.169.236.101] [from:INSIGN] [to:+9039238251]
Re: dlr-url information
Write a script which takes input parameters. Set dlr-url to the path of this script. The info can be sent anywhere you want. On Fri, Mar 27, 2015 at 6:36 PM, Nestor Durañona nestor.duran...@unnaki.com.py wrote: Hi I'm new in kannel, and I want to know how can I gather all the information of the delivery report when I send a message from kannel to a cell phone. I want to save that information in a database. Thanks.
Re: Fastest method to insert a million MT messages to Kannel
SQLBOX is way faster for bulk traffic. On Fri, Apr 24, 2015 at 1:48 AM, Rene Kluwen rene.klu...@chimit.nl wrote: Unless your database is on another server. Sqlbox keeps a tcp connection open to bearerbox. If you use smsbox, you need to connect each time you send an sms. I don’t have hard figures though. It will be interesting to know them. *From:* users [mailto:users-boun...@kannel.org] *On Behalf Of *Tapan Kumar Thapa *Sent:* woensdag 22 april 2015 7:43 *To:* Alberto Mijares *Cc:* kannel users@kannel.org *Subject:* Re: Fastest method to insert a million MT messages to Kannel Also while sqlbox is doing its operations with DB like select from send_sms,submit to bearerbox and than inserting the same to sent_sms table and doing delete from send_sms, it will add some time lag and will put load on server too. On Wed, Apr 22, 2015 at 11:10 AM, Tapan Kumar Thapa tapan.thapa2...@gmail.com wrote: My 2 cents: Adding messages to send_sms table is not an issue. We can add messages to send_sms table very quickly however once sqlbox is submitting those messages to bearerbox, and if beaerebox is unable to submit the same to upstream smsc at desired speed (because upstream smsc is not taking messages at provided speed, (Many factor involves here like hardware capacity, internet bandwidth)) then we will have huge queue at beaerebox level, which actually slow down the overall performance of kannel. On Wed, Apr 22, 2015 at 11:00 AM, Alberto Mijares amijar...@gmail.com wrote: I'd say: with the propper DB and DBI (PostgrSQL + Perl DBI, ie), using PREPARE and COMMIT, SQLBox is your best bet by far. Regards, Alberto Mijares On Wed, Apr 22, 2015 at 12:50 AM, Makhanu Sinja jeysi...@gmail.com wrote: Well last week The same issue was raised on another thread in this mailing list. Let us consider the amount of time sqlbox has to do database CRUD for 1M messages compared to using spool or files. Is there anyone who has worked with both? On 4/21/15, Rene Kluwen rene.klu...@chimit.nl wrote: 1. I think Kannel does support Keep-Alive connections. Not sure about the server side, but I think it does. Just make sure your client also supports it. 2. Yes, probably SQL Box does insert 1,000,000 a lot faster than you can do by http. Question is if your upstream providers handle such a rate. You will end up with a lot of pending messages in the bearerbox queue. == Rene -Original Message- From: users [mailto:users-boun...@kannel.org] On Behalf Of Cliff Court Sent: dinsdag 21 april 2015 10:11 To: users@kannel.org Subject: Fastest method to insert a million MT messages to Kannel Hi All I have set up Kannel with bearerbox and smsbox, which is working and I am writing dlr's to a mysql db. Currently I am submitting messages using a sendsms GET or xml-based POST, as per the Kannel documentation. However, using individual http GET or POSTs for each message is relatively slow when needing to send a large volume of messages. Let's assume I have a 100 msgs/sec connection to an external SMSC using SMPP from bearerbox, which will take ~3 hours to send 1 million MT messages. So my question is what is the fastest method to submit messages to bearerbox to send a million MT messages? I have seen that SQLbox is available and that one can insert messages into the send_sms table for faster submission, but I'm wondering what is the fastest method of submission to bearerbox? Thanks Cliff
