Hi, I tired to send the complete message to Kannel via HTTP request. Kannel split the message and sent to device. I experienced the same behaviour on the device. Second part of the messge is messed up (boxes).
Kannel log shows the following: [18:55:38] Latitude says: 2009-10-02 18:52:58 [29620] [3] INFO: sendsms sender:<test:Sync> (10.223.202.35) to:<491733114042> msg:<Jesús test msg Whatatimelycomment,Denly'sagaingotastartandsquanderedit.Morgan'sgotintoabitofaholeatoneend,anditwasDenly> 2009-10-02 18:52:58 [29620] [3] DEBUG: Stored UUID c94c60c7-a0a7-4c29-9347-ad75bd93166a 2009-10-02 18:52:58 [29620] [3] DEBUG: message length 238, sending 2 messages 2009-10-02 18:52:58 [29620] [0] DEBUG: Got ACK (0) of c94c60c7-a0a7-4c29-9347-ad75bd93166a 2009-10-02 18:52:58 [29620] [3] DEBUG: Status: 202 Answer: <Sent. Message splits: 2> 2009-10-02 18:52:58 [29620] [3] DEBUG: Delayed reply - wait for bearerbox I sent %C3%BA for "ú" and that is fine since log shows that character was understood by Kannel. Any clue? Thanks. On Tue, Sep 29, 2009 at 1:50 PM, Benaiad <bena...@gmail.com> wrote: > Dear Latitude, > > in my tests the character "ú" was encoded to "%3F" , but when I decode it > back I get "?" :( > and when I decode yours "%C3%BA" I get the correct character, ie "ú". > > Anyway, I think it's better if you leave the splitting of your long text > and udh stuff to be handled by kannel, so, just send the entire text in to > kannel cgi, and tell us your results. > > Benaiad > On Tue, Sep 29, 2009 at 12:01 PM, Benaiad <bena...@gmail.com> wrote: > >> Dear Latitude Test, >> >> When I URL encode your text I get a different thing from the one you are >> trying to send, and this is the resulting text: >> >> Jes%3Fs+test+msg+abcdefghijklmnopqrstuvwxyz+abcdefghijklmnopqrstuvwxyz+abcdefghijklmnopqrstuvwxyz >> >> Regards >> >> Benaiad >> >> >> >> On Mon, Sep 28, 2009 at 10:42 AM, Latitude Test <latitude.de@ >> googlemail.com> wrote: >> >>> Hi, >>> >>> I am having problems in sending Long SMS via Kannel with UTF-8 charsert >>> wuith special characters in the content. >>> >>> For example I am sending the following text: >>> >>> Jesús test msg abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz >>> abcdefghijklmnopqrstuvwxyz >>> >>> My application is sending the following GET requests to Kannel: >>> >>> GET /cgi-bin/sendsms?username= >>> test&password=test&to=491733114042&udh=%05%00%03%3F%02%01&text=Jes%C3%BAs+test+msg+abcdefghijklmnopqrstuvwxyz+abcdefghijklmnopqrstuv&from=Synchronica&coding=2&charset=utf-8 >>> GET >>> /cgi-bin/sendsms?username=test&password=test&to=491733114042&udh=%05%00%03%3F%02%02&text=wxyz+abcdefghijklmnopqrstuvwxyz&from=Synchronica&coding=2&charset=utf-8 >>> >>> Everything looks good at Kannel (SMPP account configured). The device >>> (Nokia N78) recognises the SMS as multipart and presents them as a single >>> SMS (good so far). >>> But the content is messend up. I see BOXES for the second part of >>> message. Sometimes I see @ sign everwhere. >>> >>> I noticed that the following character is causing the problem: ú >>> >>> But if I send the following text via Kannel, everthing is fine: >>> Jesús >>> >>> So it seems that ú character when sent with multipart sms (long sms) is >>> causing the problem. >>> >>> Please guide. >>> >>> Thanks. >>> >> >> >
