GSM-7 Character Support

GSM-7 Character Support SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 20, 2013 » GSM-7 Character Support « Previous || Next »
Author Message
SUPMON
New member
Username: Supmon

Post Number: 1
Registered: 10-2012
Posted on Wednesday, October 17, 2012 - 05:54 pm:   

Does NowSMS support GSM-7 character set? I don't see any provision for it in the dropdown box on either the SMPP Web options box or the SMSC server connection "Advanced" section.

I am testing the latest NowSMS via trail with a client who is trying to send GSM-7 character set.

They are sending the following string: ¿ABC€@!&%§?$DE?¡wxyzäöñüà$èéùìòÉÇÑ?ßæÆ{}[]()

But they are receiving the following: ?ABC?e?!&%_??DE?@wxyz{|}~?????????]?????(?)?()

Its obvious that somewhere between my server and their handset that the text is being translated differently, but I can't figure out where and I really just want to know how to identify where and control it. All I know is that they are sending GSM-7 but there is no obvious support for it on the NowSMS server.

Thanks in advance for your help.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4152
Registered: 08-2008
Posted on Wednesday, October 17, 2012 - 06:19 pm:   

Hi,

The default SMPP character set in NowSMS is GSM-7 (with a data_coding value of 0 indicating the default character set).

If you go to the Advanced settings page for the SMPP connection, you can also select IA5 (GSM), which is the same GSM-7 character set, but in this case NowSMS explicitly sets the data_coding value to indicate the GSM-7 character set is being used.

Based upon your sending/receiving example, I'm guessing that the issue is one of not being able to determine the input character set, not the output.

How is the message being submitted into NowSMS?

Try using the built-in web form first. If that doesn't work, then there is an issue in the configuration of the outbound SMPP character set, as you expect.

If instead, the built-in web form works fine, then how are these characters being submitted to NowSMS? SMPP? HTTP?

For HTTP input, NowSMS assumes that UTF-8 is being used. However, you can also use &charset=xxxx to specify the character set being used for the input. For example, &charset=iso-8859-1 for Western Europe or &charset=iso-8859-6 for Arabic are common charset values used. (I don't believe there is any charset value we support for direct input of GSM characters via HTTP input.)

--
Des
NowSMS Support
SUPMON
New member
Username: Supmon

Post Number: 2
Registered: 10-2012
Posted on Friday, November 02, 2012 - 05:49 pm:   

Thanks for the info Des.

We are still struggling trying to understand if we are the root cause of the issue or they are. We are submitting messages to them using binary GSM values and also Latin charset. However, each time, the message is received on the handset with incorrect characters.

The tech asked me to provide them with a complete PDU log of the submit_sm. I am not sure where to find this information on the platform. Can you kindly point me in the right direction?

Thanks again.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4184
Registered: 08-2008
Posted on Friday, November 02, 2012 - 06:57 pm:   

Hi,

But, how is the message being submitted into NowSMS?

Try using the built-in web form first.

It is important to determine whether the problem is on the input or output side, so it is very important to start with the built-in web form for this determination.

If you enable the SMSDEBUG.LOG (checkbox on the "Serial #" page), this will also enable SMPPDEBUG.LOG which will log the submit_sm PDU.

However, I'd recommend downloading Wireshark and using it to capture packets, as it performs some human readable translation of the packets. Most techs like to see Wireshark logs to troubleshoot these types of issues.

--
Des
NowSMS Support
SUPMON
New member
Username: Supmon

Post Number: 3
Registered: 10-2012
Posted on Friday, November 02, 2012 - 07:27 pm:   

Its being submitted via SMPP always.

I've tried with the webform too but with other carriers it seems to work fine whether I submit via SMPP or webform.

I will try the wireshark capture too and see if the gives any insight. I really don't think the issue is on my side.

thx.
SUPMON
New member
Username: Supmon

Post Number: 4
Registered: 10-2012
Posted on Tuesday, November 20, 2012 - 02:20 pm:   

Hi Des,

So my carrier keeps saying that the issue lies with me and that my encoding is incorrect. I have tried every encoding setting on the NowSMS platform and still no joy.

On the other hand using the default or IA5 settings, I can send the same character set to other carriers and with a couple of exceptions, the texts are correct.

Right now, I am at wits end. I am using a trial of NowSMS and hoping that we can resolve this somehow using your software.

Any ideas you have about how to troubleshoot this further would be greatly appreciated.
SUPMON
New member
Username: Supmon

Post Number: 5
Registered: 10-2012
Posted on Tuesday, November 20, 2012 - 02:24 pm:   

Further Info:

When I am sending : ¿ABC€@!&%§?$DE?¡wxyzäöñüà$èéùìòÉÇÑ?ßæÆ{}[]()12345

They are receiving: `ABCe!&%_?DE?@wxyz{|}~]?()<>()12345

This is what is showing on the providers platform.

Where would you say the problem lies?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4206
Registered: 08-2008
Posted on Tuesday, November 20, 2012 - 02:39 pm:   

Hi,

Before we go back to my troubleshooting suggestion above, try setting the SMPP character set for this outbound connection to iso-8859-1.

My guess is that this provider expects iso-8859-1. It's fine that the SMPP client is using the GSM character set, NowSMS will translate.

If that does not work, manually edit SMSGW.INI and under the [SMPP - host:port] section for this server, add:

SMSCCharsetDefault=Yes

(You should also see SMSCCharset=iso-8859-1 in the SMSGW.INI file. Add this setting right below that setting.)

Try again with this setting in place.

If neither of these settings works, then I want you to go back to the second of my posts above. (Remember to remove SMSCCharsetDefault=Yes)


quote:

Try using the built-in web form first.

It is important to determine whether the problem is on the input or output side, so it is very important to start with the built-in web form for this determination.




Submitting via the web form, try sending the same characters using the different character set advanced options for the outbound SMPP connection:

1.) Default (this uses the GSM character set with data_coding = 0)
2.) IA5/GSM (this uses the GSM character set with data_coding set to explicitly indicate this character set is in use)
3.) iso-8859-1 (this uses the iso-8859-1/ANSI character set with data_coding set to explicitly indicate this character set is in use)
4.) iso-8859-1, plus add SMSCCharsetDefault=Yes as detailed above (this uses the iso-8859-1/ANSI character set with data_coding = 0)


--
Des
NowSMS Support

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