Hi, please try SVN version. Looks like 1.4.4 has issue with TLVs…
Alex > Am 15.08.2016 um 06:43 schrieb Черепанов Алексей Владиславович > <sw_cherepa...@motivtelecom.ru>: > > Here's the dump of packets. > > > Short Message Peer to Peer, Command: Submit_sm - resp, Status: "Ok", Seq: > 684, Len: 25 > Length: 25 > Operation: Submit_sm - resp (0x80000004) > Result: Ok (0x00000000) > Sequence #: 684 > Message id.: 2D8B40B4 > > Short Message Peer to Peer, Command: Deliver_sm, Seq: 674395051, Len: 95 > Length: 95 > Operation: Deliver_sm (0x00000005) > Sequence #: 674395051 > Service type: (Default) > Type of number (originator): International (0x01) > Numbering plan indicator (originator): ISDN (E163/E164) (0x01) > Originator address: 79028710256 > Type of number (recipient): International (0x01) > Numbering plan indicator (recipient): ISDN (E163/E164) (0x01) > Recipient address: 3432690000 > .... ..00 = Messaging mode: Default SMSC mode (0x00) > ..00 01.. = Message type: Short message contains SMSC Delivery Receipt > (0x01) > 00.. .... = GSM features: No specific features selected (0x00) > Protocol id.: 0x7f > Priority level: GSM: None ANSI-136: Bulk IS-95: Normal (0x00) > Scheduled delivery time: Immediate delivery > Validity period: SMSC default validity period > .... ..00 = Delivery receipt: No SMSC delivery receipt requested (0x00) > .... 00.. = Message type: No recipient SME acknowledgement requested > (0x00) > ...0 .... = Intermediate notif: No intermediate notification requested > (0x00) > .... ...0 = Replace: Don't replace (0x00) > Data coding: 0x00 > SMPP Data Coding Scheme: SMSC default alphabet (0x00) > GSM SMS Data Coding > 0000 .... = DCS Coding Group for SMS: SMS DCS: General Data Coding > indication - Uncompressed text, no message class (0x00) > ..0. .... = DCS Text compression: Uncompressed text > ...0 .... = DCS Class present: No message class > .... 00.. = DCS Character set: GSM 7-bit default alphabet (0x00) > GSM CBS Data Coding > 0000 .... = DCS Coding Group for CBS: CBS DCS: Language using the GSM > 7-bit default alphabet (0x00) > ..00 0000 = DCS CBS Message language: German (0x00) > Predefined message: 0 > Message length: 0 > Optional parameters > Optional parameter: message_state (0x0427) > Tag: 0x0427 > Length: 1 > Message state: DELIVERED (2) > Optional parameter: network_error_code (0x0423) > Tag: 0x0423 > Length: 3 > Error type: GSM (3) > Error code: 0x0000 > Optional parameter: receipted_message_id (0x001e) > Tag: 0x001e > Length: 9 > SMSC identifier: 2D8B40B4 > Optional parameter: source_subaddress (0x0202) > Tag: 0x0202 > Length: 12 > Source Subaddress: a03739303238373130303939 > > > 14.08.2016 20:07, Rene Kluwen пишет: >> Even, the message appears in your log files. >> If you set the debug level high enough, you can just see it appear there. >> >> -----Oorspronkelijk bericht----- >> Van: devel [mailto:devel-boun...@kannel.org >> <mailto:devel-boun...@kannel.org>] Namens Milan P. Stanic >> Verzonden: zondag 14 augustus 2016 12:44 >> Aan: devel@kannel.org <mailto:devel@kannel.org> >> Onderwerp: Re: [Couldnot parse DLR string sscanf way,fallback to old way. >> Please report!] -- problem with message id >> >> On Fri, 2016-08-12 at 15:27, Черепанов Алексей Владиславович wrote: >>> Hi, there. Having a problem with handling deliver_sm. >>> Kannel couldn't parse message id: >>> >>> 2016-08-12 14:45:59 [2952] [6] DEBUG: SMPP[SMSC]: Couldnot parse DLR >>> string sscanf way,fallback to old way. Please report! >>> 2016-08-12 14:45:59 [2952] [6] ERROR: SMPP[SMSC]: got DLR but could >>> not find message or was not interested in it id<> dst<79028710256>, >>> type<2> >>> 2016-08-12 14:45:59 [2952] [6] DEBUG: message_id: NULL >> Look like your provider (upstream SMPP server) does not send 'standard' >> DLR message. >> Actually there is no standard format for DLR message but most providers >> format it following sample in SMPP specification document. >> >> Could you check with your provider in what format their server send message >> to your kannel. Or, you can extract it with some network capture tools >> (tcpdump, tshark/wireshark) and see in what format messages are. >> >> >> > > -- > С уважением, > Черепанов Алексей
