Received message is broken

Received message is broken SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 16, 2008 » Received message is broken « Previous || Next »
Author Message
lge
New member
Username: Lge

Post Number: 13
Registered: 02-2007
Posted on Wednesday, July 16, 2008 - 07:20 am:   

I use “NOW SMS 2008”.
When I send a message(text: fiejifjjefi:11characters 1SMS message, Message Type: Normal, Message Class:Default) at “Send Text Message”, message is not broken.
But when sent message is 164 characters 2SMS message(Message Type: Normal, Message Class:Default), received message is broken.
Another “Message class”(class 0,class1,class2,class3) is not broken.
At this time “Encode long text messages with 7-bit packed encoding” in Now SMS/MMS gateway is checked,
when sent message is 164 characters 2SMS message(Message Type: Normal, Message Class:0, Class 1, Class 2, Class 3), received message is broken.
Another “Message class”(Default) is not broken
At this time “Encode long text message with 7-bit packed encoding” is unchecked,
I would like to know the reason.
Attached files are packet data of Now SMS output, text message at “Send Text Message and Now SMS/MMS gateway setting value.”
One of them is 1page packet data(text: fiejifjjefi:11 characters 1SMS message).
The other is 2page packet data(text:164charaters 2SMS message).
Please compare with No.36 of 1page-default.cap file and No.40 of 2page-default .cap file.

sent message(164 characters 2SMS message)
sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss123
received message
fryo>EOgsxo>EOgsyn>EOgsyo>EOgsyo>EOgsyo>ENgsyo>EOfsyo>EOgryo>EOgsxo>EOgsyn>EOgsyo>EOgsyo>EOgsyo>ENgsyo>EOfsyo>EOgryo>EOgsxo>EOgsyn>EOgfryo>EOc2
application/octet-stream1page-default
1page-default.cap (10.0 k)
application/octet-stream2page-default
2page-default.cap (41.3 k)
now sms 2008 2page borkenNow SMS SMPP
lge
New member
Username: Lge

Post Number: 14
Registered: 02-2007
Posted on Wednesday, July 16, 2008 - 07:39 am:   

This is Now SMS/MMS gateway setting value.”Now SMS SMPP
lge
New member
Username: Lge

Post Number: 15
Registered: 02-2007
Posted on Wednesday, July 16, 2008 - 08:15 am:   

application/octet-stream
1page-default.cap (10.0 k)
application/octet-stream
2page-default.cap (41.3 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7634
Registered: 10-2002
Posted on Thursday, July 17, 2008 - 05:47 pm:   

I don't understand what your question is.

The SMPP standard does not explicitly define some unusual situations, such as long message encoding.

In our experience, in the real world, different SMPP providers require different encoding options. That's why we have several different settings to choose from.

If you still have a question, then please clarify what your question is.

If I look at packet #36 in the first CAP file, I see the text is encoded with "Encode long text messages with 7-bit packed encoding" UNchecked.

Packet #40 in the second CAP file is encoded as if that setting were checked.
lge
New member
Username: Lge

Post Number: 16
Registered: 02-2007
Posted on Monday, July 21, 2008 - 03:50 am:   

I choosen "Message class:Default"
When sent message was over 2pages after “Encode long text message with 7-bit packed encoding" in Now SMS/MMS gateway had been checked, received message was borken.
But when sent message was over 2pages after“Encode long text message with 7-bit packed encoding" in Now SMS/MMS gateway had been unchecked,receive message is not broken.

I choosen "Message Class:Class 0,1,2,3."
When sent message was over 2pages after “Encode long text messages with 7-bit packed encoding” in Now SMS/MMS gateway had been checked, received message was not borken.
But When sent message was over 2pages after “Encode long text messages with 7-bit packed encoding” in Now SMS/MMS gateway had been unchecked, received message was borken.

1page message is not broken, but over 2pages message(message class:Default)is broken in case of checked“Encode long text messages with 7-bit packed encoding"
when only message class is Default ,i would like to know reason to be broken
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7647
Registered: 10-2002
Posted on Friday, July 25, 2008 - 08:51 pm:   

Cross-reference thread with additional detail:

http://support.nowsms.com/discus/messages/1/24071.html

I understand now.

This would appear to be an issue that is specific to your SMSC.

When a text message is sent with a data coding value that includes a message class, it expects the text to be 7-bit packed.

When a text message is sent with a standard data coding, it expects the text to be standard 8-bit text.

That is, of course, inconsistent, as the data coding still indicates text, and text should be handled the same way regardless of message class.

Unfortunately, we can't fix the SMSC. But we can provide a work-around.

An updated version has been posted to http://www.nowsms.com/download/nowsmsupdate.zip.

This update includes the following new setting which should resolve your problem:

* SMPP: Work-around for strange SMPP SMSC behaviour with long text messages. This particular SMSC expected "Encode long text messages with 7-bit packed encoding" to be UNchecked when a text message is submitted with the default data coding (DCS) value. However, if the data coding specified a message class value, the SMSC would corrupt the message unless "Encode long text messages with 7-bit packed encoding" was checked. (With that setting checked, messages using the default encoding would be corrupt.) As a work-around, if dealing with this situation, edit SMSGW.INI, and under the [SMPP - host:port] section of the file, add GSMPackLongSMSWithMessageClass=Yes.


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