Hi Jovan,

I think the problem is the sending via sqlbox.  If we do an http post to the Kannel server, it seems to work correctly, but not if we insert into the table via the web application. 

Also we get different results if the providers SMC accepts messages in ISO8859-1 or only 7 Bit GSM.  Most only accept 7-bit GSM, but neither case works perfectly with the special characters.

Right now, characters   €  and \ are giving us problems with the iso8859-1 connection and the normal 7 bit GSM connections are giving us problems with ñ Ñ, € and several other 'special' characters.


Jovan Kostovski wrote:
On Wed, Feb 24, 2010 at 9:06 AM, preeteesh kakkar
<preeteesh.kak...@gmail.com> wrote:
  
Nikos,

Yes correct but then would Jovan suggestion work for Greek, Chinese, Hindi &
lets say any other character set?
    

As Nikos pointed out, If you want to save on payload (number of
characters that you can send in one sms)
and use the same service to send in different character sets the
wisest solution would be to
set alt-dcs, coding, charset and every other relevant parameter on per
sms basis. Just specify these
parameters in the cgi-bin/sendsms url.

This means when you want to use Greek characters you'll use the
default GSM 7 alphabet (alt-dcs = 0
or alt-dcs = 1 depending on the default alphabet used by the SMSC),
for Chinese and Hindi use UTF-8
encoding (charset =utf-8 coding = 2).

BR, Jovan


  

Reply via email to