Thanks Enrique this helped.
Best regards Amit Sharma From: Enrique Echeverria [mailto:enriqueocta...@gmail.com] Sent: Wednesday, December 16, 2015 5:55 PM To: amal...@kannel.org Cc: Amit Sharma (VAS); users@kannel.org Subject: Re: Not ACKED message found, will retransmit. Hi Amit: At SMPP level, every time you send and MT you send a submit_sm PDU, that needs to receive back a submit_sm_resp PDU (this would be the ack) from the SMSC. Every time you receive the ACK (submit_sm_resp PDU), that message is "tagged" as sent (and so deleted from kannel queue), and as long as the ACK is not received the message is still tagged as "not sent" (and so still queued). Obviously, there is a timeout for that ACK (submit_sm_resp PDU) to come back, and once the timeout expires the message is queued for retry (and so the "Not ACKED message found, will retransmit." message is logged to the bind level log) Kannel has 2 parameters for controlling this behaviour : wait-ack ->A message is resent if the acknowledge from SMSC takes more than this time. Defaults to 60 seconds. wait-ack-expire -> Defines what kind of action should be taken if the ack of a message expires. The options for this value are: 0x00 - disconnect/reconnect, (default) 0x01 - as is now, re-queue, but this could potentially result in the msg arriving twice 0x02 - just carry on waiting (given that the wait-ack should never expire this is the must accurate) So, the fact that you are seeing the "Not ACKED message found, will retransmit" but the MTs are anyway reaching the handset means that the ACK is arriving from the SMSC when your timeout is already expired. You should capturer traffic, measure the submit_sm_resp arrrival delay, and set your wait-ack parameter accordingly. Using wait-ack-expire would be nastier. Hope this helps, kind regards: enrique On Mon, Dec 14, 2015 at 11:04 AM, <amal...@kannel.org<mailto:amal...@kannel.org>> wrote: Hi, check your logs whether you received ACK/NACK for those sequence numbers and if not ask by SMSC operator why you don’t receive ACK/NACK within > 60 sec. Alex Am 14.12.2015 um 11:33 schrieb Amit Sharma (VAS) <amit.shar...@mtsindia.in<mailto:amit.shar...@mtsindia.in>>: Hi, I am getting following error of “Not ACKED message found, will retransmit” again and again due to which at times a single number receives multiple sms. In below case “9142294005<tel:9142294005>” number received 9 msgs. Please suggest the reason for the below error & rectification to be done accordingly. 2015-12-13 09:36:49 [15072] [18] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:37:55 [15072] [18] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<66>sec. ago, SEQ<187878>, DST<9142294005<tel:9142294005>> 2015-12-13 09:40:16 [15072] [22] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:41:20 [15072] [22] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<64>sec. ago, SEQ<189768>, DST<9142294005<tel:9142294005>> 2015-12-13 09:43:44 [15072] [8] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:46:04 [15072] [10] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:47:06 [15072] [10] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<62>sec. ago, SEQ<189281>, DST<9142294005<tel:9142294005>> 2015-12-13 09:48:10 [15072] [16] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:49:17 [15072] [16] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<67>sec. ago, SEQ<189655>, DST<9142294005<tel:9142294005>> 2015-12-13 09:51:18 [15072] [8] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:52:36 [15072] [8] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<78>sec. ago, SEQ<188844>, DST<9142294005<tel:9142294005>> 2015-12-13 09:53:42 [15072] [20] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:56:09 [15072] [6] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:57:13 [15072] [6] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<64>sec. ago, SEQ<189816>, DST<9142294005<tel:9142294005>> 2015-12-13 09:58:14 [15072] [8] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 09:59:15 [15072] [8] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<61>sec. ago, SEQ<189177>, DST<9142294005<tel:9142294005>> 2015-12-13 10:01:47 [15072] [20] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 10:04:14 [15072] [20] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 10:05:23 [15072] [20] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<69>sec. ago, SEQ<189456>, DST<9142294005<tel:9142294005>> 2015-12-13 10:08:14 [15072] [12] DEBUG: destination_addr: "9142294005<tel:9142294005>" 2015-12-13 10:09:20 [15072] [12] WARNING: SMPP[MTS]: Not ACKED message found, will retransmit. SENT<66>sec. ago, SEQ<190251>, DST<9142294005<tel:9142294005>> Configuration is as follows: group = core admin-port = 13010 smsbox-port = 13012 log-file = "/u03/kannel/logs/bearerbox.log" box-allow-ip = "10.130.252.160,127.0.0.1" access-log = "/u03/kannel/logs/bearerbox_access.log" dlr-storage = internal ##############################TX-1################################## group = smsc smsc-id ="MT" smsc = smpp host =10.10.22.10 port = 5016 system-type = "INAPPS" interface-version = 34 receive-port =0 source-addr-ton = 1 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 keepalive = 30 log-level =0 throughput = 50 max-pending-submits=50 reconnect-delay = 60 reroute = true log-file = "/u03/kannel/logs/smsc_conn.log" ######################RX-1################################ group = smsc smsc-id ="MTS" smsc = smpp host =10.10.22.10 port = 0 system-type = "INAPPS" receive-port =5016 interface-version = 34 source-addr-ton = 1 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 keepalive = 30 log-level =0 reconnect-delay = 60 reroute = true log-file = "/u03/kannel/logs/smsc_conn.log" group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 global-sender = YD-MTS log-file = "/u03/kannel/logs/smsbox.log" log-level = 0 #SMSBOX ROUTING group = smsbox-route smsbox-id = smsbox smsc-id ="MT" group = sendsms-user username = smsg password = smsg@123 default-smsc="MT" concatenation= true max-messages = 6 group = sms-service keyword = default url = http://10.130.250.58/receivesms.php?sender=%p&text=%b<http://10.130.250.58/receivesms.php?sender=%25p&text=%25b> catch-all = true max-messages = 1 text = "This is a reply" Best regards Amit Sharma (VAS) Head, IN & VAS Operations Division IT Shared Service Center, CORPORATE CENTER Sistema Shyam Teleservices Limited MTS Tower2 Building No. 313, Udyog Vihar Phase IV,Gurgaon MTS +91 913 600 6473 Direct +91 124 481 2500<tel:%2B91%20124%20481%202500> Email: amit.shar...@mtsindia.in<mailto:amit.shar...@mtsindia.in> <image001.jpg><http://www.mtsindia.in/> ________________________________ This E-Mail may contain Confidential and/or legally privileged Information and is meant for the intended recipient(s) only. If you have received this e-mail in error and are not the intended recipient/s, Kindly notify the sender and then delete this e-mail immediately from your system. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail, its contents or its attachment/s other than by its intended recipient/s is strictly prohibited and may be unlawful. Internet Communications cannot be guaranteed to be secure or error-free as information could be delayed, intercepted, corrupted, lost, or contain viruses. Sistema Shyam Teleservices Limited does not accept any liability for any errors, omissions, viruses or computer problems experienced by any recipient as a result of this e-mail. ________________________________ This E-Mail may contain Confidential and/or legally privileged Information and is meant for the intended recipient(s) only. If you have received this e-mail in error and are not the intended recipient/s, Kindly notify the sender and then delete this e-mail immediately from your system. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail, its contents or its attachment/s other than by its intended recipient/s is strictly prohibited and may be unlawful. Internet Communications cannot be guaranteed to be secure or error-free as information could be delayed, intercepted, corrupted, lost, or contain viruses. Sistema Shyam Teleservices Limited does not accept any liability for any errors, omissions, viruses or computer problems experienced by any recipient as a result of this e-mail.
