Dear All,
Thank you for your replies.

We are using kannel 1.4.5 with the following setup: sqlbox -> bearerbox ->
smsc and  connected in  transceiver mode to SMSC.
we are inserting into mysql send_sms table for sending.
We are working with several SMSC and they where able to provide us with
logs clearly showing that they have submitted a DLR to our kannel server
and have received ACK from our kannel server.
In the example below the final Deliver_sm WE DO NOT see in any of the logs
(access or SMSC) once or ever and the DLR is stuck in dlr table with where
ts = 150903932114
There aren't any errors in sql box logs (we are using mysql).
We do not see any errors in SMSC logs except: "Could not parse DLR string
sscanf way, fallback to old way. Please report!"
I will reiterate that missing DLRs are happening intermittently about 25%
of them are stuck in dlr table, and even with the error above 75% of them
still come in normally.
Also in the BB logs we have a lot of the following:
"
sms_router: handling message
Routing failed, re-queued
"
Not sure if it is all connected or not ...
Any help would be much appreciated!

here is an example: ( sensitive parts were redacted)
Our Submit_sm as logged on our server:
022-03-30 07:11:59 [9] [11] DEBUG:   type_name: submit_sm
2022-03-30 07:11:59 [9] [11] DEBUG:   command_id: 4 = 0x00000004
2022-03-30 07:11:59 [9] [11] DEBUG:   command_status: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   sequence_number: 8513 = 0x00002141
2022-03-30 07:11:59 [9] [11] DEBUG:   service_type: ""
2022-03-30 07:11:59 [9] [11] DEBUG:   source_addr_ton: 5 = 0x00000005
2022-03-30 07:11:59 [9] [11] DEBUG:   source_addr_npi: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   source_addr: "srcaddr"
2022-03-30 07:11:59 [9] [11] DEBUG:   dest_addr_ton: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   dest_addr_npi: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   destination_addr: "***********"
2022-03-30 07:11:59 [9] [11] DEBUG:   esm_class: 3 = 0x00000003
2022-03-30 07:11:59 [9] [11] DEBUG:   protocol_id: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   priority_flag: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   schedule_delivery_time: NULL
2022-03-30 07:11:59 [9] [11] DEBUG:   validity_period: NULL
2022-03-30 07:11:59 [9] [11] DEBUG:   registered_delivery: 1 = 0x00000001
2022-03-30 07:11:59 [9] [11] DEBUG:   replace_if_present_flag: 0 =
0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   data_coding: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   sm_default_msg_id: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   sm_length: 48 = 0x00000030
2022-03-30 07:11:59 [9] [11] DEBUG:   short_message:
2022-03-30 07:11:59 [9] [11] DEBUG:    Octet string at 0x7ffb08002320:
2022-03-30 07:11:59 [9] [11] DEBUG:      len:  48
2022-03-30 07:11:59 [9] [11] DEBUG:      size: 50
2022-03-30 07:11:59 [9] [11] DEBUG:      immutable: 0
2022-03-30 07:11:59 [9] [11] DEBUG:      data: MY
2022-03-30 07:11:59 [9] [11] DEBUG:      data: SHORT
2022-03-30 07:11:59 [9] [11] DEBUG:      data: MESSAGE
2022-03-30 07:11:59 [9] [11] DEBUG:    Octet string dump ends.
2022-03-30 07:11:59 [9] [11] DEBUG: SMPP PDU dump ends.

As logged on their server

9:11:59.460 DEBUG @ <SMPP Session-*******:***** - ****> [SMPPServer]:
Read PDU [submit_sm seq 8513 status 0] - service_type=''
source_addr_ton='5' source_addr_npi='0' source_addr='srcaddr' des
t_addr_ton='0' dest_addr_npi='0' destination_addr='*******'
esm_class='3', protocol_id='0' priority_flag='0',
schedule_delivery_time='', validity_period='',
registered_delivery='1', replace_if_present=
'0', data_coding='0', sm_default_msg_id='0', short_message='my short message',

Their Submit_sm_resp as logged on our server (In dlr talbe there is
pending dlr with ts =150903932114 ):

2022-03-30 07:11:59 [9] [11] DEBUG:   type_name: submit_sm_resp
2022-03-30 07:11:59 [9] [11] DEBUG:   command_id: 2147483652 = 0x80000004
2022-03-30 07:11:59 [9] [11] DEBUG:   command_status: 0 = 0x00000000
2022-03-30 07:11:59 [9] [11] DEBUG:   sequence_number: 8513 = 0x00002141
2022-03-30 07:11:59 [9] [11] DEBUG:   message_id: "150903932114"


Their Deliver_sm as logged on their server *which we have no trace of*!:

09:12:07.737 DEBUG @ <pool-4-thread-11> [SMPPServer]: Write PDU
[deliver_sm seq 140444686 status 0] - service_type=''
source_addr_ton='1' source_addr_npi='1' source_addr='********'
dest_addr_ton='0' dest_addr_npi='0' destination_addr='srcaddr'
esm_class='4', protocol_id='0' priority_flag='0',
schedule_delivery_time='', validity_period='',
registered_delivery='0', replace_if_present_flag='0', data_coding='0',
sm_default_msg_id='0', short_message='id:150903932114 sub:001
dlvrd:001 submit date:220330091159 done date:220330091203 stat:DELIVRD
err: 000 text:DELIVERED', message_state='2'
receipted_message_id='150903932114'

09:12:07.792 DEBUG @ <SMPP Session-******:***** - *****> [SMPPServer]:
Read PDU [deliver_sm_resp seq 140444686 status 0] - message_id = ''

Reply via email to