| SMS message must be submitted with Unicode |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I get this line in my smsdebug.log: "SMS message must be submitted with Unicode" The question is; How do i submit anything in unicode if i am POST'ing to nowsms from a .VBS file? | |||
| Bryce Norwood - NowSMS Support |
Is the message being displayed correctly on the receiving handset? Basically what this message means is that the message that was submitted contains extended characters, and in order to send that message via SMS, the gateway has to use Unicode encoding. Basically, there are 127 characters that are part of the standard GSM character set, and a few additional characters that are part of the extended GSM character set. If your message contains any characters outside of this set, then the gateway needs to submit the message in Unicode format. (The downside of this is that if a message uses only the standard GSM characters, the limit is 160 characters ... if a message includes any chararacters that can only be expressed in Unicode format, then the whole message must be submitted in Unicode format, and the limit is then 70 characters in a single SMS message.) The gateway expects messages to be POST'd (or HTTP GET URL) using the UTF-8 character set, which is an 8-bit representation of Unicode. If you are submitting using a different character set, then you need to include a parameter charset=xxxxxx in your URL request to specify the character set that you are using. Supported charset values include iso-8859-1, us-ascii, big5 (or big-5), gb2312 (or gbk or gb2312-80), shift-jis (or shift_jis), iso-8859-2, iso-8859-4, iso-8859-5, iso-8859-6, iso-8859-7, iso-8859-8, or iso-8859-9. -bn | |||
| Anonymous |
Thanx i see your point. If charset was not set i got some weird characters. I tried using the 8859-9 and it worked like a charm. | |||
