Concatenated messages with GSMPackedEncoding

.NET library for SMPP protocol
Locked
didimo
Posts: 8
Joined: Thu Jan 23, 2014 9:23 pm

Concatenated messages with GSMPackedEncoding

Post by didimo » Wed Jun 17, 2015 6:20 pm

Hi,

We have an issue: when we send a concatenated message with GSMPackedEncoding, the SMSC receive the message data with wrong chars.

According with the support team of SMSC, the problem is:
You missed „fill bits“ between UDH and content in front of every concatenated sms.

Just look here:

http://en.wikipedia.org/wiki/Concatenated_SMS
Note. if a UDH is present and the data encoding is the default 7-bit alphabet, the user data must be 7-bit word aligned after the UDH.[2] This means up to 6 bits of zeros need to be inserted at the start of the [message].
We are send the pdu submit_sm to SMSC with the features below:

- Data coding Scheme (DCS) = 241 (Class1)
- Convert the ShortMessage bytes from septets to octets

We are mapping the data coding as below:

Code: Select all

            smppClient.MapEncoding(Inetlab.SMPP.Common.DataCodings.Class1, new Inetlab.SMPP.Encodings.GSMPackedEncoding());
 
            Inetlab.SMPP.SMS.ForSubmit()
                  .Coding(Inetlab.SMPP.Common.DataCodings.Class1)
                  .From(sourceAddr, srcTON, srcNPI)
                  .To(destAddr, destTON, destNPI)
                  .Text(text)
                  ;
See the example below.

Text:
Dna 12.6.2015 o 20:00 vyvrcholi sutaz MERCEDES SLOT SERIES! Prijmite nase pozvanie do herne Rebuy Stars Zvolen! Mozno prave na Vas caka automobil Mercede s triedy A. Vsetkych ucastnikov Finaloveho vecera cakaju sutaze o zaujimave ceny, bohaty sprievodny program, obcerstvenie a dobra nalada!Tesime sa na Vas

We send 1st part:
4477181493b96c2e192c5603bd413298
0e0603d9f376f918fd66a741f33a3dac
07358bd26191589c82a6cc2715342d4a
93c569080495a7d5ed34bd0c7287e765
10fcadb787dde93288fc06a1cb727719
242d8beb79d0941e96cf415afb9b5d76
8740cdb7defd06c1e5617b19e40e83ac
e139681c5e8741e13afddd7e8bd36c50
b32c1f97c965
according with SMSC, this is the message data that we will send:
88EE30282673D95C3258AC067A836430
1D0C06B2E7EDF231FACD4E83E6757A58
0F6A16A5C322B138054D994F2A685A94
268BD310082A4FABDB697A19E40ECFCB
20F85B6F0FBBD36510F90D4297E5EE32
485A16D7F3A0293D2C9F83B4F637BBEC
0E819A6FBDFB0D82CBC3F632C81D0659
C373D038BC0E83C275FABBFD16A7D9A0
66593E2E93CB
we send 2nd part:
73105d9e2e93f3a0a00b649d97e9ebfc
180daa8fc373ba3bbd7edb41c6b43bcc
7edbcbe837c85e1e97e561d038bc0eab
eba0799d1ed697416f903e5c57a7db61
7b19342ebbf32c90f88d0ed3f3a0395c
9e2edbdf64771e0497bfcff2709b057a
8bc765f99c6e2fbbd3655018447e8be5
61903bcc0e93c3216a799e6e9741f330
c81d0659c373
according with SMSC, this is the message data that we will send:
E620BA3C5D26E7414117C83A2FD3D7F9
311A541F87E774777AFDB6838C697798
FDB697D16F90BD3C2ECBC3A071781D56
D741F33A3DAC2F83DE207DB8AE4EB7C3
F632685C76E75920F11B1DA6E74173B8
3C5DB6BFC9EE3C082E7F9FE5E1360BF4
168FCBF239DD5E76A7CBA03088FC16CB
C32077981D268743D4F23CDD2E83E661
903B0CB286E7
It's an library issue?, or We are building the pdu wrong?

How should we do to solve the issue?

Thanks in advance.

Didimo
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: Concatenated messages with GSMPackedEncoding

Post by alt » Thu Jun 25, 2015 8:15 am

fixed in the version 1.1.21.0
Locked