decrease part size to 152

.NET library for SMPP protocol
Locked
zkerdzevadze
Posts: 5
Joined: Fri Jan 13, 2017 11:06 am

decrease part size to 152

Post by zkerdzevadze » Fri Jan 13, 2017 11:13 am

We have message that contains 200 gsm7 characters.
When sending, message is split into 2 parts: 153 and 47
or
We have message that contains 100 unocide characters.
When sending, message is split into 2 parts: 67 and 33

1. Is it possible to decrease concatenated message part to be 152 instead of 153 characters when sending GSM7 message?
2. Is it possible to decrease concatenated message part to be 66 unicode chars instead of 67 characters when sending unocode message?
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: decrease part size to 152

Post by alt » Sun Jan 15, 2017 8:34 pm

Library tries to use maximal possible size for each segment.
Why do you need to decrease the part size?
zkerdzevadze
Posts: 5
Joined: Fri Jan 13, 2017 11:06 am

Re: decrease part size to 152

Post by zkerdzevadze » Mon Jan 16, 2017 7:49 am

Hello,
Gateway developers has warned us, that they have a bug is the system.
To decrease the part size to 152 or 151 characters is the workaround that works.
Do you know how to decrease part size?
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: decrease part size to 152

Post by alt » Wed Jan 18, 2017 4:25 pm

Hello zkerdzevadze,

In which system? and why size decrease helps to fix it?

For now it is impossible to change part size in the SMS builders of the library.
but you can create SubmitSm instances manually and define UserData.ShortMessage as you want.

On the other side I can implement MaxPartSize method for SMS Builders in short time. But size will be defined in bytes and not in characters.
zkerdzevadze
Posts: 5
Joined: Fri Jan 13, 2017 11:06 am

Re: decrease part size to 152

Post by zkerdzevadze » Wed Jan 18, 2017 5:11 pm

MaxPartSize would be great!
When will you implement MaxPartSize ?
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: decrease part size to 152

Post by alt » Mon Jan 23, 2017 8:11 pm

I have added MaxPartSize methods for SMS builders in the version 1.1.28
zkerdzevadze
Posts: 5
Joined: Fri Jan 13, 2017 11:06 am

Re: decrease part size to 152

Post by zkerdzevadze » Mon Jan 23, 2017 11:27 pm

Thank you for quick resolution!
So,
1. I want to send UCS2 message. I want each part to contain no more than 60 characters . Do I set MaxPartSize to 2*60 which is 120?
2. I want to send GSM7 message. I want each part to contain no more than 150 characters. Do I set MaxPartSize to nearest biggest integer of (150*7)/8 which is 132 ?
zkerdzevadze
Posts: 5
Joined: Fri Jan 13, 2017 11:06 am

Re: decrease part size to 152

Post by zkerdzevadze » Tue Jan 24, 2017 12:26 am

When i send unicode text containig more than 70 characters and MaxPartSize is 120, I receive normal message.
But, when i send unicode text containig 15 characters and MaxPartSize is default, I receive Chinese character, instead f Georgian characters.
Why?
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: decrease part size to 152

Post by alt » Fri Feb 10, 2017 9:10 pm

zkerdzevadze wrote: 1. I want to send UCS2 message. I want each part to contain no more than 60 characters . Do I set MaxPartSize to 2*60 which is 120?
2. I want to send GSM7 message. I want each part to contain no more than 150 characters. Do I set MaxPartSize to nearest biggest integer of (150*7)/8 which is 132 ?
Correct, you always need to convert size in characters into size in bytes.
zkerdzevadze wrote:when i send unicode text containig 15 characters and MaxPartSize is default, I receive Chinese character, instead f Georgian characters.
Why?
I don't have explanation for this. Default size in bytes is 140.
Could you find out how your provider processes UCS2 messages?
Locked