Splitting long binary SMS messages

Splitting long binary SMS messages SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through March 09, 2004 » Splitting long binary SMS messages « Previous || Next »
Author Message
Fernando
Unregistered guest
Posted on Sunday, December 14, 2003 - 03:46 pm:   

Up to now I can send logos of 72x14 without problems, but when it comes to logos of doble size it doesn´t work. I suppose I need to break it up into smaller messages,
but I haven´t been able to achieve it yet.

1- What is the maximum size for the binary data that I can put into a single
SMS when working with SMPP?

2- I have tried to split the message up into two strings (adding the
corresponding info in the UDH) and send them one after the other but doesn´t
work.

string opcode = "42F450";
string raw1 = "0B0A00036402010415821582" + opcode +
"00481C0100000000000000000000000000830000000000000001C18180000000000001E3038
0000000000000C30780000000000000E10600000000000070C00C000000000000384F0400000
00000003C3E0000000000000008700000000000000000C00000000000000000C020000000000
003E187F0000000000003F307F800";
string raw2 = "0B0A00036402020415821582" + opcode +
"0000000000A1C3F800000000000003C63800000000000003C63800000000000003443800000
0000000F9C07E000000000001F9E03C000000000003D1ED6C00000000000000FFF8000000000
000007FE00000000000000E3E800000000000001C0F000000000000001E02000000000000001
80000000000000000000000000000";

the whole OTA bitmap is:
00481C0100000000000000000000000000830000000000000001C18180000000000001E30380
000000000000C30780000000000000E10600000000000070C00C000000000000384F04000000
0000003C3E0000000000000008700000000000000000C00000000000000000C0200000000000
03E187F0000000000003F307F8000000000000A1C3F800000000000003C63800000000000003
C638000000000000034438000000000000F9C07E000000000001F9E03C000000000003D1ED6C
00000000000000FFF8000000000000007FE00000000000000E3E800000000000001C0F000000
000000001E0200000000000000180000000000000000000000000000

Does anyone know what's wrong with this?

Thanks in advance,

Fernando
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1387
Registered: 10-2002
Posted on Monday, December 15, 2003 - 08:23 pm:   

Fernando,

If you are using NowSMS, it is best to let NowSMS perform the splitting.

Just give it the UDH assuming that the message was a single part message, and it will adjust the UDH as appropriate.

As far as your UDH above goes ... well, it looks like a corrupt EMS encoding.

A typical UDH for a multipart SMS going to the Nokia operator logo port would look like this:

Message 1:

0B0504158215820003xx0201

Message 2:

0B0504158215820003xx0202

(The "xx" is a type of identifier, and this would vary.)

The opcode would only appear in the first message, as it is part of the data of the message, not a header.

-bn
Fernando
Unregistered guest
Posted on Tuesday, December 16, 2003 - 07:33 am:   

Thanks a lot. You have been a great help :-)

Fernando
Anonymous
 
Posted on Thursday, February 05, 2004 - 01:08 pm:   

what can the "xx" be in the 0B0504158215820003xx0201 string?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1829
Registered: 10-2002
Posted on Wednesday, February 11, 2004 - 05:34 pm:   


quote:

what can the "xx" be in the 0B0504158215820003xx0201 string?




Any hex value (0 thru 9 or A thru F for each character).

This is a message id, that is part of the concatenation header.

In the above, 03xx0201 is the part of the UDH that specifies a concatenated message. "xx" allows the recipient to put the pieces of the separate messages back together, so you want to keep this value changing. 02 specifies the number of messages that are part of this concatenated message. 01 specifies the message number of this part of the concatenated message.


Topics Topics Search Last 30 Days Login Login / Register Logout Logout