Actually I'm using a new carrier and it seems that the DLR is inserted correctly but not retrived propertly from kannel in the dlr_mysql.c
In kannel logs, upon smpp deliver_sm, I get all the parsing of the PDU and at the end kannel reports: 2007-03-16 16:34:29 [10563] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=mysmsc, ts=101748338, dst=0, type=2 But in the PDU I can read: 2007-03-16 16:34:29 [10563] [6] DEBUG: dest_addr_ton: 0 = 0x00000000 2007-03-16 16:34:29 [10563] [6] DEBUG: dest_addr_npi: 0 = 0x00000000 2007-03-16 16:34:29 [10563] [6] DEBUG: destination_addr: "393356359515" Infact usually I get: 2007-01-25 00:34:44 [2346] [7] DEBUG: DLR[mysql]: Looking for DLR smsc=myothersmsc, ts=250107004454, dst=00393356359515, type=2 So, the question is: do you think I should set the dest_addr_ton and npd in a special way to get the dst correctly parsed ? Thanks Julien PS: The smsc I'm using reports to be smpp 3.4 standard compliant PPS: I know that kannel does not use, in its original version, the dst value to retrive the DLR from the database, but using only the TS can be a problem when using EMI smsc that has no unique sms id
