| hundling special characters |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through November 14, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| Stoner2008 New member Username: Stoner2008 Post Number: 8 Registered: 05-2013 |
Hi, I tried sending a SMS containing "é" character to my NowSMS server, it seems to treat it as invalid character. I have checked the NowSMS logs, it has received the character as "é". But NowSMS sends out as "é" to my application server based on the packet that I have captured. Is that any encoding that I need to set inorder for NowSMS to be able to handle this special character? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4534 Registered: 08-2008 |
Hi, By default NowSMS expects HTTP applications to use the utf-8 character set. If you are submitting via HTTP and using a character set other than utf-8, you can specify this in the URL parameters using the &charset= parameter ... for Western Europe, this is usually &charset=iso-8859-1 If this does not work for sending the characters correctly, send a test messaging using the forms in the web interface. Those forms force the use of utf-8, so if they don't work properly, it suggests a different character set must be configured for the SMSC. (For SMPP SMSC connections, there are advanced settings available for specifying which character set the SMSC expects.) For received messages routing to a 2-way command, on the 2-way page, there is a configuration setting to specify which character set NowSMS should use (defaulting to utf-8). -- Des NowSMS Support | |||
