Question about multipart datafields and encoding

Question about multipart datafields and encoding SearchSearch
Author Message
Nikos Mavrakis
New member
Username: Nmavra

Post Number: 41
Registered: 05-2007
Posted on Wednesday, February 24, 2010 - 09:20 am:   

Hello, I have submitted the following message:

http://localhost:8080/?PhoneNumber=123123123&SMSCRoute=SC11111&Text=AAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA&user=test& password=test&ReceiptRequested=Yes


And the files that were created are the following:

[SMS]
SubmitUser=test
SubmittedBy=127.0.0.1
ReceiptRequested=Yes
Data=82C16030180C0683C16030180C0683C16030180C0683C16030180C0683C16030180C0683C16 030180C0683C16030180C0683C16030180C0683C16030180C0683C16030180C0683C16030180C068 3C16030180C0683C16030180C0683C16030180C0683C16030180C0683C16030180C0683C16030180 C0683C16030180C0683C16030180C0683
UDH=050003340201
Binary=1
PhoneNumber=123123123
SMSCRoute=SC11111

[SMS]
SubmitUser=test
SubmittedBy=127.0.0.1
ReceiptRequested=Yes
Data=82C16030180C0601
UDH=050003340202
Binary=1
PhoneNumber=123123123
SMSCRoute=SC11111

Can somebody tell me how the Data fields are formed, what type of encoding is it? I think it has something to do with 7 bit encoding, but can somebody shed some light and if possible suggest to a .Net library/function that encodes this ways?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1840
Registered: 08-2008
Posted on Wednesday, February 24, 2010 - 04:18 pm:   

Hi Nikos,

I'm not sure about any libraries, but ETSI GSM 03.38 defines the 7-bit packed encoding. And ETSI GSM 03.40 defines segmentation/concatenation using UDH.

What are you trying to do? I'm guessing that you're trying to create the Q files directly?

--
Des
NowSMS Support
Nikos Mavrakis
New member
Username: Nmavra

Post Number: 43
Registered: 05-2007
Posted on Thursday, February 25, 2010 - 09:29 am:   

I want to send multipart messages of less than 153 characters each. I see that the only way to do this with NowSMS is to create the UDH manually and to submitted it along with the text message in encoded form:

http://localhost/?PhoneNumber=123123&SMSCRoute=SMSC1&user=test&password=test&Rec eiptRequested=Yes&data=8C46A3D168341E8FC7E3F1783C1E8F&udh=050003A50101

So, I have to create somehow the data field myself.

Btw,I have tried instead of data= to use text= and then the message in clear text and it arrived on the phone scrambled.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1858
Registered: 08-2008
Posted on Thursday, February 25, 2010 - 08:51 pm:   

Hi Nikos,

What multipart segment size do you have to use? (I'm also curious if you know why there a different segment size is needed. We did recently have a customer who needed to use 16-bit reference numbers in segmented messages instead of 8. This reduces the 153 character limit to 152. If you only need to chop one character off, I can describe that setting.)

There is one possibility that I can think of ...

I believe this will work:

http://localhost/?PhoneNumber=123123&SMSCRoute=SMSC1&user=test&password=test&Rec eiptRequested=Yes&text=text+message+here&udh=050003A50101

You still need to generate the UDH, but NowSMS will see that the data is text and will handle it appropriately.

--
Des
NowSMS Support