Hi Spamaden,
No, the problem does not appear when sending the messages, the problem appears 
when I receive the SMSs.
Cheers.

________________________________
> Date: Thu, 29 Mar 2012 
01:24:33 +0400 
> Subject: Re: UTF-16BE 
encoding problem 
> From: spameden@gmail.com 

> To: emmanuelchanson@gmail.com 
> CC: 
rob_gar_esp@hotmail.com&#59; users@kannel.org 
>  

> You need to use charset=utf8 & coding=2 for sending 
such messages. 
>  
> i.e.:  
> 
"http://localhost:90/kannel-sms?from=%2Bxxxxxx&to=xxxxxxx&msg=%04%1F%04%3E%04%3D%04O%04B%04%3D%04%3E%00+%042%04A%04Q%00.%044%040%00+%04A%04%3E%00+%04A%04B%04%3E%04%40%04%3E%04%3D%04K%00.%048%00+%04B%04%3E%00+%04%3D%045%00+%042%04A%045%043%044%040&originSMSC=mySMSC&charset=utf8&coding=2"
 
>  
> be aware that 1 message part will be maximum 
67 symbols in case you  
> want to use cyrillic or mixed up with 
cyrillic charsets. 
>  
> otherwise use coding=0, 
omitting charset. 
>  
>  
> 2012/3/29 
Emmanuel CHANSON  
> 
<emmanuelchanson@gmail.com<mailto:emmanuelchanson@gmail.com>>
 
>  
> Is there any option like mo-recode=true 
? 
>  
> Br 
>  
> 
Emmanuel 
> 
Http://miig.mediacom.nc<http://Http://miig.mediacom.nc> 

>  
> Le 29 mars 2012 07:57, "Rob GB"  

> 
<rob_gar_esp@hotmail.com<mailto:rob_gar_esp@hotmail.com>>
 a écrit : 
>  
>  
> Hi all, 

>  
> I'm using Kannel to send Cyrillic 
messages, I send SMSs with UTF-16BE  
> encoding and they work 
perfectly, however I have a serious problem with  
> incoming 
messages. I have this config: 
> group = 
sms-servicekeyword = defaultcatch-all =  
> 
truemax-messages=0get-url =  
> 
http://myhost:13180/kannellistener/kannel-sms?from=%p&to=%P&msg=%a&originSMSC=%i&charset=%C
 
> In access logs the URL looks like: 
> 
2012-03-28 19:05:07 SMS HTTP-request sender:+xxxxxxx 
request: 'OK' url:  
> 
'http://localhost:90/kannel-sms?from=%2Bxxxxxx&to=xxxxxxx&msg=%04%1F%04%3E%04%3D%04O%04B%04%3D%04%3E%00+%042%04A%04Q%00.%044%040%00+%04A%04%3E%00+%04A%04B%04%3E%04%40%04%3E%04%3D%04K%00.%048%00+%04B%04%3E%00+%04%3D%045%00+%042%04A%045%043%044%040&originSMSC=mySMSC&charset=UTF-16BE'
  
> reply: 200 '<< successful >>' 

> I use a Java webapp as the listening servlet, in logs the 
messages look  
> like this: 
> 
[http-13180-54] com.xxx..KannelIncomingSmsServlet.doGet - entry text 
=  
> ^D%^D>^DG^DC^@ 
^D?^D>^D7^D=^D0^D:^D>^D<^D8^DB^DA^D0^@
 ^DA^@ ^D<^DC^D6^@  
> 
^@5^@3^@ ^@5^@5^@ 
^D&#59;^D5^D B^@ ^D4^D&#59;^DO^@ 
^DA^@/^D> 
> I have tried a lot of Java 
methods to decode the message,  such as: 
> 
URLDecoder.decode(text, "UTF-16BE"))&#59; 
> 
new String(text.getBytes("UTF-16BE"), "UTF-16") 

> text = 
Charset.forName("UTF-16BE").decode(text).toString()&#59;
 
> and some more big methods that are not necessary to list, the 
point is  
> that the message never gets decoded. 
> 
I wonder if there's something in Kannel config I could do to fix this  

> problem. 
> Thanks in advanced. 
>  

>  
>  
>  
>  

>  
>  
>  
                   
                  

Reply via email to