NowSMS submitted concatenate SMS with a space character added to th...

NowSMS submitted concatenate SMS with a space character added to th... SearchSearch
Author Message
Nelson Lam
New member
Username: Nelsonlam

Post Number: 28
Registered: 02-2013
Posted on Thursday, August 28, 2014 - 09:53 am:   

Dear Support

The following concatenate SMS were submitted by a handset:

\1111111111222222222233333333334444444444
5555555555666666666677777777778888888888
9999999999000000000011111111112222222222
33333333334444444444555555555566\66666666
7777777777888888888899999999990000000000
1111111111222222222233333333334444444444
5555555555666666666677777777778888888888
9999999999000000000011111111112222222222
3333333333444444444455555555556666666666
7777777777888888888899999999990000000000

The above SMS contains 402 characters and splitting into 3 SMS.
When the 3 SMS received by NowSMS via SMPP connection, we had accounting
callback to do billing and routing. Then when NowSMS sent out the 1st and
2nd SMS to the upstream SMPP provider, a space (hex code 20)add to the end.

If I check with the smpp packet of the 1st SMS sending to NowSMS
the message contains the UDH header and the 152 characters:
UDH - 05 00 03 0 03 01
message text -
\1111111111222222222233333333334444444444
5555555555666666666677777777778888888888
9999999999000000000011111111112222222222
3333333333444444444455555555556

I have also sent the smpp packet and the sms-debug log in separate email.

Pls help to investigate why there is space character added to the end.
Since the upstream SMS provider has rejected this SMS, can you remove
the space character added at the end ?

Thanks.

Best Regards
Nelson
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5019
Registered: 08-2008
Posted on Thursday, August 28, 2014 - 05:56 pm:   

Hi Nelson,

I aam attempting to recreate this problem.

Do you encounter the same problem submitting that long text from the web interface of NowSMS, or does it have to come in via an SMPP client to trigger the problem?

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5020
Registered: 08-2008
Posted on Thursday, August 28, 2014 - 07:11 pm:   

Hi Nelson,

I think this is a character set issue.

You are interpreting it as \ (which is the iso-8859-1 character for 0x5C), but if you look at the NowSMS accounting callbacks, NowSMS is interpreting the character as Ö (GSM character 0x5C).

I think you want to change both of your SMSC character sets to "iso-8859-1 as default", and that should resolve the problem.

I am a little intrigued with the question of where the space character is coming from, but in my tests, it does go away in this particular scenario when the character set is set to iso-8859-1.

--
Des
NowSMS Support