| Forcing Unicode Encoding of Message |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 11, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Joseph Smith New member Username: Falangjoe Post Number: 23 Registered: 08-2006 |
Union Telephone v2009.06.11 I am sending SMS message via (HTTP Url Submissione). When I use the GSM character set the character "@" is encoded incorrectly. When I switch to iso-8859, other characters are encoded incorrectly. When a message is convert automatically to unicode, everything works perfectly. Is there any way I can force a message sent by URL to Unicode? Thanks, Joseph | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2879 Registered: 08-2008 |
Hi Joseph, Does your provider or vendor have any documentation to explain what encoding they expect for the "@" character? When you use the iso-8859-1 character set, is "@" correct but others are wrong? (That would answer my first question.) Encoding in Unicode for this purpose is not desirable because it requires SMS messages to be limited to 70 characters per message. -- Des NowSMS Support | |||
| Joseph Smith New member Username: Falangjoe Post Number: 24 Registered: 08-2006 |
I switched to iso-8859-1 and that fixed the problem, but I had to switch back to GSM. I did some tests with our SMSC both sending and receiving while having SMPPDEBUG enabled. When I sent from a phone the SMSC encodes "@" as 40 with data_coding = 0. When I send an SMS using the web interface with "@" = %40. It encodes it as 00. Is there any way I can force sending 40 and not 00 with the web interface. I guess our SMSC uses 40 and not 00 to encode "@". Thanks, Joseph | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3074 Registered: 08-2008 |
Hi Joseph, Do you have any problems with the $ symbol, or is it just with @? $ is encoded with 0x02 in the GSM character set, but 0x24 in iso-8859-1 (US/Western Europe). Basically, I'm curious what the reason was that you changed the setting back. And I think it would be a good idea to look at your test results using both the @ and $ character to decide which character set to use. If the reason that you switched back is because is because the data_coding = 3 value that NowSMS uses when configured to use iso-8859-1 caused other problems, then change back to using iso-8859-1. Then edit SMSGW.INI, and locate the SMSCCharset=iso-8859-1 setting in the [SMPP - server:port] section of the file. Under that setting, add SMSCCharsetDefault=Yes. This will have the effect of still using iso-8859-1 character encoding, but with a data_coding value of 0. If the reason for switching back is because @ was encoded correctly, but some other characters were having problems, then there is an old setting that just remaps the @ character encoding when the GSM character encoding is being used. To enable this, under the [SMPP - server:port] section of SMSGW.INI, add NullRemap=40 One of these solutions should work. Most likely the SMSCCharsetDefault=Yes setting. If you have to use NullRemap instead, then I'd like to know about it because this setting is one that we consider to be outdated. -- Des NowSMS Support | |||
