Sending multipart SMS messages through a SMPP provider

Sending multipart SMS messages through a SMPP provider SearchSearch
Author Message
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 171
Registered: 01-2008
Posted on Thursday, June 09, 2011 - 12:10 pm:   

Hello!
Tell me why, if we use the TLV parameters (sar_msg_ref_num, sar_gegment_seqnum and sar_total_segments) in the segmentation,
it is necessary to divide the parts to 152 characters (GSM 03.38 character set) and 66 characters (Unicode) ?
Although this article http://www.nowsms.com/long-sms-text-messages-and-the-160-character-limit said that there must be 153 and 67.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3247
Registered: 08-2008
Posted on Thursday, June 09, 2011 - 02:04 pm:   

Hi Alexandre,

This must be an issue with a specific provider you are using.

If long messages are encoded with a 16-bit reference number (instead of an 8-bit reference number), then you lose another byte for the header, which reduces the number of characters that can fit into each message segment.

If you add the following setting under the [SMSGW] header of SMSGW.INI, then NowSMS uses 16-bit reference numbers: ConcatRef16Bit=Yes

Note that if a client submits a message already segmented, NowSMS will not resegment to the adjusted length.

Using 16-bit reference numbers does reduce the number of characters that can fit in each segment, as you describe. That's why in practice the majority of implementations stick with 8-bit reference numbers.

--
Des
NowSMS Support
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 172
Registered: 01-2008
Posted on Thursday, June 09, 2011 - 02:48 pm:   

Thanks!

Yes client submit message already segmented and use 16-bit reference number. This is the reason for the loss of one character
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3255
Registered: 08-2008
Posted on Thursday, June 09, 2011 - 05:10 pm:   

Hi Alexandre,

Are you saying that the client submits to NowSMS using TLV parameters?

It is true that if they submit with a sar_msg_ref_num larger than 255, we have to use 16-bit (2 bytes) reference number encoding to preserve this value.

If sar_msg_ref_num <= 255, it can be encoded in a single byte which gives more character space.

--
Des
NowSMS Support