| Special Characters (@ etc) via 2 Way SMS (Att Des) |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 14, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Tim Williams New member Username: Timw Post Number: 6 Registered: 09-2010 |
Hi Des, Hoping you can help me here, our SMSC providers have now amended the SMSC so we have no issues with long messages or other character sets which is good, but we now face a problem where NowSMS removes any @ characters when the SMS is sent via 2 Way SMS, is there a way to encode/escape these so they are not removed? Regards Tim | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2690 Registered: 08-2008 |
Hi Tim, I'd suggest verifying that this problem is not unique to 2-way SMS. Try sending a message from the NowSMS web interface, and see if you encounter the same problem. The @ character causes issues for some providers because in the GSM character set, @ is encoded as a NULL character. Some SMSCs expect the iso-8859-1 character set to be used, and they convert before sending over the air. Chances are that they expect you to be using that character set, which can be configured under the "Advanced Settings" for the SMPP connection. (Or it's possible that their recent changes have caused confusing for the @ character because of its unique encoding issues.) The € symbol can be another headache. In raw GSM, it is sent as a two character sequence. Take a look at the GSM character set tables in this post: http://www.nowsms.com/long-sms-text-messages-and-the-160-character-limit ... and that should help give you an idea of other characters that you might need to test. -- Des NowSMS Support | |||
| Tim Williams New member Username: Timw Post Number: 7 Registered: 09-2010 |
Hi Des, Cheers for that! Changing the character set worked, the outbound SMSC is different from the Inbound one and it was only affecting SMS going to that particular outbound SMSC. Regards Tim | |||
