Regarding class 0,1,2 problem

Regarding class 0,1,2 problem SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through November 14, 2013 » Regarding class 0,1,2 problem « Previous || Next »
Author Message
Johnny
New member
Username: Johny

Post Number: 41
Registered: 02-2009
Posted on Wednesday, August 14, 2013 - 07:59 am:   

Hi
I use Now sms 2013.07.02

I have requested for this case
http://support.nowsms.com/discus/messages/1/71597.html

I install the newest now sms and send message.
When I capture the smpp packet, I have question.

I disable “Encode text messages with 7bit packet encoding” and
“Encode long text messages with 7bit packet encoding”

I selet class2.
I input 160 characters and send a message.
At this time, smpp length is 160
But When I input 180characters and send a message, smpp length is 140.
When I send 180characters(2pages), message is encoded( gsm 7bit)

I wonder why 2page is sent using gsm 7bit encoding
I think message have to be not encoded because I don’t activate
“Encode text messages with 7bit packet encoding”
“Encode long text messages with 7bit packet encoding”


And I want to know the reason that why length is diffrent with selecting default and class2
Please let me know this case.


class2 160characters





class2 180characters




default 160characters




default 180characters

Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4598
Registered: 08-2008
Posted on Wednesday, August 14, 2013 - 01:18 pm:   

Hi Johnny,

I do not see the same results as you.

If I disable/uncheck “Encode text messages with 7bit packet encoding” and “Encode long text messages with 7bit packet encoding”, I get the following results:

160 characters, default class - 8-bit encoding, length = 160

160 characters, class=2, 8-bit encoding, length = 160

180 characters, default class - 8-bit encoding, first message length = 159, second message length = 33

180 characters, class=2 - 8-bit encoding, first message length = 159, second message length = 33


I do not see any 7-bit encoding in either case.

Now if we go back to the other thread you reference, we actually added a setting for you to force 7-bit encoding when a message class is specified.

If I add that setting (GSMPackWithMessageClass=Yes), then the Class 2 results change as expected.

160 characters, class=2, 7-bit encoding, length = 140

180 characters, class=2 - 7-bit encoding, first message length = 140, second message length = 30


This is still different from the results that you are seeing.

But if we go back again to your earlier thread, it shows that you are using the setting GSMPackLongSMSWithMessageClass=Yes.

That setting is telling NowSMS to use 7-bit packed encoding for long messages with a message class set.

If I apply that setting, then I get the same results as you ... as I would expect.

So I would conclude that the reason NowSMS is encoding the class 2 message with 7-bit encoding is because you have applied a configuration setting requesting it do so.

These settings, GSMPackLongSMSWithMessageClass=Yes and GSMPackSMSWithMessageClass=Yes, are work-arounds for unusual and inconsistent SMPP implementations. So if these settings worked before but are now causing problems, it is because your SMPP server has been updated to fix the problems that these work-arounds were required for.

--
Des
NowSMS Support
Johnny
New member
Username: Johny

Post Number: 43
Registered: 02-2009
Posted on Monday, September 02, 2013 - 12:41 am:   

Hi
I have resolved some problems. We fix some parameters in the SMSC.
However, some problems also have occurred as follow.

Case 1) select class 0, more input 160 alphabet characters

When I select class 0 and I input 160 characters(alphabet), 160 characters are received and pop up is occurred.
When I select class 0 and I input 180 characters(alphabet), 153 characters are received and pop up is occurred.
When I select class 0 and I input 320 characters(alphabet), 153 characters are received and pop up is occurred.
Some characters are missing.

I attach the Now SMS Server wire shark log, when I input 180, 320 characters.

Case 2) Sending Unicode(Korean) problem

When I select Default, Class1 and I input Unicode such as Korean, all of characters are received.
When I select class 0 and I input Unicode 70 Characters(Korean), 70 characters are received but pop up is not occurred.
When I select class 0 and I input Unicode 170 Characters(Korean), 170 characters are received but pop up is not occurred.

When I select class 2 and I input Unicode 70 Characters(Korean), 70 characters are received but message don’t be saved in the sim card.
When I select class 2 and I input Unicode 170 Characters(Korean), 170 characters are received but message don’t be saved in the sim card.

SMSC engineer said that Nowsms have problem for these cases.

I attach the Now SMS Server wire shark log when I input Unicode.

So I want to follow up issues.
Thanks


application/x-zip-compressed
NowSMS class test.zip (3.1 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4626
Registered: 08-2008
Posted on Monday, September 02, 2013 - 01:32 pm:   

Hi Johnny,

For case 1, I do not detect any missing characters. The lengths of the messages match your description exactly.

If a problem is occurring, it is either with the SMSC or the SMS client in the device. (I suspect the SMS client does not bother to reassemble so-called pop-up messages.)

For case 2, this is an SMPP issue. In the SMPP protocol specification there is no valid data_coding value to support message class with a Unicode message.

In GSM, values of 0x18, 0x19, 0x1A and 0x1B would be used to indicate a Unicode message with class of 0, 1, 2 or 3, respectively.

However, in the SMPP protocol specification those values are marked as reserved and invalid to be used. For that reason, NowSMS remaps those values to remove message class and use a generic Unicode data_coding value of 8.

There is a configuration parameter to disable this remapping and use the GSM "data coding" value as the SMPP "data_coding" value, even though it is invalid in SMPP. Just be aware that your SMSC may not support it.

The configuration setting is applied in SMSGW.INI under the [SMPP - server:port] header, RemapMessageClassDCS=No

You can find more discussion of this issue in our earlier dialog at http://support.nowsms.com/discus/messages/1/71115.html

--
Des
NowSMS Support

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