first short message: 000000ce - command_length 00000005 - command_id 00000000 - command_status 00000002 - sequence_number 736d73633900 - service_type 0101 - source_addr_ton, source_addr_npi 383535393836313037353300 - source_addr 0001 - dest_addr_ton, dest_addr_npi 3233363700 - destination_addr 40 - ...

id - The message ID allocated to the message by the SMSC when originally submitted. sub - Number of short messages originally submitted. dlvrd - Number of short messages delivered. submit date - The time and date at which the short message was submitted. The format is :YYMMDDhhmm done date - The tim...

Yes, you can use ALT.SMS.SmppClient library in commercial product. But your product should not provide the same functionality as library. In other words your product should not be extended SMPP library.

For better integration with your project you can buy source code license.

Since version 2.6.4 you can change DeliverSmResp or DataSmResp.

DeliverSm class now has Response property which can be modified in the event evDeliverSm.

If your SMSC sends information about concatenated messages than you can combine message parts. Here is code from SmppClientDemo private Dictionary<string, UserData[]> collector = new Dictionary<string, UserData[]>(); private void client_evDeliverSm(object sender, DeliverSm data) { if (data.SegmentNu...

Thank you again, Jabberwok.
Fixed.

Everybody can download new build.

Who has source code license, please write me an email. I'll send update.
Don't forget to include purchasing information.

Obfuscator stil not released.
I'll notify here when ALT.SMS library start to support x64 platform.

Can you still get Invalid DELIVER_SM packet?

I have checked once again and found that packet 00000042000000050000000000000003736d736339000101383535393836313037353300000132333637004000000000010000000d474f4f44444159203420552120 is parsed well with last version Please remove all instances of ALT.SMS.SmppClient.dll from your computer and extract f...

What library version do you use?

fixed

Please download last version.

I've fixed "Invalid DELIVER_SM packet" problem for your examples.
But again without ability to combine these two messages. I hope you understood why I can not provide this ability.

Please download last version.

Your first message is 153 (0x99) bytes length and I believe it contains "G-get up O-open your eyes O-out of your bed D-day has risen M-merry life O-old dreams cum true R-rise $ shine N-new frnds I-idea of life N-nice future G-" and second message is 13 (0x0d) bytes length and it contains "GOODDAY 4 ...

Normal concatenated message should contain information about 1) msg_ref_num 2) total segments 3) sequence number But your packets does not have such information neither in UDH nor in SAR parameters. I'll think how to avoid "Invalid DELIVER_SM packet" in your second case. But it is not normal for con...

Dear rag123456,

Please send me your log file.
SequenceNumber supports concatenated messages created using UDH and also using SAR TLV parameters.

I think you have the same problem as chaoraksa has.